[OpenAFS] Windows clients / roaming profiles and OpenAFS

[Dave Botsch]

I can tell you what we're doing, with Windows 7...

redirect as many folders as possible to AFS. However, there is still
some part of the profile which roams (such as the registry files). So,
you still have a roaming profile you need to do something with. As such,
our roaming profiles are actually stored in AFS.

For each user, we have an afs homedirectory. In their homedirectory,
they have:

1. windowsprofile.v2 (where the roaming profile is stored)
2. win_folders (with a subfolder for each redirected folder)

Of course, you'll run into the occasional silly application that stores
its data in the local profile and not the roaming profile.

Up through OAFS 1.5.78, everything works great. I've seen some evidence
of weirdness with the roaming profiles bit not working correctly in
1.6.x but have not yet had time to troubleshoot/test more/report a
bug/etc.

On Wed, Jan 18, 2012 at 10:55:25AM -0500, Coy Hile wrote:
> I'm finally getting aorund to getting my cell set back up (mostly for
> playing around), and I have something new in the mix that I didn't
> have last time: Windows clients.  What is considered best practice for
> dealing with Windows profiles and OpenAFS? I see the following
> possibilities:
> 
> (1) Make all the profiles local, users have to copy things to AFS by hand
> (2) Make profiles local (or roaming using MSFT infrastructure) and
> redirect folders such as My Documents/Music/etc to \\AFS UNC path
> (3) Store the roaming profile data in AFS directly.
> 
> What's the Right Way(tm) to do it?
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info
> 

-- 
********************************
David William Botsch
Programmer/Analyst
CNF Computing
botsch@cnf.cornell.edu
********************************