Proper steps to bring Domain Controller back online within the WAN - DC was offline for 5 weeks.

A recent hurricane tore up one of my facilities over a month ago.  Since then the domain controller has been offline and users have been working of their local machines from home.

Next week I have to bring this network back up and I'm concerned about the domain controller.

I'm looking for the best approach  to bring this back online.  Note, this is a WAN that replicates to other DC's across the state.
sknoll84Asked:
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.

SysExpertCommented:
I think that a long as you have not changed the default 90 day AD expiration, you should be fine.

Just put it on the WAN and force a replication of AD.


I hope this helps !
0

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
Joseph DalyCommented:
I think you should be alright to just bring it back online cause it was only offline for thirty days. If you are truly that concerned you may be able to take a system state backup from one of your DC's that has been running correctly and using directory services restore mode load that data into your DC that was powered off.

To me that seems a little overkill as said above just turn on the DC and make it replicate to an up to date DC. The up to date DC should be the authoritative memeber in the replication.
0
Brian PiercePhotographerCommented:
You MUST check the tombstone setting - is normally either 60 days or 180 depending on the version of AD. - Check with this command

dsquery * " cn=Directory Service,cn=Windows NT,cn=Services,cn=Configuration,dc=<ForestRootDN>" -scope base -attr tombstonelifetime

If the server has been down for LESS than the tomstone period then no issues
0
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.

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.