Something I ran into today and thought I'd share.
I created a package, inside said package is our basic deployment for all our workstations (IE Chrome, Firefox, VLC, etc...). A few days ago I started working on a deployment package for our developer systems (Stuff like JDK8, JDK11, etc to custom directories) and put it in the same folder as the existing package. I renamed the existing one to match up "Windows 10 - Baseline" and "Windows 10 - Developer Baseline". Simple stuff really.
So here's where the problem started. We got a new laptop for a user yesterday and my desktop guy kept trying to deploy the baseline package and it would just sit at "Waiting for agent". Restarted the guest, PDQ several times, made sure it could connect, reinstalled the agent, everything I could think of. I then deployed another package manually for "testing" purposes and it worked. So then I thought, what was changed... simply renaming "Baseline Deployment" package to "Windows 10 - Baseline" couldn't have been the issue could it?
So I took a screenshot of all my 14 nested packages and deleted it. Recreated the package with the same name "Windows 10 - Baseline" and added all the nested packages and then hit deploy to find... it worked.
Figured I'd bring this up for anyone coming up with this similar issue.
- PDQ Deploy: 220.127.116.11
- PDQ Inventory: 18.104.22.168
Please sign in to leave a comment.