This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(208, 9%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKC%3C/text%3E%3C/svg%3E)
Hi,
I've searched high and low for an answer on this and cannot seem to find one!
I've run ECHO %username% and that displays what I want (firstname.surname)
If I browse manually in file explorer inside AVD, I can access the correct folder:
\<storageaccount>.file.core.windows.net\userdata%UserName%
I want to use a GPO for mapped drives but this doesn't seem to work. Any ideas please anyone?
It sounds like you are trying to map a network drive in Azure Virtual Desktop (AVD) using a GPO, but it is not working. Here are some troubleshooting steps you can try:
Make sure that the GPO is applied correctly to the AVD session hosts**1**. You can use the Group Policy Results wizard in the Group Policy Management Console to check if the GPO is being applied.
Check the event logs on the AVD session hosts for any errors related to the GPO or network drives.
Make sure that the network location for the mapped drive is accessible from the AVD session hosts. You can test this by manually browsing to the network location from the AVD session hosts.
Try using the IP address of the storage account instead of the hostname in the network location for the mapped drive. For example, instead of using \<storageaccount>.file.core.windows.net\userdata%UserName%, try using \\<ip-address>\userdata%UserName%.
If you are using Azure AD DS, make sure that the AVD session hosts are joined to the domain and that the user accounts have the necessary permissions to access the network location.
If none of these steps resolve the issue, you may need to consult the Azure Virtual Desktop documentation or seek assistance from Microsoft support.
Thanks for the reply Prrudram, I managed to resolve this by using the %logonuser% rather than %username%
I am glad to know you have resolved the issue.