Quick note on the migration process. Microsoft has recently updated their Public Folder documentation and require higher levels of Exchange 2007 and 2010:
- The Exchange 2010 server needs to be running Exchange 2010 SP3 RU8 or later.
- The Exchange 2007 server needs to be running Exchange 2007 SP3 RU15 or later.
I was going through my normal process which I have copied to my One Note and I received this error message:
Upon getting the error message, I reviewed the Public Folder Legacy to Exchange 2013 migration document which can be found here. That is where I saw the requirement updates. Apparently there is an update to the code because of previous issues migrating Public Folders which an be found documented here. The wording in the article is clear in that if a condition occurs, a warning message will pop-up about the RU15 update being required to move forward:
The new recommendation would seem to be upgrading Exchange 2007 to RU15 if you have Public Folders to migrate.
*** UPDATED ***
The Microsoft Public Folder article is missing a couple of other items and has some typos in the document as well:
(1) Step 5 – Exchange 2007 section – #1:
This PowerShell one liner:
New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server <Source server name>) -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) NotificationEmails <email addresses for migration notifications> -BadItemLimit $BadItemLimitCount
Should read as:
New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server <Source server name>) -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte) -NotificationEmails <email addresses for migration notifications> -BadItemLimit $BadItemLimitCount
The difference is that the NotificationEmails switch is missing a ‘-‘ in front of it.
(2) Step 5 – Exchange 2007 – #2
Missing is the step to actually kick off the migration batch. Exchange 2010 has this, but the Exchange 2007 section is missing. To start the Public Folder migration, just run this:
(3) Step 5 – Exchange 2010 – #2:
The PowerShell one line is incorrect for starting up the migration batch as the migration batch is misspelled.
Should read as:
I’ve already filed a documentation note with Microsoft. In case you run into these before the document is updated, you know what to do.