How SCCM Became MEMCM, or Just ConfigMgr
When you start working on Configuration Manager, one of the more puzzling things is how you’re supposed to refer to it in the first place.
You might know someone who still calls it “SMS”. Or at least you’re wondering why “SMS” keeps appearing as an acronym in some of the log files.
SCCM is the most common way you’ll hear it referred to, but technically that hasn’t been true since 2019.
And yet its full name is too long — so people keep calling it SCCM.
Without getting TOO deep into the history of Configuration Manager, I wanted to show how this happened.
- 1994 – Released as Systems Management Server (SMS)
- 2007 – Released as System Center Configuration Manager (SCCM) 2007
- Dec. 2019 – Released as Microsoft Endpoint Configuration Manager (MECM)
In June 2007, Microsoft created the System Center suite of tools, which included:
- Configuration Manager (renamed from SMS)
- Operations Manager
- Data Protection Manager
- Reporting Manager
- Virtual Machine Manager
- Capacity Planner
The app was renamed to Configuration Manager, as part of System Center, so: System Center Configuration Manager, or SCCM.
As explained in this ITProToday article from 2007, SCCM was the chief tool of a deployment and configuration strategy that centered around System Center.
In my experience, many people inexperienced with ConfigMgr think “System Center” is part of the app’s official name, because SCCM is still the most common way to refer to it.
They may not even be aware that System Center is its own suite of tools, with its own documentation site.
- SMS – The veterans know
- SCCM – Typical way I see it still referred to today, but inaccurate
- ConfigMgr – Second-Most typical way I see it referred to. Accurate abbreviation for MECM. Some Microsoft teams use this.
- MECM – The full acronym for ConfigMgr, as it exists as part of Endpoint Manager
Craig Wall is a public sector systems administrator with experience in deployment and print management.