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

How do I promote a win2003 dc to primary?

I have a Windows 2003 Standard R2 Server that is presently AD, DNS, DCHP, Exchange 2003 Std, Veritas Backup Exec, Print Serving, and File Serving and recently recovered from a system failure. This finally convinced my boss to buy me 4 servers to separate all these services off of this one machine.  I have built a server running windows 2003 std r2 so that i can dedicate it just to AD. what steps should I take to promote the new one and demote the old one?
2 Solutions
Lee W, MVPTechnology and Business Process AdvisorCommented:
Don't do it.  You should NEVER promote or demote a server that is running Exchange - doing so can break exchange.

My recommendation would be this:
New Server 1 - Exchange (migrate from the first server to here)
New Server 2 - Backups/DC/DNS
New Server 3 - File and Print
New Server 4 - DC/DNS/DHCP

LAST step is to demote the old system, moving the FSMO masters off the current DC.
I agree with LeeW, its much better not to have Exchange on a DC.
By all means have at least one additional DC but keep keep DCs and Exchange apart.

If you want to make another machine a DC then the process is:

Install Windows 2003 on the new machine

Assign the new computer an IP address and subnet mask on the existing network
Make sure that the preferred DNS server on new machine points to the existing DNS Server on the Domain (normally the existing domain controller)

Join the new machine to the existing domain as a member server

From the command line promote the new machine to a domain controller with the DCPROMO command from the command line Select "Additional Domain Controller in an existing Domain"

Once Active Directory is installed then to make the new machine a global catalog server, go to Administrative Tools, Active Directory Sites and Services, Expand ,Sites, Default first site and Servers. Right click on the new server and select properties and tick the "Global Catalog" checkbox. (Global catalog is essential for logon as it needs to be queried to establish Universal Group Membership)

Make sure the new DC is also a DNS server, install DNS. Assuming that you were using Active Directory Integrated DNS on the first Domain Controller, DNS will have replicated to the new domain controller along with Active Directory.

You can also install configure and authorise DHCP on the new server, make sure that you use scopes that do not overlap.

All the clients (and the domain controllers themselves) need to have their Preferred DNS server set to one domain controller, and the Alternate DNS to the other, that way if one of the DNS Servers fails, the clients will automatically use the other - this some will machines will need this setting in the TCP/IP properties of the NIC, others will need to have it set via the DHCP options.

Both Domain Controllers by this point will have Active Directory, Global Catalog, DNS and DHCP. If any machien were to fail then the other could provide all the network services required for logon and authentication.
gserlisAuthor Commented:
Hey Guys,

I really appreciate the prompt response on this.  I'll get on it as soon as I get those servers in which should be monday or tuesday and start with that and let you guys know.

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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