Reboot order of servers

[KashMarsh]

We have a primary and secondary server. What happens if they get rebooted out of order? We have MS Server 2003.

Primary got rebooted first while the 2ndary was sill running. Does this automatically promote the 2ndary as the primary?

I always tought the 2ndard needs to come down first all the way down. Then bring down the primary. Then bring up the Primary first, wait until it is fully up and then bring up the 2ndary.

Thanks in advance, I know this should be basic knowledge but I have been away from OS for so long now.

 

[cdtech9198]

Not sure what you mean by primary and secondary. Are you taking about domain controllers or clusters?

 

[KashMarsh]

Domain Controllers.

 

[technome]

There is no promotion involved. If you shut down the FSMO and bring up other AD DCs first, if correctly setup, you should be able to login to an AD network, with a small delay in some cases involving the DNS preferred server choice, again dependent on the setup. Aside from a few errors in the eventlogs, your users will be able to access the network if the "secondary" server comes up first, no harm done.



........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[KashMarsh]

OK great. I guess my next question is going to be, how do you know if it is "correctly setup"?
Thanks in advance.

 

[technome]

Download the windows support tools.....

http://www.microsoft.com/downloads/...B3BE-4E7AC4F0912D&displaylang=en#RelatedLinks

Run Netdiag.exe and DcDiag.exe in verbose mode. 95% of the errors in a simple AD setup will be picked up by these two utils; most intial errors are generally related to DNS misconfiguration.

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm