Removing Terminal Server licenses from. Standard x64 Edition Windows Vista Business. For more information about how to back up and restore the registry.

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. Nic Nick Laurino. 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. Nick Nick Laurino. I already looked at that and on the 64 BIT machines there are no entries in the HKLM SOFTWARE Microsoft MSLicensing and I changed the users permissions for the HKLM SOFTWARE Wow6432Node Microsoft MSLicensing to Full and it still isn't working on WIN 7 64BIT.

I also noticed one 'funny' thing. On one of the Vista 32 BIT machines, the RDP Web connection is working okay, but there are no sub-keys below the HKLM SOFTWARE Microsoft MSLicensing key such as Hardware or Store. Best Astrology Programs. I guess it is a non-issue since it works, but is odd since it should have a license key of some sort.

Download Hypercam 3 3 1110 26 Multilingual Full-admin Crack Software. In any case, I am not sure what to do at this point and really need a fix for this. I cannot get any of the Windows 7 machines either 32 or 64 BIT working and only the WinXP and Vista 32 BIT are fixed using this process. Nic Nick Laurino. Has anyone found a solution for this issue yet? I am having the same problem, but on some newly purchased Windows Embedded Standard 7 thin clients. Under the embedded system, the thin clients startup and automatically login under a default 'standard' user account.