Follow up to Dfs and romaing profiles...

[corn29]

Hello,

I couldn't post a reply to the original March 18 thread from Google so
here goes...

1. Struggling with some concepts here... I'm running W2K and I have
two DCs. We have some requirements for fault tolerance so that if we
lose DC1, we can still authenticate on the domain because DC2 is also
a Global Catalog Server.

2. In such a scenario, the roaming profiles are stored on DC1 and
wouldn't be available. There would be a time out period and the user
would receive a window that pops up and says the roaming profile
couldn't be located and they're using a profile where and changes made
are lost at logoff.

3. So, we could make a Dfs/replica of the roaming profiles. Let's
say for the sake of argument, both DC1 and DC2 have a folder called
c:\profiles and the profiles are replicated between both of those
folders. This is what my Dfs MMC looks like:

Root

domain.local\profiles
|_Profile Link
|_\\DC1\profiles
|_\\DC2\profiles

4. But that still doesn't resolve anything... in the ADUC user's
properties, where the path and drive for the profile is entered, what
the heck would go in there then? If you put in c:\profiles\username,
it's referring to DC1 right? Then let's say we lose the DC1. How
would the system know to get the profile from DC2?

Thanks,

--CW

 

[Jerold Schulman]

How about:

\\%Logonserver%\Profiles$\%UserName%

where ProfileS is the share on DSC1 and DC2 that points to the profiles folder.

When the user logs on, the profile will be sourced from the authenticating DC.

Hello,

I couldn't post a reply to the original March 18 thread from Google so
here goes...

1. Struggling with some concepts here... I'm running W2K and I have
two DCs. We have some requirements for fault tolerance so that if we
lose DC1, we can still authenticate on the domain because DC2 is also
a Global Catalog Server.

2. In such a scenario, the roaming profiles are stored on DC1 and
wouldn't be available. There would be a time out period and the user
would receive a window that pops up and says the roaming profile
couldn't be located and they're using a profile where and changes made
are lost at logoff.

3. So, we could make a Dfs/replica of the roaming profiles. Let's
say for the sake of argument, both DC1 and DC2 have a folder called
c:\profiles and the profiles are replicated between both of those
folders. This is what my Dfs MMC looks like:

Root

domain.local\profiles
|_Profile Link
|_\\DC1\profiles
|_\\DC2\profiles

4. But that still doesn't resolve anything... in the ADUC user's
properties, where the path and drive for the profile is entered, what
the heck would go in there then? If you put in c:\profiles\username,
it's referring to DC1 right? Then let's say we lose the DC1. How
would the system know to get the profile from DC2?

Thanks,

--CW

Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com

 

[corn29]

Thanks for the reply... about an hour after I posted this, the
lightbulb in that imaginary cloud over my head finally burst and I saw
the light.