We've created a Server Task to deploy the McAfee agent in a certain set of machines obtained via syncing with an Active Directory.
This task gets stuck because some of the workstations do not exist but are still present in the AD (and in the System Tree), and this makes it impossible for the task to run in the workstations that actually need the Agent.
We have found a timeout parameter in the Task configuration, but it looks like it does not work or that it completely ignores it, since it still gets stuck.
Why could this be happening?
Thank you.
Hi SiacloudNetsec,
Thanks for writing in!
Basically are you trying to deploy McAfee agent to client machines?
Could you confirm the LDAP sync is enabled?
What ePO version you are using? We should not attempt to run server task for machines which is not available. It will go in 'Infinite loop' and will never complete.
Those tasks can be killed if you restart ePO services.
The timeout is per system, meaning, it will try each system that time period. I would set the retry limit to one instead of continuous. See if that helps any.
That is one problem with AD sync, if active directory is not maintained. One thing that can be done is when a system no longer exists, either clean it out from active directory, or move them into a decommissioned folder or something similar and exclude that folder from the AD sync point.
Was my reply helpful?
If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: