Fix it now
The Remote Desktop Licensing service is not running, so session hosts cannot obtain Client Access Licences. Microsoft does not publish message text for the Service Control Manager events in this family, so work from what is documented: the service state, the deployment’s licensing configuration, and whether the licence server is activated and has CAL packs on it.
Get-Service | Where-Object DisplayName -like '*Remote Desktop Licensing*'
Get-PSDrive C | Select-Object Used,Free
- Start the service by hand from services.msc, find it under Remote Desktop Licensing, and read the error it gives you. That message is worth more than the event ID.
- Check free space on the system volume before anything else. A licence server that has filled its system drive stops in a way that looks like corruption and is not.
- Open Remote Desktop Licensing Manager from Server Manager, Tools, Remote Desktop Services, and confirm the server appears and is activated. Activate it with Action, Activate Server if it is not.
- Confirm CAL packs are present: Action, Install Licenses installs them, and you will need the licence code or agreement number from your licence programme.
- On each session host, confirm the licence server and the licensing mode. In a Connection Broker deployment that is Server Manager, Remote Desktop Services, Overview, Edit Deployment Properties, RD Licensing. Without a broker it is Group Policy, at Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Licensing.
If the licensing mode on the hosts does not match the CALs you own, licensing will not work even with a healthy licence server. Per User CALs are for domain-joined servers only; a workgroup deployment must use Per Device.
If the service stays up and hosts are issuing licences, stop here. The next section covers what the licence server actually holds and what happens when that is damaged.
Why it happens
A Remote Desktop licence server keeps a store of its own: the CAL packs installed on it and the record of which licences have been issued. Session hosts contact it as users or devices connect and ask it to issue a licence from that store. It is not part of Active Directory, and it is not rebuilt from anywhere else, which is why losing it is more expensive than losing most services.
The events people arrive with, 7024, 7031, 7034, 7023 and 7001, come from the Service Control Manager rather than from Remote Desktop Services, and Microsoft does not publish message text for them. This article will not tell you what each number means. What it will tell you is that they all describe how the service stopped rather than why, that the entry itself in the System log names the service and carries the numeric detail, and that reading the error you get from trying to start the service by hand is a faster route to the same information.
The consequence takes time to appear, which is why this often surfaces days after the failure. Session hosts do not stop the moment the licence server does. A newly deployed host has a grace period before it must have an issued licence, and previously issued device CALs have their own validity, so an estate can keep working for a while on licences it already holds. When that runs out, connections start being refused and the outage looks sudden even though the licence server has been broken for weeks. Treat the delay as unpredictable rather than as a budget.
The system volume is full
You have this one if The service starts and stops again in a loop, and the system drive has little or no free space.
- Free space on the system volume before touching anything else, then start the service.
- Find out what filled it. On a licence server that is also a session host, user profile data and logs are the usual answer.
- Confirm the service stays running for a full day before assuming nothing else is wrong.
- Put monitoring on that volume, because this will recur.
Do this first every time. It is the cheapest cause to rule out and the most common one that looks like something worse.
The hosts are not pointed at the licence server, or are in the wrong mode
You have this one if The licence server is healthy and activated, and session hosts still report licensing problems or disconnect users.
- In a Connection Broker deployment, set both in Server Manager, Remote Desktop Services, Overview, Edit Deployment Properties, RD Licensing.
- Without a broker, set them by Group Policy at Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Licensing.
- Make the mode match the CALs you actually own. A host set to Per User with only Per Device CALs installed will not license correctly.
- Confirm the host can reach the licence server and that name resolution returns the right machine.
Per User CALs are documented as available for domain-joined servers only. If any part of the deployment is workgroup, it has to use Per Device.
The licensing store on the server is damaged
You have this one if Everything above checks out, the service still will not stay running, and Licensing Manager cannot read the server’s configuration.
- Stop and take a full copy of the server, or at least a file-level backup, before you do anything else.
- Get your CAL paperwork in front of you: the licence programme, and the licence codes or agreement numbers for every pack you own. You will need them to reinstall.
- Open a support case rather than improvising. Microsoft does not publish a rebuild procedure for the licensing store, and the procedures circulating online destroy the record of every pack installed and every licence issued.
- If the server is beyond recovery, build a replacement, activate it, reinstall the CAL packs from your paperwork, and repoint the hosts.
Whatever you do, do not start by deleting or renaming the licensing data folder. That is the step that turns a service that will not start into a licence entitlement you have to prove from scratch.
Full reference
What is published here, and what is not
This is one of those areas where a lot is written and little is published. Six event IDs appear in this article and Microsoft publishes message text for none of them. Rather than repeat somebody’s reconstruction of what each number says, here is what to do with them:
- Read the entry in the System log on the server. It names the service and carries the numeric detail, and that detail is the thing to act on.
- Then ignore the number and start the service by hand from services.msc. The error dialog is usually more specific than the event.
- Check the two cheap causes before anything else: free space on the system volume, and whether the service has a dependency that is not running.
- Only then treat the licensing store as suspect, and treat that as a support case rather than a procedure.
The Remote Desktop Licensing Manager operations that are documented
| Task | Route |
|---|---|
| Open the tool | Server Manager, Tools, Remote Desktop Services, Remote Desktop Licensing Manager |
| Activate the licence server | Select the server, then Action, Activate Server |
| Choose how it activates | Automatic connection (recommended), Web Browser, or Telephone |
| Install CAL packs | Action, Install Licenses, then enter the licence code or agreement number for your licence programme |
The Install Licenses wizard asks for the licence programme first, then the licence information, then the product version, licence type and number of licences. What it wants for the licence information varies by programme, which is why the answer to “what do I type here” is always the paperwork rather than a screenshot.
Where the licensing settings live on the session hosts
| Deployment | Where the licence server and mode are set |
|---|---|
| With a Connection Broker | Server Manager, Remote Desktop Services, Overview, Edit Deployment Properties, RD Licensing |
| Without a Connection Broker | Group Policy: Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Licensing |
Per User and Per Device, as licensed rather than as folklore
- Per User CALs are documented as available for domain-joined servers only.
- Per Device CALs can be used for both domain-joined and workgroup servers.
- If your RDS deployment uses workgroup servers, you have to use Per Device CALs; Per User is not permitted.
- Beyond that hard rule, the choice is arithmetic: Per Device suits shared machines used by many people in shifts, Per User suits people who connect from several devices, and whichever count is smaller for how your organisation actually works is the right answer.
Do not remove or edit registry values to extend a grace period on a session host. It is not a supported fix, it creates no entitlement, and it leaves you licensed incorrectly with an audit trail that says you knew.
Recovering a licence server without making it worse
- Take a copy of the whole server before you change anything. If the licensing store is intact but the service will not start, that copy is what lets somebody recover it.
- Assemble your entitlement paperwork: licence programme, agreement or licence numbers, product version and quantity for every pack. Reinstalling packs you already own costs nothing; proving you own them without paperwork is the expensive part.
- Rule out the free causes: disk space, dependencies, permissions on the licensing data after a restore or a baseline.
- Raise a support case rather than following an unpublished rebuild procedure. The procedures in circulation discard the record of every CAL pack installed and every licence issued, and they do it before you have found out whether that was necessary.
- If you do end up rebuilding, activate the new server, reinstall every pack, repoint the hosts, and connect a test session before you tell anyone it is fixed.
When a licence is the actual fix
Once the licence server is healthy, the CAL packs have to be on it, and this is where paperwork matters more than technical work. If you have the licence codes or agreement numbers, reinstalling packs you already own costs nothing. You buy when the entitlement cannot be traced, or when the estate has grown since the packs were bought. RDS Device CAL 2025 suits shared machines such as clinical workstations, shop terminals and shift-based desks, where many people use a few devices, and it is the only option at all where any part of the deployment is workgroup rather than domain-joined, because Per User CALs are documented as domain-joined only. Arco supplies RDS CALs, will work out whether device or user licensing is the cheaper fit for how your people actually connect, and will confirm the CAL version against the Windows Server version your session hosts run before you order, because that pairing is worth settling on paper rather than discovering afterwards.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
Event ID 7024 |
A Service Control Manager entry in the System log describing how a service stopped. Microsoft publishes no message text for it; read the entry, which names the service and carries the numeric detail | not published by the vendor |
Event ID 7031 |
Another Service Control Manager entry in the same family, with no published message text. Treat it as a pointer to the service, not as a diagnosis | not published by the vendor |
Event ID 7034 |
Also Service Control Manager, also unpublished. Starting the service by hand usually gives a more specific error than any of these three | not published by the vendor |
Event ID 4115 |
Quoted in Remote Desktop licensing troubleshooting. Microsoft publishes no meaning for it, so confirm the licence server and licensing mode on the host directly instead | not published by the vendor |
Event ID 7023 |
A Service Control Manager entry recorded when a service ends with an error. No published message text found | not published by the vendor |
Event ID 7001 |
A Service Control Manager entry associated with service dependencies. No published message text found; read the Dependencies tab in services.msc, which is authoritative for your build | not published by the vendor |
Confirm the fix worked
- Confirm the Remote Desktop Licensing service is running and set to start automatically.
- Confirm Remote Desktop Licensing Manager shows the server as activated.
- Confirm the installed CAL packs and their counts appear in Licensing Manager.
- Confirm each session host names the correct licence server and a licensing mode that matches the CALs you own.
- Connect a test session, then check the System log the next day for new service failures.
Questions people ask about this
What does Event ID 7024 actually say?
Microsoft does not publish the message text for it, so nobody should be quoting you one with confidence. Read the entry on your own server: it names the service and carries the numeric detail, and starting the service by hand from services.msc usually produces a clearer error than the event does.
Do I have to buy CALs again if the licence server has to be rebuilt?
Not if you can produce the licence codes or agreement numbers for the packs you already own. Reinstalling those is free. You buy when the entitlement cannot be traced, or when your usage has outgrown what you originally bought.
Should I delete the licensing database folder to make the service start?
No. Microsoft does not publish that as a procedure, and it destroys the record of every CAL pack installed and every licence issued. Rule out disk space, dependencies and permissions first, take a full copy of the server, and raise a support case rather than following it.
Should I use device or user CALs?
Start with the hard rule: Per User CALs are documented as available for domain-joined servers only, so a workgroup deployment must use Per Device. Beyond that it is arithmetic. Per Device suits shared machines used in shifts; Per User suits people who connect from several devices.
How long before users are locked out?
Longer than you would like and less than you can plan around. New hosts have a grace period and previously issued device CALs have their own validity, so the estate keeps working for a while. Microsoft’s licensing pages do not put a figure on it that this article can point you at, so treat it as weeks and fix the licence server.
