Consider the following scenario:
- In your Microsoft Exchange environment, Exchange Server 2010 coexists with either Exchange Server 2013 or Exchange Server 2016.
- Public folders are hosted on the Exchange 2010 servers.
- Access to the legacy public folders has been configured in compliance with the guidelines in the TechNet topic that's mentioned in the "More Information" section.
- There are multiple Exchange 2010 public folder databases.
This issue occurs if the mailbox database that hosts the user's mailbox is configured for a public folder database that differs from the public folder discovery mailbox database.
To resolve this issue, configure the user's mailbox database to use the same public folder database as the discovery mailbox:
- Assign a public folder discovery mailbox to the user's mailbox by using the Set-Mailbox cmdlet, as follows:
Set-Mailbox <User> -DefaultPublicFolderMailbox <ProxyMailbox>
- Assign the public folder database for the user's mailbox database by using the Set-MailboxDatabase cmdlet, as follows:
Set-MailboxDatabase (Get-Mailbox <User>).Database -PublicFolderDatabase (Get-MailboxDatabase (Get- Mailbox <ProxyMailbox>).Database).PublicFolderDatabase
- Run the following cmdlet to restart the Microsoft Exchange Rpc Client Access service on the server that's running Exchange Server that hosts the public folders:
Article ID: 3177600 - Last Review: Sep 8, 2016 - Revision: 1