Rodney M. Dyer wrote:
There is a new "undocumented" third way that I might mention here. The
latest OpenAFS Windows client has the unique ability to access a users
volume directly by volume name. You must have the "freelance" option
enabled to do this, and it goes somthing like this...
\\afs\cell#user_volume\dir1\dir2\...
This does not (or at least should not) require Freelance.
There is one last way to deal with the "folder redirection" issue, that still involves hacking, but does not use the new "direct to volume" AFS syntax ( the \\afs\cell#user_volume\path ) that I outlined above. It involves creating a "symlink" to the users home volume under the "\\afs\all" mount. You can only do this with "freelance" enabled, and only as administrator. So basically we would, during our hacked "afslogon.dll" script, and in real time, during the logon, create the "symlink" for the user logging on. So we have something like...(Note: Unfortunately you need a drive mounted for this because you can't create a symlink at the root of a UNC path using the existing symlink command syntax.)
Use this syntax: symlink make \\afs\all\link /afs/cell/path No drive mapping required.
smime.p7s
Description: S/MIME Cryptographic Signature
