License error occured

Question

License error occured

Tarwani, Riya 0

[Window Title]

RemoteApp Disconnected

[Content]

A licensing error occurred while the client was attempting to connect (Licensing timed out).

Please try connecting to the remote computer again.

[^] Hide details [OK]

[Footer]

For more tips on how to resolve the issue, refer to the Troubleshooting Guide

[Expanded Information]

Error code: 0xf06

Extended error code: 0x0

Timestamp (UTC): 2026-09-01T15:14:28.1049405Z

Activity ID: 2b7fc9f5-d2f4-49d9-b0ad-d79d3fb60000

Press Ctrl+C to copy.

0 comments

2 answers

Your answer

Answer 1

John Jefferson Doyon 89,925 Independent Advisor

Hi, @Tarwani, Riya

That error is related to the Remote Desktop/RemoteApp licensing connection. It can happen if the remote server cannot reach its Remote Desktop licensing server, so the issue may be on the remote environment rather than your device.

First, try restarting the device and connecting again.

If the same error appears, to help narrow this down:

Are you connecting from a Windows PC or a Mac?
Is this RemoteApp provided by your employer, school, or another organization?
Were you able to connect normally before, and if so, when did this error start?
Are other users getting the same licensing error?

If this is an organization-managed RemoteApp, the administrator may need to check the Remote Desktop licensing server and its configuration.

Click "Add comment" to let me know.

Thanks!

Tarwani, Riya 0 Reputation points

2026-09-01T18:52:46.8633333+00:00

Ans to above question
1.Windows
2.Organization-Accenture
3.Yes,it started in between a task started hanging and got closed after this when i am clicking on connect it started loading and thn this error.
4.I have to connect with others and check.
John Jefferson Doyon 89,925 Reputation points Independent Advisor

2026-09-01T19:19:17.45+00:00
Thanks for the details.

Since this is an Accenture-managed RemoteApp and it started after the previous session hung and closed, there may still be a stuck session or a licensing issue on the organization’s Remote Desktop server.

For now, please completely restart your Windows PC, then try connecting again.

Also, if possible, check with one or two colleagues whether they can connect to the same RemoteApp. This will help determine whether the problem is only affecting your PC or the RemoteApp service itself.

If they can connect normally but you still receive error 0xf06, let me know:

Have you already restarted Windows since the issue started?

Are you connecting through the Windows App, Remote Desktop Connection, or another Accenture application/portal?

Does the error appear immediately, or does it load for a while before showing the licensing timeout?

Thanks!

Answer 2

This error usually means the Remote Desktop Session Host cannot get a license from an RD Licensing server, or the licensing check is timing out.

Check these items in order:

Verify the RD Licensing configuration on the RD Session Host
- Open Local Group Policy Editor: gpedit.msc
- Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Licensing
- Open Use the specified Remote Desktop license servers
  - Set it to Enabled
  - Enter the license server name
- Open Set the Remote Desktop licensing mode
  - Set it to Enabled
  - Choose Per Device or Per User as appropriate
If using an RDS deployment, verify deployment settings in Server Manager
- Open Server Manager
- Go to Remote Desktop Services > Overview
- In Deployment Overview, select Tasks > Edit Deployment Properties
- Select RD Licensing
- Confirm the licensing mode and licensing servers are correct
Check whether the licensing grace period has expired
- If the grace period has expired and no valid license server is configured, connections are denied.
- Typical related signs include messages such as:
  - "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license."
  - "A licensing error occurred while the client was attempting to connect (Licensing timed out)."
Check the license server and connectivity
- Make sure the Remote Desktop Licensing service is running on the license server.
- Make sure firewalls are not blocking required ports between the RD Session Host and the RD Licensing server.
Check Event Viewer for licensing-related errors
- On the RD Session Host:
  - Applications and Services Logs > Microsoft > Windows > RemoteApp and Desktop Connections
  - Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager
  - Applications and Services Logs > Microsoft > Windows > TerminalServices-RemoteSessionManager
- On the RD license server:
  - Applications and Services Logs > Microsoft > Windows > TerminalServices-Licensing
- Relevant events include:
  - Event ID 1088: licensing grace period expired and no license server registered
  - Event ID 1010: could not locate a license server
  - Event ID 1004: cannot issue a client license
If the issue is tied to license certificate corruption, refresh the X509 certificate registry keys
- Warning: registry changes are risky. Back up the registry first.
- This is relevant when errors include security-related disconnects or the RD License Diagnoser reports X.224 protocol stream errors.

If this is an Azure Windows VM and only temporary access is needed, one documented workaround is to connect with:

mstsc <File name>.RDP /admin

That disables licensing for just that connection.