![]() Specify a license server, and then select Add. If you use workgroup servers for your RDS deployment, you have to use Per Device CALs In that case, Per User CALs are not permitted. If you use domain-joined servers for your RDS deployment, you can use both Per User and Per Device CALs. Select the Remote Desktop licensing mode (either Per User or Per Device, as appropriate for your deployment). :::image type="content" source="media/cannot-connect-rds-no-license-server/server-manager-rd-config.png" alt-text="Select the Edit Deployment Properties option to open the Remote Desktop licensing settings in Server Manager."::: In Server Manager, select Remote Desktop Services > Overview > Edit Deployment Properties > RD Licensing. ![]() On the RD Connection Broker computer, open Server Manager. Configure licensing for an RDS deployment that includes only the Remote Desktop Session Host (RD Session Host) role and the RD Licensing role.Ĭonfigure licensing for an RDS deployment that includes the RD Connection Broker role.Configure licensing for an RDS deployment that includes the Remote Desktop Connection Broker (RD Connection Broker) role.The details of the configuration depend on the type of deployment that you have: The RDS deployment uses the correct license server, licensing mode, and policy settings. :::image type="content" source="media/cannot-connect-rds-no-license-server/rd-licensing-manager-config.png" alt-text="RD Licensing Manager, showing a correctly configured license server."::: There should be a green check mark beside the license server name, and the numbers in the columns should reflect the numbers of total and available licenses. The configuration of the licenses should resemble the following screenshot. The license server has a client access license (CAL) for each user and device that can connect to RDS.įor more information about this configuration, see Install RDS client access licenses on the Remote Desktop license server. The RD Licensing role is installed and the license server is activated.įor more information about this configuration, see Activate the Remote Desktop Services license server. You can check the RD Licensing configuration by using Server Manager and RD Licensing Manager. In this case, refresh the X509 Certificate registry keys. After making sure that you are signed in to the network, try connecting to the server again. Such problems tend to be associated with user messages, such as the following:īecause of a security error, the client could not connect to the Terminal server. If the RD License Diagnoser lists other problems, such as "The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client", there may be a problem that affects the license certificates. In this case, check the RD Licensing configuration. The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.The remote session was disconnected because there are no Remote Desktop client access licenses available for this computer. ![]() These issue could be caused by the following user messages: This could be caused by network connectivity problems, the Remote Desktop Licensing service is stopped on the license server, or RD Licensing isn't available.
0 Comments
Leave a Reply. |