That is correct. Your Test/Dev environments do NOT have to be licensed, as long as the data isn’t moved from that environment into your Production environment. So, Test/Dev don’t need to be licensed, but if you have a true Staging environment, that would need to be licensed.
We just went through our EA renewal drill ☺ From: [email protected] [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Wednesday, June 15, 2016 6:27 AM To: [email protected] Subject: RE: [mssms] RE: OT: Licensing SCCM Distribution Points That’s valid although from memory, and I could totally be wrong on this, Microsoft has never really cared about licensing for non-production environments as long as you have your production environment licensed. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Todd Hemsell Sent: Tuesday, June 14, 2016 3:28 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: OT: Licensing SCCM Distribution Points We have a large test and dev environment. Instead of licensing the servers and products in it we buy everyone that accesses the te3st/dev environment a MSDN license. Saves a LOT of money. On Sat, Jun 11, 2016 at 9:02 AM, Jason Sandys <[email protected]<mailto:[email protected]>> wrote: OMG. Run away, don’t walk. There’s no reason for you to have MSDN either. See https://www.microsoft.com/en-us/Licensing/product-licensing/system-center-2012-r2.aspx. The FAQ pretty much covers all of the details. J From: <[email protected]<mailto:[email protected]>> on behalf of David McSpadden <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Friday, June 10, 2016 at 5:15 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [mssms] RE: OT: Licensing SCCM Distribution Points Here is what I received: (We are SCCM 2012R2 with 1 Primary Site and 25 DP’s (Not BDPs sorry for the misinformation) and we have Systems CALS in our Core CAL licensing already.) Good Afternoon David, Thanks again for your time today, it was a pleasure to speak with you. Please see the attached updated IFCU SAM baseline workbook. It has all the granular data we used to put together the assessment as well as the summary of gap analysis. In terms of actual gap – here’s what I have for now. The following are pending. A) System Center – the gap may go down if I can find any documentation which supports not licensing Distribution Points. I’ve spent the time since our call researching this and I haven’t found anything definitive within the Product Rights or Licensing guide that says this. I’m willing to dive deeper into it on Monday. B) MSDN – Some sort of MSDN needs to be purchased for the administration of your test machines because you don’t have actual developers. MSDN Platforms is probably the Edition that would suit you the best, but I will let you review and confirm. Here is a link that compares V studio 2015 offerings. https://www.visualstudio.com/en-us/products/compare-visual-studio-2015-products-vs.aspx Here is a summary of the current gaps: License Gaps Application Shortage notes Windows Server 2012 R2 Datacenter [per 2-processor] 3 Double checking System Center - re Distribution Points. Assuming all installs must be licensed - an alternate option is Qty 6 CIS Suite Datacenter and Qty 30 CIS Suite Standard Windows Server 2012 R2 Standard [per 2-processor] 2 System Center 2012 R2 Datacenter [per 2-processor] 3 System Center 2012 R2 Standard [per 2-processor] 41 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.
