FNMS - Windows Server and SQL Server Optimization reports (on Premise)
- Author: Nicolas Rousseau
- Author Email Address: firstname.lastname@example.org
- Solution Type: Custom Report
- Flexera Product & Version: FlexNet Manager 2016-2020R1
- Environment: On Premise Only
- Development Effort (Days): 2
- Implementation Effort (Days): 0.1
SOLUTIONS ARE PROVIDED ON AN "AS IS" BASIS. NEITHER FLEXERA NOR ITS SUPPLIERS MAKE ANY WARRANTIES, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. LICENSEE MAY HAVE OTHER STATUTORY RIGHTS. HOWEVER, TO THE FULL EXTENT PERMITTED BY LAW, THE DURATION OF STATUTORILY REQUIRED WARRANTIES, IF ANY, WILL BE LIMITED TO THE SHORTER OF (I) THE STATUTORILY REQUIRED PERIOD OR (II) THIRTY (30) DAYS FROM LICENSEE’S ACCEPTANCE OF THE AGREEMENT.
This document gives the details for two Microsoft Optimization reports, that allow to analyze the optimal licenses for virtualized environments (ESX servers and virtual machines) for Windows and SQL Server.
Indeed, Windows Server and SQL Server have complex licensing rules such environments. Depending on the infrastructure (particularly, the number of virtual machines per host), the use of an edition or another will be financially optimal.
This document is intended to SAM Managers that will use these optimization reports for their true ups for instance and FlexNet Manager admins that will be able to implement the code for the reports.
Business need and approach
Licensing Windows Server and SQL Server on ever changing virtualized infrastructures is a challenge.
Microsoft give a poisonous choice to license Windows Server:
- Pay more and cover the ESX servers for an unlimited number of VMs with Windows Server Data Center Edition
- Or cover the ESX with Windows Server Standard with a complicated licensing rule, proportional with the number of hosted VMs and a “mobility” rule that stipulates: “A license cannot be reused for 90 days on another host”.
This rule is very hard to apply, the calculations are complex… customers chose the safe but expensive (in USD millions) way of licensing all ESX server with Windows Server DataCenter!
A second complexity for Windows Server is that a bundle license (Microsoft Core Infrastructure Server (DataCenter or Standard Edition)) allows to license Windows Server (DataCenter or Standard Edition) and SCCM (all System Center agents).
For SQL Server, like for Windows server, there is a great temptation to cover virtualized environments with SQL Server Enterprise that can cover an unlimited number of VMs installed with SQL Server in any edition, while each VM must be licensed with Standard Edition. Contrarily to Windows Server, If SQL is covered by Software Assurance, you can license the “snapshot” position. No mobility rule exists for SQL server.
When they do not license all ESX servers’ cores with Enterprise Edition (Highly expensive approach), SAM Managers can spend hours in Excel for basic optimization (one complexity being the mix of SQL server Standard and Enterprise on the same hosts) before Microsoft true ups…
The two reports provided below will compute optimal license to choose on each ESX server and evaluate the saving FNMS allows, taking the assumption that without the report, SAM Managers would license all ESX servers with SQL Server Enterprise or Windows Server Data Center edition.
An extension of the reports is to use an allocation script (a sample is provided for Windows Server), that will allocate the hosts and the VMs to the optimal license, every morning, as a step in the custom Inventory
Microsoft - Windows Server Consumption and Optimization (NR)
Microsoft - SQL Server Consumption and Optimization (NR)