Volume Activation for VDI Scenarios

  • Article

Applies To: Windows 8.1

For a Virtual Desktop Infrastructure (VDI) deployment in education you can use Active Directory-Based Activation (ADBA) and Key Management Service (KMS) for license activation of your VMs.

You must provide Windows 8.1 license activation for the VMs used in VDI scenarios. The following is a list of the Microsoft Volume Activation technologies available for Windows 8.1 and a brief description of each:

  • Active Directory-Based Activation (ADBA). ADBA is a role service that allows you to use AD DS to store activation objects, which can further simplify the task of maintaining Volume Activation services for a network. With ADBA, no additional host server is needed, and activation requests are processed during computer startup. ADBA works only for domain-joined devices running Windows 8.1.

  • Key Management Service (KMS). The KMS role service allows organizations to activate systems within their network from a server on which a KMS host has been installed. With KMS, you can complete activations on your local network, eliminating the need for individual computers to connect to Microsoft for product activation. KMS does not require a dedicated system, and it can be cohosted on a system that provides other services. By default, volume editions of Windows 8.1 connect to a system that hosts the KMS service to request activation. No action is required from the user.

Note

For information about licensing the clients used to access your VDI, see the Client Licensing for VDI section in this guide.

Table 8 lists the Volume Activation technologies and the information necessary for selecting the appropriate technologies for your institution. You can use any combination of these technologies to design a complete Volume Activation solution.

Note

Although you can perform Volume Activation by using Multiple Activation Keys (MAKs), Microsoft does not recommend MAKs for VDI because they cannot be dynamically applied to VMs based on VDI demands. Use ADBA or KMS, instead.

Table 8. Volume Activation Technology Selection

  ADBA KMS

Domain joined

Yes

Yes

Devices must connect to the network at least once every 180 days

Yes

Yes

Supports Volume Activation of Microsoft Office

Yes (Microsoft Office 2013 only, not Microsoft Office 365 or previous versions of Office)

Yes

Requires Volume Activation services in Windows Server 2012 R2

Yes

No

Microsoft Volume Licensing information is stored in AD DS

Yes

No

Infrastructure

AD DS

  • AD DS

  • KMS Server

ADBA and KMS are both role services in the Volume Activation Services server role in Windows Server 2012 R2. KMS is also available in prior versions of Windows Server. You can use Server Manager or Windows PowerShell cmdlets to install and configure these role services.

You can centrally manage Windows, Office, and other Microsoft products’ volume and retail activation processes by using the Volume Activation Management Tool (VAMT), which is included in the Windows Assessment and Deployment Kit.

Note

You can use the same Volume Activation infrastructure to manage VDI activation and activation for your other Windows 8.1, Windows 7, Windows Server 2012 R2, and Windows Server 2008 R2 operating systems.

Additional resources

See also