We have mounted an NFS share to I: in the OS but can't connect to the mapped driver with visual cron. Visual cron does not seem to have an option to connect directly to an nfs mount or set the umask.
What is needed is the ability to use the already created mapped drive from the OS of the ability to create an nfs mount with custom umask from visual cron

Network drives are not shared with SYSTEM account. I suggest using UNC paths and if you cannot do that map the network drive in VisualCron using the built in mapping tool.

---

If we use UNC, permissions are set as 744 on the NAS, but we need to set the permission as 770. We can do this by mounting the nfs drive to a letter and use a mask of 007. However, Visual Cron can not see the mapped drive and if we attempt to use the drive letter that we mapped with the mask, visual cron converts to the unc path. We either need to be able to use the nfs mounted drive or we need to be able to set umask from visual cron. I don't see any nfs connection options from visual cron.

If you want to use a logical (mapped) drive you have to map it in VisualCron - not outside. But we do not have any special mapping options.

You can control auto-convert to UNC in File menu->Client settings. However, it does not matter if you map outside.

Best option is to not map anywhere but use UNC path on a drive that is shared for a specific user. Then you will not run into fewer problems and have less dependencies (for example if a logical drive is removed).

---

That is why this is a feature request. As I have said I can not use unc, as the permissions to an NFS mount need to be masked.

The drive is mounted using the following "mount -o fileaccess=770 \\kansn005\upload_sites i:" This creates the mount correctly and permissions are set to 770, can I mimic this in visual cron?

Ok, sorry, I read this as a "problem". Thank you for the Feature request and we will look at this later to see if the Windows API allows this kind of control.

---