*POP!* Somewhere a bubble just burst. Patch 3 is no longer available for download.
We have received reports and now confirmed an issue with the extension shipped with patch 3.
It fails to migrate policies when a task includes the "Cookie Scan" scan item, but that's not too bad - what's bad is when this fails all your VSE policies are lost.
Before total panic ensues, read some more...
This would affect you only if you have a scan task created or edited such that you are only scanning 1 or 2 items in your "What to scan" list, and one of those items is the Cookie Scan item. This is not a default configuration and I would have thought uncommon in the field, but some recent escalations suggest otherwise.
When the extension check-in process encounters that error, it then goes into roll-back mode - and alas, there is an issue there also such that roll-back fails. End result = no VSE policies.
Both these issues are being corrected in an updated extension. Patch 3 will be available again as soon as these has been corrected and the fixes verified.
If you have already added the Patch 3 extension and not experienced any failure, which will be most of you I suspect, you need not worry about a thing.
Still, when we post Patch 3 again with the updated extension, it would be in your best interest to add the updated extension too.
And, if you want Patch 3 in its current state because of a pressing need to install to Windows 8 or Server 2012, please contact McAfee Support. Once we qualify you won't be affected by this issue we will make the patch available to you.
I had just this AM checked the extensions that came with VSE patch 3 into my EPO not the patch itself yet, as my VSE
policies are still there looks like I had not been affected? Or this issue only happens on a client after you had deployed patch 3?
I was not aware the there is a migration performed if you check in new extension?
Would my reollback be just to remove the :
Message was edited by: magics on 11/01/13 10:22:18 CST
Message was edited by: magics on 11/01/13 10:22:50 CST
Message was edited by: magics on 11/01/13 10:24:44 CST
You were unaffected by the issue.
My recommendation - do nothing.
My other recommendation - wait for us to post an updated Patch 3 extension package, and check that in too.
This issue was resolved. Patch 3 is available again.
Note, all we had to fix was the extension (and policy migration tool); the actual patch that updated VSE binaries is unchanged.
The readme was updated just a tad also, so it reflected the right build/version number regarding the extension update.
hi wwarren this a last version? build 1128
Did you mean "latest" version? Yes. It is the latest version. If in doubt, you can check the download site for what is the latest.