>>>>>>>>I have been having a problem connecting to a customer server using Remote Desktop. The message says "No Remote Desktop client access licenses available ..." I found a page that indicates that deleting the following key solved the issue for some.
>>>>>>>>
>>>>>>>>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
>>>>>>>>
>>>>>>>>How dangerous is it to delete this key?
>>>>>>>
>>>>>>>If it's a server, you probably don't want to mess around with that.
>>>>>>>
>>>>>>>If the server is not a Terminal Server, and it's Windows Server 2003 or later, it's limited to 2 simultaneous sessions. If it's a Terminal Server, it can be many more but the number is controlled by Terminal Server Licensing.
>>>>>>>
>>>>>>>The first thing to check is that the server you're trying to connect to is not already at that limit. Have an admin log on to the server and use Terminal Services Manager to view current sessions, and close down any dead or orphan sessions that may have been caused by people disconnecting without logging off properly first.
>>>>>>
>>>>>>I have been trying to talk (email, telephone messages) with the admin person since Sunday. He won't return calls/emails. So I don't know what it is. But the customer (users) need help and I am trying all that I can to connect. I suppose I will wait another day before deleting anything in my registry. Thank you.
>>>>>
>>>>>Can any on-site user connect to that server, or do they get the same message as you?
>>>>
>>>>They do not use Remote Desktop to connect to the server; they are right there on the network. So they have no problem using the application. But I need to make some changes.
>>>
>>>Can you ask them to try to connect via Remote Desktop? If they can't, probably the server is at its session limit as I described above. If they can, you have a problem - in that case, have you been able to connect successfully to that server in the past, or is this your first attempt?
>>
>>I was just about to do that; although explaining to the user on how to connect via Remote Desktop will be a challenge. I have been connecting to the server successfully for about 6 months. On a few occasions there was a problem, just like this. And then the problem got resolved. They didn't tell me what was the problem; my guess it was license limit.
>
>Most likely you are hitting the session limit. The best bet by far is to get the admin to clean up any unneeded sessions.
>
>Another possibility is to ask the users if any of them have logged on to the server via RD, and disconnected without logging off (creating an orphan session). If they have, they can log on again (in which case they'll reconnect to their orphan session), then properly log off. That will free up a session.
>
>If all else fails, you could get them to restart the server (after closing any open files). But, they may not be able to do that cleanly unless they can log on as an admin. They could always force a restart by pressing the power button for 4+ seconds, but that's not ideal, only good for an emergency.
>
>By the way, if no-one is able to log on to the server as an admin, you're not going to be able to make any registry changes, so the original topic of this thread is probably moot.

I just got an email from the user (I am on cc) to the network admin asking to increase number of sessions. So it must be number of sessions. But the admin does not respond at all; not only to my messages but to their users (managers) either. And this is about 300 million dollar company! But in the end I will be the one to blame (one user this morning was almost rude to me that I was not taking care of the problem). But I am used to it; I have thick skin. Thank you very much for your help.