THANK YOU ALL SO MUCH.
This made it much more clear.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Jay Parekh
Sent: Wednesday, June 22, 2016 9:09 AM
To: [email protected]
Subject: RE: [mssms] RE: licensing servers with sccm

Also keep in mind, Core CAL and Enterprise CAL includes CM, SCEP, and VMM but 
doesn't include other SC components such as OpsMgr, Orch, SM, and DPM.  For 
those you need the CMS ML.

________________________________
From: [email protected]<mailto:[email protected]>
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] RE: licensing servers with sccm
Date: Wed, 22 Jun 2016 10:35:37 +0000
Ok.
And the Client is built into my Core Cal but  the Servers (Standard, Data 
Center) are not.
Just starting to become clear.


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Jason Sandys
Sent: Tuesday, June 21, 2016 10:40 PM
To: [email protected]<mailto:[email protected]>
Cc: Patch Management Mailing List 
([email protected]<mailto:[email protected]>)
 
<[email protected]<mailto:[email protected]>>
Subject: RE: [mssms] RE: licensing servers with sccm

You're not managing differently at all. All managed systems need an ML. There 
are three types of MLs:

-          Client (these are for workstations and cost less of course)
-          Server Standard (there are for physical servers and cost more and 
are per every 2 CPUs)
-          Server Datacenter (I said enterprise below but meant datacenter, 
these are for the physical hosts, cover all VMs on that host, and are also per 
2 CPU - these cost a lot)

You license what *is* managed not what you are managing with.

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of David McSpadden
Sent: Tuesday, June 21, 2016 5:31 PM
To: [email protected]<mailto:[email protected]>
Cc: Patch Management Mailing List 
([email protected]<mailto:[email protected]>)
 
<[email protected]<mailto:[email protected]>>
Subject: Re: [mssms] RE: licensing servers with sccm

So to patch a server,
(Physical), like I patch a workstation,
I need a ml license because I am managing the server differently than the 
workstation?


Sent from my iPhone

On Jun 21, 2016, at 5:43 PM, Jason Sandys 
<[email protected]<mailto:[email protected]>> wrote:
All *managed* servers must be licensed with a management license (ML) - that is 
correct. Standard is for physical systems and Enterprise is for all VMs on a 
physical system.

*Management* servers require no license just to run ConfigMgr site components 
or roles. If they are also managed though, then they of course do require a 
license management license (ML).

J

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of David McSpadden
Sent: Tuesday, June 21, 2016 2:52 PM
To: [email protected]<mailto:[email protected]>; Patch 
Management Mailing List 
([email protected]<mailto:[email protected]>)
 
<[email protected]<mailto:[email protected]>>
Subject: [mssms] licensing servers with sccm

I am on the phone right now with Microsoft licensing and they are stating that 
I need to license all my member servers with Systems Center Standard license 
per each server.
What am I missing?



David McSpadden
System Administrator
Indiana Members Credit Union
P: 317.554.8190
<image001.jpg><http://imcu.com/>  
<image002.jpg><https://www.facebook.com/IndianaMembersCU>  
<image003.jpg><https://twitter.com/IndMembersCU>

<image004.jpg>
<image005.gif><http://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0ahUKEwjFztf-tePJAhXK5iYKHcPtAxEQjRwIBw&url=http://www.amuletsolutions.com/awards.aspx&bvm=bv.110151844%2cd.amc&psig=AFQjCNHkrx8CednTEOOq4zUxYyrRUGzUsg&ust=1450459757284499>

This e-mail and any files transmitted with it are property of Indiana Members 
Credit Union, are confidential, and are intended solely for the use of the 
individual or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or otherwise have reason to believe that you have 
received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.

Please consider the environment before printing this email.


This e-mail and any files transmitted with it are property of Indiana Members 
Credit Union, are confidential, and are intended solely for the use of the 
individual or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or otherwise have reason to believe that you have 
received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.

Please consider the environment before printing this email.


This e-mail and any files transmitted with it are property of Indiana Members 
Credit Union, are confidential, and are intended solely for the use of the 
individual or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or otherwise have reason to believe that you have 
received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.

Please consider the environment before printing this email.

This e-mail and any files transmitted with it are property of Indiana Members 
Credit Union, are confidential, and are intended solely for the use of the 
individual or entity to whom this e-mail is addressed. If you are not one of 
the named recipient(s) or otherwise have reason to believe that you have 
received this message in error, please notify the sender and delete this 
message immediately from your computer. Any other use, retention, 
dissemination, forwarding, printing, or copying of this email is strictly 
prohibited.

Please consider the environment before printing this email.



Reply via email to