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.We’ll cover it all in the next sections of this post. 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.
Once you install the ADK for Windows 10 you will lose the ability to modify your Win PE 3.1, 4.0 or 5.0 boot images and you’ll only be able to modify Win PE 10 boot image.
You can still use these down level boot images, you just can’t modify them in the SCCM console.
Reference : MDTIf 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. Reference : – 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.
It adds new feature and fixes lots of issues, which some of them are important.
If you’re not familiar with the new SCCM servicing model, read our New Update and Servicing section of the 1602 upgrade post which explain it all.
SCCM 1511 is still the baseline version if you’re starting from scratch.
SCCM 1606 is now available as a new baseline media.
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. Client from SMS_R_System where Operating System Nameand Version like '%Workstation 10.0%' We cover in depth this topic in a previous post.