Server 2003 DC Failover setup


We currently have 1 x DC on server 2003. We would like to have a failover DC on another server. could anyone explain the implications of doing this.

i.e. is there any clustering software needed? Is there a license implication? Which DC taking priority?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Pete LongTechnical ConsultantCommented:
Simply promote another member server to be a domain controller

Start > run > dcpromo {enter}

>>s there any clustering software needed?

>>Is there a license implication?

Not if the server you are promoting  already has a CAL

>>Which DC taking priority?

The model is multi master, but the first server will retain the FSMO roles unless you move them.

Nick RhodeIT DirectorCommented:
Steps for a 2nd DC:

You would have to purchase a server license.  It is actually pretty simple to add a 2nd domain controller and gets even easier with 2008 and 2012

Just don't forget to add the Secondary DNS to point to the backup domain controller to the DHCP scope
MAS (MVE)EE Solution Guide - Technical Dept HeadCommented:
You could install an additional DC which needs only one windows server license.
and Microsoft strongly recommends to have an additional DC in a network

You have to run these commands to install windows2008
adprep /forestprep and adprep /domainprep
Please check this as well
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Brian PiercePhotographerCommented:
Its quite simple:
You need another 2003 (or later server and licence)

Install Windows on the machine add it to the domain

Run DCPROMO on the new machine and promote it to be a DC.

Add the Global Catalog and DNS roles to the new DC

If you are using DHCP add DHCP to the new DC

If you are using DHCP configure the old and new machines to have complimentary but none overlapping scopes - eg.
DC1 - Scope -
DC2 - Scope -

Set the DCHP options on both machines to give the IPs of DC1 and DC2 as DNS servers

For any static IP machines configure DC1 as the preferred DNS server and DC2 as the alternate DNS server.

On the DC1 set the static IP config to point to DC2 as its preferred DNS server and to itself as alternate DNS server.

On the DC2 set the static IP config to point to DC1 as its preferred DNS server and to itself as alternate DNS server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
unrealone1Author Commented:
Ok thanks I get the secondary config thats neeeded. What needs to be done as far as intergration with exchange 2010 goes?
Nick RhodeIT DirectorCommented:
Nothing, When you join the 2nd DC it replicates the AD settings and everything so exchange is tied to AD which will be replicated to the 2nd DC.  Do you have exchange 2010 in your environment now?  If you don't and plan on installing it I would setup/install 2008 R2 or later
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.