How Data ONTAP matches a directory with a user

Effects of home directory naming styles on user matching

You can specify the naming style of home directories, which determines how Data ONTAP matches a directory with a user.

The following list describes the naming styles:

Windows name--Data ONTAP searches for the directory whose name matches the user's Windows name.
Hidden name--If the naming style is hidden, users connect to their home directories using their Windows user name with a dollar sign appended to it (name$), and Data ONTAP searches for a directory that matches the Windows user name (name).
Windows domain name and Windows name--If users from different domains have the same user name, they must be differentiated using the domain name. In this naming style, Data ONTAP searches for a directory in the home directory path that matches the domain name. Then it searches the domain directory for the home directory that matches the user name.
Example: To create a directory for engineering\jdoe and a directory for marketing\jdoe, you create the two directories in the home directory paths. The directories have the same names as the domain names (engineering and marketing). Then you create user home directories in these domain directories.
Mapped UNIX name--If the naming style is UNIX, Data ONTAP searches for the directory that matches the user's mapped UNIX name.
Example: If John Doe's Windows name jdoe maps to the UNIX name johndoe, Data ONTAP searches the home directory paths for the directory named johndoe (not jdoe) and offers it as the home share to John Doe.

Effects of not specifying a home directory naming style

If you do not specify a home directory naming style, Data ONTAP uses the user's Windows name for directory matching. This is the same style used by versions of Data ONTAP prior to version 6.0.

There are some differences between Windows name directory matching and the directory matching of Data ONTAP versions prior to 6.0. For more information about these differences, see About symbolic links used as home directory names.

About symbolic links used as home directory names

In releases prior to Data ONTAP 6.0, if you wanted home directories to reside in different volumes, you had to specify symbolic links as home directories in the home directory path. Because Data ONTAP now supports home directories in different volumes, you do not need to use symbolic links as home directory names. However, Data ONTAP continues to support symbolic links as home directory names for backward compatibility.

Effects of naming styles on symbolic links

The way symbolic links work depends on the home directory naming style.

Pre-6.0 naming style

If you do not specify a naming style, Data ONTAP uses symbolic links the same way it used them before 6.0. It follows any symbolic link that points to a directory outside the home directory path to locate a home directory.

Example

Suppose the home directory path is /vol/vol0/eng_homes and you use the pre-6.0 home directory naming style. To locate the home directory for jdoe, Data ONTAP searches for /vol/vol0/eng_homes/jdoe, which can be a symbolic link pointing to a directory outside the home directory path, such as /vol/vol1/homes/jdoe.

Other naming styles

If you specify a home directory naming style, by default a symbolic link works only if the symbolic link points to a directory in the home directory path.

Example

Suppose the home directory path is /vol/vol0/eng_homes and you use the Windows naming style. To locate the home directory for jdoe, Data ONTAP searches for /vol/vol0/eng_homes/jdoe. If the path is a symbolic link, the user can access the home directory only if the target of the symbolic link resides in the home directory path. For example, the symbolic link works if it points to the /vol/vol0/eng_homes/john directory; it does not work if it points to the /vol/vol1/homes/john directory.

Note
You can change the default filer settings to allow CIFS clients to follow symbolic links to destinations outside the home directory path. For information on the options for symbolic links, see Controlling CIFS access to symbolic links.