Configuration Manager: A History of Names
For more on Configuration Manager Click Here
Disclaimer: I create this content entirely on my own time, and the views expressed here are mine alone (not my employer’s). Because I love leveraging new tech, I use AI tools like Gemini, NotebookLM, Claude, Perplexity and others as a “digital team” to help research and polish these articles so I can share the best possible insights with you!
For nearly three decades, Microsoft Configuration Manager has been a cornerstone of enterprise device management. From its origins as Systems Management Server (SMS) to its evolution into System Center Configuration Manager and today’s Microsoft Configuration Manager, the product has played a critical role in how organizations deploy operating systems, manage software, secure endpoints, and maintain compliance at scale. Trusted by IT teams across industries, Configuration Manager has shaped modern endpoint management practices by providing reliability, deep control, and proven scalability—establishing a legacy that continues to underpin hybrid and on-premises environments even as the industry transitions toward cloud-native management.
If you see SCCM, MECM or Microsoft Configuration Manager, they all refer to the same ConfigMgr product, just from different points in its naming history.
There was no product change, licensing change, or functionality split — only a name change to align with Microsoft Endpoint Manager branding at the time.
Many long-time admins still say “SMS server” out of habit — and everyone knows exactly what they mean.
Name Evolution
- SMS – Systems Management Server
- System Center Configuration Manager (SCCM) – the original name many admins still use
- Microsoft Endpoint Configuration Manager (MECM) – rebranded name introduced in 2019
- Microsoft Configuration Manager – the current official name used by Microsoft
| Era | Product Name | Focused On |
|---|---|---|
| Mid-1990s – Mid-2000s | Systems Management Server (SMS) | Software distribution, hardware and software inventory, basic patch management |
| 2007 – 2019 | System Center Configuration Manager (SCCM) | Enterprise-scale device management, OS deployment, software updates, reporting, and integration with the System Center suite |
| 2019 – 2022 | Microsoft Endpoint Configuration Manager (MECM) | Same core capabilities as SCCM; rebranding aligned with Microsoft Endpoint Manager and modern management initiatives |
| 2022 – Present | Microsoft Configuration Manager | Simplified branding; stable, secure on-premises and hybrid endpoint management, often used alongside Microsoft Intune |
Important Clarification
- MECM ≠ Microsoft Intune
- MECM (ConfigMgr) is still the on-premises / hybrid device management solution
- Intune is the cloud-native endpoint management platform
- Both can be used together via co-management
Microsoft Configuration Manager is not just a product—it is a platform that defined enterprise endpoint management for decades and continues to provide stability, scale, and trust as organizations navigate the transition to modern, cloud-based management.
Have questions, ideas to share, or just want to connect? I’d love to hear from you! Check out my About Page to learn more about me or connect with me.