Hi, when the second person connects and the first one gets kicked out, it usually means the VM is running a single-session Windows edition or has a local policy limiting it to one session; the AVD host pool’s max session limit only tells the broker how many sessions it can assign, but the VM must still support them. First, check the OS edition with systeminfo | findstr /B /C:"OS Name" – it must say Windows 11 Enterprise for Virtual Desktops, not just Enterprise or Pro; if wrong, rebuild the VM with a multi-session image. Then check local policies under RDS Host - Connections: limit number of connections should be not configured or ≥ 20, and restrict users to a single session should be disabled. Also, confirm the AVD agent is at least SxSStackVersion 229 and AllowNewSession is true. After that, disconnect all sessions and retest – both users should get separate session IDs and stay connected; if not, collect the LocalSessionManager event log and escalate, though OS or policy misconfig are by far the most common causes.
azure virtual desktop multisession issue
GKV
0
Reputation points
Hi,
We have created a azure virtual desktop with two session hosts, each session host will have 20 sessions.
The selected OS image is Windows (Windows 11 Enterprise multi-session), RDP properties are as shown below.
For single user it works fine but when multiple users parallelly tries to login then the session goes off for all the users and it disconnects.
What could be the issue here?
Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,835 questions