|
You don't have to transfer FSMO role to a different DC if you are not performing activities like Schema modification/update, Exchange installation, Domain update etc..
But here are the best practice recommendations for FSMO role optimization:
http://support.microsoft.com/default.aspx?scid=kb;en-us;223346&sd=tech
HTH
Santhosh
Santhosh Sivarajan
MCSE(W2K3/W2K/NT4),MCSA(W2K3/W2K/MSG),CCNA
Houston, TX
On 11/29/05, Craig Cerino <ccerino@xxxxxxxx> wrote:
Amy,
If it's what you need to hear (for peace of mind – or reassurance) leave the FSMO roles where they are - you'll be fine. You don't need to transfer the rolls if your talking about a timeframe of 2 hours - - -when you bring it back on line - -I would just leave the other DC online for at least and hour (unless you have adjusted the replication intervals) to make sure any changes are replicated.
We have two DC's, one which holds the Forest FSMO roles, the other which holds the domain FSMO roles.
I plan to take each server down at different times so that one of the two servers can provide authentication etc while the other gets maintained.
Initially, I was planning on moving the FSMO roles to the other DC while maintainance work is carried out and transferring it back once it's online again. I would then do the same for the other DC.
I was then told that you don't need to move the FSMO roles when you perform maintenance on a DC holding the roles. Each server will be down for about 2hrs.
Does anyone have advice for me? I would like to move the roles for peace of mind knowing they are available, but if I don't need to do that, I won't bother
Is there any recommended practice?
To help you stay safe and secure online, we've developed the all new
Yahoo! Security Centre.
--
Santhosh Sivarajan
MCSE(W2K3/W2K/NT4),MCSA(W2K3/W2K/MSG),CCNA,Network+
Houston, TX
|
