Licensing Protocol Error using RDP Web connections

[guest]

We have several clients receiving errors after we replaced our TS License server when trying to connect through RDP Web connections.

I have been able to fix all of the XP users by deleting the HKEY_Local_Machine\Software\Microsoft\MSLicensing sub-key as mentioned in several documents, but this does not work with all Vista or any Windows 7 machines. We have many remote users with mixed clients and some are 32 BIT some 64BIT Vistal and Windows 7.

I did find information on running IE as an administrator and this only works on a per session basis. That is not acceptable since a lot of our users are not administrators nor can use admin credentials on company computers. Although it does recreate the MSLicensing key, it will still give the error after that if used normaly from a shortcut created to the RDP Web server.

Any help will be appreciated since this is causing major issues for several remote clients.

[guest]

After changing our TS License server, All of our clients were receiving "The remote computer disconnected the session because of an error in licensing protocol" when trying to access our Windows 2003 Terminal Server using RDP Web.

All the information I could find indicated that deleting the sub keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing key should resolve this issue (the applies to was for Windows XP). I did this on several Windows XP clients and it worked okay but, I tried it on a Vista and Windows 7 without any luck. We have a several clients running Vista and Windows 7 (32 or 64 BIT) that need to access our terminal services environment both through VPN or RDP Web sessions. They use both 32 and 64 BIT systems so What can I do to fix this for those clients?

Any help is appreciated.

[guest]

Please make sure that Users have Full Control rights on the following key or keys on their local PCs:

32-bit machines

HKLM\SOFTWARE\Microsoft\MSLicensing

64-bit machines

HKLM\SOFTWARE\Microsoft\MSLicensing
HKLM\SOFTWARE\Wow6432Node\Microsoft\MSLicensing

[guest]

On the Windows Vista and Windows 7 clients, please backup and remove the MSLicensing key as the Windows XP does. After that, use the administrative permission to run the mstsc.exe, check if the issue still persists in this situation.



Thanks.



· Lionel Chen
TechNet Subscriber Support in forum

[guest]

I deleted the MSLicensing key (HKLM\SOFTWARE\Wow6432Node\Microsoft\MSLicensing) on a 64bit Windows 7 pc, then ran mstsc as administrator. This fixed the problem for me.

[guest]

After the reboot of my workstation and correcting the time on the Server, I was able to logon.