jhudson1977
asked on
Why is the Microsoft Exchange Migration tool sending mailboxes to a database other than the one I select?
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?
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?
ASKER
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..."
"The operation couldn't be performed because object 'db2' couldn't be found..."
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
get-mailboxdatabase db2|fl isexcludedfromprovisioning