Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error Event ID 1130

Event ID 1130 and 1131: RD Session Host cannot find a licence server at all

10 min read Updated October 5, 2026 Windows Server: RDS, Hyper-V & Clustering

Fix it now

Event 1130 says the RD Session Host has no Remote Desktop licence server specified. Event 1131 says it has one and could not contact it. While the grace period lasts you see the events and nothing else; when it ends, the same gap becomes a lockout.

Elevated PowerShell on the RD Session Host

Get-RDLicenseConfiguration -ConnectionBroker cb.contoso.local
Test-NetConnection lic.contoso.local -Port 135
  1. Read Get-RDLicenseConfiguration for a deployment, or check the Licensing policies under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Licensing.
  2. Name the licence server by its fully qualified name: Set-RDLicenseConfiguration -LicenseServer lic.contoso.local -Mode PerUser -ConnectionBroker cb.contoso.local, or set the policy and run gpupdate /force.
  3. For 1131, read TcpTestSucceeded in the Test-NetConnection output. RD Licensing uses RPC, so TCP 135 plus the dynamic range 49152 to 65535 must both be open.
  4. On the licence server, confirm the Remote Desktop Licensing service is running and that the server is registered in DNS under the name the host is using.
  5. Re-run the RD Licensing Diagnoser from Server Manager, Remote Desktop Services, Overview until it reports no issues.

A Group Policy setting overrides the console. If a change in the console appears to do nothing, check the policy branch of the registry.

If the Diagnoser is clean you can stop here. If not, the next section covers where the configuration lives and why the console sometimes lies.

Why it happens

An RD Session Host does not hold licences. It asks a licence server for one each time a client connects, and hands the result to the client. Both of these events are the host reporting that it cannot complete that conversation – but for different reasons, and the difference decides where you work.

Event 1130 is the empty-configuration case. Microsoft’s text is “The Remote Desktop Session Host server does not have a Remote Desktop license server specified”, with the remedy of specifying one. Nothing is broken on the network; nobody has told the host where to ask. Event 1131 is the unreachable case: “The Remote Desktop Session Host server could not contact the Remote Desktop license server <name>. Ensure that the Remote Desktop Licensing service is running on the license server, that the license server is accepting network requests, and that the license server is registered in WINS and DNS.” The host knows where to ask and got no answer.

Both are written by Microsoft-Windows-TerminalServices-RemoteConnectionManager on the Session Host, and while the 120-day grace period is running they are informational in effect: sessions still work, so nobody investigates. The events are the only warning you get. When the grace period ends the same missing configuration becomes Event 1128 and users are refused.

The configuration itself lives in three places and they do not all have equal weight. Group Policy writes LicenseServers and LicensingMode under HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services. The Remote Desktop Services console writes LicensingMode under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core and SpecifiedLicenseServers under HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers. Domain policy wins over local policy, which wins over the console. A host inside a GPO scope will ignore what you set in the console and keep logging 1130.

No licence server has ever been named

You have this one if Event 1130, and the RD Licensing Diagnoser reports the host has not been configured with any licence servers.

  1. For a deployment managed by a Connection Broker: Set-RDLicenseConfiguration -LicenseServer lic.contoso.local -Mode PerUser -ConnectionBroker cb.contoso.local.
  2. For a standalone host: set Use the specified Remote Desktop license servers and Set the Remote Desktop licensing mode under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Licensing.
  3. Run gpupdate /force, then re-run the Diagnoser.

Use the fully qualified name. A short name resolves inconsistently across sites and produces intermittent 1131 events later.

Group Policy is overriding the console

You have this one if You set the licence server in the console, it does not stick, and 1130 keeps appearing.

  1. Read HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services on the host. If LicenseServers or LicensingMode are present, policy is in control.
  2. Fix the value in the GPO rather than on the host, then gpupdate /force.
  3. Confirm which GPO is applying with gpresult /h C:\Temp\gpresult.html before editing anything.

The RPC path to the licence server is blocked

You have this one if Event 1131 naming the licence server, and Test-NetConnection on port 135 reporting TcpTestSucceeded False.

  1. Open TCP 135 from the Session Host to the licence server, plus the dynamic RPC range TCP 49152 to 65535 on Windows Server 2008 and later.
  2. Test from the Session Host’s own subnet – a path that works from somewhere else proves nothing.
  3. Where per-user CALs are in use, TCP and UDP 389 to Active Directory is needed as well, because tracking writes to the user object.

The licence server is not answering

You have this one if Event 1131, the network path is open, and the Diagnoser reports the licence server as unavailable.

  1. Confirm the Remote Desktop Licensing service is running on the licence server.
  2. Confirm the server is registered in DNS under exactly the name configured on the host.
  3. In Remote Desktop Licensing Manager, right-click the server and choose Review Configuration, then publish it in Active Directory Domain Services.

The Session Host is not permitted to ask

You have this one if The path is open, the service is running, and the licence server still does not answer this particular host.

  1. On the licence server, check whether the License server security group policy is enabled.
  2. If it is, add the Session Host’s computer account to the Terminal Server Computers local group on the licence server.
  3. Restart the Remote Desktop Licensing service and retry a connection.

That policy is under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, RD Licensing. When it is on, only members of that group get answers.

Full reference

Two events, two different jobs

Event What it says Where the work is
1130 No Remote Desktop licence server is specified The Session Host’s configuration
1131 Could not contact the named licence server; check the service, network requests, WINS and DNS The network, the licence server, or name resolution

Where the settings live, and which one wins

Set by Registry path Values
Group Policy HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services LicenseServers, LicensingMode
RDS console HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core LicensingMode
RDS console HKLM\SYSTEM\CurrentControlSet\Services\TermService\Parameters\LicenseServers SpecifiedLicenseServers

LicensingMode is 2 for Per Device and 4 for Per User. Precedence runs domain Group Policy, then local policy, then the console. If the console and the registry disagree, the registry is telling you the truth.

Ports RD Licensing needs

Port Purpose
TCP 135 RPC endpoint mapper, between the Session Host and the licence server
TCP 49152-65535 The RPC dynamic range on Windows Server 2008 and later
TCP 443 Outbound from the licence server to the Microsoft Clearinghouse for activation
TCP and UDP 389 LDAP to Active Directory, needed where Per User CALs are tracked

Discovery in a forest

Microsoft’s recommended discovery scope for a licence server is forest scope: publish the server in Active Directory Domain Services and Session Hosts in the same forest can find it with no further configuration. That is what Review Configuration in RD Licensing Manager does. Explicitly naming the server on each host still works and is more predictable in a mixed or multi-forest estate, which is why most deployments end up doing both.

When the Diagnoser is clean and users still fail

  • Confirm the licence server actually holds CALs. A correctly configured host pointed at an empty licence server stops logging 1130 and starts logging that it cannot issue a licence.
  • Check the licensing mode against the CAL type installed. Per Device and Per User are not interchangeable.
  • Check CAL and server versions: CALs must be the same version as the Session Host’s Windows Server or newer, and the licence server must run the CAL version or later.
  • Look on the licence server for Event 4141, which records a licence refused because the host is not a member of the Terminal Server Computers group.
  • In a multi-domain deployment, confirm the trust relationships between the Session Hosts, the licence server and the users’ domain.

When a licence is the actual fix

Naming a licence server only helps if that server holds CALs. A correctly configured host pointed at an empty one stops logging 1130 and starts logging that it cannot issue a licence, and users are refused just the same once the grace period ends. Choose the CAL type to match how people connect: User CALs where staff use several devices each – a laptop, a home machine, a phone – because you licence the person once instead of every endpoint they touch; Device CALs where machines are shared between shifts. Then check two version rules before ordering: the CALs must be the same version as your newest Session Host or later, and the licence server itself must run the same Windows Server version as the CALs or later. Tell Arco your Session Host version, your licence server version and your named user count, and we will supply RDS CAL packs that install first time, with the agreement details the Install Licenses wizard asks for.

Every code this article covers

Code What it points at Source
Event ID 1130 TerminalServices-RemoteConnectionManager on the Session Host: “The Remote Desktop Session Host server does not have a Remote Desktop license server specified” Microsoft Learn
Event ID 1131 The same source: the Session Host could not contact the named licence server. Check that the Remote Desktop Licensing service is running, that the server is accepting network requests, and that it is registered in WINS and DNS Microsoft Learn

Confirm the fix worked

  1. Get-RDLicenseConfiguration returns the licence server you intended, by fully qualified name, with the correct mode.
  2. Test-NetConnection lic.contoso.local -Port 135 reports TcpTestSucceeded True from the Session Host.
  3. The RD Licensing Diagnoser reports no issues.
  4. Events 1130 and 1131 stop appearing on the Session Host after a reconnection.
  5. The issued count in Remote Desktop Licensing Manager rises as users connect.

Questions people ask about this

Why do sessions still work while these events are logged?

Because the 120-day grace period is still running. The events are the warning, not the outage. Once the grace period ends the same missing configuration produces Event 1128 and connections are refused.

I set the licence server in the console and it did not stick. Why?

Group Policy takes precedence over the console. Check HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services on the host; if LicenseServers is there, fix the GPO rather than the host.

Is opening TCP 135 enough?

No. RD Licensing uses RPC, which negotiates a second port. You need TCP 135 plus the dynamic range TCP 49152 to 65535 on Windows Server 2008 and later. Per User CAL tracking also needs LDAP on TCP and UDP 389.

Should I publish the licence server in Active Directory or name it on each host?

Microsoft recommends forest discovery scope with the server published in AD DS, which lets hosts in the same forest find it automatically. Naming it explicitly on each host is more predictable in mixed estates, and doing both is common.

The host now finds the server but users are still refused. What next?

The server has nothing to give. Check that CALs are installed, that their version is at least that of the Session Host, and that the licensing mode on the host matches the CAL type installed on the server.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Event ID 1069 and 1205: a clustered role keeps failing and will not stay online Free Fix 0x81000019 and 0x8100002F: backup cannot read the shadow copy it just made License Error Event ID 1511 and 1515: RDS users land in a temporary profile every logon License Error Event ID 1306 and 1296: Connection Broker cannot redirect users to a host
โ† Back to Knowledge Base