Yes. The extensions and policy gets upgraded.
The only option would be to bring up a test ePO and manage the new SVA with this ePO and test it.
Hmm that's a worrying limitation - more other McAfee products allow upgraded extensions to manage older versions.
In larger environments, it isn't conceivable to upgrade the extension and all your SVAs in a single change window.
Does this same limitation apply when moving from 3.5 to 3.6?
Here the extension can be on 3.5 and SVA on 3.6 and vice-versa. This is till the upgrade is carried out. What i am trying to say here is the mixed combination works fine.
But make sure to be on the same version always.
FYI, wanted to add some knowledge here for others. I'm upgrading to MOVE 3.6.1 from 3.0 and have found a couple of things I wanted to share with others considering the upgrade.
1) the MOVE 3.0 SVA's will still detect threats and report into ePO, even after installing the 3.6 extension. After installing the 3.6 extension, I dropped an eicar test file on a VM on a host with a 3.0 SVA on it and the file was immediately cleaned and reported to ePO.
2) I had to power off my SVA's as part of the deployment process. otherwise they were showing up in ePO, checking in, waking up, pinging, etc, but wouldn't scan files. once I powered them off (not reboot, but power off) vShield ran a reconfigure VM task. then I powered them on and they started scanning fine.
Upgrade from 3.0 to 3.6.1 is not supported.
Supported upgrades to v3.6.1 are from 3.5 and 3.6.
Cool story. The problem with your comment about it not being supported is that I called in to tech business support TWICE and nobody had any issue with me going from 3.0 to 3.6.1. One guy even did some testing in his lab environment to help answer some questions I had about 3.0 to 3.6.1. So if it's not supported you might 1) tell your support teams it's not supported and 2) update your documentation to say so because that is not mentioned anywhere. which is par for the course for McAfee documentation honestly. I do see the notes that say "upgrade from 3.5 to 3.6.1", but there's nothing about previous versions not being supported to upgrade from. nor is there a recommended upgrade path listed for anything previous to 3.5.
Did you refer the product guide for MOVE Agentless v3.6.1 page number 65 ?