How to deploy a Microsoft .MSU patch file silently using the BMC Client management?

This example deploys a .msu file from Microsoft using the Windows Update Standalone Installer.  This same methodology can be used deploy other file types including MSI files using msiexec, or even using a properly fabricated batch file.

• Create a new Custom Package, this example uses Deploy Custom MSU however any name will suffice.

• Add the .msu file to the custom package:

Select the Custom Package Configuration -> Installation Tab and populate the Destination and Run Command fields:

• on Destination

  • C:\temp\Cust_MSU

• if this location doesn't exist on the assigned device(s) it will be created

• An alternate location can be selected as long as the path in the run command is updated

Run Command:

C:\WINDOWS\SYSTEM32\wusa.exe c:\temp\Cust_MSU\Windows6.1-KB2819745-x64-MultiPkg.msu /quiet /norestart

Additional: For .msp package, run the command as below:

msiexec /p “<msp file name with path>” /qn

• Here populating the fully qualified path to the binary wusa.exe is must. Since, this will run as the Local System account used by the Client Management service.

  • It is also possible to run this as an alternate user account by populating the "Run As" tab.  In this example, as with most examples, it wasn't needed and Local System execution was sufficient..

• Publish the Package to the Master Server:  

• Once Published, assign to the appropriate device using the default schedule:

Once the operational rule is assigned, to monitor the installation progress via task manager. Go to the device and launch the Task manager and check if the WUSA.exe process is running. Which means the installation is going on.

• Once Complete verify via the Console that the package executed properly.

• Additionally, the Windows Event Logs on the assigned device will verify the installation, which was confirmed via the following dialog:

See also:  BEST FAQ on BMC Client Management Package Deployment Issues