Windows Server / Services, IIS & Secure Operations
Investigate Remote Desktop Session Host licensing before changing connection limits
A session host can reject users because its licensing configuration or license-server dependency is wrong. Identify the server role and exact event first.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-WindowsFeature RDS-RD-Server, RDS-LicensingRead the result
This ServerManager query identifies installed session-host and licensing roles. It does not prove entitlement, CAL availability or correct licensing-mode configuration.
Resolve and verify
Use the supported RDS licensing diagnostics and event logs to compare configured mode and server reachability. Correct the managed licensing configuration with the responsible owner.
Before changing production
Do not reset grace periods, edit licensing databases or bypass licensing controls to admit more sessions.