Re: Making the active directory redundant
- From: "Don Wilwol" <donWilwol@(EMAIL)yahoo.com>
- Date: Sun, 7 May 2006 18:42:21 -0400
you need the seize the roles, only after the failure. This should help
explain.
http://spaces.msn.com/wilwol/blog/cns!5FFF892E00A8D9E5!108.entry
--
--------
Hope It Helps!
dw
_______________________________
Don Wilwol
Distributed Application Technologies.
dwilwol(DELETE)@datbusiness.com
www.AtTheDataCenter.com (personal website)
www.skysphere.com (hosting available)
"inadmin" <inadmin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:362BB47C-1813-4BFB-AEE2-A2CC2E0B0E11@xxxxxxxxxxxxxxxx
So I do not need to do anything else?
"Joe Richards [MVP]" wrote:
FSMO roles do not move transparently, however, unless you have legacy
clients on
the network FSMO role tranfer doesn't have to happen immediately anyway
(in most
cases it could be hours or days or even weeks that roles have to move).
joe
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
inadmin wrote:
Hi,
I have two windows 2003 domain controllers, both are global catalogs. I
think that I need to perform one additional step in order to make sure
that
in case DC1 fails (which holds all the FSMO roles) DC2 take its place
and
that it will be transparent to the users. What am I missing?
Thanks in advace.
.
- References:
- Re: Making the active directory redundant
- From: Joe Richards [MVP]
- Re: Making the active directory redundant
- Prev by Date: Re: integration of new servers on a network...
- Next by Date: Adding a raid to a Windows 2000 server
- Previous by thread: Re: Making the active directory redundant
- Next by thread: Re: Making the active directory redundant
- Index(es):
Relevant Pages
|