PDQ Agent (Beta) – Parent/Teacher Conference

UPDATE 9/23/19:

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/

PDQ Agent Beta

We just returned from a Parent / Teacher conference where we discussed the progress of our child, PDQ Agent.

We were, admittedly, a little sad to hear his teacher say “He is not like the other children”. We understand his attendance record is sub-par. We understand that he is often a distraction to the other kids in the class and that he has a tendency to fart during story time. For these (and other) reasons we, his parents, have decided that he needs to be held back a grade.

Yep, he’s going to have to retake 1st grade (Grade One to our Canadian friends). Sure, he will get poked fun at by the older kids that move on to 2nd grade and, perhaps, looked at oddly by the younger kids who will wonder why he is now in their grade but, as his parents, we are doing what we think is best for the little guy in the long run.

What does this mean? Quite simply we are at a point where we think it best to reclassify our young little agent as “still in beta”.

In all seriousness, we had anticipated that the agent would be popular but the adoption rate was higher than we anticipated as was the subsequent stress that was placed on our infrastructure. This new stress caused PDQ Inventory and PDQ Deploy to operate below our standards.

PDQ Agent – Beta

So, while we vigorously examine our options we are going to put the PDQ Agent back into beta status. You will still be able to use the agent but we only recommend using it for testing purposes (as with any beta). There will almost certainly be some big improvements to not only our agent but the underlying architecture.

This does not mean that PDQ Deploy and PDQ Inventory are in beta JUST the agent.

To help him get back on track we are limiting him to three hours of Xbox per week and his TV time will only include reruns of Benny Hill. Oh, and he has to clean Colby’s keyboards. All of them.

If you see him on the playground please be aware that he is embarrassed about being held back but go ahead and poke a little fun. It’s good for his character.

Start a trial of PDQ Inventory

16 responses

  • Hahaha….that was funny.

    Haven’t used the PDQ Agent, heck still trying to catch up with other goodies in Deploy and Inventory.

    • If you’re not using the agent, there won’t be any impact on your network. If you are using the agent, you’ll want to evaluate the impact the agent may have on your network. A good practice is to use the agent only on machines that leave your network for an extended period of time, such as laptops, that may be connecting through external networks. Most machines inside your network do not need to have the agent installed and can use the heartbeat trigger to accomplish a similar function.

  • Please add an “alternate” external location to pull custom packages from. An FTP server or Web folder would be perfectly fine for us as we just want to push custom packages to our field personnel.

    This would be a great option in general so there is a redundant location to pull files from in the main PDQ Deploy program

    Kids these days!

  • I’d just like to note that the agent is the biggest reason I subscribed in the first place. I hope you guys will give the agent development a high priority on your list of things to do. Having a working agent, and especially one that would allow custom packages and/or custom scripting would let you guys be a major player in the RMM market.

  • I have to agree, I’m using the Agent on a ton of remote machines because it’s my only visibility to them. This is an important part of what we’re doing now from an inventory standpoint. What are we supposed to do now that we started using it? Doesn’t seem like there’s any recourse in place.

  • Chris, we certainly can understand where you’re coming from. It seems we tried to run before we could walk. As we looked at the performance of the Agent, we could see that it was not performing up to the standards that we and our customers have come to expect. As we continue to work on the performance issues, we recommend limited use of the Agent while it is in Beta.

  • The description is cute and funny, but I am wondering if there are maybe some more technical details that can be put forth?

    It sounds like you are saying that PDQ servers are being overwhelmed by updates from the installed agents which is then causing long delays to the agent status messages.

    I currently have the agent deployed to 55 laptops in our organization. I started with testing and was in that phase for quite a while, while I learned how it worked. I finally pulled the trigger, despite it’s beta status, because it appeared to be doing its job well…. until recently.

    It seems like the “waiting for agent” problems are something new that had never come up in testing nor in the early days of full deployment.

    Is there anything we can do, short of uninstalling the agent, to work around this issue?

  • Sorry about the sparse information. We’re still trying to figure out how to proceed with the Agent. Once we figure that out we’ll have more information for you.

  • Hey PDQ team,

    Are there any updates on this situation you can share with us? I love what you are doing over there, but we did select this product based on the availability of the agent to manage our more remote users. At present I am unable to reliably deploy applications to them at this time with PDQ, greatly depreciating the value of this to us.


  • We are continuing to evaluate the Agent performance issues and are working to stabalize the Agent. We plan to keep the Agent in beta while we work on these issues. We apologize for the delay and hope to have additional information soon.

  • I’m confused why this seems to be such a complex feature to grasp. Computer deployement agents have been around for at least a decade if not more.

  • The agent would be a game changer for us. Off network machines are a pain at the moment. Another problem I haven’t seen mentioned is the agent not switching to Internal once the computer is back on the network. I hope this issue can be fixed soon.

    Is there an update page we can visit to see current news on getting the agent to the 2nd grade and beyond?

  • Any update on the Agent????

    I do hope that you guys are able to get the production version of the agent up and running. Not being able to deploy custom packages and batch files to off network machines it whats keeping our company from using your product….and we like your product 🙁

  • I purchased PDQ because of the agent for remote PCs/laptops that are off my network. I have approx. 500 PCs/laptops that are running the agent and right now are saying “Computer Name Could not be Found” on all remote PCs and laptops.

    The Teacher Conference write up was cute, but right now I don’t need cute. Right now I need it to work. How long before the agent is working again? I am dead in the water on all my remote PCs/laptops without the agent.

Your email address will not be published.

Your Name

This site uses Akismet to reduce spam. Learn how your comment data is processed.