Same end user name/host name while creaating AVD

Question

Hello guys,

I was working on AVD and creating the AVD successfully by using custom image but the problem I am facing is every user while login on to the avd with there own credentials they are getting same host name or end user name because of this it only allowing one user to login in some of applications. and also i would like to know how i can find a identity disk which holds AD information may be that causing issue. is this disk is necessary to identify the users also if i am missing that disk how i can create that disk.

please guys help me i am stuck in this situation from many days, i done this many time now and creating the AVD successfully but some of the applications are clashing and not allowing other users to login as already another user is login there because the end user name or machine name is same its clashing on one machine only. I am updating my custom image then sysprep and capturing the image then using that image to create the AVD.

Answer 1

Hi,

You need to contact the software vendor and ask them how it needs to be set up/configured to be compatible with Terminal Services/Remote Desktop Services. In your previous Citrix environment they were likely using a compatibility flag and/or some sort of virtualization technique and/or similar method to allow multiple instances of the app to run on the same server.

Another alternative is to analyze the application and determine the method(s) it is using as it relates to the error and then based on that change how you have things configured. For example, figure out how it is checking that "device is already logged in to MatchMaker" and then you can come up with ways to work around it.

Many years ago it was somewhat common for multiuser software to use the hostname of the PC it is running on, and if more than one user tried to start the software with the same hostname it would fail. In an environment where each user has a dedicated PC, this is okay. In environment where multiple users are sharing same PC (Terminal Server, RDS, AVD multi-session), this is not okay and may be resolved by compat flag.

-TP

Answer 2

Hi

its sounds like your Session Host VMs have been activated with a single-session license activation key instead of a multi-session key. I've seen this happen before with AVD deployments where custom images are SysPrep-ed and then AVD Pools built using the custom image. Changing the license key normally fixes the problem. Its likely that in the portal when you check the VM, it will show the OS as "Windows 10" instead of "Windows 10 Multi-Session"

Unless you have other working AVD Pooled VMs that you can export the activation keys from, I would suggest raising a support request through the Azure Portal to get this resolved.

https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

Hope this helps,

Thanks

Michael Durkan

• If the reply was helpful please upvote and/or accept as answer as this helps others in the community with similar questions. Thanks!