This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are a hybrid setup with Exchange 2013 on premises. I have migrated all users to O365. Now I have started on the migration of the shared mailboxes. When using the migration wizard I am unable to find some of these mailboxes.
Does this mean they are already migrated to O365? Is it safe to disable them(on premise)?
The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.
The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
What does
get-recipient <shared Malbox>
show using on-prem Exchange Powershell for an example one that isnt showing up?
I am writing here to confirm with you any update about this thread now.
If the suggestion below helps, please feel free to accept it as an answer to help more people.
Here is detailed information about mailbox type in hybrid:
For migrated shared mailbox: RemoteRecipientType is "Migrated, SharedMailbox"
For remote shared mailbox: RemoteRecipientType is "ProvisionMailbox, SharedMailbox"
For migrated user mailbox: RemoteRecipientType is "Migrated"
For remote user mailbox: RemoteRecipientType is "ProvisionMailbox"
Answer accepted by question author
Ok, cool.
Now confirm its a remote mailbox:
get-remotemailbox <shared Malbox>
If that returns the remote mailbox, then no need to migrate it, its already moved to 365 and it should show as a mailbox there.
I ran the command on two of the mailboxes that are missing. Two different results...
Both came back with RemoteSharedMailbox for RecipeintTypeDetails
However for the RmoteRecipientType - one mailbox came back Migrated, SharedMailbox and the other said ProvisionedMailbox,SharedMailbox
,
Thats fine! they are both shared mailboxes. :)
One was moved from on-prem, one was created directly as a remote shared mailbox which synced to Azure/365.
Based on these results its safe to "leave" these mailboxes on the 2013 server? I am migrating to a 2016 exchange server which will not have databases but will be used for management purposes only. All users (already migrated) and shared mailboxes(checking remaining) will be in O365.
Yes, no need to worry about remote mailboxes. They are actually pointers to the 365 mailbox and not tied to an on-prem server.
You can safely remove the 2013 in the future and the remote mailboxes you see now in 2013 will show up in the 2016 EAC as well.
P.S. When you migrate to 2016, you will need at least one small database for the arbitration mailboxes. You will need to move those system mailboxes from 2013 to the 2016 server:
https://blog.rmilne.ca/2018/03/19/arbitration-mailboxes-lay-of-the-land/
Easily Move All Arbitration Mailboxes To A Specific Database
The below is one simple example to move all Arbitration mailboxes to a specific database. It is expected that any Exchange database which contains arbitration or system mailboxes is made highly available using a Database Availability Group. This provides the ability to have multiple copies of a given mailbox database.
Get-mailbox –Arbitration -Database <LegacyDatabaseNameGoesHere> | New-MoveRequest –TargetDatabase <ShinyNewDatabaseNameGoesHere>