First a little background info: We use PDQ Deploy/Inventory for two main reasons. The first is to keep every package in our network up to date (obviously), but the second one is for the deployment of software after imaging a fresh Windows install on our clients.
For example, a new laptop comes in, we deploy a default Windows image on it and join the domain. After the sync/scan it becomes visible in a set of collections which are linked to different schedules. So there's a collection/schedule for Adobe Reader, Java, 7Zip, and so on.
This works flawless when it comes to a new client. Or rather, for clients that have a unique hostname that never has never been a deployment target for one of the schedules. Why? Because I use the schedule option: Stop deploying to computers once they succeed
Now, I can decide not to use this setting, but that poses another problem. The schedules run every 30 minutes, so if I deploy, for example, Java on a client, PDQ Inventory will not have a chance to scan the PC again, so it remains in the collection. So after 30 minutes, the schedule kicks off again and starts the deployment over. And over.
What can I do to overcome this problem? Yes, I can change both the scan and deployment schedules to once an hour, but that means I might have to wait for over 2 hours before a deployment is finished. Not to mention the performance problems associated with a high interval application scan.
Would love some insight from you guys!
Please sign in to leave a comment.