If you have 300,000 Public Folders you won’t use the Exchange Management Console to changes names of Public Folders (well, I cannot imagine you would).Ĭheck for any previous migration attempts in your Exchange environment: Get-OrganizationConfig | Format-List PublicFoldersLockedforMigration, PublicFolderMigrationCompleteīoth values should have a value of False:
You can use any tool you like to change the name, depending of the number of Public Folders of course. To retrieve a list of all Public Folders with a back slash or forward slash in their name, you can use the following command: Get-PublicFolderStatistics -ResultSize Unlimited | Where | Format-List Name, Identity Customers tend to use strange characters in the Public Folders names (back slash, forward slash) and these are not supported. Most customers will run into issues with naming of their Public Folders. Get-PublicFolder -Recurse | Get-PublicFolderClientPermission | Select-Object Identity,User -ExpandProperty AccessRights | Export-CliXML C:\PFMigration\Legacy_PFPerms.xml Get-PublicFolderStatistics | Export-CliXML C:\PFMigration\Legacy_PFStatistics.xml Basic PowerShell and the output is exported to an XML file: Get-PublicFolder -Recurse | Export-CliXML C:\PFMigration\Legacy_PFStructure.xml The first step is to take a snapshot of the existing environment, both the Public Folders, their statistics and permissions. Mailboxes still on Exchange 2010 cannot access Public Folders on Exchange 2016! Take snapshot of existing Public Folders on Exchange 2010
Migrating Public Folders can only be done when all mailboxes are migrated to Exchange 2016. I know there are several other blogs available on this topic, but this way I also have my own reference available.
- Testing modern public folders, and then unlocking them for access by users (the outage is now over).
- Locking the public folders for final migration (this requires an outage, usually of at least an hour, but longer for very large environments).
- Starting the migration, and waiting for initial synchronization to complete.
- Creating public folder mailboxes in Exchange 2016 databases.
- Generating CSV files using the Microsoft scripts.
- Preparing the organization for public folder migration.
- Downloading scripts from Microsoft from.
- Migrating Public Folders looks easy, it’s a matter of gathering information regarding the Public Folders and its permissions, copying that over to a Public Folder database and keeping the contents in sync and when you’re ready finalize the migration. 1000 mailboxes and maybe 100 Public Folders (in only one Public Folder database) but they were real Public Folders with real users using them ? The Exchange 2010 (hybrid) to Exchange 2016 (hybrid) migration included approx. So far, all my customers had decommissioned Public Folders in the Exchange 2010 timeframe, all migration I did have never included Public Folders, until now.