Server Side File Tracking: Only works when home dir is on the system disk

We have found that Server Side File tracking for Mobile Home directories only works when the user's network home resides on the Mac OS X Server system disk. The apparent cause is that the SSH daemon looks for the user's public key on a path like... /Network/Servers/my.server.com/ShareName/username/Library/FileSync/FileSyncAgent_key_dir/FileSyncAgent_key.pub In our specific case, the "ShareName" portion of that path refers to an AFP share named "PHD" which is actually on a RAID connected to the home dir server. However, shares on the home dir server are not visible in the /Network/Servers folder and, as a result, the public key cannot be found and Server Side tracking cannot be initialized. Creating a symlink at the root of the system disk to the RAID volume "PHD" corrects this problem, but I am wondering if there isn't a better solution. Perhaps I am going about this the wrong way entirely?