: Make sure you understand the licensing requirements for your specific situation, including any compatibility issues with different Windows Server versions.
: Check your internet connection and ensure you have the correct license information.
An RDS Client Access License (CAL) is required for any user or device connecting to a Windows Server’s Remote Desktop Services (formerly Terminal Services) beyond the default administrative limits (two concurrent admin sessions). Without proper RDS CALs, users may be disconnected after a 120-day grace period. rds license
You cannot substitute one for the other.
| Problem | Likely Cause | Solution | |---------|--------------|----------| | | No license server or incorrect configuration | Install and activate license server; point session hosts to it | | Event 205 (license server unavailable) | Firewall blocking port 135 (RPC) or TCP 445 | Open required ports or check service (Remote Desktop Licensing) | | Per User CALs not tracked correctly | License server in Domain Group Policy or AD mismatch | Ensure license server is discovered via GPO or registry; Per User CALs are tracked in AD, not in LS | | Temporary licenses issued (Event 17) | License server has no installed CALs | Install appropriate number of RDS CALs for your environment | : Make sure you understand the licensing requirements
: Ensure your RDS server is configured to use the license server for CAL tracking.
When you install the Remote Desktop Session Host (RDSH) role on a server, it enters a . During this time, you do not need licenses installed to connect. Once this period expires, the server will stop accepting non-administrative connections until valid RDS CALs are installed and activated. This is the most common panic point for new administrators. Without proper RDS CALs, users may be disconnected
To deploy RDS licenses, you cannot simply type a product key into the server hosting the sessions. You must deploy the .
