Hi Alphoneix... have you reed this?
Seems that is not supported the upgrade from 5.0 to 5.1
There is a my post about this just a little bit down
I just went to read it....
Somewhere frightening !
A so new version, and already so many issues ???
So what, upgrade from 5.0 to 5.1 is NOT supported ???
Where have you seen that information ? If it's really the case, well, this is simply unacceptable from McAfee...
"There is a my post about this just a little bit down"
Can you precise ? I don't understand what you mean.
Here my post...take a look in to https://community.mcafee.com/message/309822#309822
I understood it from this... seems that for now there isn't a workaround. Hope it's a mistake. look the "bold"
Issue: For ePO 5.1.0, the Upgrade Compatibility Utility supports upgrade from 4.5.7, 4.6.4, 4.6.6, and 4.6.7. However, you cannot use the utility to migrate an ePO 5.0 server.
- The Installation Guide incorrectly states that the Upgrade Compatibility Utility can be used to migrate a 4.5, 4.6, or a 5.0 server to 5.1.
- If you run the utility on a not-supported for upgrade version of ePO, the error message does not list the correct versions supported for upgrade by the utility.
I think you've perhaps misunderstood the use of UCU ?
UCU is only here in order to migrate from ePO 4.x to 5.x... It's there to verify the packages/extensions you have installed in 4.x are compatible with 5.x.
(I had the case for an extension of SiteAdvisor which needed to be upgraded before migrating to 5.0 - otherwise, the extension would have been disabled).
So, of course, UCU isn't useful to migrate from 5.0 to 5.0.1 or to 5.1 !
That doesn't mean upgrade from 5.0 to 5.1 is impossible.
And this morning, when I launched the setup, it indeed stated "upgrading" because it detected my previous 5.0.1.
So well, I'm still with my problem...
I'll perhaps try again tomorrow, after having rebooted the server with the 8.3 setting changed...
I fond this post as I'm currently in the same situation.
Alain, the discussion ends here so I'm hoping the registry change did solve the problem, please post back.