Application running on Azure Virtual Desktop cannot access Remote Desktop Virtual Drive

Question

Hi, we are using Azure Virtual Desktop, we have a desktop application that is installed on the server and accessed via Remote Desktop Web Client

The problem is related to the Remote Desktop Virtual Drive, our application does not have permission to save files to the Downloads folder, it always has this error

The Uploads folder is fine using the Upload button on the toolbar. We can manually browse to that folder with the virtual desktop app, but our application can't. Please advise what to change

Answer 1

Hello,

If your desktop application running on Azure Virtual Desktop is unable to save files to the Downloads folder but can save files to the Uploads folder, it is likely related to the permissions and configurations on the virtual machine hosting the application.

Here are some steps to troubleshoot and resolve the issue:

Check Folder Permissions:

Ensure that the folder where the application is trying to save files (Downloads folder) has the appropriate permissions for the user accounts running the application. Check both the NTFS permissions and the sharing permissions to ensure that the users have the necessary write permissions to the folder.

Verify User's Profile:

Check the user profile configuration for the Azure Virtual Desktop users. Make sure that the profile settings allow users to access and save files to the Downloads folder.

Check Remote Desktop Virtual Drive Settings:

Confirm that the Remote Desktop Virtual Drive (RDVH) feature is correctly configured on the Azure Virtual Desktop host. This feature allows users to access their local file system within the remote session. Ensure that the virtual drive settings are configured to allow access to the Downloads folder.

Use Environment Variables:

When accessing file locations within a remote desktop session, it is advisable to use environment variables rather than hard-coded paths. For example, use %USERPROFILE%\Downloads instead of a specific path. This ensures that the application can adapt to different user profiles and environments.

Application Compatibility:

Verify that the desktop application is compatible with Azure Virtual Desktop and remote desktop environments. Some applications might require special configurations or adjustments to work correctly in a remote desktop session.

Test Different File Locations:

Test saving files to different locations on the virtual machine, such as the user's Documents folder or a custom folder with appropriate permissions. This can help identify if the issue is specific to the Downloads folder or a broader permissions problem.

Check Group Policy Settings:

If the virtual machine is part of an Active Directory domain, review the Group Policy settings related to user profiles and remote desktop environments. Ensure that there are no restrictive policies preventing file access.

Application Logging and Error Handling:

Implement detailed logging and error handling within the application to capture any specific error messages or exceptions related to file access. This can help pinpoint the exact issue and guide troubleshooting efforts.

If the issue persists after following these steps, consider reaching out to Microsoft Support or Azure Virtual Desktop experts for further assistance. They can help investigate the specific configuration and identify any additional settings that might be affecting file access for your desktop application in the Azure Virtual Desktop environment.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 2

The solution is simple. Save the file in a local folder elsewhere then copy it into the Downloads folder later. The Virtual Drive Downloads folder doesn't like to have files saved directly into it.

Answer 3

I solved this same type of problem by changing the program source code to use the Windows API "CopyFileA(source,destination,FALSE)" function instead of Clarion's built-in "Copy(source,destination)" procedure. The Clarion "Copy( )" procedure would return Error # 5 - Access denied and possibly perform a disconnect.