windows 7 professional
· With OS Vista & XP the Professional Version included a permanet License to connect remotely to our office server, purchased Windows 7 Professional and in a few weeks the License stopped working, do I have to upgrade to Windows Ulitmate to get a permanent Lics.? the server I was connecting to runs server 2000 , using remote desktop worked for the first 60 Days, then it stated (the remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator") My windows 7 ultimate connects every time and so does my xp professional. The server which we are connecting to has licenses, so Im thinking it is on my computer ? As we have many computers that are able to access the server it jut seems to be the windows 7 professional ones that will not connect. Am i missing a setting or something that would let it connect?
September 29th, 2010 1:12am

“The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator”. Cause: The terminal server might not be able to locate the license server. Solution: Perform the following steps: 1. Verify that the license server is correctly installed. 2. Verify that the Terminal Server Licensing service is running on the license server. 3. Verify that the client, the terminal server, and the license server can communicate by ensuring that Domain Name System (DNS) is configured correctly on each computer. To do this, run the ping command from each computer to each computer using the IP address, FQDN, and the NetBIOS name. If any of the ping commands fail, verify the DNS configuration on the network. 4. On the terminal server, set a preferred licensing server to connect to. You can do this by using the registry, a Windows Management Instrumentation (WMI) script, or, in Windows Server 2003 with Service Pack 1, you can use Group Policy settings or Terminal Server Configuration. See also: Install Terminal Server Licensing; Set preferred Terminal Server license servers; Terminal Server license server roles Solution: If the previous solution does not resolve this problem, create a backup of the MSLicensing registry key and its sub keys on the client, and then remove the original key and sub keys by doing the following: 1. On the client, navigate to the following registry sub key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing. 2. Click MSLicensing. 3. On the Registry menu, click Export Registry File. 4. In the File name box, type mslicensingbackup, and then click Save. 5. If you need to restore this registry key in the future, double-click mslicensingbackup.reg. 6. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey. 7. Close Registry Editor, and then restart the computer. When the client is restarted, the missing registry key is rebuilt. Caution: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. See also: Removing Terminal Server Licenses From an RDP Client Refer this link: http://technet.microsoft.com/en-us/library/cc756826(WS.10).aspx#BKMK_8 Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2010 3:35am

Thank you this looks too technical for me so I will refer it to my computer person I did look at the licenses and I have 15 but the yellow trianagle is on there so that must be the issue, I will let you know
October 5th, 2010 2:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics