This content has been marked as final. Show 5 replies
If your ePO directory is organised by branch location you could run the task for one branch at a time. Or push out the agent and VSE updates manually using SMS, Altiris or whatever you're using.
Or am I missing some essential point of your question?
I'm in the middle of just such upgrades right now, with the exception of moving from ePO 3.6.1 to 4.5. I would not try to update all 3 at the same time; divide them into 3 distinct projects. I'm doing the 8.7 upgrade first, which I will follow with the Agent, then finally the ePO server.
Our ePO directory is set up by office departments so I can push the upgrades to just one department at a time, reducing the effect that such traffic would have on our network performance. This also allows me to send out upgrades to lower priority departments as a final means of testing. Once I'm assured that the package is going out and installing normally, then I can schedule the updates to departments when they are least busy (for instance, at night for the departments that are not open 24/7).
thanks for the reply!
i'm going to upgrade one step at the time.
starting with VSE first, let it run for a week, and then the rest.
Will see what happens, in worst case scenario i have to start over.
I'm investigating the current situation, and make a plan, how to ....
i'll keep my fingers crossed.
Thanks so far.
I'd do the upgrade in a different order.
MA 4.0P3 first (don't forget to check the agent extension into ePO extensions as well)
Make sure engine 5400 is checked into ePO and deploying.
Then 8.7i with Patch 2.
Only then upgrade / sidegrade / downgrade to ePO 4.5.
Personally, I'd hold back from 4.5 until after ePO 4.5 Patch 1 is relesed.