Solved

Exchange MOVE mailbox broke my mailbox

Posted on 2008-10-20
9
598 Views
Last Modified: 2012-06-21
Used the built in Move mailbox option in Exchange Tasks.   After the move, it left a duplicate in the original store.  So I right clicked the mailbox and it deleted the mailbox.  But my "Keep mailbox for" setting on the mailstore was set to 30 days.  I changed the setting to 0 days and after running cleanup agent on the mailstore it still won't let me deleted it.
NOTE: After running RUS it allowed me to purge the old mailbox.  But still the new mailbox is not attached to the user in AD and the users AD Exchange Tasks shows "Create" as an option which leads me to believe no mailbox is attached to that account.  MOVE MAILBOX stinks!!  Why doesn't this work?

NOTE:  In mailbox store 2, I have no options when right clicking the new mailbox to reconnect to a user.  Everything is greyed out...

If I understand the situation correctly, AD is confused and the user account needs to be attached to the new mailbox that was created in the second mail store which is sitting out there not collecting mail.  In the meantime the old mailstore is collecting all new mail for the mailbox.  

Thoughts?

Dave
0
Comment
Question by:dlabbadia01
  • 5
  • 4
9 Comments
 

Author Comment

by:dlabbadia01
Comment Utility
More info:

This is the same user in the same domain on the same exchange server.  Was just moving between two mailstores!!
0
 
LVL 19

Accepted Solution

by:
MrLonandB earned 250 total points
Comment Utility
Let's take the old mailbox first. Find out which user account is attached to that mailbox. Once found, go to that User's account in AD Users and Computers, right-click the account, run the Exchange Tasks and choose to delete the mailbox. It won't really delete the mailbox of course,,,it will just detach the User Account from it. Then create a new user account in ADUC...without an Exchange Mailbox. Once the account is created, go to Exchange System Manager and run the RUS and mailbox cleanup agent again for good measure. Right-click that old mailbox and connect it to new user account that you created.

The new mailbox. Find the user account that is attached to the mailbox and delete the mailbox from the User's properties just as you did with the old mailbox. Run the mailbox cleanup again in ESM and connect the correct user account that you want attached to the new mailbox and make sure that User Account has the email address assigned to it that had been previously used with the old mailbox. Next...

Go to the properties of the new user account that you had created earlier. Under the "Exchange Advanced" tab > Mailbox Rights...give the User Account that is now associated with the new mailbox...full access to that mailbox. Then...

Have the User Account that is assigned to the new mailbox, log on to a computer and create an Outlook profile. Once the Outlook profile is created, in Outlook, go to: File > Open > Other Users Folder. Move any of the old mail from that old mailbox...into the Inbox of the Outlook profile. That old mailbox should no longer be receiving mail, the new mailbox will be receiving it and you will have all the old mail recovered.
0
 

Author Comment

by:dlabbadia01
Comment Utility
Thanks for the information.  I managed to actually get this to work by following a similar set of steps.  What I need to know now is what the BEST way to move a mailbox is.  Like the exact sequence of events.  I don't want the user to see any downtime or any mails to get lost.  The steps I took caused an outage for the user for about a half hour.  

Go to mailstore 1, find user mailbox and choose Move Mailbox and opt to move it to mailstore 2.
After all the files move over I am left with two mailboxes, one in mailstore1 and one in mailstore2.
At this point, Outlook doesn't connect successfully, neither does OWA.  
What is the correct next step to get rid of the mailbox in mailstore 1 and connect the user to mailstore2.

I actually accomplished this the other day by just trying to MOVE the mailbox back to mailstore 1.  It said "the mailbox already exists, deleting existing mailbox" or something of that nature and BAM, everything starting working in mailstore 2.  And the mailbox in mailstore 1 was gone.  

Then I figured just deleting the mailbox in mailstore 1 would do the trick.  But it didn't.  Perhaps it's a lag in time from how fast AD catches up with the changes made in Exchange but any assistance would be handy.

Moving mailboxes on SAME Exchange 2003 Enterprise server just between two mailstores.  

AD is local to this machine's LAN.
0
 
LVL 19

Assisted Solution

by:MrLonandB
MrLonandB earned 250 total points
Comment Utility
When you do the move...give it some time. Run the RUS afterwards and then the mailbox cleanup agent if needed and the mailbox should no longer be there. It takes a few minutes for Active Directory to update the User's properties to reflect that his mailbox is now located in another store.
0
Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

 

Author Comment

by:dlabbadia01
Comment Utility
OK.  I was under the impression that it was seemless to the end user.  But during this time it takes for the mailbox cleanup agent and RUS to run, the Outlook doesn't connect.  Is this expected?  Thanks.

Dave
0
 

Author Comment

by:dlabbadia01
Comment Utility
Also during the move, the outlook was inaccessible as well.  For a 4 GB mailbox this is a problem as the move is going to take awhile.  Sorry if I seem confused.  Just trying to weigh my options.

Dave
0
 
LVL 19

Assisted Solution

by:MrLonandB
MrLonandB earned 250 total points
Comment Utility
If I needed to move a mailbox and time was an issue, I would go to ADUC, right-click the User Account, select "Exchange Tasks" and move the mailbox from there.
0
 

Author Comment

by:dlabbadia01
Comment Utility
I didn't even know that was an option.  I will give it a try.  Thanks for all your help.

Dave
0
 
LVL 19

Expert Comment

by:MrLonandB
Comment Utility
You can do it either way and there was nothing wrong with your steps before...you had it right. It looks like the AD was not updated very quickly and that's why thought it didn't work correctly.

You can probably close this out.
0

Featured Post

Do email signature updates give you a headache?

Do you feel like all of your time is spent managing email signatures? Too busy to visit every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

6 Experts available now in Live!

Get 1:1 Help Now