License | Remote Desktop Server

| License Type | Approximate Retail Price (USD) | |--------------|-------------------------------| | Windows Server 2025/2022 Standard (16 core) | $1,100 – $1,300 | | RDS User CAL | $120 – $180 per CAL | | RDS Device CAL | $120 – $180 per CAL | | RDS External Connector (per server) | $2,000 – $2,500 |

Beyond the type of license, organizations must also choose the licensing mode: Per Device or Per User. This configuration is set within the Remote Desktop Session Host configuration. If a server is configured for "Per User" mode, it expects User CALs to be installed on the Remote Desktop License Server; if configured for "Per Device," it looks for Device CALs. While it is technically possible to configure the server for Per User mode without strictly tracking the consumption of licenses within the licensing manager, this does not absolve the organization of the legal requirement to purchase a CAL for every user. Microsoft audits frequently flag this discrepancy, leading to hefty penalties. remote desktop server license

Furthermore, the management of these licenses relies on the Remote Desktop Licensing (RD Licensing) role service. This component must be installed on a server—often a dedicated one—to issue and track the CALs. When a user or device connects to the RDSH for the first time, the License Server issues a temporary license, which is eventually converted into a permanent CAL after a validation period. This architecture introduces a single point of failure that IT administrators must manage: if the License Server goes down or runs out of available CALs, new users will be unable to connect, and existing sessions may be interrupted. Therefore, proper high-availability planning for the licensing role is as vital as planning for the session hosts themselves. | License Type | Approximate Retail Price (USD)

Alternatively, open on your license server to view issued and available CALs. While it is technically possible to configure the

This report is for informational purposes only and does not constitute legal or official Microsoft licensing advice. Always consult a Microsoft Licensing Specialist or your software reseller for your specific environment.