Adding PCs to AD Groups
James Daisy
I am in the process from converting to PDQDeploy/Inventory from System Center. I have 3 daily schedules setup to run on each of my applications.
1. Deploy to PCs in an AD Group - stop deploying once succeeded
2. Deploy to PCs that need the software -
3. Deploy to PCs that need the newer version installed -
My issue is that I want to populate the software AD group with the PCs but since the software is already installed on the PCs I don't want the daily schedule to re-install the software.
0
Comments
Do you have 3 different schedules to install the same applications, or are these 3 different applications?
I have 3 different schedules to install each application. The first looks at an AD group and if a new PC is there, install it. The second deploys to a filter collection in Inventory, if the version installed has a lower version that what is currently installed it installs. The third checks the AD group to see if the PC is a member, if it is and the software is not installed, install it. I'm basically trying to mimic the functionality of System Center without all of the issue that come with it.
We have several internally developed applications with several versions that run through DEV UAT and Prod.
I would recommend building 1 collection that checks all 3 conditions.
This will populate a collection with computers that are members of the AD group "Application X" that either have an old version of "Application X" or do not have "Application X" installed.
Colby has the right solution to this problem. A Collection containing all three criteria would target all of your clients, and make reporting a lot cleaner, that is if you are using the reports for anything meaningful.
I hope to be able to try this today, but it looks like it is exactly what I am looking for. Thank you