Centralized Licensing Management for Microsoft VDI
Tuesday, 14 December 2010 by Michel Roth

 This blog post introduces the new Centralized Licensing Management work, implemented in Windows Server 2008 R2 Service Pack 1 (SP1) as a part of the RemoteFX feature, for centrally managing the licensing configuration in a Microsoft Virtual Desktop Infrastructure (VDI) deployment.

 This post assumes that you have a basic understanding of the following:

  • Windows PowerShell
  • Various Remote Desktop Services role services
  • Remote Desktop Licensing
  • Microsoft VDI with Remote Desktop Services

What is Centralized Licensing Management?

Centralized Licensing Management is a new sub-feature that has been implemented in Windows Server 2008 R2 SP1, as a byproduct of RemoteFX work. It enables Microsoft VDI administrators to specify licensing configuration for the entire VDI deployment centrally from one place; that is, from the RD Connection Broker server.

Why is centralized licensing management required?

Until Windows Server 2008 R2, in a VDI deployment the RD Virtualization Host server was not aware of licensing settings because only the RD Session Host server participated in licensing and performed license validations for the client session/connection requests. But the new licensing model for Microsoft VDI (in Windows Server 2008 R2 SP1) requires that the Remote Desktop licensing mode and the list of Remote Desktop license servers must be specified in all RD Session Host servers (configured in VM redirection mode) as well as in all the RD Virtualization Host servers (with RemoteFX enabled), because the RD Virtualization Host servers can also participate in VDI licensing. Therefore, an option was provided for the admins to specify licensing configuration on the RD Connection Broker server. This would address the following concerns:

  1. Lack of a GUI interface for specifying a licensing configuration on an RD Virtualization Host server, which makes it difficult for VDI administrators to configure this on multiple RemoteFX-enabled RD Virtualization Host servers.
  2. Licensing mode mismatch across the RD Session Host server configured for VM redirection and RD Virtualization Host servers. (Licensing mode inconsistency across the deployment leads to license wastage and/or potential service denials.)

How does centralized licensing management work?

As a part of this feature, the licensing settings (Remote Desktop license type and the list of specified Remote Desktop license servers) can be specified on the RD Connection Broker server. This feature also provides an option to turn centralized licensing management ON or OFF (in case the VDI administrator decides to configure licensing separately on different servers).

Source:  http://blogs.msdn.com/b/rds/archive/2010/12/05/centralized-licensing-management-for-microsoft-vdi.aspx


Related Items:

Control the Issuance of RDS CALs (18 September 2009)
Terminal Services Licensing Diagnosis (3 December 2007)
Remote Desktop Connection Broker (Part Two) (19 October 2009)
Windows 2008 R2 Remote Desktop Services (7 December 2009)
Terminal Server Licensing Diagnosis In Windows Server 2008, Part 2 (21 December 2007)
What’s New In Terminal Services Licensing For Longhorn? (Part 4) (24 April 2007)
Brian Madden Paper On "New" Citrix Licensing (Part 1 Of 2) (9 February 2005)
Microsoft to revise VECD licensing in 2010 (28 January 2010)
A Pretty Complete Online Guide to Terminal Services (5 November 2009)
Terminal Server Licensing/Gateway WMI Providers (18 September 2006)
Comments (0)