Public folder contacts not updating
To their credit, Microsoft listened to customers and started to invest a small amount of engineering resource into public folders in Exchange 2007 and have continued on this path in Exchange 2010.Public folders are only required in Exchange 2010 if you: 1.By contrast, Exchange 2013 synchronizes public folder mailboxes by connecting to the mailbox that contains the primary hierarchy and adjusting a secondary copy based on the primary.Synchronization is obviously tremendously important. Normally everything happens automatically and you should never have to interfere.The more curious will want more detail and fortunately this can be gained by running the Get-Public Folder Mailbox Diagnostics cmdlet.As its name indicates, this cmdlet is designed to help debugging problems with public folder mailboxes, but it does reveal some interesting data.
Update: If you’re interested in upgrading to Exchange 2013 and need to migrate some public folders to the modern format (or indeed, to migrate some public folders to Exchange Online in Office 365), then you might like to read my thoughts on the migration process. They continue to persist despite seemingly being on the edge of extinction several times.
All other public folder mailboxes contain a not-writeable or secondary copy of the hierarchy that are updated by an Exchange mailbox assistant every 24 hours at a minimum, or every 15 minutes if clients are connected to a public folder mailbox that contains a secondary copy of the hierarchy.
Synchronization ensures that all of the public folder mailboxes present the same hierarchy to clients.
But if such a situation arose, as in the case when a user reports that no trace of a newly created public folder is visible to them, you can force synchronization for a mailbox that holds a secondary copy of the public folder hierarchy by running the Update-Public Folder Mailbox cmdlet.
For instance, this example instructs Exchange to synchronize the hierarchy in the “PFMBX2” mailbox with the primary copy: [Note: this is also the solution to the bug that Microsoft discovered soon after Exchange 2013 RTM CU2 was released when permissions on secondary public folder mailboxes disappeared following a move] If everything goes to plan, you’ll see a message saying that “” and you can go on with your life.