PDQ.com mobilePDQ.com desktop

…and then there was one.

Shane CorellianShane Corellian

Last week Microsoft released about 14 patches. I didn’t want to distribute 14 different deployments to all of my computers so I went old school and just deployed using a single batch file.

Contents of my batch file

Directory of the deployment files. The batch file will call each of these patch files in succession.

I then opened up Admin Arsenal and chose to deploy to my Windows 2003 (x86) collection.

Pay particular attention to my deployment window. I check the “Include entire directory” checkbox. This way I can be certain that all the patch files (listed above) will ready for my batch file.

Admin Arsenal Deployment window

Since I placed the the Command Line arguments in the actual script I didn’t need to add them on the deployment window. I could have passed the arguments via the deployment window and have the deployment script reference the %1, %2 and %3 variables.

This is a simple and effective method for deploying applications and/or patches in rapid succession. This method is great for installing an application and then successive Service Packs or Updates.

Ready to get started?

Take our 14-day Free Trial.
This round is on us!

Don't miss the next post!

Using PowerShell to Install Printers

When installing printers, we will need to do the four things; Add Driver to the Store, Install the Driver, Create Printer Port, and Install the Printer