Remote desktop error

Anonymous
2010-02-10T16:54:05+00:00

I am receiving the error "the remote session was disconnected because the remote desktop client access license stored on this computer has been modified" when trying to connect to a server 2003 machine.  I am running Windows 7 but have no trouble connecting to two other server 2003 machines or XP.  It seems to be some type of conflict with this specific machine and Windows 7.  I can connect to this server from an XP machine.

Windows Server Remote and virtual desktops Remote desktop clients

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2010-02-11T15:40:39+00:00

    Hi Russ,

    First, I would suggest you to create a System Restore Point manually, so that in case, something goes wrong while performing these steps, you may always perform a System Restore and revert back.

    Normally we receive this error message if the TS license in the computer is damaged or corrupt, you may need to remove it from the TS client. The license is stored in the client's registry.

    1.  Click on Start

    2.  In the start search box type REGEDIT and press enter.

    1. In the registry editor access the following key:  HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.

    To clean the client's license cache, just delete this key and its sub keys. The next time the client connects to the server, it will obtain another license.

    Registry Disclaimer:

    Sometimes this problem is caused by two Windows registry entries that have become corrupted. To fix the problem, you have to use Registry Editor to delete the corrupted Registry entries.

    However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

    For more information about how to back up and restore the registry, follow the steps as in the KB Article: http://support.microsoft.com/kb/322756/

    Hope this helps. Let us know the results.

    Thanks and Regards,

    **Srinivas R Microsoft Support.**Visit our Microsoft Answers Feedback Forum and let us know what you think.

    74 people found this answer helpful.
    0 comments No comments

27 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-11-30T21:01:33+00:00

    This worked best as a quick fix, had to remove the registry entry first although before running RDP as administrator and logging in fresh. Logged in multiple times and rebooted afterwards and still worked after this. Mine was doing the same as others where you could connect once then after that it was hosed. Bug? Policy issue on the domain with Win10? Will be researching more, thanx.

    0 comments No comments
  2. Anonymous
    2016-11-30T21:04:28+00:00

    I was able to get mine working by having someone export their working key and sending it to me. I made a backup of mine and imported the registry key on my machine, restarted and I can now run the 3 remote sessions I need through CyberArk again. Assuming it'll keep working tomorrow. Will report back if it doesn't.

    Hope this helps others.

    0 comments No comments
  3. Anonymous
    2016-11-30T21:17:40+00:00

    I'm having the same problem.  This is a Windows 10 64 bit laptop with the Anniversary Update installed.  I have to delete the registry key every time she needs to remote into a Terminal Server.

    0 comments No comments
  4. Anonymous
    2016-12-16T20:39:38+00:00

    I did this. The problem seems not be fixed. There is another problem.

    The remote session was disconnected because license store creation failed with access denied.Please run remote desktop client with elevated privileges.

    Furthermore, I didn't back up.

    0 comments No comments