System Center Configuration Manager: Support for Windows 10 and Microsoft Intune

First published on CloudBlogs on Oct 27, 2015
Note: For the most relevant information on System Center Configuration Manager: Support for Windows 10 and Microsoft Intune, please visit the following blog post documentation links:

• EMS blog: FAQ: System Center Configuration Manager (Current Branch)
• EMS blog: Configuration Manager: a progress update on the current branch and a new servicing branch
• Support for Windows 10 for System Center Configuration Manager documentation

Author : Aaron Czechowski, Senior Program Manager, Enterprise Client and Mobility Windows 10 brings with it powerful new options for deployment and servicing. In System Center, we are committed to providing enterprise customers with best-in-class management for Windows 10 with System Center Configuration Manager, specifically by helping you successfully deploy, manage, and service Windows 10 in the way that suits you best. As I trust you already know by now, Windows 10 comes in two basic flavors: (1) a Current Branch (also known as Windows-as-a-Service) and (2) the Long-Term Servicing Branch with a more traditional support model. The Current Branch also has the option of Current Branch for Business, which is the same build as the Current Branch, just deferred to a later date to give you time to further validate in your environment. If this is all news to you, stop reading and click here for more information and guidance. Then come on back when you are ready. The new System Center Configuration Manager As we announced at Microsoft Ignite with our first technical preview, we will release a new version of Configuration Manager by the end of this calendar year.  This new version will bring full support for the deployment, upgrade, and management of Windows 10. The new System Center Configuration Manager , as it will simply be called, is designed to support the much faster pace of updates for Windows 10 and Microsoft Intune.  This new version will also simplify the Configuration Manager upgrade experience itself, and allow us to listen and more quickly respond to your feedback. We have taken your feedback on making Configuration Manager easier to update, and one of the core capabilities of this upcoming release is a brand new approach for updating the features and functionality of Configuration Manager. Moving faster with System Center Configuration Manager will allow you to take advantage of the very latest feature innovations in Windows 10, as well as other operating systems such as Apple iOS and Android when using Configuration Manager integrated with Microsoft Intune for mobile device management (MDM) and mobile application management (MAM) capabilities. The new System Center Configuration Manager will also be a straightforward in-place upgrade of sites and clients, similar to a service pack. System Center Configuration Manager will support Windows 10 in any flavor: Current Branch, Current Branch for Business, and Long-Term Servicing Branch. This is because we will be able to deliver incremental updates to support the capabilities of future versions of the Windows 10 Current Branch. The fact that we are not including a calendar year in the name is a reflection of the fact that the new System Center Configuration Manager will be updated frequently.  In documentation, in product, and for evaluation and volume licensing download sites we will denote each particular version with a version number, for example “v1512”, for a version shipping in December 2015. We plan to support each version/update for 12 months before we require that customers upgrade to the latest one to continue support. Finally we do intend to ship a version aligned with the rest of System Center and Windows Server when they ship in 2016. Windows 10 support with System Center 2012 Configuration Manager Back in May, the release of System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2 delivered full compatibility with existing features for Windows 10 deployment, upgrade and management. Also note that we released Cumulative Update 1 in August to further enhance support for Windows 10. (For simplicity, I’ll just refer to these products collectively as “ConfigMgr 2012” for the rest of this post.) The ConfigMgr 2012 Supported Configuration article on TechNet only lists support for Windows 10 Enterprise LTSB 2015. Knowing that customers are eager to deploy Windows 10 Current Branch now prior to the release of the new System Center Configuration Manager later this calendar year, we are extending ConfigMgr 2012 support for Windows 10 to also include the first two builds of the Windows 10 Current Branch. This translates to the initial build of Windows 10 released this summer, and the second build of Windows 10 expected to release this fall. We will not extend support for further versions of Windows 10 Current Branch with ConfigMgr 2012 because we need the new System Center Configuration Manager updating model to keep pace with Windows as a Service and Microsoft Intune. In Summary: Planning and Guidance

Product Version	Release Timing	Windows Servicing Support
System Center Configuration Manager	By end of 2015 for initial release	Windows 10 Current Branch, Current Branch for Business, and Long Term Servicing Branch
System Center 2012 Configuration Manager SP2 CU1 AND System Center 2012 R2 Configuration Manager SP1 CU1	May 2015, with cumulative updates as needed	Windows 10 LTSB 2015, Windows 10 CB/CBB through February 2016*

*ConfigMgr 2012 supports Windows 10 version 1507 (build 10.0.10240) and 1511 (build 10.0.10586) for the lifecycle of these builds. Any new Windows 10 CB/CBB builds released in the future will not be supported With ConfigMgr 2012 and will require System Center Configuration Manager current branch for supported management. If you want to deploy Windows 10 in your environment today, you should have already upgraded ConfigMgr 2012 to the latest service pack and cumulative update as many of our customers already have. If you are deploying Windows 10 Current Branch, then you also need a plan to upgrade to System Center Configuration Manager. Once your environment is upgraded to System Center Configuration Manager, then you will be ready to start managing future builds of Windows 10 Current Branch as they are released. If you don’t think you’ll be able to upgrade your environment to System Center Configuration Manager in the next several months, then you’ll need to deploy Windows 10 Enterprise LTSB 2015 with ConfigMgr 2012 to remain in a supported configuration going forward. Subsequent releases of the Windows 10 Current Branch in 2016 and beyond will not be supported with ConfigMgr 2012. Frequently Asked Questions Q) How can I use Configuration Manager to deploy Windows 10? System Center Configuration Manager as well as ConfigMgr 2012 can be used to deploy Windows 10. In addition to traditional OS deployment methods, System Center Configuration Manager will include new capabilities that will enable you to use task sequences to upgrade systems to Windows 10. This task sequence upgrade process can also be used for upgrading Windows 10 Current Branch builds to the latest version. System Center Configuration Manager will also have new capabilities specifically for Windows 10 servicing. Q) What version of Windows do I have to be running in order to complete an in-place upgrade to Windows 10? You will be able to manage in-place upgrades to Windows 10 from Windows 7, Windows 8, and Windows 8.1 with System Center Configuration Manager. Additionally, sample task sequence content is available on the ConfigMgr team blog on how to achieve this scenario using ConfigMgr 2012. Q) Can I manage devices that are configured for the Windows Insider program? Configuration Manager can perform some management capabilities on devices that are running a Windows Insiders build, but since updates are delivered via Windows Update some Configuration Manager features will not be available. This includes, but is not limited to: Software Update Management, Endpoint Protection, and the deployment of third-party updates via System Center Update Publisher. Q) Can I use Microsoft Edge for the Configuration Manager Application Catalog? No, the Application Catalog only supports Internet Explorer at this time. When System Center Configuration Manager becomes generally available by end of this calendar year, it will include a combined end user portal where all company approved software will be located for end users to discover and install. With this change, applications previously available only in the Application Catalog can be viewed in the Software Center. Q) Can I use Configuration Manager 2007 to manage Windows 10? Yes. On September 24, 2015, a compatibility pack was released for System Center Configuration Manager 2007 SP2 to provide support for the management of Windows 10 LTSB 2015 with existing Configuration Manager features. (Note: OS deployment is not supported.) Q) What about System Center 2016 and Windows Server 2016 next year? Will System Center Configuration Manager release a product update in alignment with System Center 2016? Yes, there will be a release of System Center Configuration Manager that will align with the release of Windows Server 2016 and System Center 2016. What other questions do you have? Let us know in the comments, as well as other comments on this topic. -- Aaron Czechowski, Senior Program Manager Configuration Manager Resources Documentation for System Center Configuration Manager Technical Previews Documentation Library for System Center 2012 Configuration Manager System Center 2012 Configuration Manager Forums System Center 2012 Configuration Manager Survival Guide System Center Configuration Manager Support Submit Configuration Manager Product Ideas Report Configuration Manager Product Issues This posting is provided "AS IS" with no warranties and confers no rights.