Reconnecting Exchange 2003 to a failed domain controller

We recently had our primary domain controller fail.  We replaced it with a new server running the same operating system as before.  We recreated the user ID's and Passwords for the domain.  We restored the data to the new server.  Since our Exchange 2003 box was a member server of the old domain how do we reconnect the exchange box to our system?  I dont want to remove it fromt he doamin until I am sure taht we will not lose any data.
Ray McGowanConsultantAsked:
Who is Participating?

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

x
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.

Neil RussellTechnical Development LeadCommented:
How did you create the new domain controller? From a system state backup of the old server? Or jus by installing AD and giving the same name as the old server/domain?
dphantomCommented:
The link below may also be helpful depending upon how you restored/recreated your AD.

http://support.microsoft.com/kb/906154
AmitIT ArchitectCommented:
It seems this server also holds FSMO roles. The best option here is load the Exchange again with DR switch.  Steps are easy
http://www.msexchange.org/tutorials/Recovering-Failed-Exchange-2003-Member-Server-Using-Disaster-Recovery-Switch.html
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Ray McGowanConsultantAuthor Commented:
We created a new AD server with the old name.
dphantomCommented:
well that is why Exchange is not working.  You have new SIDs, accounts etc.  The forest and domain prep have not been run so the schema is not ready for the Exchange server.

The above procedure should work.  Hopefully you have good backups of your Exchange mail.  You will need them to do a restore at the end of the recovery period.
dphantomCommented:
edit my post above.  that procedure will NOT work.  It assumes AD has not been touched.
AmitIT ArchitectCommented:
As you created new AD server, now the next option for your to mimic the old Exchange step and then restore date from the backup. For this you need to use the legacyexchangedn tool, note these are advance steps and required high level exchange expert.

If you have Microsoft support, call them.
AmitIT ArchitectCommented:
Forget to post the link, here is the tool details, you need to read the legacyexchangedn tool section. This kind of scenario is used mainly for public folder restore. But you can use it for mailbox db also. Also wait for other EE's to reply, if they have any other suggestions.

http://www.msexchange.org/tutorials/Understanding-LegacyExchangeDN.html

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
Neil RussellTechnical Development LeadCommented:
If you created a new domain then your in do-do!!
Did you not have a system state backup of the old domain? Did you ONLY have a single domain controller?
Ray McGowanConsultantAuthor Commented:
The original DC failed.  We installed a new system, reloaded Server 2003 and created a new domain.
AmitIT ArchitectCommented:
As old dc is gone, that means users are also gone. Buy 3party tool like edb to pst and merge the data.
DaveCommented:
" We recreated the user ID's and Passwords for the domain."

You can't, yes the names will be the same, but every user has a SID which will be different, and Exchange knows its different. Can you confirm you only had one DC? Are you sure you have no remenants, copies or backups of the DC anywhere?

In addition the exchange config is stored in AD so you have lost that as well. You need a tool to export the mail from the mailbox database EDB files to PST files with no AD in place. Make sure you copy your Exchange EDB before starting. Some tools I found which may work:-

http://www.quest.com/recovery-manager-for-exchange/

http://www.edb-pst-converter.com/buy-edb-conversion-software.php

http://www.lucid8.com/pricing/pricelist_digiscope.asp

http://www.unistal.com/exchange-recovery-tool-buy-now.html

http://www.krollontrack.com/information-management/email-management-for-exchange/

I haven't personally tried any of the above. The Quest tool is often praised in other forums, but it may be too expensive for your use. Once you are happy you have the mail backed up in PST files the you will need to re-install exchange from scratch, mail-enable the new users, and import the PST files.

Good Luck.
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
Web Browsers

From novice to tech pro — start learning today.