We're going to migrate our public folders from Exchange 2010 to Exchange 2013 where all our user mailboxes are now. I've been reviewing the Technet article, "Use batch migration to migrate public folders to Exchange 2013 from previous versions" for the required migration steps.
I noticed from reading other blog posts, the Technet article has different command for Step 6, "Lock down the public folders on the legacy Exchange server for final migration", this is what it says to run
Set-OrganizationConfig -PublicFoldersLockedForMigration:$true
The other blogs have these two commands instead
Get-PublicFolderMigrationRequest | Set-PublicFolderMigrationRequest -PreventCompletion $false
Get-PublicFolderMigrationRequest | Resume-PublicFolderMigrationRequest
Has anyone stumbled upon this before?
Orange County District Attorney