testing new version of application which supersedes older version. Have found in testing that simply uninstalling the old MSI is not sufficient - a reboot is needed. Therefore sequence of events from SCCM perspective is
1. New app - V 1.1 supersedes old msi (uninstall) V1.0
2. V1.0 uninstall runs msiexec /x xxxxx to uninstall
3. reboot
4. Install New version 1.1
So question is how to gracefully handle the reboot
I could create a separate uninstall job with an exit code that tells SCCM to reboot with the usual countdown but this splits the job into two and user would be without their application once done
However, I'm not sure if putting a shutdown.exe -r into the v1.0 uninstall cmd is a great idea
Ian Burnell, London (UK)