Multi-session problem in Azure Virtual Desktop

Question

I have setup a Azure Virtual Desktop with host pool type- pooled and max session limit to 5. I have added users in assignments under application groups.

After creating the workspace, I'm able to login but other users cannot access it. i have chosen enterprise multi session windows VM in host pool under add virtual machines.

Even after creating it this way, we are still unable to login with multiple sessions. Please suggest a solution for this

Answer 1

Hello @Ashitha S ,
Welcome to Microsoft QnA.
To allow multiple users to connect to an Azure RemoteApp virtual machine, you need to ensure that the virtual machine is configured correctly and that you have the necessary licenses.

Here are some steps you can follow to troubleshoot the issue:

1)Make sure that the virtual machine is running Windows Server 2019 or Windows Server 2016 with the Remote Desktop Services (RDS) role installed.

2)Check that the Remote Desktop Services (RDS) role is properly configured on the virtual machine. You can do this by running the following PowerShell command on the virtual machine:

Get-RDSessionHostConfiguration | Select-Object *  

This command will display the current RDS configuration on the virtual machine.

3)Ensure that you have the necessary licenses to allow multiple users to connect to the virtual machine. You can check the available licenses by running the following PowerShell command:

Get-RDSessionHost | Select-Object *  

This command will display the available licenses and the number of active sessions.

4)If the virtual machine is configured correctly and you have the necessary licenses, you may need to check the connectivity between the client and the virtual machine. You can use the Remote Desktop Connection (RDC) tool to test connectivity and see if there are any errors or issues.

If you continue to have issues, you may want to check the event logs on the virtual machine for any errors or issues, and please feel free to reach back to me and tag me in your response. Thank you :)

----------

Please accept as answer and upvote if the above information is helpful.

Answer 2

The issue is resolved after adding the below

1. RDP property targetisaadjoined:i:1 was not added to the AVD host pool
   * In Azure portal > select host pool configured for Azure AD Joined > select RDP Properties blade > Select Advanced Tab >
   confirm targetisaadjoined:i:1 is present
   * If the RDP property does not exist you will need to add it to the AVD Host Pool RDP Properties
2. User was not granted Virtual Machine User Login or Virtual Machine Administrator Login role
   * In Azure portal go to WVD VM > Select Access control (IAM) > Select Role Assignments > Confirm the User account has
   been granted Virtual Machine User Login or Virtual Machine Administrator Login
   * If the user which is failing the login does not have this role assigned you will need to assign him the role to mitigate
   the authentication issue

Answer 3

I had similar case just a week ago and the root cause was that VMs did KMS activation and picked up wrong Windows OS version and stopped became multi-session. You should ensure, are VMs you created really multi-session version or not.

So I had this problem, where end users were kicking each other away from RDP connection...