Exchange 2010 Removal of 1st Server

Hi All,

Here is my situation, I inherited a bunk exchange deployment of a single server. The bad part is that it was never migrated correctly from 2003 and the domain controller crashed.

Here is where i am at:

- Recovered old crashed domain controller to new server (Everything is fine here)
- Manually removed all instances of the botched old legacy exchange 2003
- Setup new Exchange Server 2010 with different name and IP

I have the new server setup and servicing our employees without issue. I was able to migrate all the mail accounts except for the 3 system mail accounts and public folders using local move request.

Not worried too much about the Public Folders as we dont use them so I figure after cleaning this mess up I can re-create them. The MAJOR problem that i have is that the Mailbox Database that contains the 3 system accounts Arbitration ect, is offline and for the life of me I cant get the database to mount. After hours of research, I found that it may be due to the issue of it was originally created with the failed DC. Checking the date stamp on this db, it hasnt had any changes since 2011 which leads me to believe that the migration from 2003 to 2010 didnt go well for the guy before me and he got enough going to make it work then gave up.

So back to my question: I have the two sservers, ill call them old and new. The old is the old 1st exchange 2010 server SP1 and the new is just that the new one that is serving the employees, exchaneg 2010 SP3 . . .

How in the world can i get rid of the MailboxDatabase on the old server so that i can cleanly remove it from ad and then re-create the system boxes ect? I would like to get the New server setup nice and clean so that I can move to exchange 2013. I have searched and found a couple of ways but would like to know what you would recommend.

I was thinking doing the following:

- adsi edit and manually remove the mbdb and then try to un-install exchange and then run adprep on the new exchange server?
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.

Scott GorcesterCTOCommented:
How many users in this domain? It might be easier to cut your loses and build a new domain. This method insures you will not have garbage in the AD.

CCSNVAuthor Commented:
I have about 280 users total. Would be a big hassle i think to re-create although the thought is still there.
Scott GorcesterCTOCommented:
It might be worth opening a support case with Microsoft to assist you in removing the objects and cleaning up the Exchange objects in the current domain.

Zacharia KurianAdministrator- Data Center & NetworkCommented:
Well, your situation can not be predicted for a better less damage results. The options you can try are;

1. Get a professional support from a reputed vendor in your local.
2. You could try the following paid tools, if your IT budget allows you so;


b) For easy migration you could try using;


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
CCSNVAuthor Commented:
Well, just went for it. What I did was use ADSI edit to remove the database from the exchange server, then was able un-install the exchange.

Ran prepare ad on the new server and it re-generated all of the system mailboxes that were needed. Re-created the PF database and used systools software to recover the mailboxes that I wanted to keep out of the offline database that i manually removed.

I also went through via adsi edit to ensure the old server was not lingering.

I then went one step further and without any major issues was able to migrate to Exchange 2013.
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

From novice to tech pro — start learning today.