In our environment, we have thousands of systems running with Agent 22.214.171.1248 and VSE 126.96.36.1995 (Patch 6). Looking at SB10151, it seems to say that you need to install hot fix 1087536 to VSE 8.8i before upgrading to VSE 8.8 Patch 7 when you are using MA 4.8x. I noticed that these hot fixes prompt the user to reboot which we are trying to avoid.
In my testing, I have noticed that I can upgrade the Agent 188.8.131.528 to Agent 184.108.40.206, without having to install hotfix 1087536, and then deploy VSE 8.8i Patch 7. This works without any users needing to reboot. Does anyone know if this is OK to do or do you have to follow the many scenarios listed in SB10151?
This whole thing is a mess at trying to follow. Another issue we have is with Agent 220.127.116.11 as it does not work with Drive Encryption 7.1.3. It has an issue with DE policies not being applied. Tech Support told us to wait until Agent 5.0.3. Not too sure when that comes out. Not too sure if Agent 18.104.22.1683 or 22.214.171.124 works with DE 7.13 yet.
This is a painful process for all of us and hard to follow.
Solved! Go to Solution.
Yes, that sequence is fine.
Moved provisionally to VSE for faster support.
> Can we go from VSE Patch 6 (126.96.36.1995) with Agent 188.8.131.528 to Agent 184.108.40.206 then Patch 7 and then Agent 220.127.116.113
No, you cannot.
"Agent 18.104.22.168" is where you went wrong.
The documentation associated with Patch 7 and MA 22.214.171.1243 should confirm it for you.
It works on my test system to go from agent 126.96.36.1998 to agent 188.8.131.52, then Patch 7 and finally Agent 184.108.40.2063. Are you telling me that this shouldn't work as it does install in that order.
Don't like hot fixes due to the need for reboots as it relies on the user to say yes/no. It is also not easy to see from the ePO side which system installed the hot fixes. We are in a non active directory environment and can't easily fix systems if they break due to this mess.
> Are you telling me that this shouldn't work...
When you installed MA 5.0.2, you fall into the VSE 8.8 P7 install requirement category that says "If you have MA 5.x you must have either MA 220.127.116.11 or MA 18.104.22.1683 installed".
This is in the P7 release notes.
I would be questioning the validity of the VSE 8.8 P7 installation. How did you perform the install?
The patch should have blocked itself from installing after detecting the installed MA version was not an acceptable one.
Sorry, I made a mistake in the subject line which I can't seem to edit. We went from Agent 22.214.171.1248 & VSE 8.8i Patch 6 (1445), then upgraded to Agent 126.96.36.199, installed VSE 8.8i Patch 7 and then finally upgraded to Agent 188.8.131.523.
This is the scenario that worked for us without any reboots as we didn't have to install any hot fixes. Does this sound like a valid install sequence.
Yes, that sequence is fine.
I edited the header for you, is it OK now?
Thanks for editing the title. It looks good.
You're welcome, hopefully someone will find the info useful.