Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

How do I demote a Windows 2003 Domain Controller?

Status
Not open for further replies.

shadowfax1066

Technical User
May 10, 2004
103
GB
Hi, we have 3 Windows 2003 DC's, I need to demote one back to a member server. How do I do this and make sure all the metadata is all "clean"?
 
From the console of the server run dcpromo and walk through the wizzard to demote it.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

[noevil]
(Not quite so old any more.)
 
great post!!!

I have additional questions...

I need to do the same. However the server I need to demote is also a DNS server (its in another location) used by 10 other member servers.

I plan on demoting server2 then promoting server3. If I perform this action then update each member server DNS server entries and reboot... Should I be okay?

Would you do it a different way?

Mark C.
Network Admin - Digital Draw Network
 
I'd promote server3 first. Put DNS on it, move over the servers to it. Then wait a day to let AD settle back down, then demote server2.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
okay, that does make more sense...

thanks Denny.

Mark C.
Network Admin - Digital Draw Network
 
One more question... A little background on my network first.

Corp office - 1 DC (name=corpserver1). Handles all AD, DNS and DHCP request for corp office network (10.0.0.1)

Collocation - 2 DC (name=server1 and server2). They handle AD and DNS for all member servers at collacation network (10.0.1.1)

I want to replace server1 and server2 with server3 and server4. I have already demoted server2.

My objective is to have any member server in the collocation to look at server3 first for AD, DNS information and if it cant find that server, look at server4.

Questions?????

1. will in need to promote server3 and server4 in any particular order or can I modify roles afterwards?

2. what roles should I make all servers in corporate and collocation?

3. when setting up AD and DNS on server3 and server4, should I be aware of anything?





Mark C.
Network Admin - Digital Draw Network
 
As far as I know there isn't any way to tell the machines which server to look at first. They will look at which ever server DNS tells them to look at.

Role placement will depend on which servers you want to perform those roles. If you'll be creating most of the objects in AD on the office DC then you'll want the RID master at the office, etc.

There shouldn't be any thing special to worry about when setting up AD and DNS.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)
[noevil]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top