I am at work so I will be quick, I was wondering whether ePO's Server Task's / Run Now tasks are subject to a time limit.
Currently I am trying to deploy rouge agents to all Windows 7 machines across our network and I am not having them all finalise the way I wished. My log is:
|6/19/13 2:07:46 PM||Started: Deploy McAfee Agent to systems task|
|6/19/13 2:07:46 PM||Deploying agents to 190 system(s)|
|6/19/13 2:14:00 PM||Completed: 52|
|6/19/13 2:14:00 PM||Failed: 1|
|6/19/13 2:14:00 PM||Expired: 137|
|6/19/13 2:14:00 PM||Completed: Deploy McAfee Agent to systems task (Completed: 52,Failed: 1,Expired: 137)|
As you can see, most are not completing. I was wondering if these 'Expired' machines are not completing because of a time limit on the task or if it points to any other specific issue.
Could anybody help with this?
Are you using the UI to initiate the client task, or the web API? Sounds like just the UI. In that case I would make two comments:
1) it's almost always preferable to assign the task, and let it complete after the next time the agent dials in. For run now to be successful, the agents have to be online, have wakeup enabled in policy, and reachable from the server. It's great for troubleshooting but the traditional client task assignment is best for deployments, generally.
2) if you are using the 'run now' in the UI, there is a second tab on the bottom labeled 'Options' that contains several fields you may want to modify, including # of attempts to contact the agent, a retry interval, and an expiration timer. You might play with upping the number of attempts, choosing 'all agent handlers' (if you have more than one), and bumping up the retry interval.
Thank you for your reply, I've just arrived at work now so I'll check all listed posibilities again and try to RDP to a machine with the UI, currently I am mobile a lot so the website has been my only access to controling anything.
I thought it might have been better to get to a UI machine but due to time limits, being mobile, ect, I thought it best to ask here in case it was a known (in the KB) issue.
Neither of those solutions helped, have tried to wake them up one by one and then test them just to see if we can get a result but no, nothing. I'm sure some of these must be machines not in use, about 1160 of them, at the time of the deployments but I was wondering if there could be other issues effecting the expired machines that I wouldn't know of yet.