[windows software] SCCM now Microsoft Endpoint Configuration Manager

[Norphy]

So, with the latest release of SCCM, it no longer appears to be a System Center product. They have rebranded as Microsoft Endpoint Configuration Manager and put it under the Microsoft Endpoint Manager banner, along with Intune and a few other odds and ends.

 

What I want to know is, what implications does this have for licensing, if any? SCCM used to be part of System Center so if you bought enough System Center licenses to cover your servers for SCOM, SCVMM, SCDPM etc, you could also manage them with SCCM. Now that ConfigMgr has been separated out, is this still the case? Will there be a separate license cost for MECM on servers down the line?

Edited January 10, 2020 by Norphy

[CHiLL]

I doubt there will be a change for us as we only purchase/use SCCM and SCEP, not any of the other System Center products.

[Norphy]

If you only use it to manage your workstations, assuming that the SCCM (Well, MECM now) CAL and a license to run a server for it still included in your Microsoft agreement then yes, there won't be any change. If, however, you use it to manage your servers like I do as well, I want to know if there are licensing implications in that case. Previously, if you wanted to run SCCM on a server, you had to buy separate System Center licenses for your servers, they're not covered under your OVS or EES licence.

[Fazza]

If you have a license for Configuration Manager (whether part of the System Center or Microsoft Endpoint Family) then you are licensed for Configuration Manager. Going forward when you next renew it will be called something different. This is not the first name change for SCCM as it used to be called SMS and I bet it wont be the last!