Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Slight Issues with Deploy - Feedback

Issues:

1. Trying to get my external users to get deployed software. My users are all over the place and usually have a different IP than they did hours ago. When I deploy software and add them, if they aren't online at the time I add them then Deploy will never find them again. I think the agent needs to call home with it's new address etc.

2. So when I deploy an update to 550 users, some fail, some retry and succeed, etc. After a week if I go back I can't find a reasonable way to get a list of all the ones that still haven't succeeded. I instead have to created a dynamic list in Inventory to check for who doesn't have that version. It would be nice to check within that deployment a total of who's done.

3. Rather than retry every 1 hour or whatever you set it would be nice from the agent on client's machine when online to call home and the server says, "oh, here's deployments you need" and pushes them to the machine.

4. Allow custom packages.

5. Network profiles for agents. Basically I set on the server that sync's to all agents with an address to get to the server for calling home. 1 profile like if local subnet is 10.0.0.0/8 server to call home will be 10.0.0.3, if not that subnet then company.com:5678.

This application has a lot of potentials but lacks some important features that a business would need to get deployments working. It works great for machines that don't leave the LAN. Keep up the good work and let me know if any these things can be done already as I can't find a solution at this time. Right now we use Kaspersky to push this stuff out but are looking for an alternative solution.

Thanks, shawn

0

Comments

3 comments
Date Votes
  • Official comment

    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/

    1. If the Agent is External its IP address shouldn't matter. Which version of Inventory and Deploy are you on? I know there have been a TON of Agent improvements in the Customer Builds.
    2. Inventory collections are what I would personally recommend for this. However, if you use a schedule and look at the Target History you might be able to get close to what you're looking for.
    3. There is an existing internal feature request for this. I have no ETA on when or if it may be implemented.
    4. We are working on this. I have no ETA on when it will be implemented.
    5. If the Agent is unable to contact your Server it will already go External and bounce through our servers at agentapi.pdq.com. I don't recommend exposing your Server to the internet.
    0
    1. Currently using 16.5.0.76 Enterprise Mode for Inventory and 17.1.0.0 Enterprise Mode for Deploy.

    5 . That's good then.

    Thanks for the reply.

    0