Hi netik, if configured AD sync will also deploy McAfee Agent to new computers that didn't already exist under the system tree.
i.e. if you launch an AD sync task and you already have unmanaged computers under your system tree, McAfee Agent won't be deployed to them as they are not new computers.
Hi Laszlo G,
Thanks. Exactly, but somehow it doesn't not work for me.
Like I said, I configured the synchronization so that it pushes the agent to new clients.
Then I deleted all the clients in my system tree and started the synchronization. ePO adds them to the systemtree, I am able to ping them, but it doesn't deploy the agent. In the servertask protocol, I see that it successfully finished the job:
Started: Synchronizing all groups
Synchronizing 1 synchronized groups
Succeeded synchronizing Test with Active Directory synchronization point [DC=epo, DC=test, DC=com]
Completed: Synchronizing all groups (Synchronized all groups)
There are no subtasks and nothing about pushing agents.
Did you have any luck with this?
I'm in the same boat, strange this is it has automatically deployed the agent with the ad sync fine for the last 4 years, but after installing latest epo it doesn't seem to work anymore, the deployment task never runs after picking up a new client. I found the same happened with automated tasks, but could fix them by removing and adding in again.
Am considering getting rid of epo and starting a fresh.
This was an issue introduced in ePO 4.6.4 which is resolved in ePO 4.6.5. From the ePO 4.6.5 release notes:
Issue: When running an Active Directory Synchronization task with the option to deploy the McAfee Agent afterward, the agent isn't deployed, even when clients that should receive the agent are identified. (Reference: 813974)
Resolution: The McAfee Agent is deployed to unmanaged clients when the task is run.
EPO 4.6.5 should be released very soon most likely this week. You can view the entire set of ePO 4.6.5 release notes via the attachment at the bottom of KB76688 here: