Deploying Windows 10 TH2 (1511) using SCCM 2012

[Added 12/21/2015] – For complete Windows 10 support, upgrade to SCCM 1511 or perform a complete SCCM 1511 installation

The latest build of Windows 10 is available since this week. Windows 10 TH2 or Windows 10 1511 build is the first important release of Windows 10 since it’s launch in July. If you are managing Windows 10 with SCCM 2012 in your organisation you may wish to deploy this latest build using SCCM 2012.

The bad news is that you can’t achieve that with SCCM 2012. You will need to wait for the next version of SCCM to deploy this update to your Windows 10 computers. The good news is that the wait is almost over, the next version SCCM should be shipped before the end of the year.

The product group official statement is :

ConfigMgr 2012 R2 SP1 or SP2 and lower versions do not support Windows 10 servicing via Software Update Management workflow.

This update with the new classification “Upgrade” can be sync’d down from WSUS after the hotfix is applied if the “Upgrade” classification is checked explicitly. However, only vNext client can complete the end to end installation successfully since this Windows 10 Upgrade is in a different format and requires special handling on the client side. Without vNext, the install will fail.

OSD Upgrade Task Sequence is still the recommended way to upgrade to Windows 10 via the current versions of ConfigMgr (excluding vNext) as these versions actually do not support Windows 10 upgrade via Software Update Management.

SCCM 2012 Windows 10 TH2 1511

Windows 10 KB3105211 update shows in the console but don’t try to deploy it through your Software Update process, it will simply fails !