大网数据广告活动
远程桌面与会话

Set up RD licensing across domains forests or workgroups

· 52CE 我爱测

This article talks about the questions around the supportability (or recommended approach) of setting up Remote Desktop (RD) licensing across domain, forest, or work groups.

This article provides information on the questions around the supportability (or recommended approach) of setting up Remote Desktop (RD) licensing across domain, forest, or work groups.

Original KB number:   2473823

Note: In Windows Server 2008 R2, Terminal Services is renamed to Remote Desktop Services (RDS).

Question

Can the RD licensing server issue a Client Access License (CAL) to users or devices connecting to RD Session Host (Terminal Server) servers under any of the following conditions?

  • RD Session Host servers are in an Active Directory Domain and RD licensing server is in a work group environment.
  • RD Session Host servers are in a work group and the RD licensing server in an Active Directory Domain.
  • RD Session Host servers and RD licensing server are in different forests. No trusts exist (One-way or Two-way trust) between these forests.
  • RD Session Host servers and RD licensing servers are in the same work group.

Answer

For both Per Device and Per User CALs issuance to work, the RD Session Host and RD licensing server in any one of the following three configurations:

  • Both in the same work group
  • Both in the same domain
  • Both in the trusted (Two-way trust) Active Directory Domains or Forest

Here is more information on these scenarios:

  • RD Session Host and RD licensing servers are in the same work group

    Consider the following points while configuring RDS and RD licensing servers in a work group environment:

    • We can use ONLY Per Device CALs in a work group environment. So, you should install only Per Device CALs on RD licensing server.
    • Per User CAL tracking and reporting is not supported in work group mode.
    • RD Session Host and RD licensing server roles can both be installed on the same server.
    • If you install RD licensing server on a different server in the work group, ensure that the RDS server is able to access RD licensing server.

    In Windows 2008 R2, automatic license server discovery is no longer supported for RD Session Host servers. You must specify the name of a license server for the RD Session Host server to use by using Remote Desktop Session Host Configuration snap-in. For more information, see Specify a License Server for an RD Session Host Server to Use.

  • RD Session Host and RD licensing servers are in the same domain

    In an Active Directory Domain scenario, we can have RD Session Host and RD licensing servers either on the same server or different servers. Consider the following points while configuring RDS environment in a domain scenario:

    • You can install both (Per Device and Per User) CALs on RD licensing server.

    • The computer account for the license server must be a member of the Terminal Server License Servers group in AD DS. If the license server is installed on a domain controller, the Network Service account must also be a member of the Terminal Server License Servers group.

    • To restrict the issuance of RDS CALs, you can add RD Session Host servers into Terminal Server Computers group on RD licensing server and then enable the License server security group policy setting on the RD licensing server.

    • The License server security group policy setting is located in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote \RD licensing and can be configured by using either the Local Group Policy Editor or the Group Console (GPMC).

  • RD Session Host servers are in one domain/forest and RD licensing server is in another domain/forest

    In this kind of scenario, you should consider the following points:

    • There should be a two-way trust between these domains/forests. It can be either Forest Trust or External Trust.

    • All the required ports should be opened on the firewall. If you have any questions about the ports that need to be opened, see Service overview and network port requirements for Windows.

    • To issue RDS Per User CALs to users in other domains, there must be a two-way trust between the domains, and the license server must be a member of the Terminal Server License Servers group in those domains.

    • To restrict the issuance of RDS CALs, you can add RD Session Host servers into Terminal Server Computers group on RD licensing servers.

    • Configure RD licensing server on all RD Session Host servers in each domain/forest. You can do it through a group policy.

    • Add administrators group of each domain/forest in the local administrators of RD licensing server. This way, you'll not get a prompt to enter your credentials when you'll open RD Session Host configuration snap-ins in trusted domains/forests.

Data collection

If you need assistance from Microsoft support, we recommend you collect the information by following the steps mentioned in Gather information by using TSS for User Experience issues.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。