This is where you manage public folders going forward. You may need to hit the refresh ( ) button. You should also see your folder structure appear under the Public Folders > Public Folders tab. If you are curious about what the final report contains check out this link. How long this takes depends on how many changes have been made in public folders since the initial seed, or, last incremental sync. Cleanup and replication are also performed in the environment. Once finished the status column will display Completed. During this time a final incremental sync is performed. The batch status will switch to Completing. Yes Yes to All No No to All Help (default is "Y"): C:\> Complete-MigrationBatch PFMigrationĪre you sure you want to perform this action? Hit enter to accept the default action of Yes. Be sure to rename PFMigration to the name of your batch, if different. C:\> Set-OrganizationConfig -PublicFoldersEnabled Remote
Let’s switch back to the 2016 server again.įrom the Exchange Management Shell run the following. It’s not uncommon for this change to take several hours for a large network. The next two commands will fail until the change is replicated through the network.
Warning: It can take some time for this lock command to propagate through your network. C:\> Set-OrganizationConfig –PublicFoldersLockedForMigration:$true Users will be blocked from accessing Public Folders. Okay, let’s switch back to the 2010 server.įrom the Exchange Management Shell run this command. You may wish to schedule this during a maintenance window. Warning: This will take your public folders offline. Now that the data is seeded its time to flip the switch. It may be best to perform these next tasks under a maintenance window. Keep in mind completing the batch will force downtime for your public folders. If you take no action the migration job will perform an incremental copy every 24 hours until you complete the batch. However, your new public folder mailbox it is not yet live. In addition, the report will list a percentage of 95 and indicate it was automatically suspended. This means the initial seed of data has been completed. C:\> Get-MigrationUser -Batch PFMigration | Get-MigrationUserStatistics -IncludeReport | flĮventually, your migration will show a status of Synced. You will need to replace PFMigration with the name of your batch if different. You can also see the same report in PowerShell by issuing the following command. If you are interested in what my detailed migration report looked like check this link. Including any additional information on errors. This link is a detailed play by play of everything the migration is doing.
The real magic is the Download the report for this user link. We can see that 5 items have synced, nothing has been skipped and, so far no errors are reported. Selecting the batch and clicking the View Details link, will give us a deeper insight into what is happening with the batch.įrom here we can see greater detail into the progress of our PFMigration batch. Once we started the batch it switches to “Syncing”. Before issuing the previous command it would have shown a status of “Created”. Once logged in, navigate to Recipients > Migration tab.įrom here we will see our PFMigration job and its current status. We can check the progress of the batch by logging into the Exchange Admin Center. If you named your job anything other than PFMigration you will need to change that here. To start the actual data copy run the following command.
C:\> New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX10) -CSVData (Get-ContentĬ:\PFScripts\FolderToMailbox.csv -Encoding Byte) -NotificationEmails Status Type TotalCount NotificationEmails specifies where to email the batch migration report. We had called this FolderToMailbox.csv and saved it to C:\PFScripts. CSVData specifies the path to our map file we created in part one of our series. SourcePublicFolderDatabase (-Server) specifies the 2010 server hosting the public folder database. Name specifies a display name to help identify the batch. C:\> New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX10) -CSVData (Get-Content C:\PFScripts\FolderToMailbox.csv -Encoding Byte) -NotificationEmails our example: From the Exchange 2016 server issue the following command. We will also finalize the migration process. In this second and final part of our series, we will copy the data from the legacy public folder databases into our newly created modern public folders. Then we ran all the necessary scripts to size and create the new public folder mailbox hierarchy. In part one of public folder migration, we prepared our environment. PREVIOUS: Exchange 2016: Public Folder migration Part 1