We would like to use PDQ Deploy to schedule a shutdown of computers based on their name and if they are not a member of a particular security group.
In PDQ Inventory I have created a dynamic collection under the (automatically created) Workstations collection called CityName - Desktops. The rule it uses is Computer - Starts With - CityName. This works and lists 97 machines.
I then have a child dynamic collection under this that drills down from the parent. Which says Not All - Member of AD Group Name - Equals - SecurityGroupNameHere. This lists 91 computers. So far this is what we are expecting to happen.
In PDQ Deploy I have created a package that runs the cmd shutdown.exe -s -t 0 -f. This is to shutdown a computer immediately and forcibly. If I test deploy this to individual PCs it works as expected. Again, so far so good.
Next I have created a schedule in PDQ Deploy called CityName - Shutdown PCs - Shutdown. This has been scheduled for weekdays at 20:00. For the targets I chose the option to link it to a PDQ Inventory collection.
Last night the schedule ran for the first time. I checked after 20:00 and the majority of PCs were still online that are in the linked to dynamic collection.
Because of this I then checked the deployment history and the targets are listed as 5. 3 of them succeeded, and 2 failed. The 2 failures were expected as I have a setting in the package for a ping test first, i.e. if the target is offline don't bother sending the shutdown command. This is where I don't understand what is happening, if we have a schedule in PDQ Deploy linked to a dynamic collection in PDQ Inventory that shows 91 members, then why did the scheduled deployment only attempt to deploy to 5? What about the other 86?
Please sign in to leave a comment.