Trying to use a locally mapped network share (a NAS) a as a Disk Group path.

[Edward_Washing1]

The Thick Client works fine, but the Core Clients fail. Web Client and Unity Client. Z:\Disk Groups....which is really \\NAS Server\Disk Groups.

[Kevin_Perron]

Edward,

Did you give the account running your Core Services access to the parent directory for the disk groups? Also have you restarted the services since this change?

KP

[Mike_Saville]

it is recommended to use UNC paths for all disk groups to avoid this type of issue.  Is there a reason you can't utilize UNC for the disk group path in Config?  Services don't have the ability to map drive letters so that is why the Core clients are failing because the Application Server can't map the Z: drive.

[Greg_Wheeler]

Mike's answer is correct--mapped drives exist only for a particular user's session. If a user changes, or the session changes, the mapping goes away.

While there are a couple ways around this, for stability and troubleshooting reasons, avoid mapped drives for any access where a UNC path (preferably DFS) is available.

Some more background here: msdn.microsoft.com/.../ms685143(v=vs.85).aspx