Microsoft Endpoint Configuration Manager FAQ
Applies to: Configuration Manager (current branch, technical preview branch)
Starting in version 1910, Configuration Manager is now part of Microsoft Endpoint Manager. This article provides answers to frequently asked questions.
Start by watching the following two-minute video from Brad Anderson, Microsoft corporate vice president for Microsoft 365:
What is Microsoft Endpoint Manager?
Microsoft Endpoint Manager is an integrated solution for managing all of your devices. Microsoft brings together Configuration Manager and Intune with simplified licensing. Continue to leverage your existing Configuration Manager investments, while taking advantage of the power of the Microsoft cloud at your own pace.
The following Microsoft management solutions are all now part of the Microsoft Endpoint Manager brand:
- Configuration Manager
- Desktop Analytics
- Other features in the Device Management Admin Console
For more information, see the following posts from Brad Anderson, Microsoft corporate vice president for Microsoft 365:
What things change in Configuration Manager with Microsoft Endpoint Manager?
In version 1910, aside from the name change, Configuration Manager still functions the same.
How do we refer to the product now?
When referring to the entire solution that includes all components: Microsoft Endpoint Manager
When referring to the on-premises component:
- On first reference, use the full brand name: Microsoft Endpoint Configuration Manager
- For general use: Configuration Manager
- For space-constrained use: ConfigMgr, only in instances where the general use name doesn't fit
Are there any licensing changes?
Yes! As announced at Microsoft Ignite 2019, if you're licensed for Configuration Manager, then you're also now licensed for Intune to co-manage your Windows PCs. For more information, see the Product and licensing FAQ.
Why do I still see "System Center Configuration Manager" some places?
It takes time to make changes across all products, services, and supporting materials like documentation.
There are also some fundamental components that may never change. The main Windows service on site servers is still SMS_Executive. The GitHub repository that supports this documentation will continue to be SCCMDocs.
Learn about the what's new in Configuration Manager incremental versions.