Not Everything is Good About Windows Server 2016
Microsoft is the latest among the big companies to plan their server licensing policy as per cloud requirements. The software giant is all set to unveil its Windows Server 2016 and there are a lot of talks going on about what this means to its clients.
Like the older versions, Windows Server 2016 will require the purchase of both the client-side and server-side licenses. The client-side licenses or Client Access Licenses (CALs) give end-user devices the right to access servers, while the Server-side licenses give organizations the right to run the software on a physical server.
The difference between the older versions and the Window Server 2016 is that, although the CALs will remain the same, the licensing of client side server will change, moving from processor based licensing to core based licensing.
According to Microsoft, “Core based licensing provides a more consistent licensing metric regardless of where the solution is deployed on-premises or in a cloud.”
In the case of Windows Server 2016, each processor will be licensed with a minimum of 8 cores and each physical server will be required to be licensed with at least 2 processors (a minimum of 16 cores). The core licenses will be sold in packs of two.
Microsoft has opted for such a change in order to support Hybrid cloud. The move also aligns the servers to a common licensing denomination that is a standard measure for capacity across different environments. Although this new Server and its capabilities with the cloud seems intriguing to customers, there are a few underlying issues, which are more worrying, particularly to the big businesses.
One of the main issues in switching from a per-processor licensing model to a per-core licensing model is that, in the latter, the licensing compliance becomes very complex.
In previous models, the number of cores fitted to a processor was irrelevant in calculating the licensing requirement. In The new licensing rules, that has been changed. The number of cores used is now the central aspect of licensing. The total licensing requirement is now based on the number of cores per processor.
The licensing cost of two cores would be 1/8th of the old licensing fee. And this is okay for normal machines with 2 processors (at 8 cores each) as there is no change in cost in comparison to the old licensing policy. But in case of high process machines, the users will have to pay extra. Especially businesses in the process of switching to systems with higher core count will be hit with heavier costs as the licensing model changes.
With the new shifts, companies will need a minimum license of eight cores per processor and 16 cores per server. Companies with Windows servers under software Assurance (SA) licensing can renew their coverage under the recently announced per-core licensing model when their existing coverage expires.
On the other hand, clients with Enterprise Agreement (EA) can continue to acquire the processor based licensing as the agreement lasts up to three years. But eventually even they will have to cash in on the new licenses when the old one expires.
The problem with the new licensing policy is that, users can easily go wrong while calculating for the number of cores. So it is better to have an inventory of the cores or risk an audit from Microsoft in case of under licensing. Software Access Management (SAM) tools come in handy here as they can assemble inventory data rather quickly.
To conclude it, the Windows Server 2016 might as well be the next big thing from Microsoft, with its huge Hybrid Cloud capabilities. But it has a few, serious drawbacks as well which companies might want to look into before abandoning their Server 2012 R2 for the latest Server 2016.
By Chris Tjotjos, VP, Cisco Solutions Practice, Black Box...
By Laura Jackson, Sr. Manager-Risk Management, ABS Consulting
By Jason Cradit, VP of Information Systems, Willbros Group
By Steve Garske, Ph.D., Senior Vice President & Chief...
By Roman Trakhtenberg, CEO, Luxoft
By Renee P Wynn, CIO, NASA
By Mike Morris, CIO, Legends
By Louis Carr, Jr., CIO, Clark County
By Andrew Macaulay, CTO, Topgolf Entertainment Group
By Dominic Casserley, President and Deputy CEO, Willis...
By Dave Nelson, SVP-Portfolio Lead, Avanade, Inc.
By Michael Cross, SVP & CIO, CommScope Holding Company Inc.
By Pauly Comtois, VP DevOps, Hearst Business Media
By Dan Adam, CIO, Extreme Networks
By Matt Schlabig, CIO, Worthington Industries
By David Tamayo, CIO, DCS Corporation
By Scott Cardenas, CIO, City and County of Denver
By Marc Kermisch, VP & CIO, Red Wing Shoe Co.
By Brian Drozdowicz, VP, Digital Services, Siemens...
By Les Ottolenghi, EVP and CIO, Caesars Entertainment