The PDQ Deploy Install step is more powerful than you may think. Jordan and I walk you through all the many uses for the Install step. These include .exe, .msi, .msp, batch files, VBscripts, Regedit files, and PowerShell scripts.
PDQ Deploy makes the installation of different install files smooth as butter. MSI files are probably the easiest slam dunk files to install. Because of the .msi extension, you’ll already know the parameters. If you have additional files that are more complex, you can load them in the ‘Additional Files’ drop down.
Another excellent use for the Install Step is PowerShell and according to Jordan,
“It is the best EVER language from Microsoft.”
By default, it runs in non-interactive, no profile, and bypass. However, if you need to add additional parameters you can add those to the ‘Parameters Line,’ and it will append it to your Command Line.
Hop in the Wayback Machine
You can also run your VBscripts (and flashback to the late 90’s) using PDQ Deploy. But because of the extension, you’ll need to run cscript .exe. If you have any further arguments, add those to the ‘Parameters Line’ as well.
Probably the second most commonly used files used are .exe files. They are great, but the only problem with .exe files is that you need to find the silent parameters. Make sure you find your vendor’s silent parameters…you can do that simply using Google. Once you find those, add them to the ‘Parameter Line.’
A batch file can be run using a command .exe. We use a lot of the same default commands for this scenario. Also, any changes you want to make to your registry can be made using a reg file. This is a great solution for single machines, but if you have multiple computers, you would want to use a Group Policy.
In this video, I provide a short introduction to the Command Step, just one of the many steps you can use in creating or editing a package.
So what kind of commands can you put in command step? Anything you can run at the command line you can run here. You can flush DNS, force GP updates, and many other basic commands.
Two things to Take Away
- Each Command goes on its own step
- Each step in and of itself is autonomous, so if you are referencing a mapped drive…. map them in each Command Step.
In this video, I take you through the PowerShell step of a Deploy package. The PowerShell step allows you to run remote PowerShell scripts and commands on remote computers from within a Deploy package