Answer
Why won't my agent commands run?
I have a PC that I set the polling interval for 15 minutes. It updates the Last Seen every 15 minutes. I then issue an agent command (Scan). The command sits in the Recent & Outstanding Commands window with a status of "Not yet received". No matter the polling interval OR if I go to the PC and right-click the webroot icon and select "Refresh configuration". The agent command never gets run. Tech Support has not been able to help me with this. Any ideas from the community?
Best answer by nic
He suggested trying an uninstall and reinstall on one of the affected machines to see if that gets them responding again.
+56The only trick I've heard of is to push a scan command right after the agent command. Have you tried that one yet? Unfortunately this feature was mostly design as a tool for our support folks to run test scrips, and isn't really ready for prime time as a fully feature remote execution tool.
Hi Nic,
Please elaborate on what you mean when you say "push a scan command after the agent command". What/where is "push"?
Thanks,
Milt
Please elaborate on what you mean when you say "push a scan command after the agent command". What/where is "push"?
Thanks,
Milt
+56Sorry, I meant just issue a scan command from the console - that should be under the agent commands section.
+56Oh sorry, I misread your original post. I thought you were trying to run an exe via an agent command, rather than just a basic scan.
What did support say? Do you have a ticket number I can look up? I can pester the folks in support if the ticket isn't getting a good resolution.
What did support say? Do you have a ticket number I can look up? I can pester the folks in support if the ticket isn't getting a good resolution.
+56Ok I see that the first ticket is waiting on logs, and the second one the logs uploaded and the agent didn't find anything amiss and was wanting to know if the commands were still stuck in the queue?
+56Ok I'll ping the agent on the case and let him know.
+56He suggested trying an uninstall and reinstall on one of the affected machines to see if that gets them responding again.
+56Glad that did the trick!
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.