Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
8,808 questions
Unable to access Azure VM
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 61%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
kinto
0
Reputation points
Hello.
I’ve a Windows Server 2019 VM on an Hyper-V Host and I have a daily image backup of this VM on an Azure Storage Account (software used MSP360).
I’ve performed a restore on Azure of this VM with no problem I can also reach the shared folder on the VM using the Public IP assigned on Azure).
When I try to connect using RDP I’ve the error “The number of connections to this computer is limited and all connections are in use right now”.
The Azure Agent is installed (i’ve installed it on the VM present on the Hyper-V host) and I can run commands on the restored Azure VM.
The following items were already configured correctly on the VM OnPrem:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits
Before I ran the last backup from which I then restored I made sure that all remote sessions were disconnected.
On the Azure VM I have:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\ MaxInstanceCount is set to a value of 0xffffffff (the maximum value possible)
qwinsta show
>services 0 Disc console 1 Conn 31c5ce94259d4... 65536 Listen rdp-tcp 65537 Listen
I’ve tried also to reset NIC and to Redeploy the VM.
Some ideas?
Thank you.
Azure Virtual Machines
{count} votes
-
Jose Benjamin Solis Nolasco 1,591 Reputation points2025-04-17T13:51:58.8966667+00:00 Hello,
I hope you are doing well,
Did you try to close all the connection running;
query session | foreach { if ($_ -match "rdp-tcp") { $parts = $_.Split() logoff $parts[2] } }Try too using mstsc/admin normally works when there not available sessions to connect
mstsc /v:<PublicIP> /admin😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 24%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
Dharani Reguri 585 Reputation points Microsoft External Staff Moderator2025-04-17T17:13:04.9366667+00:00 Hi kinto,
In addition to Jose Benjamin Solis Nolasco, can you please check if the "Restrict Remote Desktop Services users to a single Remote Desktop Services session" is Disabled in Group policy? If not, please try to Disable it and reboot the machine.
Also, please check the UserSessionLimit. This key does not exist by default. If this value is set, this means that this was done manually by the you at some point in time by manipulating the registry. If this registry value is set, it limits the number of concurrent user sessions.
To check the UserSessionLimit, try running the command below.
reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v UserSessionLimitIf it shows a value, then that is the limit set.
- As this value is not a default configuration, you can opt out to either remove the quota by deleting this value or increasing the quota to a higher value or unlimited.
- Option to remove the quota
reg delete "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v UserSessionLimit - Option to set the quota to unlimited
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v UserSessionLimit /d 0xffffffff /f - Option to set the quota to a higher value. This ilustrates how to add a limit to a 100 (64 in hexadecimal) connections
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v UserSessionLimit /d 0x00000064 /f
- Option to remove the quota
Please let me know if you have any questions.
Thank you.
- As this value is not a default configuration, you can opt out to either remove the quota by deleting this value or increasing the quota to a higher value or unlimited.
-
kinto 0 Reputation points
2025-04-17T18:19:33.9733333+00:00 I supplement the information given above:
In Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
- the "Restrict Remote Desktop Services users to a single Remote Desktop Services session" item is Disabled
- the "UserSessionLimit" item is enabled and set to 999999
In Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits
- the "Set time limit for disconnected session" item is enabled and set to 2 hours
- the "Set time limit for active but idle Remote Desktop Services sessions" item is enabled and set to 2 hours
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\MaxInstanceCount is set to a value of 0xffffffff (the maximum value possible). I've tried also with the default value (not configured).
On the Azure VM I've not lunched "query session" but I've lunched "qwinsta show" which should provide equivalent information. Right?
I remember that before launching the backup and then restoring to the cloud, I performed a reboot (shutdown -r -f -t 0) precisely to close any connections that might be idle or inactive.I tried connecting with “mstsc /admin” and also with Azure Bastion but with the usual problem.
Thank you.
-
Dharani Reguri 585 Reputation points Microsoft External Staff Moderator
2025-04-21T11:25:19.7533333+00:00 Hi kinto,
Yes, both "query session" and "qwinsta" shows equivalent information. I request you to please share the output of the qwinsta show.
Also, could you please try setting the UserSessionLimit key to 0 to resolve the issue. This can be done by going to start - run - regedit HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server UserSessionLimit key to 0.
Please let me know if you have any questions.
-
Dharani Reguri 585 Reputation points Microsoft External Staff Moderator
2025-04-22T09:51:17.7033333+00:00 Hi kinto,
Just checking in to see if you have got a chance to see my response to your question in resolving the issue.
Please let me know if you have any questions.
Thank You.
Sign in to comment
Sign in to answer