This problem keeps coming up every now and then so I thought it would be good to document it. If you get licencing error messages when you connect to a Terminal Services session on a remote server then this might fix the problem (you might also get this error if you use the Remote Application Service (RAS) here at Newcastle).<\/p>\n
Open regedit<\/p>\n
Create a backup of the MSLicensing registry key and its subkeys on the client, and then remove the original key and subkeys by doing the following:<\/p>\n
1.\tOn the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\MSLicensing.
\n2.\tClick MSLicensing.
\n3.\tOn the Registry menu, click Export Registry File.
\n4.\tIn the File name box, type mslicensingbackup, and then click Save.
\n5.\tIf you need to restore this registry key in the future, double-click mslicensingbackup.reg.
\n6.\tOn the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.
\n7.\tClose Registry Editor, and then restart the computer.
\nWhen the client is restarted, the missing registry key is rebuilt.<\/p>\n
Its probably also worth checking to make sure you have the RDP 7 client installed, see http:\/\/blogs.msdn.com\/rds\/archive\/2009\/10\/28\/announcing-the-availability-of-remote-desktop-connection-7-0-for-windows-xp-sp3-windows-vista-sp1-and-windows-vista-sp2.aspx (we rolled this out on campus at the end of 2009)<\/p>\n","protected":false},"excerpt":{"rendered":"
This problem keeps coming up every now and then so I thought it would be good to document it. If you get licencing error messages when you connect to a Terminal Services session on a remote server then this might … Continue reading