Having the new SP1 for SCCM2012 R2 in place one of the most interesting features promises to get rid of the hassle of failed task sequences after Application/ Update initiated reboots. The retry this step if computer unexpectedly restarts option let you set a counter how many times the TS should try to resume itself after an unexpected reboot.
With this feature in mind and no changes on updates deployed in SCCM, I’ve started another installation of a reference computer on hyper-v. Everything went well until the updates step kicked in, which is configured according to best practices:
The TS behavior was like
– Scan for all Updates and evaluate them
– Install all Updates on the computer
– Initiate a reboot within the “InstallSoftware Updates 1” Step
– Initialize ConfigMgr Client after the reboot
– Reboot after 1 Minute of Initialization
– Boot to logon window outside of the TS
– After I logged on with the local admin Account I found a fully operational ConfigMgr Client and all 148 Updates in the Software Center with Status Reboot required.
The SMSTS.log states “Task Sequence environment not found”.
First I suspected an issue within the boot images (not deployed correctly?). But the WinPE Version 6.3.9600.16384 matches the expected version and the log files didn’t show any errors for the components used during WinPE.
Then I found an old post from Kenny Buntinx (http://scug.be/sccm/2013/10/09/task-sequence-fails-in-configuration-manager-if-software-updates-require-multiple-reboots/) and the official MS Statement on http://support.microsoft.com/kb/2894518.
After removing the deployment of the Updates listed below, my OSI TS ran through successfully
3036493 MS15-030: Description of the security update for Remote Desktop protocol: March 10, 2015
2984976 RDP 8.0 update for restricted administration on Windows 7 or Windows Server 2008 R2
2965788 MS14-030: Description of the security update for Remote Desktop Security Release for Windows: June 10, 2014
Interestingly I have deployed some evil multi-reboot updates for Windows 8.1 and set the retry option too in the TS and there, everything works, even after Update initiated reboots…
Time to move to W10 though