Windows File Transfer destination path not working with NAS or VMware shared foldersSolved

Participant
Discussion
3 weeks ago Sep 12, 2026

I’m testing the File Transfer feature for Windows devices in Hexnode. Does the destination path support a NAS shared folder, like a UNC path? I was thinking of using something like \\<server>\<share> as the target location.

I also tried a VMware shared folder as the destination, but that didn’t seem to work either. Just wanted to confirm whether shared/network paths are supported or if the destination has to be local on the Windows device.

Replies (1)

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Sep 12, 2026
Marked SolutionPending Review

Hi @margaret,

For Windows File Transfer in Hexnode, the destination path must be a local path on the managed device.

Network-based destinations such as NAS shares or UNC paths, for example “\\<server>\<share>”, are not supported as direct destination paths for the file transfer action. The same limitation applies to shared folders exposed through virtualization tools, such as VMware shared folders.

Use a local Windows path such as “C:\Users\Public”, “C:\Temp”, or another existing local folder on the managed Windows device. Once the destination is set to a valid local path, the file transfer action should execute successfully.

Regards,
Sienna Carter
Hexnode UEM

Save