Mapped Drive Permissions

You need mapped drive permissions when you are using either a mapped drive or a Network Appliance filer to store a source or a workspace.

The procedure you need to follow varies between Solaris and Windows:

If you are using Solaris, you only need to give the machine running the core application root access to the mounted drive.
If you are using Windows, there are several possible scenarios depending on how you are running the ContentDirector service. See Windows scenarios for details.

The simplest scenario for using a filer for ContentDirector sources or workspaces under Windows fulfills both of the following conditions:

The filer and the machine on which the ContentDirector core application resides are both in the same domain.
The ContentDirector service runs as a user in that domain, with permissions on the filer.

There are three other scenarios that are more complex:

ContentDirector runs as a local system account.
Because the local system account runs with a NULL session ID, you must enable special privileges on the server side to allow access to a NULL session ID. For instructions on configuring the NULL user in DataONTAP, see "Using a NetApp Filer with Lotus Domino Server R5 for Windows NT/2000," section 7.1.1, on the Network Appliance NOW site, now.netapp.com.
The filer and the machine running the ContentDirector core application are in separate domains.
The client where the ContentDirector core application is resident must access the filer as the user FilerDomain\username.
The filer is not in any domain, but in a workgroup instead.
You must make a registry change to enable plain text passwords on the client where the ContentDirector core application resides. For instructions on enabling plain text plain text passwords for filers, see solution 3.0.1234115.2574126 on the Network Appliance NOW site, now.netapp.com. For information on running applications as services under Windows NT 4.0, see Srvany.doc in the Windows NT Resource Kit.