Windows Domain Controller -- RESTORE ?

I have three sites, with a Windows 2003
DC at each location, that replicates from
site-to-site and might have lost one site
that have no good backup tape.

Can I drop a fresh Windows 2003 DC at that
location and have it get updated via the
other locations that are still working ?

I will then upgrade everything to
Windows 2012 after this 2003 issue
gets stable.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Thomas GrassiSystems AdministratorCommented:
Which dc owns the ad roles?

If the dc that failed had any roles then you need to force the roles on to one of the other dcS

After that demote the dc

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
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
If the failed DC holds the FSMO rights then you could seize it at one of the other DCs. I assume the failed DC is not operational and if that is the case then simply power it off and disconnect from the network.  Install a new DC and use a different name. Prior to the DC installation I suggest you do meta data cleanup.  Below is a link for it:
Will SzymkowskiSenior Solution ArchitectCommented:
If you can demote this DC gracefully then do it, if not you will need to do a dcpromo /forceremoval. If this DC holds any of the FSMO roles you will need to Seize the roles to another domain controller. Once you have this DC demoted perform metadata cleanup and in the mean time point your clients at the site with the failed DC to another geographical close site for DNS. You will then be able to authenticate from the other site and this will get you back up and running until you have another DC in the site.

If you have Exchange in this environment and you only have 1 DC then you will need to add another DC to this site. If Exchange is not envolved then do not worry about this.

Seize in this context means a forced transfer of the FSMO roles.
I would actually never recommend to do this if this is not necessary.
Just try a normal transfer of the FSMO role first before thinking of seizing the role. So if the problem DC was holding a FSMO role and it's somehow possible to bring it back I would first look into that.
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
Active Directory

From novice to tech pro — start learning today.