(Waiting for Agent)

Follow

Stephen Eller

• May 06, 2018 19:45

After installing Inventory 16.1.0.0 about 1/3 of the computers I put the agent on are reporting '(Waiting for Agent)' in the Scan Status field. They seem to be stuck in that state. If I go to the target Agent page, it says the Status is 'unavailable', but I know the machine is on and connected to the LAN. I've tried rebooting the target computer, restarting Inventory, uninstalling the agent and reinstalling it. How do I troubleshoot this?

0

• Official comment

  

  Colby Bouma

  • September 23, 2019 17:01

  We are announcing the End of Life (EOL) of the optional PDQ Agent beta from our existing products. See this blog post for more information https://www.pdq.com/blog/pdq-agent-status-update/

  Comment actions Permalink
• 

  Steven Powell

  • May 07, 2018 13:38

  I'm seeing this on a few laptops. They are showing as online but scan status is (waiting on agent) and i cant get it to scan manually. If i re-install the agent everything goes back to normal, both laptops are Windows 10 1709

  Cheers

  0

  Comment actions Permalink
• 

  Chris James

  • May 07, 2018 18:56

  Hey guys, looks like you're running into a bug and we'd like it if you would submit a ticket to support@pdq.com and we'll take a look at it and handle the issues you're seeing there.

  Thanks!

  0

  Comment actions Permalink
• 

  Joe Slitzker

  • May 08, 2018 14:01

  Just chiming in to add that I'm seeing this as well. I also have several hundred that go pending in scanning status for hours waiting on agent. I either have to abort the scan, or reinstall the agent to get it to clear and successfully scan.

  0

  Comment actions Permalink
• 

  Stephen Eller

  • May 08, 2018 15:30

  Going to the Agent page, then Reinstall Agent in the upper right, does seem to resolve the issue. I see this more as a work-around than a fix. I believe the PDQ guys are looking into a proper solution.

  0

  Comment actions Permalink
• 

  Stephen Eller

  • May 17, 2018 18:16

  Based on the release notes, it looks like 16.2.0.0 might address this issue.

  0

  Comment actions Permalink
• 

  Francisco Rojas

  • May 18, 2018 15:05

  I have the same issue with 16.2.0.0, whe i uninstall the Agent all work fine again

  0

  Comment actions Permalink
• 

  Craig Whetton

  • June 07, 2018 08:54

  Same issue in version 16.3.0.0. This is quite the annoyance.

  0

  Comment actions Permalink
• 

  Bijoykrishna Das

  • June 13, 2018 10:42

  I am facing same issue after reinstallation of Agent also, Raised the Ticket

  0

  Comment actions Permalink
• 

  Patrick Pierce

  • June 13, 2018 16:28

  Contact support to get a fix from the customer build after 16.3.0.0.

  0

  Comment actions Permalink
• 

  Jason Burds

  • July 12, 2018 20:57

  Same issue in 16.4.

  I have hundreds of computers waiting for agent.

  Reinstalling agent seems to have fixed it.

  0

  Comment actions Permalink
• 

  Christopher Gordon

  • July 19, 2018 14:39

  Same issue as well. I have to uninstall the agent then re-install before it will work, then begins again the next day. Issue began after updating to 16.4.

  0

  Comment actions Permalink
• 

  Dusan Mrozek

  • June 11, 2019 09:05

  Same issue in version 17.1, agent reinstall does not help. Is there any solution or workaround?

  0

  Comment actions Permalink
• 

  Matt Ayres

  • June 14, 2019 12:10

  Same issue.. 17.1 reinstalling the agent doesnt work... all devices are stuck on (waiting for agent) ......help?

  0

  Comment actions Permalink
• 

  Colby Bouma

  • June 17, 2019 14:16

  @Dusan_Mrozek @liltbrockie

  The Agent has been moved back to beta. I recommend uninstalling it if it is causing problems (Computer --> Uninstall Agent). We are working on bugs like this, but it's going to take a while. If you really need the Agent and wish to attempt to troubleshoot it, please contact support@pdq.com.

  0

  Comment actions Permalink

Please sign in to leave a comment.