In PDQ Deploy Install Step (Part 1), we discussed PDQ Deploy and the Install Step, the Command Step, and the PowerShell Step. If you missed it, you can get back up to speed by reading the article here. Now, let’s dive into a few other PDQ Deploy Install steps.
The Nested Package Step
The great thing about the Nested Package Step is that you’ve got packages that are already built, and you only need to build one package to deploy many other nested packages.
With a baseline package, Deploy allows you to select multiple nested packages and deploy multiple other packages at the same time, in one single deployment.
File Copy Step
The File Copy Step is pretty self-explanatory. If you want to copy files to a target machine you can use this deploy step. There are a few caveats you need to know when copying files:
- You need to know your source and destination. Your source is where your files are coming from and your destination is where those files are going to go.
- In regard to your source file…the easiest way to copy the files would be directly from your source machine.
- UNC path is recommended especially if you are using a pull method instead of a push. Also, make sure the folder you are copying from has permissions for your console to grab those files.
- The destination path or target folder is where you want those files to go.
- If there is an existing install file then you would want to select, ‘Override Existing File.’
- You also have the option to, ‘Ignore Override Errors’.
- Another option is to select an entire install folder and everything in it or even subfolders and copy over all those files.
- Copying file patterns is also an option.
The source needs a good UNC path or needs to come directly off of your console. ‘Target,’ is where those files are going to go on the target machine. Also, make sure you select and consider all of your other options when copying files using the ‘File Copy Step’.
The Reboot Step is ideally named because that is exactly what it does, reboot a machine.
Why would you use it….well to reboot or shutdown a machine.
PDQ Deploy allows you to choose how many seconds before the target machine is rebooted. You can also send a message to the end user if you’re rebooting their machine. Lex mentions that one of his favorites is, “Good luck saving your data.” That’s just part of his full contact IT philosophy.
Deploy even allows you to select the ‘Shutdown Only’ box, which will shut down the target machine as opposed to rebooting it.
And remember to be careful, you don’t want to send those commands out to servers accidentally.