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 ?
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 ?