This project has moved. For the latest updates, please go here.

Support for .msu

Topics: Feature Request
Nov 17, 2015 at 10:13 AM
Is there a possibility to implement Support for .msu files ?
These files are used for Hotfixes, but also for the new Windows UPGRADES ( 1511 ), if you download online via Windows Update Service.
Because there are undefined situations for these Upgrades in Domain areas and Wsus, a sideloading WPP to WSUS will be a good idea.
It is not possible to import it these files in WSUS directly. There are a Workaround to prepare a Update with netECM:MsuToExe, for using with SCUP.
Is there a recommandation for WPP to handle .msu files ?
Editor
Nov 17, 2015 at 5:33 PM
Yes, you can use a Batchfile with this Content:

%windir%\System32\wusa.exe Name_of_your_Package AND PARAMETERS

For exact Syntax run: wusa.exe /? and try one or two times for getting the correct Syntax.

But: How you will check if the update is installed? Otherwise WU-Agent will install many times the Hotfix.
Nov 18, 2015 at 8:12 AM
Dont know, for hotfixes :-) .
But for Windows Upgrades - simple check the build number.

Ok hope I understand....... the workaround ist:
1 Create a Scipt in servers Software Deployment Folder
2 Create a Custom Update in WPP, including:
2a use "Allow to Copy, Delete, Rename a file", use action "Copy"" to transfer the *.msu to a clients folder, eg %windir%\temp
2b use "Allow to Copy, Delete, Rename a file", use action "Copy"" to transfer the Batch file to a clients folder, eg %windir%\temp
3 use " Allow to execute Vb Script, PowerShell Script " and run the batch file.
4 ......
Check return codes ??.........

REALY ? A little bit....difficult...

I think a repackaging, to generate a exe. is easyer to handle ? I can use the WPP standard updat creating process with rules. Ok, I lost the WPP deinstallation option with .exe files.

WPP support "native" .exe, .msi, .msp, What is the (technical or logic) problem with .mus ?
Coordinator
Nov 18, 2015 at 3:27 PM
WPP support "native" .exe, .msi, .msp, What is the (technical or logic) problem with .mus ?
It is a limitation on the Wsus API : See PopulatePackage methods