September 2016 Hosting and Cloud Newsletter

This useful newsletter has three items of licensing interest this month – let’s take a look.

First of all there’s confirmation that Windows Server 2016 and System Center 2016 will be available in October 2016, with Service Providers being able to download the products from 17 October. The licensing model changes to Core licences and there’s a requirement for a minimum of 8 Core licences per processor. The virtualisation rules are pretty much the same as for 2012 R2: license all the cores with Datacenter edition for unlimited virtualisation, and license all cores with Standard edition for the rights to run a single VM.

Then there’s confirmation that Windows 10 Enterprise E3 is available in the CSP program from 1 September 2016. Licensed users may install the software on up to 5 devices but they will not have access to any virtualisation rights or Software Assurance benefits. Note that qualifying licences of Windows 10 Pro and above are required.

And finally, you’ll want to put 29 September in your diary for the quarterly licensing briefing from the Microsoft SPLA team. The agenda is set to cover the detail of licensing Windows 10 Enterprise E3 through CSP, and Windows Server and System Center 2016 through SPLA. Register for the Cloud Channel Network to attend: or, if you’re already a member, add the event to your calendar here:

Sign up for this free monthly newsletter here:

Windows Server and System Center 2016 Licensing FAQ

There’s an updated (May 2016) Licensing FAQ for Windows Server and System Center 2016. The last version published by Microsoft was in December 2015 and there are some interesting new things documented that are worth a look.

First of all, there’s some further information about how the transition from Processor-based to Core licences will work: essentially it won’t affect SA customers until renewal, at which point there will be grants of a minimum of 16 Core licences for each Processor-based licence. If customers need more Core licences to cover their existing hardware, then they need to inventory their environment and the additional licences will be granted. See page 3 for details.

There’s also an example on pages 3 and 4 of how an existing Enterprise Agreement customer would proceed with trueing up more Datacenter licences after the launch of Windows Server 2016. You’ll need to read the detail, but essentially it’s all dependent on the renewal date of the agreement. Along similar lines, there’s a new question on page 6 which details that early commitment for a renewal is an option if a customer wants to lock in Processor-based licences for a further agreement term.

And finally, page 6 gives us some more detail on the editions that we can expect. First of all, we learn that Windows Server Foundation and Essential editions will be merged into a single product – Windows Server 2016 Essentials, and that its licensing will continue to be processor-based. Then there will just be a single product for MultiPoint Server – Windows Server 2016 MultiPoint Premium Server, which will be available through Academic Licensing Programs only and not through Open, OEM or retail channels. Interestingly, if required, corporate customers can use the MultiPoint Premium Server role that will be available in Standard and Datacenter editions as long as they also acquire non-Academic Windows Server and RDS CALs.

As usual, find this guide along with all of its Licensing Guide friends here:

Microsoft Hosting and CSP Newsletter

The December 2015 Hosting and Cloud Service Provider newsletter is out.

It’s got links to recent topics of interest in the hosting world: the launch of E5, licensing changes for Windows Server and System Center 2016, and the changes to Licence Mobility for SA rights which allow customers to fail-over to shared hardware.

There are also links to useful CSP resources and the next quarterly licensing webcast on 20 January, 2016.

Sign up for this free newsletter here:

System Center 2016 Licensing Guide

There’s a new System Center 2016 Licensing Guide from Microsoft.

It confirms that the licensing model will be the same as Windows Server 2016, so it’s gone to Core licensing with a minimum of 8 Core licences for each physical processor and a minimum of 16 Core licences for each server.

Read the guide to find out comparative pricing information and what organisations should do at SA renewal when they come to convert from Processor to Core licences.

You can find it here amongst the other Microsoft Licensing Guides we’ve gathered together:

Windows Server 2016 and System Center 2016 Pricing and Licensing FAQ

There’s a December 2015 Pricing and Licensing FAQ for Windows Server and System Center which gives some more detail on the upcoming 2016 versions of these products. Here are the new and interesting things revealed:

Windows Server

  • Windows Server 2016 is licensed by physical cores, therefore using hyper-threading does not change the Core licences required
  • If processors are disabled for use by Windows then the cores on that processor do not need to be licensed
  • Windows Server 2016 supports nested virtualisation – a VM running inside a VM – which counts as two virtual machines from a licensing perspective
  • There will be an External Connector licence for Windows Server 2016
  • Nano Server is a deployment option within Windows Server 2016 and requires no further licences


Azure hybrid-use benefit

  • Anticipated to be available in the first quarter of 2016
  • Customers with Windows Server with SA can use Windows Server images in non-Windows VMs in Azure
  • Each Windows Server 2012 R2 Processor licence allows customers to run 2 instances on up to 8 cores each, or 1 instance on up to 16 cores
  • When the benefit is used with a Standard edition licence, that licence may no longer be assigned to another server, but Datacenter licences can continue to be used for unlimited virtualisation in an on-premises deployment


System Center

  • System Center 2016 will also move to the Core licensing model
  • The Core Infrastructure Server Suite will also be licensed with Core licences


Find this jolly useful FAQ here: – look in the Core Infrastructure section.