according to the interwebs Microsoft Installer: MSI: Installation and Uninstallation of MSU in silent mode you should run:
wusa.exe ??SOURCE?? /quiet /norestart
maybe there are some logging options for wusa to see what happens? and does that work outside of bsa ?
generally the flow is:
- make it work silently outside of bsa
- add it to bsa and test it.
For some reason it does not worked for me too either based syntax I have not figured it out why but there are couple of are workaround compile an exe with msu (same syntax) and call the exe on the server or add patch to catalog and include those in the smart group and include only that smart group to analysis the server
It does not work how?
Outside of bsa?
Inside of bsa ?
I have no idea I havent investigated about it, but it so easy to call an exe through BL rather an msu .
Compile an exe for msu rest of the process is same New > Software > Custom Software>Select the complied exe
I've done this successfully before... Add the msu to the depot as an msi package. Set the Install command as Bill mentioned : wusa.exe ??SOURCE?? /quiet /norestart
Then add this to a BL Package and deploy the BL Package
If it's not working add: /log c:\temp\netframework.log to the install command to capture more information.
@Richard McLeod - that worked! Thanks. It seems all I needed to do was changed the software type to MSI rather than Custom Software.