SCCM 2012 SP1 installation reboot behaviour on 3010 return code

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 –

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!

Leave a Reply