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.

Deployment Issue

Brad McClave

February 26, 2019 13:24

I have a package setup for deploying software to new workstations. It is a collection of other install packages. In this package, I have it targeted at computers that were added to PDQ Inventory during the last day. In the conditions of the package, it applies to only Windows desktop OS versions (10,8,7) and excludes all versions of Windows server. Despite these settings, I see this package trying to deploy to two new Windows 2016 servers (fortunately, they were unsuccessful as the servers are currently turned off). Why is that package trying to deploy to machines that are explicitly excluded from this package?

Comments

2 comments

Brad McClave
February 26, 2019 14:47

Well apparently this is a non-issue. Once the machine is turned on and the deployment was attempted, it was not run due to OS condition. I guess PDQ Deploy has to talk to the machine first and not rely on what PDQ Inventory is reporting.

0
Ryan Joachim
March 08, 2019 01:38

It sounds like Inventory hadn't actually updated the information on that server, so it hadn't moved it to (or out of) your collection. Since it existed in your collection, the default behavior is to connect first -> verify requirements.

0