• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 290
  • Last Modified:

Planned System Shutdown. Two DCs and two Member servers (2003 DOMAIN)


I'm planning on shutting down my network for some planned office maintenance.

What order should I shut down the servers and how should i boot them back up again??

Two DCS. One with Exchange and the other with SQL.

Two member servers (print,backup servers, etc)

I need to check which DC is GK (Maybe both) and I've yet to check which server has which FSMO roles.... However, how should I proceed?
1 Solution
Start the one with AD and DNS first.
You can check FSMO roles by running "netdom query fsmo" from command prompt on your DC.
Short guide how to identify GC via command line: http://www.websense.com/support/article/kbarticle/How-Do-I-Find-a-List-of-Global-Catalog-Servers-Using-nslookup

I would go for shutdown with following order; member server, DC, DC (fsmo holder)
Power up: DC (fsmo holder), another dc, member servers

DC order might be bit different, depending on how FSMO roles are split,  how DNS is used etc...
I think you mean GC (global catalog).  The DC boot order really doesn't matter.  There's no service at startup for the DCs that will not fix itself once the other DC is back online.  If you need to maintain authentication services, do one DC at a time, making sure one of them is always online.

As for the member servers, Exchange should be done while the global catalog server is online.  Worst case scenario, you boot exchange up while the GC or DC is offline and a service fails to start.  You should be checking those services anyways and the service should start just fine after the DC is back online.
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Nick RhodeIT DirectorCommented:
Typical order is

Shutdown = DC's Last

Startup = DC's 1st (primary DC then Secondary DC)

Since you have SQL, fire that one up next and then fire up the other servers connecting to it.
Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:

To determine FSMO and all other roles, perform the following

1.Click Start, click Run, type dsa.msc, and then click OK.
2.Right-click the selected Domain Object in the top left pane, and then click Operations Masters.
3.Click the PDC tab to view the server holding the PDC master role.
4.Click the Infrastructure tab to view the server holding the Infrastructure master role.
5.Click the RID Pool tab to view the server holding the RID master role.


I have done this several time during various DR testings that I have carried out, you are very lucky that your network is not so complex.

Shutdown procedure, assuming all clients has been shutdown

1.Shutdown the two member servers (print,backup servers, etc)
2. Stop and set to manual all the Exchange and SQL services
3. Shutdown the two DCs order does not matter

Restart procedure, just reverse the shutdown procedure
1. Startup the two DCs, order does not matter
Wait for about 15mins, check event logs
a.Run replmon or repadmin /showrepl,
b. Run dcdiag /v and netdiag /v
If everything okay with AD services proceed to step 2
2. Start the Exchange Services and set back to Automatic (Check event logs for any error)
3. Start SQL services and set back to Automatic (Check event logs for any error)
4. Start the two member servers -- check the services and the event logs)

Perform some basic testing.
a. All computers can see each other
b. that exchange is sending and receiving email
c.  You can connect to database, ODBC test is enough
d. Print test
e. All other related function.

Note Step 2 and 3 above can be interchange.
APC_40Author Commented:
Very helpful
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now