Vladimir Buzalka
asked on
System mailbox problem for Exchange
Hi Experts
I am moving Exchange 2010 to exchange 2016 (on premise). I have updated domain schema, I have install Unified Communication API.
I installed E2016 and now I am moving mailboxes.
For system mailbox I received warning
The object BUZALKA.local/Microsoft Exchange System Objects/SystemMailbox{532F F86F-C2B9- 464C-80E5- B006B924CC A8} has been corrupted or isn't compatible with Microsoft support requirements, and it's in an inconsistent state. The following validation errors happened:Database is mandatory on UserMailbox.
Can you advice what is wrong? How to proceed on?
Many thanks
Vladimir
I am moving Exchange 2010 to exchange 2016 (on premise). I have updated domain schema, I have install Unified Communication API.
I installed E2016 and now I am moving mailboxes.
For system mailbox I received warning
The object BUZALKA.local/Microsoft Exchange System Objects/SystemMailbox{532F
Can you advice what is wrong? How to proceed on?
Many thanks
Vladimir
Check if the HomeMDb is set for that system Mailbox if not just set the HomeMdb pointing to any of your Exchange 2010 DB and then move the Mailbox
reff- https://www.experts-exchange.com/questions/28269745/Exchange-2010-Attendant-homeMDB-Attribute-Mailbox-Database-0365048811.html
You will have to select your Mailbox
reff- https://www.experts-exchange.com/questions/28269745/Exchange-2010-Attendant-homeMDB-Attribute-Mailbox-Database-0365048811.html
You will have to select your Mailbox
ASKER
Dear Pradiip and Fox
I found that problem is related to systemmailbox which is remnant of old 2003 exchange server. I moved from 2003 to 2010 3-4 years ago and I can remember that it was quite painfull with several problems during swing migration.
Now when I tried to move to 2016, it is easy, however obviously E2016 searched registry and found that remnant mailbox. See the picture, the only reference which I found in registry is on picture. When I listed system mailboxes of working E2010 those are different.
So what I did is simply I deleted that registry key and all is OK.
Should I test something else?
i have that scenario uploaded in ESX server so that I can play safely in any way, and after I will feel OK, I will proceed on to migration in production environment.
Thanks
V
2018-08-13_11-56-44-SystemMailbox.jpg
I found that problem is related to systemmailbox which is remnant of old 2003 exchange server. I moved from 2003 to 2010 3-4 years ago and I can remember that it was quite painfull with several problems during swing migration.
Now when I tried to move to 2016, it is easy, however obviously E2016 searched registry and found that remnant mailbox. See the picture, the only reference which I found in registry is on picture. When I listed system mailboxes of working E2010 those are different.
So what I did is simply I deleted that registry key and all is OK.
Should I test something else?
i have that scenario uploaded in ESX server so that I can play safely in any way, and after I will feel OK, I will proceed on to migration in production environment.
Thanks
V
2018-08-13_11-56-44-SystemMailbox.jpg
It should be okay
Just check if OAB is working fine, I am sure it would be alos runt get-mailbox -arbritation and see if its giving waking or error
Just check if OAB is working fine, I am sure it would be alos runt get-mailbox -arbritation and see if its giving waking or error
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ref link: https://technet.microsoft.com/en-us/library/mt441791(v=exchg.150).aspx