The roaming profile is easy to change on a per-user basis, but the folder redirection path is set in GPO and is a little trickier to test on a small scale.
-----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2008 11:01 AM To: NT System Admin Issues Subject: Re: Problems using alias for server? On Mon, Nov 17, 2008 at 10:04 AM, John Hornbuckle <[EMAIL PROTECTED]> wrote: > One other question on this... If I create a DFS target pointing to the > existing share and then reconfigure group > policies and profiles to point to the DFS path instead of \\server\share, > that should be totally transparent to > users and their computers, right? At least theoretically? I believe so. Always worth testing, and this one is pretty easy to test, since you can override it on a per-account basis with ease. One thing worth noting: As I recall, the path used for the roaming profile is looked up only at logon. So if a user logs on and you then change the roaming profile path in their account, that logon session will still use the old path at logout. This shouldn't matter for the scenario described above, but if you're actually changing servers it can. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
