9 Replies Latest reply on Mar 10, 2016 5:42 AM by exbrit

    Need to avoid hotfixes and reboots. Can we go from Agent 4.8.0.1938 & VSE 8.8i Patch 6 (1445), then upgrade to Agent 5.0.2.188, install VSE 8.8i Patch 7 and then finally upgrade to Agent 5.0.2.333?

    twenden

      In our environment, we have thousands of systems running with Agent 4.8.0.1938 and VSE 8.8.0.1445 (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 4.8.0.1938 to Agent 5.0.2.188, 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 5.0.2.132 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 5.0.2.333 or 5.0.2.188 works with DE 7.13 yet.

       

      This is a painful process for all of us and hard to follow.