Automate deployment to new machines in certain OU?
Is there a way to automate deployment of multiple packages (in a certain order) to a machine after it is detected in a certain OU?
For example. When we bring a machine online, we want to certain peices of software pushed to it, in a certain order. The OU the machine will be placed in is an OU just for provisioning.
Once PDQ sees a machine in said OU, we'd like PDQ to kick off the deployments.
Is this possible?
0
Comments
Seems logical.
Now - this is what perplexes me. I only want the deploy done one time.
What I envision is creating a "provisioning" OU of which when new machines are joined to the domain, they are placed in this OU. I then want PDQ to discover these through sync and deploy 4 packages and that's it, only once.
Will PDQ continue to try pushing this package on a schedule?
Yes.
Create a dynamic list in PDQ Inventory that shows computers in your set OU.
Then create a schedule in Deploy that is linked to that Dynamic list in Inventory. If you set it up with a heart beat trigger it will fire off right when the computer comes online.
In the schedule add the packages you want to deploy and sort them in order from top to bottom that you want them deployed.
I think I just found my answer. Thanks.
to go one step further, create a package that copies a file to the computer. This package will only be pushed out during provisioning. Make this file copy the last step or package for your provisioning.
then create a custom scan profile that scans for that file.
You can then know once a computer has been provisioned it will have the file you copied to it and you can then do things like automatically make it drop back out of the Provisioning list after its been provisioned.
One "issue" I'm seeing is that after I add my machine to the OU, and the scan happens, it's not deploying until I hit "Start Schedule" in the heartbeat schedule deployment. It's already on, but it seems I have to force it again?
Is this normal?
the way heart beats work is that every few minutes pdq runs a heartbeat check on all the computers and if their status changes from offline to online it will trigger the schedual to run on that computer that has come online. You can change the frequency that hearbeats happen in preferences.
You could also add another timed trigger in addition to the heartbeat, so lets say you schedual it to run every 30 minutes, no matter what it will trigger every 30 minutes as a backup to the heartbeat.