Recently, we had a situation where we deployed a small client via SCCM 2012 SP1.
All tested fine and the pilot group appeared fine – but upon deploying the client widely, the customers helpdesk started getting calls about a reboot message popping up.
Sure enough, the msi has a /noreboot switch and wasn’t causing a reboot on test machines where the command was run outside of configmgr…. so what was happening?
Well – as detailed here – http://www.1e.com/blogs/2013/05/07/sccm-2012-agent-reboots-when-msiexec-uses-reallysuppress-switch/
a setting – which i think it is fair to say, a setting which isnt very clear, will cause the CM agent to initiate a reboot, even if the install command line supresses the reboot, but the return code is 3010 (soft reboot).
A little disappointing – this is the type of thing that really should be very clear in the interface…. but once finding out, its unlikely we (or you) will make the same mistake again!