1. PDQ Deploy & Inventory Help Center
  2. Community
  3. PDQ Deploy
 

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.

Create Deploy for standard group of applications for new build

Avatar
Broxap Helpdesk

I want to create a standard build for new PCs.

This will allow our admin to build a new PC, add the PC to the domain then push out a deployment of all of our standard applications.

Can this be done and what is the best way of doing it.

0

Comments

2 comments
Date Votes
  • Avatar
    Stephen Valdinger

    Ha! I actually just did this!

     

    We use FOG as our imaging solution in-house. When it images a machine, it adds that machine to the domain to a specific OU. 

    What I did is wrote a powershell script that runs as a scheduled tasks that periodically looks at that OU and any new machines it finds, it adds to a specific security group. 

    I then created a Dynamic Collection in PDQ Inventory that contains members of that security group.

    From there I have created a heartbeat schedule with all of the base applications we require for machines, and have it targeted at that Dynamic Collection from inventory. 

    Now when our helpdesk staff images a machine, it gets dumped to an OU, added to the proper group, and PDQ Deploy pushes our software to it. 

    When the machine is deployed to an end user it is taken out of the security group when my powershell script looks at the OU at the next run.

    0
  • Avatar
    mmuni
    This is what I'm doing. (I'm using WDS and WDT to image machines, it auto creates domain account in specific OU) #1 Set PDQ inventory to sync with active directory so that it knows about new machines. #2 Create a custom scan profile in PDQ inventory that scans for a .txt file of your choice. Example C:\PDQ\Baseline.txt #3 Create a dynamic computer group called Baseline that contains all computers that do NOT have the Baseline.txt file. #4 Create your baseline package that installs everything you want to be install on a new computer (Nested packages are good for this) and then on the last step of the baseline package you will want it to create the C:\PDQ\Baseline.txt file. This will cause the computer to drop out of the baseline dynamic computer collection. #5 Create a schedule that deploys the baseline package to all computers in the baseline dynamic computer collection. Set its trigger as HEARTBEAT so that it gets pushed out to the computer as soon as PDQ see's it.
    0