This content has been marked as final. Show 6 replies
If I were you I would create a deploy task for CMA 3.6 but not for 3.5.5 because it's only officially supported for NT servers on virtual machines.
Use the reporting function to generate the Agent Version report.
Add the updated Agent to ePo Repository.
Configure the depoloyment task to upgrade the agents.
Ensure the deployment task is enabled on your sites in the ePO Directory.
Thank you Jim...
Is there a difference between CMA 3.5.5 and ePO Agent 3.5.5 ?
Not in an enviroment that's centrally managed via ePO or Pretection Pilot - it is possible to implement the CMA on standalone systems as well - although I've always had a problem with it being referred to as the CMA in such cases ;)
Hello again !
Is there any risk of making a server rebooting when deploying the new ePO agent by a deployement task ?
I'm concerned about the network traffic.
I actually have 3 repositories with 1000 servers in each. Should I consider making a plan to progressively deploy on my 3000 servers ? any advices on that concern ?
Hi everybody !
I'm back on my ePO console v3.6.1 Patch 4.
I have 2 simple questions :
-How do determine precisely on how many servers are my ePO agent installed ? Can I have a plain text list of these servers ?
-And how do I initiate a report including the version number of the ePO agents deployed on these servers ?
I'm sorry to be boring about this migration but I'm still not 100% sure my agents are OK for migration to version 4.