Microsoft's Windows Server 2016, due in the third quarter of 2016, will be moving from per-processor to per-core pricing.

Microsoft plans to switch the licensing for next year's Windows Server 2016 to a per-processor-core basis, a move analysts said is at least partly a grab for money.

Windows Server 2016, not likely to arrive until the second half of next year, is going to shake up the way Microsoft licenses its server operating system, moving away from per socket licensing to ...

“With the virtual core licensing option, customers can elect to license Windows Server by the number of virtual cores they are using in virtual machines, making Windows Server easier to license ...

This example uses an 8-core server running SQL Server Enterprise Edition. PAYG billing has lower upfront cost. The point where core-based licensing provides a cost advantage over PAYG is after ...

The move to per-core licensing could increase the costs of Windows Server substantially and impact Software Assurance customers as well ...

Microsoft published a few licensing details this month about its forthcoming Windows Server 2016 and System Center 2016 products.

Hold onto your hats, everybody. Microsoft is simplifying Windows Server Licensing. Coming May 2017, Microsoft is introducing a new 16-pack of Core Licenses for Windows Server, System Center, CIS ...

Microsoft said last week that it will switch from a per-processor to a per-core licensing model when Windows Server 2016 Standard and Datacenter editions hit the market sometime next summer ...

Microsoft eases licensing terms for its Windows Server product lineup to pose greater competition to rivals. They are dropping certain restrictions to lower costs for customers and increase adoption.

Microsoft in its Windows Server 2016 Pricing and Licensing FAQ claims that the change to core based licensing is one of several steps that the company is taking to evolve its server licensing to ...

To license under Microsoft SQL Server Enterprise 2012 they would license it as 40 (4×10) core licenses. (See the note about “Software Assurance Implications” below).