RDP to Azure VM fails with "No Remote Desktop License Servers available"


You can use mstsc /admin to work around the following licensing error when attempting to connect with RDP to an Azure VM:

The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license.

Please contact the server administrator. 

Using mstsc /admin disables licensing for that connection only, so you could only ever have a maximum of two connections made with /admin at the same time. But it is helpful in this scenario where the 120-day Remote Desktop licensing grace period has expired and you need to access the VM to install RDS licenses. Note that if you encounter this error and you don’t need more than two RDP connections to the VM at the same time, you can use Server Manager to remove the RDS role so licensing is not enforced and you go back to having a maximum of two administrative connections.

Note that you can also edit the RDP file in a text editor and add /admin to achieve the same thing as running mstsc /admin.

full address:s:MYVM.cloudapp.net:57362 /admin

See also:

Use command line parameters with Remote Desktop Connection
http://windows.microsoft.com/en-us/windows/command-line-parameters-remote-desktop-connection/

 

Comments (21)

  1. Binu Don says:

    Thanks.. It's working for me..:) :)

  2. Dmitriy says:

    Thanks a lot! It helped out :))

  3. Rohan says:

    Thanks a Lot..!!

  4. BY says:

    Do we need license for remote access for more then 2 admin account.

    If so does anyone know the part number for it. How much for 5user licenses.

    Please don't  forward to any other site for the details.

  5. Forextor says:

    Cool!.. I manage to connect finally!.. Thank you!

  6. soma says:

    Hi,

    it is remote desktop server role has been installed and it is looking for terminal license server

  7. Hari says:

    Thanks a lot. Facing this issue for long time,. Finally able to connect with your help.

  8. Gary says:

    Nice!

    Worked great!

  9. Mrdefense says:

    Great information. I have been fighting with this for 3 months. Removing the RDS role did the trick for me.

    Thank you.

  10. diboj says:

    Thanks, that is it!

  11. Rakesh says:

    Thanks a lot. Its working fine.

  12. shibin says:

    Thank you so much …….you are a genius!!!!!

  13. Vijay says:

    Thanks mate. :)

  14. Takeshi Ozawa says:

    Great post!  Thank you very much.

  15. Rafael Emmi says:

    Great post. Exact the information i am looking for weeks.

  16. kimi says:

    simple.. just remove remote desktop services from role and features wizard, delete both

    1.remote dekstop licensing

    2.remote desktop senssion host..

    or easy say.. remove all.. :)

    hope its will help

  17. Vicky says:

    Thank you

  18. atulp says:

    Great..!!

    mstsc /admin

    working for me…

    Thanks

  19. Waldek says:

    I had the following message:

    "The remote session was disconnected because there are no Remote Desktop License Servers available to provide a license. Please contact the server administrator."

    I have lost 2 unproductive days trying to configure this stupid License Server. I only occassionally need to access the server for admin purposes.

    …And here found the ultimate solution…

    so simple and so quick – brilliantly.

    And even didn't need to go down to ugly and cold server room in the basement of my building:

    mstsc /admin  — allowed to connect!

    Thank you!

  20. Anil says:

    Thank You Craig! Your post helped me save from escalation.! Bravo…really appreciate it!!!