Like a lot of people right now I'm busy migrating from MOVE MP 3.6.1 to MOVE MP 4.5. (and then later 4.6)
All is going well with only one real issue - the need to update the default SVM Manager OVF with the hotfix to plug the TLS 1.2 requirements.
Deploying the full 188.8.131.52 OVF is no problem
Using a client task to apply the hotfix to bring up to 184.108.40.2067 gives unpredictable results. Post running the client task I get the following behaviours:
1. the client task remains 'In Progress' and never ends . I end up rebootting the ePO after a while to clear the server log
2. the MOVE version reported in the ePO always updates to .257
3. some SVM Managers prompt for a reboot, after which all is well with them and they direct client requests to SVMs
4. some SVM Managers do not appear to actually apply the hotfix (no prompt to reboot and manual reboot doesn't fix). These appliances unsurprisingly do not direct clients to SVMs as the SVMs are at .268
Regarding point 4 I'm totally tearing my hair out right now. Point 1 is also irritating but not critical.
Has anyone seen similar behaviour or am I doing something wrong? I can't see any other information on this from googling.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.