1 of 1 people found this helpful
Hi pcuellar, you have of course to disable the AD sync task because you preobably set credentials for deploying Mcafee Agent.
Be sure to disable any AD sync tasks under Menu->Automation->server tasks on the ePO 4.6 server
Thank you for your response. I'm wondering, might there be any way to make this work without turning off the AD sync in 4.6? I'd like for new builds to continue to get the agent and stay in communication with the current ePO. However, I would also like to have only a select group of "controlled" machines in the new ePO environment to make sure evyerhing works, so I rather keep AD sync on 5.1 off.
In other words, I'd like to transfer computers from ePO 4.6 to 5.1 while keeping AD Sync in 4.6 turned ON, and OFF in 5.1 during this initial transition. Is this an option?
The best way would be disabling the McAfee Agent deployment option under the AD sync settings so computers ould appear again under ePO 4.6 but won't get automatically McAfee Agent deployment.
Once this is modified you can set a new tag for the unmanaged computers (the ones that will be managed by ePO 5.1) and then set an autmated task that will deploy McAfee Agent every X hours to any non-managed computers except the ones that will have the prior define tag
I like that approach. Thank you for your input, Laszlo G!
@pcuellar did you register epo 4.6 and configure as agent handler on 5.1.1 or vice versa, in same situation migrating to 5.1.1 but getting error agent no communicating with epo server
I have tried to point the Agent Handler to the new ePO from the old one (Agent Handler modified with published DNS Name/IP Address on 4.6 to 5.1.1) but no joy..
It seems to have been working with side-by-side upgrade. One issue though, agent keep going back to old ePO 4.6 after some time, disabled all Task, AD Synch and also changed the Agent Handler to the New 5.1.1 as target FQDN in published DNS/IP name. Also some are coming up with Agent failed to communicate with epo server. The Registered Server could not connect to ePO4.6 (not really bother so much about that) failed during test connection. I used this KB as a guide KB82126..