If you plan to use home directories, you must also make one additional change on the server side. On the Access Connect DFS root server, in addition to the automatically created DFS root volume, you must also separately share the home directory subfolder inside of that DFS root volume.
For our example we will be using a DFS path home directory of \\GLILABS\DFSHOMES\Sales\phd which from the Macintosh side looks like the following:
webinar:~ phd$ sudo dscl . read /Users/phd | grep Home
NFSHomeDirectory: /Users/phd
OriginalHomeDirectory: <home_dir><url>afp://GLILABS.glilabs.com/DFSHOMES</url><path>Sales/phd</path></home_dir> OriginalNFSHomeDirectory: /Network/Servers/GLILABS.glilabs.com/DFSHOMES/Sales/phd
SMBHome: \\GLILABS\DFSHOMES\Sales\phd
SMBHomeDrive: H:
For home directories, unlike the basic solution where we have a DFS Root Emulator volume represent the namespace(s), we have a server represent the first half of the namespace (the DomainHost portion). An example will probably make this clear. If the DFS path to the user’s home directory is \\GLILABS\DFSHOMES\Sales\phd, at login that will be converted to afp://GLILABS.glilabs. com/DFSHOMES/Sales/phd, therefore we have to have a volume called DFSHomes on a server named GLILABS. The DFSClient script takes care of the first part but you need to make sure there is a volume on the server that matches the second portion of the DFS namespace. In this example, you would share the Sales folder. This folder should already exist In C:\Program Files\Group Logic\Access Connect\DFS Volumes\namespace\ and just needs to be shared as an Access Connect volume. This volume represents the specific DFS namespace on the DFS DomainHost where the user’s home directory is located. With this subvolume shared out, the Macintosh user will be able to use their DFS home directory.