Is available through event logs and network tracing. This article is to document the RDP connection and licensing sequence that takes place for the most common RDP connection scenarios. 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.In supporting RDS, the two most common issues are the connection / reconnection process and licensing. This way, you'll not get a prompt to enter your credentials when you'll open RDS host configuration snap-ins in trusted domains/forests. You can do it through RDS host configuration snap-in or through a group policy.Īdd administrators group of each domain/forest in the local administrators of RDS licensing server. To restrict the issuance of RDS CALs, you can add RDS Host Servers into Terminal Server Computers group on RDS licensing servers.Ĭonfigure RDS licensing server on all RDS Host Servers in each domain/forest. 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. If you have any questions about the ports that need to be opened, see Service overview and network port requirements for Windows. It can be either Forest Trust or External Trust.Īll the required ports should be opened on the firewall. There should be a two-way trust between these domains/forests. In this kind of scenario, you should consider the following points: RDS Host Servers are in one domain/forest and RDS licensing server is in another domain/forest 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). To restrict the issuance of RDS CALs, you can add RDS Host Servers into Terminal Server Computers group on RDS licensing server and then enable the License server security group policy setting on RDS licensing server. 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. The computer account for the license server must be a member of the Terminal Server License Servers group in AD DS. You can install both (Per Device and Per User) CALs on RDS licensing server. Consider the following points while configuring RDS environment in a domain scenario: In an Active Directory Domain scenario, we can have RDS Host and RDS licensing servers either on the same server or different servers. RDS Host and RDS licensing servers are in the same domain For more information, see Specify a License Server for an RD Session Host Server to Use. 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. In Windows 2008 R2, automatic license server discovery is no longer supported for RD Session Host servers. If you install RDS licensing server on a different server in the work group, ensure that the RDS server is able to access RDS licensing server.RDS Host and RDS licensing server roles can both be installed on the same server.Per User CAL tracking and reporting is not supported in work group mode.So, you should install only Per Device CALs on RDS licensing server. We can use ONLY Per Device CALs in a work group environment.RDS Host and RDS licensing servers are in the same work groupĬonsider the following points while configuring RDS and RDS licensing servers in a work group environment: Here is more information on these scenarios:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |