Justin-
Redirecting App Data is only part of the equation in terms of making a
user's settings roam. And in fact, for the reasons you've mentioned, I
rarely find value in redirecting App Data alone. In order to truly get the
user's settings to roam, you would have to set up a roaming profile for that
user. Outlook, for example, stores the user's Outlook settings partly in
HKEY_CURRENT_USER (a.k.a. ntuser.dat) and partly in AppData. Stuff like
which server I'm connected to, which pst files I have loaded, etc. are
stored in the user profile in ntuser.dat, not AppData. So, if you truly want
to have the user roam, I would set them up with a roaming profile. In that
case, AppData will roam as well, but you won't be accessing AppData
continuously over the LAN, but only when the user first logs on and its
copied down to the local profile.
Darren
Justin Allen said:
My question is this: What exactly is the point of redirecting appdata? I
did this in the hopes that users could logon to a different PC and have
their Outlook there. Unfortunatly, this is not occuring. All it seems to do
is take forever to login on a new machine (as appdata is large for most
users). Is there any way to get outlook to work when a user logs onto a
diff. computer? Non-exchange, that is