Let’s check how ConfigMgr Client Upgrade from Caused Reboot? ConfigMgr 2012 Client Upgrade from SP1 to R2 can Cause a Reboot of SCCM Endpoint Manager. Update: TechNet Library has been updated with the restart information. April 2014!
- Clarified that the client prerequisite Microsoft Visual C++ 2010 Redistributable version 10.0.40219.1 might require a restart when it is installed on client computers. More details here.
One of my ConfigMgr community friends, Harjit Dhaliwal, experienced this issue while doing SCCM 2012 SP1 to R2 client upgrade. All credit to him for doing research and coming up with these findings!! I thought of sharing this because this would help some others in the community. ConfigMgr 2012 Client Upgrade?
ConfigMgr 2012 Client Upgrade from SP1 to R2 can Cause Reboot
Also, the SCCM 2012 R2 upgrade checklist is available for the SCCM 2012 SP1 to R2 Upgrade Checklist.
End-user systems were getting rebooted after ConfigMgr 2012 R2 client upgrade. Using a proper maintenance window could be avoided, especially the new option in SCCM 2012 R2 dedicated to software updates. ConfigMgr 2012 Client Upgrade?
More details http://technet.microsoft.com/en-us/library/dn236351.aspx#BKMK_WhatsNew_Software. This unexpected reboot may happen only in the scenario which is explained below:-
What Triggered the forced reboot? ConfigMgr Client Upgrade from Caused Reboot SCCM Endpoint Manager
Security Update for Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package (KB2565063). A security issue has been identified leading to MFC application vulnerability in DLL planting due to MFC not specifying the full path to system/localization DLLs. ConfigMgr 2012 Client Upgrade?
You can protect your computer by installing this update from Microsoft. After you install this item, you may have to restart your computer.
How security patch installation got triggered suddenly after the ConfigMgr SCCM R2 client upgrade?
Since “Security Update for Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package (KB2565063)” was released/revised in March 2012. The update is in a Software Update Group deployed in April 2012. The update has become mandatory and passed due for the systems that now need it due to the NEW CM 2012 R2 client prerequisite and the reboot requirement, which some of our CM users have noticed.
Few more details on NEW CM 2012 R2 client prerequisite
Microsoft Visual C++ 2010 Redist (version 10.0.40219.1) is now a prerequisite for the ConfigMgr 2012 R2 client (5.00.7958.1000) install, along with Microsoft Visual C++ 2005 Redist (8.0.6100).
You’ll find references to it in the ccmsetup.xml file located in c:\windows\ccmsetup. Also, on the ConfigMgr server, you’ll find the prereq installers located in c:\Program Files\Microsoft Configuration Manager\Client\x64 or \x86, and the vcredist_x64.exe or vcredist_x86.exe is the 2010 redist.
The client prereq info located in the doc below is incorrect.
When you look at client prerequisites, it’s very clearly mentioned that .Net Framework 4.0 installation can trigger a reboot (When the .NET Framework 4 is installed on computers, a restart might be required to complete the installation). Still, this scenario is not explained over there.
Resources ConfigMgr Client Upgrade from Caused Reboot SCCM Endpoint Manager
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a logger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…