Improve company productivity with a Business Account.Sign Up

x
?
Solved

Why is the Microsoft Exchange Migration tool sending mailboxes to a database other than the one I select?

Posted on 2015-01-18
4
Medium Priority
?
62 Views
Last Modified: 2015-05-19
When using the MS Exchange Migration tool through the Exchange Admin center (http interface) to move mailboxes, the migration tool sent the mailbox to a completely different database than the one selected.  We have three databases, db1, db2, and spamdb.  We are moving servers to a datacenter offsite.  DB1 and SPAMDB are local to each other (i.e. on the same server) and DB2 is the datacenter.  All mailboxes are on DB1.

When I migrated mailboxes to DB2, some actually went and others went to the SPAMDB.  Now, when I individually select the mailboxes in SPAMDB to migration to DB2, it tells me it migrated fine but I look and they're all still on SPAMDB.

Any suggestions?
0
Comment
Question by:jhudson1977
  • 3
4 Comments
 
LVL 4

Expert Comment

by:pcmghouse
ID: 40556912
can you please check if you have the database excluded from provisioning. manual moves should work but there is a bug.
get-mailboxdatabase db2|fl isexcludedfromprovisioning
0
 

Author Comment

by:jhudson1977
ID: 40556976
I guess I have another issue I need to figure out first.  I ran the above command and got:

"The operation couldn't be performed because object 'db2' couldn't be found..."
0
 

Accepted Solution

by:
jhudson1977 earned 0 total points
ID: 40558780
Well, to fix this, I did a crash course in EMS.

I first found out that all of the move requests were getting in the way so I removed all of those using:
     "get-moverequest -movestatus completed|remove -moverequest"

Then, I did a batch move of all mailboxes in "spamdb1" back to "db1" by:
     "get-mailbox -database spamdb1|New-moverequest -BatchName "WhateverINamedIt"

Then, I did another clear of all the move requests using the commands from step 1.

I guess this was set to simply move back to the database on the local server as I didn't specify "db1".  So, in hindsight I would probably specify the target database next time (see command set below).

But, when that was all done, I went to the Exchange Admin Console (web interface) and validated that it saw everything where it was supposed to be.  Then, for giggles, I tried another migration of five small mailboxes using this interface.  It got all wonky again.  So I decided I would use the EMS again for the batch move.

I did one mailbox just to make sure I had the command correct (and it worked) and then went for the whole banana tree using:

     "get-mailbox -database db1|New-MoveRequest -TargetDatabase db2 -BatchName "WhateverYouWantToCallIt"

Everything queued up and the first three moved fine.

So, I guess the moral of the story is learn and use EMS because outside of learning the syntax, it gave me zero headaches.
0
 

Author Closing Comment

by:jhudson1977
ID: 40784721
I accepted my comment as the solution because it worked.  Not sure what else to say.  I included all the code I used in PowerShell to assist others who might run into this issue.
0

Featured Post

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

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Are you in the migration process of your Exchange to Exchange Online? Be aware of customized solutions developed on the transport role on your old Exchange server. They might not be convertible to Exchange Online!
This is a very interesting topic. Ransomware has been around for a while but has increased drastically over the last year or so.
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
To export Lotus Notes to Outlook PST or Exchange and Domino Server files to Exchange Server or PST files with ease, go for Kernel for Lotus Notes to Outlook conversion tool. Through the video, you can watch the conversion process. A common user with…

589 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