Public folders provide a way to collect, organize, and share information with other people in your organization. They can help users organize content in a deep hierarchy that's easy to browse in Outl...
Updated May 22, 2023
Version 3.0
Blog Post
Can you please give us a little bit more insights regarding EXO processes handling this issue and possible other stuff regarding Public Folder? (e.g. PublicFolderInvalidDumpsterFixingProcessor)
Recently, we had a Public Folder migration (close to 250k folders) to EXO and we are still facing issues. (MS Case still open)
This seems to be related to fact we had to migrate with the -ExcludeDumpsters switch due to the amount of folders.
After the batch was completed, we had issues during testing and after some investigation it looked like that some process started, touching all public folders.
Example from the Auditlog:
$audit = search-AdminAuditLog -StartDate (get-date).AddHours(-1) -EndDate (get-date) -ResultSize 250000
$audit | group CmdletName | sort name | select count,name
Count Name
----- ----
345 Set-PublicFolder
8518 Update-PublicFolderMailbox
Example of Update-PublicFolderMailbox Audit Event:
ObjectModified : PrimaryHierarchyPFMBX
CmdletName : Update-PublicFolderMailbox
CmdletParameters : {Identity, InvokeSynchronizer, FolderId, CreateAssociatedDumpster}
ModifiedProperties : {}
Caller : NT AUTHORITY\SYSTEM (MSExchangeMailboxAssistants)
ExternalAccess : False
Succeeded : True
IsValid : True
ObjectState : NewI assume that this process started, and fixed (almost) *all* folders, since we were migrating without dumpster? Correct?
Does this mean that, more or less, the complete hierarchy was being changed by this process? (keeping in mind that we migrated without dumpster)
Right now we are facing issues described above (e.g. folders, items can't be deleted) and it seems that the hierarchy sync has troubles to sync the mailboxes serving the hierarchy.
Additional it would be nice to learn more about all processes... what, when, how, since it looks like those are not well documented, additionally it seems that MS support is also not aware of this stuff:
PublicFolderHierarchySyncProcessor
PrimaryPublicFolderMailboxProcessor
PublicFolderItemProcessor
PublicFolderDiscoveryHoldsProcessor
PublicFolderItemProcessor_DueDateForUsageStatistics
PublicFolderSplitProcessor
PublicFolderMailboxRemovalProcessor
PublicFolderMailboxMaintenanceProcessor
PublicFolderInvalidPermissionsCleanUpProcessor
PublicFolderInvalidDumpsterFixingProcessor
Regards
A.