Exchange 2007 Mailbox/Database Question (moving mailboxes between DBs)

I have a very unique situation and I want to know the ramifications prior to doing something that could cause issues down the road.

We are an Exchange 2007, single server environment with all updates and Service Packs.  We have 5 DB Groups.  One of those DB Groups has 4 DBs.  3 of those DBs are dismounted due to corruption.  1 has been repaired and is working fine.  We are in the process of repairing the other DBs, but the repair time is extremely long and I have about 10-15 VIPs that I need to get up ASAP.  Here is my question...

If I disable a mailbox from a dismounted database, I can then create a mailbox for that user on the mounted database.  I can then convert that user's OST to PST and import that data into the mailbox and get the user up and running.  I have tested this in a lab so I know it works.  

My concern is what will happen when the corrupt DB with that mailbox is repaired and is then mounted?  Will there by any issues since that mailbox was disabled from the EMC and a new mailbox added to another DB?  Or will Exchange recognize that the mailbox was marked for deletion?

Thanks in advance.
Chris BabcockDirector of Information TechnologyAsked:
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.

Well, easy answer is if you have a lab setup already, test it.  Create 2 DBs.  Add a user to one of them.  Send some mail to the user.  Dismount the user's DB.  Disable the mailbox.  Create mailbox on the other mounted DB.  Export the OST.  Import to new mailbox.  Mount the dismounted DB.  

I think since AD is used to keep track of these changes it will work fine, however doing the above would give you the answer you are looking for.  Never had to do this myself.

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
MASEE Solution Guide - Technical Dept HeadCommented:
If you disable the user from the mounted database and connect a mailbox from a repaired database will give you a bounce back email "Delivery has failed to these recipients or groups ........ RESOLVER.ADR.ExRecipNotFound; not found ##"
You will have to clear the user from the cache and send again as a new user.
AmitIT ArchitectCommented:
I suggest to continue with the repair.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

MASEE Solution Guide - Technical Dept HeadCommented:
Agree with Amit
MAS brings up a point I had forgotten.  The Outlook autofill entry will need to be deleted on any system internally that had sent to that address previously, otherwise it will indeed cause the email to bounce.  This is due to Outlook seeing both users as being different people even though it is the same name.
imkotteesSenior Messaging EngineerCommented:
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.