Monday, April 25, 2011
License Server Assignment and Activation
Licensing:
The Remote Desktop Services role and its role services are included as part of the standard
Windows Server license and do not require any additional licenses. The RD Session Host
license is also covered by the Windows Server license with the same considerations as any
other Hyper-V host.
Each user or device that directly or indirectly accesses a computer running Windows
Server to interact with a remote graphical user interface (using the Windows Server 2008 R2
RDS functionality or other technology) must have a Windows Server 2008 RDS Client Access
License (CAL) in addition to the Windows Server CAL. RDS functionality is considered those
features or services that are enabled with the RDS role and/or role service(s) in Windows
Server 2008 R2. This includes, but is not limited to, RD Gateway, RemoteApp, RD Web Access,
and RD Connection Broker.
RDS CALs are available as Per User or Per Device CALs. RD Session Host servers are configured
for Per Device or Per User mode, and require an appropriate RDS CAL for access.
Licensing
Each Per Device RDS CAL allows one device to connect to the RDS resources, regardless
of how many users use the device. Conversely, a Per User RDS CAL allows a single user access
to the RDS resources from as many devices as he or she happens to have. Companies should
carefully consider their users and the type of devices and access they need to RDS resources
before purchasing CALs and deciding what mode RD Session Host servers will use.
Windows Server 2008 R2 RDS CALs and Windows Server 2008 TS CALs are equivalent and
can be used interchangeably. However, RDS CALs can only be managed from Windows Server
2008 SP2 Terminal Server License servers or Windows Server 2008 R2 RD License servers. The
RD Licensing Manager, shown in Figure 4-13, adds important new capabilities, including the
ability to automatically migrate licenses and dynamically activate or deactivate license servers.
Figure 4-13 The RD Licensing Manager
License Server Assignment and Activation
Windows Server 2008 R2 changes how RDS Session Hosts locate and connect to license servers.
In Windows Server 2008, Terminal Servers used a discovery mechanism to find and connect
to a license server. This created problems if the license server was unavailable, or if the
discovery process encountered problems, and it became the source of a significant number of
support calls. In Windows Server 2008 R2, this is changed so that RD Session Hosts explicitly
specify the RD License servers they will connect to, as shown in Figure 4-14, and when a specific
license server is unavailable, licenses are automatically migrated.
and VDI: Centralizing Desktop
and Application Management
Figure 4-14 The RD Licensing Server is specified in the RD Session Host Configuration console.
When an RD Session Host is initially installed, it has a 120-day grace period before a
license server needs to be specified. If no license server is specified and available at the end
of that grace period, the RD Session Host will stop accepting connections. This grace period
cannot be reset and is not an “evaluation” or “temporary” license.
Virtual Desktop Licensing:
Complete and correct licensing of a Microsoft VDI environment requires licensing of both the
Windows client operating system running in a centralized location and the infrastructure and
management components that enable an end-to-end VDI environment.
Virtual Enterprise Centralized Desktop (VECD) is the license for Windows as a guest operating
system in the data center. VECD is available for client devices that are covered by Software
Assurance (VECD for SA), and those that are not, including devices such as thin clients. VECD
or VECD for SA is required for any VDI environment running Windows as the guest operating
system.
Most VDI environments also include management components such as System Center
Virtual Machine Manager (SCVMM) or System Center Operations Manager to manage the
environment. For licensing the infrastructure and management components of a Microsoft
VDI environment, there are essentially two options: You can license the infrastructure components
(RD Session Host, RD Virtualization Host, RD Connection Broker, etc.) with RDS CALs
and license the management components separately; or, if you’re a Volume License customer,
you have a pair of new options—the Microsoft Virtual Desktop Infrastructure Standard Suite
and the Microsoft Virtual Desktop Infrastructure Premium Suite. These two suites combine
the products for an optimum VDI experience in a value package.
1. Microsoft Virtual Desktop Infrastructure Standard Suite (VDI Standard
Suite) Includes the core products and CALs required to enable and manage VDI,
including:
• Remote Desktop Services (RDS) The RDS component of the VDI Suite is
licensed solely for use in a VDI context; it does not provide a license to use sessionbased
RDS resources.
• Microsoft Desktop Optimization Pack (MDOP) This is a collection of technologies
that enable desktop virtualization and management, including App-V.
• System Center Virtual Machine Manager (SCVMM) Client Management
License This provides centralized management of the Microsoft® Hyper-V™-
based virtualization components of the VDI host.
• System Center Configuration Manager Standard Server Management
License This provides centralized configuration management of the (physical) VDI
hosts of the VDI Suite.
• System Center Operations Manager Standard Server Management
License This provides centralized monitoring and performance management of
the physical VDI host of the VDI Suite.
n Microsoft Virtual Desktop Infrastructure Premium Suite (VDI Premium
Suite) Includes all the components of the VDI Standard Suite, plus the following:
• App-V for RDS This provides application-level virtualization for RDS sessions.
• RDS The RDS license is not use restricted to the VDI scenario only, but can also be
used for session-based desktop and applications scenarios.
Note T he System Center components of the VDI Suites are only licensed for use in a VDI
scenario, and can’t be used for general management of virtualization hosts with mixed
workloads.
The Remote Desktop Services role and its role services are included as part of the standard
Windows Server license and do not require any additional licenses. The RD Session Host
license is also covered by the Windows Server license with the same considerations as any
other Hyper-V host.
Each user or device that directly or indirectly accesses a computer running Windows
Server to interact with a remote graphical user interface (using the Windows Server 2008 R2
RDS functionality or other technology) must have a Windows Server 2008 RDS Client Access
License (CAL) in addition to the Windows Server CAL. RDS functionality is considered those
features or services that are enabled with the RDS role and/or role service(s) in Windows
Server 2008 R2. This includes, but is not limited to, RD Gateway, RemoteApp, RD Web Access,
and RD Connection Broker.
RDS CALs are available as Per User or Per Device CALs. RD Session Host servers are configured
for Per Device or Per User mode, and require an appropriate RDS CAL for access.
Licensing
Each Per Device RDS CAL allows one device to connect to the RDS resources, regardless
of how many users use the device. Conversely, a Per User RDS CAL allows a single user access
to the RDS resources from as many devices as he or she happens to have. Companies should
carefully consider their users and the type of devices and access they need to RDS resources
before purchasing CALs and deciding what mode RD Session Host servers will use.
Windows Server 2008 R2 RDS CALs and Windows Server 2008 TS CALs are equivalent and
can be used interchangeably. However, RDS CALs can only be managed from Windows Server
2008 SP2 Terminal Server License servers or Windows Server 2008 R2 RD License servers. The
RD Licensing Manager, shown in Figure 4-13, adds important new capabilities, including the
ability to automatically migrate licenses and dynamically activate or deactivate license servers.
Figure 4-13 The RD Licensing Manager
License Server Assignment and Activation
Windows Server 2008 R2 changes how RDS Session Hosts locate and connect to license servers.
In Windows Server 2008, Terminal Servers used a discovery mechanism to find and connect
to a license server. This created problems if the license server was unavailable, or if the
discovery process encountered problems, and it became the source of a significant number of
support calls. In Windows Server 2008 R2, this is changed so that RD Session Hosts explicitly
specify the RD License servers they will connect to, as shown in Figure 4-14, and when a specific
license server is unavailable, licenses are automatically migrated.
and VDI: Centralizing Desktop
and Application Management
Figure 4-14 The RD Licensing Server is specified in the RD Session Host Configuration console.
When an RD Session Host is initially installed, it has a 120-day grace period before a
license server needs to be specified. If no license server is specified and available at the end
of that grace period, the RD Session Host will stop accepting connections. This grace period
cannot be reset and is not an “evaluation” or “temporary” license.
Virtual Desktop Licensing:
Complete and correct licensing of a Microsoft VDI environment requires licensing of both the
Windows client operating system running in a centralized location and the infrastructure and
management components that enable an end-to-end VDI environment.
Virtual Enterprise Centralized Desktop (VECD) is the license for Windows as a guest operating
system in the data center. VECD is available for client devices that are covered by Software
Assurance (VECD for SA), and those that are not, including devices such as thin clients. VECD
or VECD for SA is required for any VDI environment running Windows as the guest operating
system.
Most VDI environments also include management components such as System Center
Virtual Machine Manager (SCVMM) or System Center Operations Manager to manage the
environment. For licensing the infrastructure and management components of a Microsoft
VDI environment, there are essentially two options: You can license the infrastructure components
(RD Session Host, RD Virtualization Host, RD Connection Broker, etc.) with RDS CALs
and license the management components separately; or, if you’re a Volume License customer,
you have a pair of new options—the Microsoft Virtual Desktop Infrastructure Standard Suite
and the Microsoft Virtual Desktop Infrastructure Premium Suite. These two suites combine
the products for an optimum VDI experience in a value package.
1. Microsoft Virtual Desktop Infrastructure Standard Suite (VDI Standard
Suite) Includes the core products and CALs required to enable and manage VDI,
including:
• Remote Desktop Services (RDS) The RDS component of the VDI Suite is
licensed solely for use in a VDI context; it does not provide a license to use sessionbased
RDS resources.
• Microsoft Desktop Optimization Pack (MDOP) This is a collection of technologies
that enable desktop virtualization and management, including App-V.
• System Center Virtual Machine Manager (SCVMM) Client Management
License This provides centralized management of the Microsoft® Hyper-V™-
based virtualization components of the VDI host.
• System Center Configuration Manager Standard Server Management
License This provides centralized configuration management of the (physical) VDI
hosts of the VDI Suite.
• System Center Operations Manager Standard Server Management
License This provides centralized monitoring and performance management of
the physical VDI host of the VDI Suite.
n Microsoft Virtual Desktop Infrastructure Premium Suite (VDI Premium
Suite) Includes all the components of the VDI Standard Suite, plus the following:
• App-V for RDS This provides application-level virtualization for RDS sessions.
• RDS The RDS license is not use restricted to the VDI scenario only, but can also be
used for session-based desktop and applications scenarios.
Note T he System Center components of the VDI Suites are only licensed for use in a VDI
scenario, and can’t be used for general management of virtualization hosts with mixed
workloads.
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment