Exchange 2010->2016 migration - Discovery Search Mailbox
Hi,
I have finished migrating all of my mailboxes over from Exchange 2010 to Exchange 2016.
THis morning I noticed there was a "Discovery Search Mailbox" in one of the databases in Ex2010 that threw an error saying it was corrupt and couldn't move. However, the Database that particular Discovery Search Mailbox is in, was never used by any mailboxes.
So my question is, do I need to worry about this MB? Can I just ignore this message and not try to move it over?
I had already run a move request to move over all Arbitration mailboxes and it was successful. Is this a type of Arbitration Mailbox?
Another question, does each DB created on an Exchange server get a Discovery Search Mailbox created?
Here is the error I get in EMC about this MB.
------------------
The object XXXXXXX.lcl/Microsoft Exchange System Objects/SystemMailbox{B2F3
Database is mandatory on UserMailbox.
---------------
If I run a "Get-mailbox -Monitoring" I get the following (See attached). All seems well here, no?
Thanks,
Nacht
Screen-Shot-2017-07-01-at-7.32.39-AM.png
I have finished migrating all of my mailboxes over from Exchange 2010 to Exchange 2016.
THis morning I noticed there was a "Discovery Search Mailbox" in one of the databases in Ex2010 that threw an error saying it was corrupt and couldn't move. However, the Database that particular Discovery Search Mailbox is in, was never used by any mailboxes.
So my question is, do I need to worry about this MB? Can I just ignore this message and not try to move it over?
I had already run a move request to move over all Arbitration mailboxes and it was successful. Is this a type of Arbitration Mailbox?
Another question, does each DB created on an Exchange server get a Discovery Search Mailbox created?
Here is the error I get in EMC about this MB.
------------------
The object XXXXXXX.lcl/Microsoft Exchange System Objects/SystemMailbox{B2F3
Database is mandatory on UserMailbox.
---------------
If I run a "Get-mailbox -Monitoring" I get the following (See attached). All seems well here, no?
Thanks,
Nacht
Screen-Shot-2017-07-01-at-7.32.39-AM.png
ASKER
I ran that command. Looks like that old one on Ex2010 is the only one. I guess I have to see if I can move it across.
ASKER
I was able to move it across to the Ex2016 server. Still getting the same error message as above though in EAC when I click on that MB.
ASKER
I am a bit confused. Is a system mailbox the same as an Arbitration MB? I had moved across all Arbitration MB's a while ago. Well before i moved user MB's over.
I am starting to suspect the System MB I am getting the error on isn't necessary. Just to be safe I moved it to a DB on the Ex2016 server I am not using.
Here is what I get when I test for Arbitration Boxes. System boxes come up! Arbitration == System?
Screen-Shot-2017-07-01-at-8.17.36-AM.png
I am starting to suspect the System MB I am getting the error on isn't necessary. Just to be safe I moved it to a DB on the Ex2016 server I am not using.
Here is what I get when I test for Arbitration Boxes. System boxes come up! Arbitration == System?
Screen-Shot-2017-07-01-at-8.17.36-AM.png
You can verify the AD account of that system mailbox and check if that's enabled however it kya corrupt you will have to delete it I have seen many cases where we need to delete those system mailboxes from legacy version while upgrading the Exchange .
In worst case if you need them there is manual way of creating if however simply you can recreate it by running the Domain prep
In worst case if you need them there is manual way of creating if however simply you can recreate it by running the Domain prep
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Discovery Search Mailbox are created by defaul in the installation with Exchange, there are similar to arbitration mailbox.
You can check how many discovery mailbox you have:
Get-Mailbox -Resultsize unlimited -Filter {RecipientTypeDetails -eq "DiscoveryMailbox"}
If you have one in Exchange 2016. You do not have to worry about it.
viktor