DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2710029 - Last Review: October 17, 2014 - Revision: 13.0

PROBLEM

Assume that you have a hybrid deployment of Microsoft Exchange Online in Microsoft Office 365 and in your on-premises Microsoft Exchange Server environment. After directory synchronization runs, shared mailboxes that were moved from the on-premises environment to Office 365 are unexpectedly converted to regular mailboxes. When this occurs, you may be unable to convert the mailboxes to shared mailboxes. If you can make this conversion, the mailboxes revert to shared mailboxes the next time that directory synchronization runs.

Also, when you view the properties of the shared mailboxes in the Office 365 portal, you may receive the following error message:
Exchange: Couldn't convert the mailbox because the mailbox <guid> is already of the type 'Regular'

CAUSE

This issue occurs if the value of the msExchRemoteRecipientType attribute isn't set correctly by the on-premises hybrid server that's running Microsoft Exchange Server 2010. The value of the msExchRemoteRecipientType attribute is incorrectly set to 0x4. A value of 0x4 indicates that the mailbox was migrated. In this situation, directory synchronization replicates the attribute to the cloud, and then Office 365 converts the shared mailbox to a MailUser object.

The value of the msExchRemoteRecipientType attribute should be set to 0x64. The hexadecimal value of 0x64 is equal to a decimal value of 100. In this situation, the shared mailbox isn't converted to a regular mailbox when directory synchronization runs. Instead, it remains as a shared mailbox. 

WORKAROUND

To work around this issue, use the Exchange Management Shell to change the value of the msExchRemoteRecipientType attribute. 

Change the value of the msExchRemoteRecipientType attribute for one user

To change the value for one user, follow these steps:
  1. Run the Exchange Management Shell as an admin.
  2. At the command prompt, type the following command, and then press Enter:
    Set-Mailbox –identity user@contoso.com –RemoteRecipientType “ProvisionMailbox, ProvisionArchive”
Note The ProvisionMailbox and ProvisionArchive flags set the msExchRemoteRecipientType attribute to the correct decimal value for the version of Exchange on which the Exchange Management Shell commands are running.

Change the value of the msExchRemoteRecipientType attribute for all users

To change the value this for all users, follow these steps:
  1. Run the Exchange Management Shell as an admin.
  2. At the command prompt, type the following commands, and then press Enter:
    $mbx = Get-Mailbox -ResultSize Unlimited -Filter {(RecipientTypeDetails -eq "UserMailbox") -and (RemoteRecipientType -eq "Migrated")}
    $mbx | fl Name, *recip*
    $mbx | Set-Mailbox -RemoteRecipientType "ProvisionMailbox, ProvisionArchive"
Note The ProvisionMailbox and ProvisionArchive flags set the msExchRemoteRecipientType attribute to the correct decimal value for the version of Exchange on which the Exchange Management Shell commands are running.

STATUS

This is a known issue. Microsoft is currently investigating the issue and will post more information in this article when it becomes available.

MORE INFORMATION

Still need help? Go to the Office 365 Community (http://community.office365.com/) website or the Exchange TechNet Forums (http://social.technet.microsoft.com/Forums/exchange/en-us/home?category=exchange2010%2Cexchangeserver) .

Applies to
  • Microsoft Exchange Online
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
Keywords: 
o365 o365022013 o365e o365m o365a hybrid kbbug KB2710029
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support