RDS licensing is separate from Windows Server licensing. You can install the RDS role on a physical server or VM, but you still need RDS CALs (Client Access Licenses) for each user or device connecting. | Component | Purpose | |-----------|---------| | RDS License Server | A Windows Server (physical or VM) that manages and issues RDS CALs. | | RDS CALs | Licenses installed on the License Server. Each user/device needs one. | | RDSH (Session Host) | The server hosting the remote apps/desktops. It contacts the License Server to request and enforce CALs. | | Grace Period | 120 days after RDSH role installation where no license server is required. | 3. Types of RDS CALs | CAL Type | Scope | When to use | |----------|-------|--------------| | User CAL | Per named user (can access from any device) | Users have multiple devices (home PC, laptop, phone) or roam between workstations. | | Device CAL | Per physical device (any user from that device) | Shift workers, shared kiosks, or factory floor PCs. | ⚠️ You cannot mix User and Device CALs for the same user/device without proper tracking. Choose one model per environment (or both, but then you must track usage carefully). 4. RDS CAL Versions RDS CALs are version-specific to the Windows Server OS:

| Windows Server | RDS CAL required | |----------------|------------------| | 2025 (when released) | RDS 2025 CAL | | 2022 | RDS 2022 CAL (backwards compatible with 2019/2016) | | 2019 | RDS 2019 CAL | | 2016 | RDS 2016 CAL | | 2012 R2 | RDS 2012 R2 CAL |

RDS Licensing is the mechanism that enforces the legal requirement for devices or users to have a valid license to connect to a Windows Server Remote Desktop Services environment. Without proper licensing, RDS will function initially (usually a 120-day grace period), after which connections will be denied.