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?