How to Enable Windows 10 and Windows 8 Patching support for SCCM? First, SCCM 2007 SP2 and above official support for Windows 10 is available only for Windows 10 Enterprise 2015 long-term servicing branch (LTSB) edition. (Other editions of Windows 10 are not supported by Microsoft).
This doesn’t mean other versions of Windows 10 patching won’t work with SCCM 2007 SP2; it does mean that Microsoft has not tested other versions of Windows 10. Windows 8.1 patching can also be accomplished via SCCM 2007 SP2.
We need to ensure that the WSUS server is updated accordingly to support Windows 10 Enterprise 2015 LTSB and Windows 8.1 patching via SCCM 2007 SP2. Update for Windows Server Update Services (WSUS) 3.0 SP2 – KB2734608 needs to be installed on your WSUS 3.0 SP2 server to enable Windows 10 and 8.1 patching.
To enable Windows 10 Enterprise 2015 LTSB and Windows 8.1 patching support in your environment, we need to follow the steps mentioned below. As usual, all these patches should be applied in a top-to-bottom approach, which means that the Tier 1 server should be patched first and followed by the hierarchy. Also, we need to keep a watch on Sitecomp.log to understand whether all the SCCM component reinstall process is going well or not.
Install the patch KB 2734608 on Tier 1/ 2/3 WSUS servers SP2 servers
Install patch KB 2750782 to enable Windows 8.1 patching support on Tier 1/2/3 SCCM 2007 SP2 and above servers
Install patch kb 3044077 to enable Windows 10 enterprise 2015 LTSB patching support on Tier 1/2/3 SCCM 2007 SP2 and above servers
Install KB2750782 and kb3044077 on SCCM 2007 SP2 Secondary Server/s
Install KB2750782 and kb3044077 on SCCM 2007 SP2 remote admin console
Install KB2750782 and kb3044077 on SCCM 2007 SP2 Clients
After installing patches on the WSUS and Tier 1 SCCM 2007 server, Windows 10 LTSB and Windows 8.1 options appear on SCCM 2007 Software Update Point component properties under the products listing.
How to Enable Windows 10 and Windows 8 Patching support for SCCM
Once these patches are installed on the central SCCM 2007 server, manually initiate WSUS sync via Run Synchronization from Update Repository in SCCM 2007 SP2 console. We can analyze details from WsyncMgr.log regarding Windows 10 and Windows 8.1 patch updates.
Sync: SMS synchronizing updates, processed 0 out of 40 items (0%) Synchronizing update a8db29ac-2343-43f6-9045-45eb9a6cd582 Synchronizing update dc226d92-7c02-40c4-94a9-63c7696b18c5: Update for Windows 10 for x64-based Systems(KB3106932) Updated 12 items in SMS database, new update source content version is 323
Synchronizing update f31549fb-f5d1-44b7-a2a0-c38a1f22f7d5 Synchronizing update b0e64138-94a4-4c66-b22c-275b76a42469: Update for Windows 8.1 (KB3112336) Synchronizing update 46df5f6c-4c03-4441-8d46-1362519777ba Synchronizing update 0887c665-7c86-41e9-b603-6bb9aa220cb2: Update for Windows 8.1 for x64-based Systems (KB3112336)
SCCM Related Posts Real World Experiences Of SCCM Admins (anoopcnair.com)
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 blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…