Microsoft documents a 120-day licensing grace period for a new Remote Desktop Session Host deployment. During that time, the environment can be configured before a licence server is required for continued client sessions. The period is an implementation window, not a free long-term access model.
Microsoft documents RDS CALs as either Per User or Per Device and requires an activated licence server for RDS Session Host deployments after the applicable grace period. Always confirm current terms for your agreement and deployment with Microsoft or your licensing provider.
Procure before the deadline
Choose Per User or Per Device, confirm quantity and obtain the correct CAL version while deployment testing is underway. Commercial lead time should not become an outage risk.
Configure the full licence path
Install and activate the RD Licensing role, install CAL packs and configure the Session Host licensing mode and specified server. Use Server Manager or Group Policy as appropriate to the deployment.
Validate rather than assume
Review RD Licensing Diagnoser, confirm the Session Host reaches the correct server and test representative new users or devices. Record the settings and entitlement source before handover.
A practical checklist
- Record the deployment start date
- Select mode and count early
- Activate and install CALs
- Clear licensing warnings before handover
Licensing reference: Microsoft Learn: RDS Client Access Licences and licensing Remote Desktop Session Hosts. Product terms and agreements control; confirm the current rules for your organisation.
The practical conclusion
Use the grace period for orderly deployment. A production service should enter normal operation with licensing configured, documented and monitored.
If you need a managed environment for this workload, NetCloud24 Windows VPS combines modern infrastructure with support for business Remote Desktop use. Describe the application and user count before choosing a plan.
← Back to all articles