Phone sales support +39 0575 05077
  Phone technical support +39 0575 0508
 
Private > 3 - Managing Microsoft Windows Server licenses > Managing Microsoft Windows Server licenses

3.1 Managing Microsoft Windows Server licenses

  For more technical and sales information on how to change the guaranteed computational resources for VMs with a Microsoft Windows Server 2016 license (and previous versions), please contact our team of experts.
Aruba Cloud changes the way Microsoft Windows Server 2016 licenses (and previous versions) are managed for the Private Cloud service. Payment for Windows licenses will no longer be subject to a direct request from the customer, but will be paid for by reducing the equivalent value of the purchased computational power (in GHz): this method will only be applied to VMs with a Windows license in operation.

For every GHz allocated to a VM with a Windows license for the vDC (virtual data center), there will be a reduction of the computational resources (in the vDC) equal to 0.7 GHz. Therefore, to have 1 GHz guaranteed on a VM with a Windows license, you need to have 0.7 GHz available to give for the cost of the license itself. Calculate how many GHz you need to ensure the vCPUs in the event of VMs with Microsoft Windows Server licenses using our calculator.

What has changed?

  • You no longer have to worry about requesting Windows instances.
  • You can manage the Windows licenses yourself.
  • The system automatically adjusts the computational power (in GHz) available based on the status of your VMs. As soon as you switch off the VMs with Microsoft Windows Server licenses, the system automatically re-credits the reduced GHz.
  • For customers who don’t have VMs with Windows licenses in the vDC, nothing changes.

Benefits

  • Reporting or informing the number of Microsoft Windows Server licenses is no longer necessary.
  • Microsoft Windows Server licenses will be counted only when VMs are turned on.
  • You will have no legal obligation to be in compliance with the payment of Microsoft Windows Server licenses, since the Aruba Cloud infrastructure will deal with this directly.
  • For customers who paid for Microsoft Windows Server licenses using the old process, the cost will be lower than before.
  • The system automatically adjusts the computational power (in GHz) available based on the status of your VMs. As soon as you switch off the VMs with Microsoft Windows Server licenses, the system automatically re-credits the reduced GHz. As such, Windows licenses will only be paid for in the event of actual use.
  • The Microsoft Windows Server 2016 operating system is available to all customers.

Examples

Find below some examples of how the calculation of guaranteed resources will change for vDCs in the case of VMs with a Microsoft Windows Server 2016 license (and previous versions):

16 GHz guaranteed for 6 Linux VMs (6 vCPUs) + 10 Windows VMs (10 vCPUs)

Resources to be guaranteed for the vDC: 16 GHz  
Resource guarantee per vCPU: 1 GHz  
vCPUs allocated to Linux VM: 6 vCPUs  
Resource guarantee for vCPUs allocated to Linux VM: 6 GHz [6 vCPUs x 1 GHz = 6 GHz]
vCPUs allocated to Windows VM: 10 vCPUs  
Resource guarantee for vCPUs allocated to Windows VM: 10 GHz [10 vCPUs x 1 GHz = 10 GHz]
Reduction of resources in GHz due to the costs of Windows licenses: 7 GHz [10 GHz x 0.7 = 7 GHz]
Resources necessary for the vDC to have 16 GHz guaranteed: 23 GHz [16 GHz + 7 GHz]

100 GHz guaranteed for 60 Linux VMs (60 vCPUs) + 40 Windows VMs (40 vCPUs)

Resources to be guaranteed for the vDC: 100 GHz  
Resource guarantee per vCPU: 1 GHz  
vCPUs allocated to Linux VM: 60 vCPUs  
Resource guarantee for vCPUs allocated to Linux VM: 60 GHz [60 vCPUs x 1 GHz = 60 GHz]
vCPUs allocated to Windows VM: 40 vCPUs  
Resource guarantee for vCPUs allocated to Windows VM: 40 GHz [40 vCPUs x 1 GHz = 40 GHz]
Reduction of resources in GHz due to the costs of Windows licenses: 28 GHz [40 GHz x 0.7 = 28 GHz]
Resources necessary for the vDC to have 100 GHz guaranteed: 128 GHz [100 GHz + 28 GHz]

Microsoft License Mobility

The Microsoft Licensing agreements do not allow for the use of personal Windows operating system licenses at cloud providers. "License portability" is only allowed for applications (and therefore only SQL, Sharepoint and Exchange) but not for the operating system. To use the specific operating system licenses (https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-license-mobility.aspx), users have to switch to the dedicated infrastructure service made available by Aruba Cloud. For more technical and sales information, please contact our team of experts.


Bookmark and Share