Introduction
The purpose of this article is to provide high level overview of hierarchy synchronization process in public folders and provide some troubleshooting steps to monitor and troubleshoot...
Updated Jul 01, 2019
Version 2.0
Blog Post
And a couple of deeper questions on this topic:
1. When a new folder is created, is this an atomic process whereby the return to the caller does not happen until the new folder is replicated? I suspect from this post that the replication of structure changes is asynchronous, meaning that there can be a delay before a user connected to PFMB02 (non-primary) sees a change to the structure, while a user connected to PFMB01 (primary) sees the change immediately?
2. Can you explain the folder assignment logic? For example, one can call new-publicfolder -mailbox PFMB02 to create a folder and assign a content mailbox for that folder. Does the logic remain the same as written in the article? Does ever replica of the same folder have the same metadata with regards to the content mailbox?
3. When bulk creating a new folder tree (perhaps for migration), is it better to create the structure all at once on the primary hierarchy mailbox first, then add additional mailboxes and change the content mailbox for specific folders, or the opposite - create all the content mailboxes first, then create AND set the content mailbox for folders?
@Eriq VanBibber, here answers to questions
#1 New public folder creation from client (like outlook) always happens in primary hierarchy mailbox and info is immediately replicated to the PF mailbox the outlook client is connected to
#2 You'll need to elaborate the question little more
#3 For deploying larger PF trees, which usually happens during PF migration, yes; one must plan and create content mailboxes and decide placement of PF's; according to size of the individual PF size.