{"id":150935,"date":"2023-10-09T08:30:44","date_gmt":"2023-10-09T08:30:44","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=150935"},"modified":"2024-04-30T11:32:12","modified_gmt":"2024-04-30T11:32:12","slug":"how-to-use-public-folder-migration-scripts","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/how-to-use-public-folder-migration-scripts\/","title":{"rendered":"How to Use Public Folder Migration Scripts?"},"content":{"rendered":"

In Exchange Server, migration of mailboxes is a little easy as you can use the New-MailboxExportRequest PowerShell command<\/a><\/strong> in the Exchange Management Shell (EMS). On the other hand, you need to use a set of scripts to move public folders to another Exchange Server or Office 365 tenant. In this post, we will be going through the process of migrating public folders from one Exchange Server to another using the Public Folder Migration Scripts.<\/p>

How to Download Public Folder Migration Scripts?<\/strong><\/h2>

Below, we will see the process of moving public folders from Exchange Server 2010 to higher Exchange Server version – 2016 or later.<\/p>

The first thing you need to do is download the migration scripts from the Microsoft site<\/a>. <\/p>

\n
\"download<\/figure>\n<\/div>

On the Public Folders Migration Scripts web page, click on Download<\/strong>. This will download six files which are needed for the migration.<\/p>

\n
\"Public<\/figure>\n<\/div>

You need to store these files on the old Exchange Server, ideally in the C:\\Scripts folder<\/strong>. Then, ensure that both Exchange Servers are updated to the latest Cumulative Updates. If you’re migrating from Exchange Server 2010, it should have a minimum service patch installed, i.e. Service Pack 3<\/strong> with RU8<\/strong>.<\/p>

How to Run Public Folder Migration Scripts?<\/strong><\/h2>

Now, you need to run the Export-PublicFolderStatistics.ps1<\/a><\/strong> script. For this, open the Exchange Management Shell (EMS) <\/strong>on the Exchange Server 2010 and run the below command.<\/p>

\n
\"run<\/figure>\n<\/div>

You will be prompted to allow the script to run a single time or always.<\/p>

\n
\"allow<\/figure>\n<\/div>

The exported file should be like the given below.<\/p>

\n
\"Export<\/figure>\n<\/div>

After this, you need to run the PublicFolderToMailboxMapGenerator.ps1<\/strong> script. You will be asked for the Mailbox<\/strong> Size<\/strong> (each public folder mailbox size). The size must be entered in bytes.<\/p>

You will then be asked for the Import file.<\/strong> This file is the ‘PublicFolderStats.csv’<\/strong> you’ve just created by running the previous script.<\/p>

The Export file is also needed for the output information.<\/strong><\/p>

\n
\"PublicFolderToMailboxMapGenerator.ps1<\/figure>\n<\/div>

You also need to keep in mind the mailbox size restrictions (if any) on the destination server. When you open the Export file, you would see what is recommended in size and public folders. This may vary depending on the setup of the legacy server.<\/p>

The script output will create the target mailboxes as Mailbox1, Mailbox2, etc. If you want to change them, then you can edit the CSV file with the name on the new server.<\/p>

Now, you need to log into the new server and copy or re-download the scripts again. Open the Exchange Management Shell (EMS) and execute the Create-PublicFolderMailboxesForMigration.ps1<\/strong> script. You will be asked to specify the mapping file. Here you need to specify the export file (created above).<\/p>

Supply values for the following parameters:
(Type !? for Help.)
FolderMappingCsv: FolderToMailbox.csv<\/code><\/code><\/pre>
Then, you will be asked for the number of concurrent users which will be using the public folders. The maximum concurrent users recommended by Microsoft are 2000.<\/p>
EstimatedNumberOfConcurrentUsers: 100<\/code><\/code><\/pre>
The script will create all the public folders needed for the migration. You need to confirm that the folders listed in the CSV file for the mapping corresponds with the created public folders.<\/p>
Create and Start Migration Batch<\/strong><\/h2>
On the Exchange Server 2016 or newer (destination), you need to run the New-MigrationBatch<\/a><\/strong> command to create new migration batch for the public folders to be copied from the source.<\/p>
New-MigrationBatch -Name <batch name> -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server <source server name>) -CSVData (Get-Content <mapping file path> -Encoding Byte) -NotificationEmails <email address for notification><\/code><\/code><\/pre>
\n
\"Create<\/figure>\n<\/div>
This will create the migration batch job. Now, you need to start the migration batch using the Start-MigrationBatch<\/a><\/strong> command (see below).<\/p>
Start-MigrationBatch <migration batch name><\/code><\/code><\/pre>
\n
\"Start<\/figure>\n<\/div>
To see the progress, log in to the Exchange Admin Center (EAC)<\/a><\/strong>, click on Recipients,<\/strong> and then click on Migration<\/strong>.<\/p>
\n
\"Check<\/figure>\n<\/div>
Once created, it will show the status as Created<\/strong>. If it is synchronizing, it will show as Syncing<\/strong>. Once it’s ready, it will show the status as Synced<\/strong>.<\/p>
\n
You may also like the article Difference between New-MigrationBatch and New-MoveRequest Commands in Exchange Server<\/a>.<\/strong><\/em><\/p>\n<\/blockquote>
Complete the Migration<\/strong><\/h2>
On the legacy server, you need to block users from accessing the public folders. For this, run the below command.<\/p>
Set-OrganizationConfig –PublicFoldersLockedForMigration:$true<\/code><\/code><\/pre>
\n
\"Set<\/figure>\n<\/div>
On the new server, you need to complete the migration batch using the Complete-MigrationBatch<\/strong> command (see the below example).<\/p>
Complete-MigrationBatch <migration batch name><\/code><\/code><\/pre>
\n
\"complete<\/figure>\n<\/div>
This will synchronize all the changes. Depending on the number of changes, it will take some time.<\/p>