Since Windows 10 is out, there’s been a ton of information coming out from the SCCM product group. Many people gets confused at what’s needed for managing Windows 10 with SCCM 2012. The goal of this post is to centralize all those information so you can reach out when your organisation will be ready for managing Windows 10 with SCCM 2012.
[Updated 12/21/2015] – For complete Windows 10 support, upgrade to SCCM 1511 or perform a complete SCCM 1511 installation
Requirement for Managing Windows 10 with SCCM 2012
Before you can manage and deploy Windows 10 in your organisation, you need to update your SCCM infrastructure.
- Your site servers needs to be updated to SCCM 2012 R2 SP1 or SCCM 2012 SP2. Refer to our installation guide if it’s not the case.
- You need to apply R2 SP1 Cumulative Update 1. Refer to our installation guide if it’s not the case.
- You need to update your boot images to Win PE version 10. Refer to the Deployment section of this article.
- If you need to integrate MDT with SCCM, update your MDT version to MDT Update 1. Refer to the Deployment section of this article.
The official documentation
is not yet updated but you can install the SCCM 2012 client on a Windows 10 device. has been updated to include the LTSB version of Windows 10 as an official supported OS.
The official statement from Microsoft is : These service packs (R2 SP1/SP2) deliver full compatibility with existing features for Windows 10 deployment, upgrade, and management.
Which means : All that you can do with older Operating System (Windows 7, Windows 8) can be done with Windows 10 in term of management. (Inventory, Remote Control, Software updates, Software deployment, Anti-Virus…). We’ll cover it all in the next sections of this post.
If you want to regroup your Windows 10 devices in a collection using a query, Windows 10 version is 10.0. (Not 6.4 as in the Tech Preview version)
Use the following query to create your Windows 10 collection :[pastacode lang=”sql” message=”” highlight=”” provider=”manual” manual=”select%20SMS_R_System.ResourceID%2CSMS_R_System.ResourceType%2CSMS_R_System.Name%2CSMS_R_System.SMSUniqueIdentifier%2CSMS_R_System.ResourceDomainORWorkgroup%2CSMS_R_System.Client%20from%20SMS_R_System%20where%20OperatingSystemNameandVersion%20like%20’%25Workstation%2010.0%25′”/]
Our Set of Operational Collections has also been updated to include Windows 10 in its collection list.
- Product Group blog article – Announcing the availability of System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2
If you want to deploy Software Update to your Windows 10 device, you just need to enable Windows 10 in your Software Update Point configuration.
- Go to Administration / Sites Configuration / Sites
- Select your most top site on which Software Update Point role is installed
- Go on Configure Sites Components from the top ribbon
- In the drop down menu, click on Software Update Point
- In the Software Update Point Components Properties window, go on the Products tab
- Check Windows 10 under the Windows section, and then click on OK
- Go to Software Library / Software Updates / All Software Updates
- Right click All Software Updates and select Synchronize Software Updates
- Once the Synchronization has completed, stay in All Software Updates and select Add Criteria on the right
- Select Windows 10 in the Product list
- At the time of this writing there’s 10 updates available
We cover in depth this topic in a previous post. Long story short, Windows Defender is now managing your Endpoint Protection clients in SCCM.
If you want to deploy Windows 10 computers using SCCM 2012, there’s a couple of things to know :
Windows Automated Deployment Kit (ADK)
You need the Windows 10 ADK to capture and deploy Windows 10 devices. You probably already have Windows 8.1 ADK installed on your SCCM Servers.
You must first uninstall the existing ADK, install the Windows 10 ADK and reboot your server before using it.
Make sure you upgrade the Windows ADK on all systems in the site that have it installed. This can include the site server, SMS Provider, and administrator consoles. The version of the Windows ADK needs to be consistent across all systems that leverage it.
Once you install the ADK for Windows 10 you will lose the ability to modify your WinPE 3.1, 4.0 or 5.0 boot images and you’ll only be able to modify WinPE 10 boot image. You can still use these down level boot images, you just can’t modify them in the SCCM console.
Windows PE 10 boot images supports deployments of Windows 7 through Windows 10.
- Product Group blog article – Windows 10 ADK and Configuration Manager
- MSDN article – Download kits and tools for Windows 10
In-place upgrade Task Sequences are not available out of the box in SCCM 2012 R2 SP1. If you want to upgrade your existing Windows 7 or Windows 8 computer to Windows 10 using an in-place task sequence, you must do it manually using custom scripts provided by the product team. SCCM Vnext will have this feature when it ships Q4 2015.
- In-Place Upgrade Task Sequence Part 1 – How to upgrade to Windows 10 using the task sequence in System Center 2012 R2 Configuration Manager
- In-Place Upgrade Task Sequence Part 2 – Revised content for the Windows 10 in-place upgrade via task sequence for Configuration Manager
If you are using MDT in your organisation to build your Windows 10 images or integrated with SCCM, the new MDT 2013 Update 1 version supports it.
MDT 2013 Update 1 is available through this link.
- Product Group blog article – MDT 2013 Update 1 Now Available
[Added 12/21/2015] – For complete Windows 10 support, upgrade to SCCM 1511 or perform a complete SCCM 1511 installation
[Added 10/30/2015] – Offical support article from the product team
The official statement from Microsoft is : The next version of System Center Configuration Manager will deliver full support for client deployment, upgrade, and management of Windows 10 and associated updates.
This means that you won’t be able to manage Windows 10 Service Branches using SCCM 2012.
If you are using MDT 2013, you will need to wait for the next release of MDT (MDT 2013 Update 1) to deploy Windows 10. This is due for end of August 2015.
- Product Group blog article – Windows 10 enterprise management with System Center Configuration Manager and Intune
- Product Group blog article – Windows 10 ADK release and MDT 2013 Update 1 plans
We hope you enjoy reading this article, with a new version of Windows comes new challenges. We’ll update this blog post as soon as Microsoft release more information about managing Windows 10 with SCCM 2012.
Visit our consulting service page if you need help deploying or managing Windows 10 with SCCM 2012.
– I installed SCCM 1702 for a sole purpose of deploying software updates for Windows 7, 8, 8.1 and 10 versions 10.0, 1511, 1607, 1702.
– As we test the software update, Windows 7, 8, 8.1 and 10 version 1607 are receiving the pushed updated, but Windows 10 version 1511 and windows 10 Version 10.0 cannot receive the pushed update.
It would be appreciated if you could provide us with documents or help with regards to the issues, we would like to validate if SCCM 1702 can support the problematic versions and build stated above.
Can you tell me or point me in the direction of why there are so many windows 10 update categories? Now with creators build seems have have added another 3 added, so in the windows 10 updates i now count 16 product categories. How do I know what to check for regular updates, and what to check for servicing? Thanks in advance!
So well explained! Congratulations. Great article. I updated to SCCM 2012 R2 SP1 to CU1 without any problem following your instructions and concepts.
Hey All, I need some help. I am try to run a report for our upcoming Windows 10 upgrade. I am using the SCCM Built-In Report “Operating System requirement status for computers in a specific collection” under the Upgrade Assesment folder. This will show me what computers are eligable to upgrade to Windows 10.
They have asked me to add 2 columns to the report that will show the User Name of the person using the computer and what department they fall under. How can I add this to the report results? I am not that good at SQL. Thank you
I can’t enable Windows 10 in my Software Update Point configuration. There is no Windows 10 listed…
I have upgraded to SCCM 2012 1511 (5.0.8325.1000). Do you have any ideas?
Your posts are super helpful. Great job!!
Can I use winpe 5.0 for windows 10 deployments? we are yet to upgrade in our production environment.
I need to manage windows 10 from this sccm, so I need to install comulative update 1 (I using this link: https://systemcenterdudes.com/managing-windows-10-with-sccm-2012/ )
But when I try to install comulative update, I get this error:
Server update status: This update applies to product version 5.0.8239. The installed version on this computer is 5.0.7804.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
So I need to upgrade my sccm 2012 sp1 r2 to sccm 2012 sp2, but when I upgrading, get error that
1. Cannot install SCCM SDK on Windows Cluster Node.
2. Cannot install the management point or distribution point site system roles on Windows Cluster Node.
On my this server failover clustering service is disabled. So whats wrong?
Photo here: http://s9.postimg.org/tesxtc6m7/img.jpg
I am on SP1 yet when I go to my sites Windows 10 is not there to update my site with. Do I need to have the ADK plugs installed to get access to 10? This guide was so helpful.
Nice Article; thanks very much dude
SCCM 2012 R2 will work with Windows 10 Professional? I ask, cause I heard, (bad me), that you have to have the Enterprise version.
Yes the Pro version will work but I suggest that you read the following post to fully understand : http://blogs.technet.com/b/configmgrteam/archive/2015/10/27/system-center-configmgr-support-for-win-10-and-intune.aspx
Thank You Benoit for the information, it helps out a lot!
Great guide. Especially helpful used with the two linked update guides to move to 2012 R2 SP1 CU1.
I’m still somewhat confused though. Feeling like I missed something.
At the top of the page you mention the need to update the boot images, but in Deployment, it mentions only the installation of the ADK. It sort of implies that the boot image should just automatically update, but then, maybe not. After the install my boot images are at 6.3.9600, and I’m kind of expecting them to be 10.xx.
So I’m not really sure if this is correct, or if something failed, or if I should now manually update the boot images.
I’m considering trying the instructions here …
… though I’M not entirely clear on what it’s doing.
No need to do all the stuff on the related blog article. Just go to your Boot Image, right-click and select Add Boot Image. Select your winPE boot image in your ADK installation directory and you’ll have your WinPE version 10 in SCCM.
This information is very handy! Thank you so much! Any thoughts on how to inject Windows 10 updates into your OS Image? Under Software Library – Operating Systems – Operating System Images when I right click on my Win10 image and select Schedule Updates I only see Windows 8 updates. I don’t see any Windows 10 updates. I’ve selected Windows 10 on my Software Update Point and resynchronized. Windows 10 updates do show up under All Software Updates and I can push them to a collection, but they are not on the list of updates I can select from to inject into the image. I’m not sure why they wouldn’t be there. We’ve got SCCM 2012 R2 SP1 here. Any help would be greatly appreciated!
There’s a hotfix to resolve this issue : https://support.microsoft.com/en-us/kb/3089193
Thank you for this 🙂
This hotfix doesn’t resolve the issue of Schedule Updates showing only Windows 8 updates.
Pingback: Managing Windows 10 with SCCM 2012 | MS Tech BLOG
With your query I cannot detect all Windows 10, so I include these 2:
Windows 10 Pro Collection:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like “%Windows 10 Pro%”
Windows 10 Enterprise Collection:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like “%Microsoft Windows NT Workstation 10%”
Thank you so much! We planning to upgrade to SCCM 2012 R2 SP1. Very helpful.