I'm having a bit of an issue with a new setup where standard users can't log into the new Virtual Desktop Infrastructure (VDI) while those with admin rights can access it just fine. Interestingly, the standard users can still log into the older VDIs that were created earlier. I started with Azure Premium Files for user profiles and later switched to NetApp Files. Can anyone provide insights on what might be going on?
4 Answers
I'm using Azure Active Directory Domain Services (AAD DS), and all users have the proper permissions. It's strange because they can log into one host pool, but only with the old VDIs created two months ago. When I set up new VDIs in the same host pool, they can't access them. The FSLogix profiles start loading and then they seem to sign out. Admins don't have any trouble logging in though. I'm also using the Windows App for Azure connections. Have you checked if the FSLogix profiles for the new VDIs are on the same storage account as the old ones? This might also be a permissions issue on those shares.
There are a few things to consider. Are the devices enrolled in Entra/Intune? Also, did you add the line targetisaadjoined:i:1? Make sure users have the correct RBAC rights, specifically the Virtual Machine User Logon rights. And yes, are they using the Windows App for connection?
First off, make sure the standard users have been assigned the necessary roles, like the Virtual Machine User Login role and the Desktop Virtualization User role. Also, check whether the VMs are joined to Entra or Active Directory. Are the users getting any specific error messages? How are they trying to connect—using the Windows App?
Have you confirmed if the users are joined to Active Directory? It might be something as simple as that. Also, check if the VMs are properly configured.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures