The "remote session is disconnected because there is no available remote desktop authorization server" problem is usually caused by a misconfiguration or insufficient license. The solution is as follows: 1. Install and activate the RD authorization role and purchase and install the appropriate CAL license; 2. Check whether the authorization mode is set to "per-device" or "per-user" to ensure that it is consistent with the license type; 3. Ensure that the authorization server is in the same domain as the RDS server and the network is communicating normally; 4. The problem can be temporarily alleviated by resetting the trial period, but it cannot replace the formal authorization; if used in a multi-user office scenario, the complete RDS authorization architecture must be deployed.

You encounter the problem of "the remote session is disconnected because there is no remote desktop authorization server available", usually because the Remote Desktop Service (RDS) authorization is incorrectly configured or insufficient authorization. Below are some common situations and solutions for your reference.

What is a remote desktop authorization server?

Remote Desktop Services (RDS) provides only two concurrent administrator connections on Windows Server. If you are using remote desktop for management, these two connections are basically enough; but if you are used for multi-person office, terminal services and other scenarios, you need to deploy a remote desktop authorization server (RD Licensing Server) to issue a formal license.

If the authorization server is not set up, the user will be forced to disconnect after logging in for a period of time and prompt "No authorization server is available".

Common causes and solutions

? No authorized server installed or activated

• If your server is an RDS environment for multi-user access, the RD authorization role must be installed and activated separately.
• The installation steps are roughly as follows:
  • Open Server Manager
  • Add roles and features
  • Select Remote Desktop Services in Roles
  • Check "Remote Desktop Authorization" in "Function"
• After the installation is complete, you also need to purchase the appropriate CAL (Client Access License) through Microsoft and then install these licenses on the authorized server.

? Authorization mode setting error

• Remote desktop servers support two authorization modes: Per Device and Per User.
• If you have installed the authorization server but still report an error, it may be that the authorization mode is not paired.
• You can check it through the following path:
  • Remote Desktop Session Host Configuration Tool
  • Check if the Authorization section correctly points to the Authorization Server
  • And make sure that the authorization model is consistent with the license type you purchased

? Authorized server cannot communicate

• If the authorized server is installed but the remote desktop server cannot find it, it may be due to a network problem or the service is not running.
• make sure:
  • The authorization server and the RDS server are in the same domain or trust relationship
  • Network ports (such as TCP 135, RPC-related ports) are not intercepted by the firewall
  • You can see the correct server status in the "Remote Desktop Authorization Manager"

Temporary solution: Extend the trial period

Windows Server provides a 120-day trial period by default, during which you can temporarily use Remote Desktop without formal authorization. If you are just testing the environment or using it temporarily, you can mitigate by resetting the trial period:

1. Open a command prompt (administrator)
2. Enter gpedit.msc to open the Group Policy Editor
3. Navigate to: Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Authorization
4. Enable "Use specified Remote Desktop Authorization Mode" and set to "Per Device" or "Per User"
5. After restarting the server, you can reset the trial cycle (up to several times)

?? Note: This is just a stopgap measure and cannot replace formal authorization.

How to determine whether an authorized server needs to be deployed?

• If you only have a few users who occasionally log in to the server to maintain it, you generally do not need to deploy an additional authorized server.
• But if your company or team is using remote desktop as a work platform (such as virtual desktops, thin client solutions), you must deploy a complete RDS authorization architecture.

Basically that's it. Although this problem seems scary, in most cases, the authorization configuration is not in place, rather than a system error. As long as you confirm that the authorization server exists, can communicate, and the license is also configured, it can be solved.

The above is the detailed content of The remote session was disconnected because there are no remote desktop license servers available. For more information, please follow other related articles on the PHP Chinese website!