Learn Exchange the Guru way !!!


Public Folders Migration from Exchange 2007/2010 to Exchange 2013

Public Folders has been discussed before and after every new Exchange server release but there are many Microsoft customers who are using it that Microsoft is not preferring to remove it completely. Even today with the great functionality of sharepoint, Microsoft decided to keep PF in the Exchange so that it can give an option to use PF or Sharepoint.

I would highly recommend our high Public Folders users to start using Sharepoint but if you have less Public Folders Data then we can still migrate Public Folder Database to Public Folder Mailboxes.

By changing the Design from Database to Mailbox, Public Folders has become highly available with DAG. So if your mailbox database is up and running in DAG then Public Folders are also available.

Public Folders Limits can be reviewed here.





-Exchange 2010 is Exchange 2010 SP3 or later

-Exchange 2007 is Exchange 2007 SP3 RU10 or later

-Login id has Organization Management and Recipient Management Permissions

-All the mailboxes have been moved to Exchange 2013

-Ensure we announce downtime or do this over the weekend

-Perform a backup of your public folder databases

Removed space and from the alias of 2007/2010 Public Folders.


Public Folder Migration Steps:

1. Snapshot of the current Public Folders: In the following steps we will take the snapshot of the current Public Folders which will be compare post migration.

       -Run the following command to take a snapshot of the original source folder structure.

       Get-PublicFolder -Recurse | Export-CSV C:PFMigrationEx2010_PFStructure.csv

       -Run the following command to take a snapshot of the public folder statistics such as item count, size, and owner.

       Get-PublicFolder -Recurse | Get-PublicFolderStatistics | Export-CSV C:PFMigrationEx2010_PFStatistics.csv

       -Run the following command to take a snapshot of the permissions.

       Get-PublicFolder -GetChildren | Get-PublicFolderClientPermission | Select-Object Identity,User -ExpandProperty AccessRights | Export-CSV C:PFMigrationEx2010_PFPerms.csv

       Save the information from the above commands for comparison at the end of the migration.


2. Preparation on Legacy Exchange server (2010/2007): We need to do the following check before preparing public folders migration.

       -Validate Exchange 2010/2007 Public Folder database is mounted

       -Validate no record of previous successful migration is present

       -Use the below cmdlet to check if there was a previous successful migration completed

       Get-OrganizationConfig | fl PublicFoldersLockedforMigration, PublicFolderMigrationComplete

       -If you find any True, then use the below cmdlet, this will take some time to become effective:

       Set-OrganizationConfig -PublicFoldersLockedforMigration:$false -PublicFolderMigrationComplete:$false 
3. Preparation on Exchange 2013 server: We need to check the following on the Exchange 2013 before starting the migration.

       -Validate no migration currently in progress by running following cmdlet


       -Validate no existing PFs or PF mailboxes by running following cmdlet





         Get-Mailbox -PublicFolder

         You should see the below output:



       -Run the below cmdlets to remove any previous Public Folders:

         Get-PublicFolderMigrationRequest | Remove-PublicFolderMigrationRequest -Confirm:$false
         Get-MailPublicFolder | where $_.EntryId -ne $null | Disable-MailPublicFolder -Confirm:$false 
         Get-PublicFolder -GetChildren  | Remove-PublicFolder -Recurse -Confirm:$false 
         Get-Mailbox -PublicFolder |Remove-Mailbox -PublicFolder -Confirm:$false


4. Export public folder hierarchy from source into CSV file: On Exchange 2010/2007 run the following script which will generate a csv file:

Important: In Exchange 2007 you might need to remove “ResultSize:unlimited” on line number 91 of the script “Export-PublicFolderstatiscis.ps1”. Don’t change anything unless you face any issue.

         .Export-PublicFolderStatistics.ps1 servernamepathfilename.csv

       Example file output

         .PublicFolderToMailboxMapGenerator.ps1 MailboxSize ImportFilePAth ExportFilePath

       ImportFilepath is the file name which was created in previous step.

       Output file screen


5. Create public folder mailboxes in Exchange 2013: We will run the below cmdlet to create public folders mailboxes in hold for migration mode.

Important: The name of the public folder mailboxes that you create must match the name of the TargetMailbox in the mapping file. You can edit the TargetMailbox names in the mapping file to match your organization’s naming conventions.

         New-Mailbox -PublicFolder MailboxName -HoldForMigration:$true –Database “2013DB”

       -Continue creating the new mailboxes as per the output file. In my case it was only one.


6. Migration Request creation: In this step we will rung the migration request cmdlet

Before creating migration request it will be good to run the below command to avoid “The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook” prompt. This command will stop this mailbox serving the hierarchy.

 Set-Mailbox <PublicFolderMailboxName> –PublicFolder –IsExcludedFromServingHierarchy:$True

Now run the migration request

“New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server <Source server name>) -CSVData (Get-Content <Folder to mailbox map path> -Encoding Byte)”

Example: New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server Exch2010) -CSVData (Get-Content C:tempMapgen.csv -Encoding Byte)

       -Move will begin as an online move and reach auto suspended state

       -Run the following cmdlet to verify the migration status.

         Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl

       -Below is sample screen – Normally you get 2-3GB per hour migration output.

       When the status reaches Autosuspended, we can move to next step


7. Lock source (Exchange 2010/2007) for final migration:

       -Once Auto Suspend state is reached, set the bit on the org object that you are making the switch

       -Downtime will be required depends on how much new content was generated since the migration reached the AutoSuspended state.

       -The cmdlet will log off the users from the public folders and lock the folders while the migration completes its final synchronization. Users won’t be able to access public folders during this process.

       -It is recommended to run the following cmdlet on Exchange 2010/2007 but this does not matter in the same org as this is org level configuration.

        Set-OrganizationConfig –PublicFoldersLockedForMigration:$true


 -If multiple source PF databases, wait Replication Interval+1 hour after locking source so they can replicate. Alternatively you can restart the Microsoft Exchange Information Store service to bypass the    waiting time.

8. Complete the suspended migration by running below 2 cmdlet:

       -Set flag on migration request that finalization has been triggered

        Set-PublicFolderMigrationRequest –Identity PublicFolderMigration -PreventCompletion:$false


       -Resume migration request

        Resume-PublicFolderMigrationRequest –Identity PublicFolderMigration


       -Migration will reach completed state

Once migration completes run the below command to allow this mailbox to serve the Hierarchy requests

 Set-Mailbox <PublicFolderMailboxName> –PublicFolder –IsExcludedFromServingHierarchy:$False” 


9. Validation

       -Check that source public folders have been moved to Exchange 2013

       -Check that hierarchy matches the source setup



10. Removing PF Database in Exchange 2010/2007

       Once you are satisfied, you can go ahead and delete the Public Folder Database from Exchange 2010/2007 then remove the database and log files from folder directory 


Public Folder Migration ends here.


Rollback Steps:

If you run into issues with the migration and need to reactivate your Exchange 2010 public folders, perform the following steps:

Important: After the migration is complete, any changes you made to your Exchange 2013 public folders won’t be reflected in the Exchange 2010/2007. As a result, you may lose public folder data if you roll back the migration.

       1. To unlock legacy Exchange public folders, run the following command on the legacy Exchange server.

        Set-OrganizationConfig -PublicFoldersLockedForMigration:$False

       2. To set the PublicFolderMigrationComplete flag to $false, run the following command on the Exchange 2010 SP3 server:

       Set-OrganizationConfig -PublicFolderMigrationComplete:$False

       3. If Public Folders will be present in exchange 2013 then users will not go to exchange 2010/2007. To remove the public folders, run the below cmdlets

        Get-PublicFolderMigrationRequest | Remove-PublicFolderMigrationRequest -Confirm:$false
        Get-MailPublicFolder | Disable-MailPublicFolder -Confirm:$false 
        Get-PublicFolder -GetChildren  | Remove-PublicFolder -Recurse -Confirm:$false 
        Get-Mailbox -PublicFolder |Remove-Mailbox -PublicFolder -Confirm:$false

For On Prem to Office 365 migrations, use this technet which has slight changed steps are step number 5. -
Best of Luck, feel free to contact us in case of any issue

Prabhat Nigam | MVP Exchange Server

Team@ MSExchangeGuru

Keywords: Exchange 2010 public folder migration, Exchange 2013 public folders, how to migrate public folders to Exchange 2013, exchange 2013, exchange 2013 PF migration, how to migrate public folders from Exchange 2007 to exchange 2013

180 Responses to “Public Folders Migration from Exchange 2007/2010 to Exchange 2013”

  1. Herbert Says:

    Beautiful! Thanks so much! :)

  2. AMIT Says:

    Excellent documentation

  3. Sathish Says:

    Excellent Article.

  4. gagan Says:

    Thanks for the excellent article, after reading this I have successfully Migrate Public folders from exchange 2010 to 2013. Except not able to delete Public folder database from exchange 2010 EMC, getting error “The public folder database “PFDB01” contains folder replicas. Before deleting the public folder database, remove the folders or move the replicas to another public folder database” Also can you guide how I can delete mailbox database of exchange 2010?Can you guide me the next stop how I can decommission exchange 2010?

    Thanks again

  5. Wizkid Says:

    Thank you for Compliments :)

    @Gagan – I would suggest you to dismount the Public Folder DB and Enjoy 2013 PF for few Days. Once you
    are satisfied you can follow the technet link –

  6. Massimo Says:

    Great article!
    One question: does step n°4 require you to copy Scripts folder from Exchange2013 to Exchange 2007 server? AFAIK the Export-PubliFolderStatistics.ps1 does not exist in Exchange2007 folder. Is that correct?

  7. Wizkid Says:

    Yes Massimo. Please copy from 2013

  8. Kyle Says:

    Thanks for the steps, however I ran into an issue. After the move was autosuspended, and then I made the PreventCompletion changes and resumed the move, it would once again suspend saying that the original database was locked. I had to go back and unlock the original database and resume the move for it to complete successfully. Any ideas on why?

  9. Wizkid Says:

    @Kyle – I guess it will be replication delay.

  10. Kyle Says:

    @Wizkid – It was a single domain controller with a single Exchange 2010 and single Exchange 2013 test setup in a vmware lab. Replication should not be an issue. Even still, I let it sit for 3 days and it was still an issue. What would there be to replicate anyway? It was correctly reporting that the database was locked, as we did that in step 7 above. I essentially had to undo that step to complete the migration.

  11. Wizkid Says:

    Every configuration stays in AD so replication is important, You had not mentioned that you have 1 DC.
    Step 7 is required and we don’t change to false until role back. I will be more than happy to help your setup fixed. Do let me know if you can reproduce the same issue.

  12. NeWay Technologies – Weekly Newsletter #39 – April 18, 2013NeWay | NeWay Says:

    […] Public Folders Migration from Exchange 2007/2010 to Exchange 2013 – 18-Apr-2013 […]

  13. Anna Says:

    Hello, I’m interested in Public Folder migration cross-forest. I wasn’t able to complete it. Always stuck at New-PublicFolderMirationRequest with its remote parameters. Some of them are marked as “for Microsoft internal use only” as OutlookAnywhereHostName or AuthenticationMethod. And some of them aren’t even recognized, as RemoteCredential or RemoteMailboxServerLegacyDN. Although they are in help.
    I tryed many ways, combine sessions, experimenting with similar comands, etc. MS scripts for creating AD objects worked fine, but it’s not enough.
    Always stuck at required parameter SourceDatabase for New-PublicFolderMirationRequest. It can’t connect remotely without proper setting.
    I’m really unhappy, but I don’t give up… yet.

  14. Wizkid Says:

    @Anna- I have not tested cross forest migration yet but it should not be much of worry. If you can share the error then I might be able to suggest you any solution.

    I will test cross forest migration shortly and share.

  15. Mark Says:

    Nice Post. So here is a good one. I wish to create a Mailbox Database in Exchange 2010 but WITHOUT Public folders. I cannot see any way to get round the setting that a Mailbox database must be associated with public folders.

  16. Anna Says:

    Thanks for reply. It’s not just about error, ut’s about missing parameters in New-PublicFolderMirationRequest. The synatx is:

    New-PublicFolderMigrationRequest -OutlookAnywhereHostName -RemoteCredential -RemoteMailboxLegacyDN -RemoteMailboxServerLegacyDN [-AuthenticationMethod ] [-Organization ] …etc etc etc….

    but first parameter -OutlookAnywhereHostName is for internal microsoft use only.

    [PS] C:\Windows\system32>New-PublicFolderMigrationRequest -OutlookAnywhereHostName
    A parameter cannot be found that matches parameter name ‘OutlookAnywhereHostName’.
    + CategoryInfo : InvalidArgument: (:) [New-PublicFolderMigrationRequest], ParameterBi ndingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-PublicFolderMigrationRequest
    + PSComputerName :

    and others are the same, just for MS only or just not recognized. For example:

    [PS] C:\Windows\system32>$s = Get-Credential
    cmdlet Get-Credential at command pipeline position 1
    Supply values for the following parameters:
    [PS] C:\Windows\system32>New-PublicFolderMigrationRequest -RemoteCredential $s
    A parameter cannot be found that matches parameter name ‘RemoteCredential’.
    + CategoryInfo : InvalidArgument: (:) [New-PublicFolderMigrationRequest], ParameterBi ndingException
    + FullyQualifiedErrorId : NamedParameterNotFound,New-PublicFolderMigrationRequest
    + PSComputerName :

    But I send a note to MS and it is a real problem not just some complicated solving method, thay answered me today and will make me a solution.

  17. Wizkid Says:

    I will explain more once I will test and I might publish another article for it. If MS is answering your concerns then let us wait for their reply.
    These are my thought about the cmdlets:
    1. New-PublicFolderMigrationRequest -OutlookAnywhereHostName
    You have missed FQDN of OutlookAnywhere, as an example it should be New-PublicFolderMigrationRequest -OutlookAnywhereHostName
    2. New-PublicFolderMigrationRequest -RemoteCredential $s
    In this cmdlet you need to add RemoteMailboxServerLegacyDN, Below is the extract from technet.
    “You must use this parameter in conjunction with the RemoteMailboxServerLegacyDN parameter.”

    Reference used:

  18. Anna Says:

    If you run help new-publicfoldermigrationrequest -detailed , you can see there are parametrers details like this:

    This parameter is reserved for internal Microsoft use.

    You cannot simply use it, command new-publicfoldermigrationrequest will just answer you “cannot found”, as I posted before.

    And yes, for remotecredentials..

    The RemoteMailboxServerLegacyDN parameter specifies the server legacy distinguished name (DN) of the back-end server. To find the LegacyExchangeServerDN property, run the following command: Get-ExchangeServer | Format-List LegacyExchangeServerDN.

    This command surprisely doesn’t work. It just jump to few more rows.

    [PS] C:\>Get-ExchangeServer server | Format-List LegacyExchangeServerDN

    [PS] C:\>

    When it doesn’t return any value it’s useless.

  19. Steve Says:

    Just migrated from 2007 to 2013. Have had lots of issues, pub folders being one of them. Just used these instructions. I now have successfully migrated the folders!
    -Had to set -baditemcount on the migration request, because it initially failed.
    -Had the migration hang due to mailbox being locked. Had to rerun the command…
    Set-PublicFolderMigrationRequest –Identity \PublicFolderMigration -PreventCompletion:$false

    Aside from these issues (not including all my typos during the process) this process worked great. Thanks!!!

  20. MikeyRod Says:

    Hi Guys,

    Just so you know, for step 4, Export public folder hierarchy from source into CSV file, If your legacy server is 2007, I could NOT get this to work until I edited the export-publicfolderstatistics.ps1 script and removed the “ResultSize:unlimited” item on line 91 of the script. On line 91 of the script, you can see that it runs “get-publicfolder statistics servername -resultsize:unlimited”, which for me, was causing an error, thus not working.

    If you right click and edit the script, you can modify and save the script and try again. I hope this tidbit helps others.

  21. Wizkid Says:

    @Mikey – Thank you! This has been updated.

  22. MikeyRod Says:

    You’re welcome, WizKid….and shame on me for not thanking YOU in the first place. Great article and thanks for the help!

  23. Wizkid Says:

    Its okay Mikey. It was great to know my publication was any help for you.

  24. Exchange 2010/2007 to 2013 Migration and Co-existence Guide « Says:

    […] […]

  25. Rony Says:

    Thank you for this great article.
    I am facing an issue at the end of the process: when i try to remove the public folder database from Exchange 2007 i am getting this error “Object is read only because it was created by a future version of Exchange: 0.10 ( Current supported version is 0.1 (8.0.535.0).” since remove-publicfolderdatabase cmdlet does not exist in 2013 i am wondering how i can do that …

  26. Prabhat Nigam Says:

    @Mike – Sorry, I missed to approve and reply you. Here is your answer: We always create mailbox database without linking Public Folders. This is a configuration option in the properties of the mailbox database.
    Basically many organizations don’t use Public folders and they don’t create Public folder Database.

  27. Prabhat Nigam Says:

    @Rony – Check the below link for the Exchange 2007 PF removal – I would suggest these links before trying Adsiedit.msc

    Try removing from Adsiedit.msc but be careful. Take the systemstate backup before deleting.

    1. Launch ADSIEdit and connect to the “Configuration” container.

    2. Navigate to “Services –> Microsoft Exchange –> Org Name –> Administrative Groups –> Group Name –> Servers –> 2007servername –> Information Store –> Storage Group”

    3. Right click the “2007 Public Folder Database” and select “Delete”. Wait for the replication to occur.

  28. Exchange 2013 Public Folders – A step toward high availability & moving to Sharepoint « Says:

    […] Exchange 2013 Public Folders Migration – […]

  29. Simon Mutuku Says:

    [PS] C:\Windows\system32>Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport |
    Creating a new session for implicit remoting of “Get-PublicFolderMigrationRequest” command…

    RunspaceId : ec7748e2-3b24-479b-a98d-af2f502f940c
    Name : PublicFolderMigration
    Status : Failed
    StatusDetail : FailedOther
    SyncStage : CreatingFolderHierarchy
    Flags : IntraOrg, Pull, Suspend, SuspendWhenReadyToComplete
    RequestStyle : IntraOrg
    Direction : Pull
    Protect : False
    Priority : Normal
    Suspend : True
    SourceVersion : Version 14.3 (Build 123.0)
    SourceDatabase : Public Folder Database 1619818525
    SourceServer : HFDT1MBX08.******************************
    BatchName :
    OutlookAnywhereHostName :
    RemoteCredentialUsername :
    AuthenticationMethod : Basic
    RemoteMailboxLegacyDN :
    RemoteMailboxServerLegacyDN :
    BadItemLimit : 49
    BadItemsEncountered : 0
    LargeItemLimit : 0
    LargeItemsEncountered : 0
    FolderToMailboxMap : {\}
    QueuedTimestamp : 6/8/2013 4:22:39 PM
    StartTimestamp : 6/8/2013 4:44:04 PM
    LastUpdateTimestamp : 6/8/2013 4:44:05 PM
    InitialSeedingCompletedTimestamp :
    FinalSyncTimestamp :
    CompletionTimestamp :
    SuspendedTimestamp :
    OverallDuration : 1.18:53:06
    TotalFinalizationDuration :
    TotalDataReplicationWaitDuration :
    TotalSuspendedDuration :
    TotalFailedDuration : 1.18:31:40
    TotalQueuedDuration : 00:21:24
    TotalInProgressDuration : 00:00:01
    TotalStalledDueToCIDuration :
    TotalStalledDueToHADuration :
    TotalStalledDueToReadThrottle :
    TotalStalledDueToWriteThrottle :
    TotalStalledDueToReadCpu :
    TotalStalledDueToWriteCpu :
    TotalStalledDueToReadUnknown :
    TotalStalledDueToWriteUnknown :
    TotalTransientFailureDuration :
    TotalIdleDuration : 00:00:00
    MRSServerName :
    EstimatedTransferSize : 0 B (0 bytes)
    EstimatedTransferItemCount : 0
    BytesTransferred : 0 B (0 bytes)
    BytesTransferredPerMinute :
    ItemsTransferred : 0
    PercentComplete : 10
    PositionInQueue :
    PreventCompletion : True
    FailureCode : -2146233088
    FailureType : DataValidationException
    FailureSide : Target
    Message : Error: Property expression “All New Users” isn’t valid. Valid values are: Strings
    formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !,
    #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be
    embedded in an alias, but each period should be preceded and followed by at least
    one of the other characters. Unicode characters from U+00A1 to U+00FF are also
    valid in an alias, but they will be mapped to a best-fit US-ASCII string in the
    e-mail address, which is generated from such an alias.
    FailureTimestamp : 6/8/2013 4:44:05 PM
    IsValid : True
    ValidationMessage :
    OrganizationId :
    RequestGuid : 72b8a1ff-242e-4062-ac00-4242dfdc3a0e
    RequestQueue : DB21
    ExchangeGuid : 40726776-b9d0-46d8-a728-d1789c1d370b
    Identity : RequestGuid (72b8a1ff-242e-4062-ac00-4242dfdc3a0e), RequestQueue:
    Report : 6/8/2013 4:22:38 PM [HFDT1MBX18] ‘******************************/Servers/craadmin’ created
    6/8/2013 4:44:03 PM [HFDT1MBX16] The Microsoft Exchange Mailbox Replication service
    ‘HFDT1MBX16.******************************’ (15.0.620.24 caps:3F) is examining the request.
    6/8/2013 4:44:03 PM [HFDT1MBX16] Connected to target mailbox
    ‘40726776-b9d0-46d8-a728-d1789c1d370b’, database ‘DB21’, Mailbox server
    ‘HFDT1MBX16.******************************’ Version 15.0 (Build 620.0), proxy server
    ‘HFDT1MBX16.******************************’ 15.0.620.24 caps:3FCB07FFFF.
    6/8/2013 4:44:03 PM [HFDT1MBX16] Connected to source mailbox ”, database ‘Public
    Folder Database 1619818525’, Mailbox server ‘HFDT1MBX08.******************************’
    Version 14.3 (Build 123.0).
    6/8/2013 4:44:03 PM [HFDT1MBX16] Request processing started.
    6/8/2013 4:44:04 PM [HFDT1MBX16] Stage: CreatingFolderHierarchy. Percent complete:
    6/8/2013 4:44:05 PM [HFDT1MBX16] Initializing folder hierarchy from mailbox ”: 72
    folders total.
    6/8/2013 4:44:05 PM [HFDT1MBX16] Folder creation progress: 0 folders created in
    mailbox ‘40726776-b9d0-46d8-a728-d1789c1d370b’.
    6/8/2013 4:44:05 PM [HFDT1MBX16] Fatal error DataValidationException has occurred.

    ObjectState : New

    [PS] C:\Windows\system32>

  30. TBone Says:

    When I run .\Export-PublicFolderStatistics.ps1, I get:

    Parameter declarations are a comma-separated list of variable names with option
    al initializer expressions.
    At C:\Program Files\Microsoft\Exchange Server\Scripts\Export-PublicFolderStatis
    tics.ps1:16 char:168
    + HelpMessage = “Full path of the output file to be generated. If only
    filename is specified, then the output file will be generated in the current di
    rectory.”)] <<<<

  31. Prabhat Nigam Says:


    The format is: .\Export-PublicFolderStatistics.ps1 \\servername\path\filename.csv
    Did you miss file path or name…. See the help message.

  32. TBone Says:

    @ Prabhat Nigam

    This is the exact input:.\Export-PublicFolderStatistics.ps1 C:\PFMigration\PSmapnametosize.csv

    I have seen where you should be on PShell 2.0. I am updating now.

  33. Prabhat Nigam Says:

    Kindly use the below cmd.
    .\Export-PublicFolderStatistics.ps1 \\Servername\C$\PFMigration\PSmapnametosize.csv

  34. TBone Says:

    @ Prabhat Nigam

    Same results either way.

  35. Prabhat Nigam Says:

    share the folder PFMigration folder and use below cmd
    .\Export-PublicFolderStatistics.ps1 \\Servername\PFMigration\PSmapnametosize.csv

  36. TBone Says:

    I think it was Power Shell 2.0. It worked this time.

  37. Prabhat Nigam Says:

    It has to be unc path. 2013 does not accept c:

  38. TBone Says:

    @ Prabhat Nigam

    Well I was running script from 2007 not 2013. I used c: and it worked fine, but thank you for a quick response. I now am getting to many corrupt items when running

    New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server servername) -CSVData (Get-Content C:\temp\Mapgen.csv -Encoding Byte)

    What’s the parameter to allow multiple bad items?

  39. Prabhat Nigam Says:


    You might also need AcceptLargeDataLoss

  40. Doug Says:

    Thanks for the article.

    I have follow all the instrustions. The replication status Failed after abount an hour. Any suggestion would be greatly appreciated.

  41. Prabhat Nigam Says:

    This article very well as this is a tested article.
    I would like to know on which step you got replication failed.
    My first thought is any firewall.

  42. Brandon Says:

    Best article I found, thank you for taking the time to document.

    My issues: when I initiated New-PublicFolderMigrationRequest it ended up having an error. In order to get it to work I had to append “-BadItemLimit 1000” to get it to finally complete (however I did check the log to see that there were no missing items and 0byte missing), still not sure how I’d correct the errors it had.

    I’m also having the issue of “The public folder database ‘Public Folder Database’ contains folder replicas.”. I’m trying to find all links to the public folder database in ADSI Edit before removing it with that method (currently I removed my PF’s from the databases) via

    When I do a Get-PublicFolder command it errors out “There is no existing PublicFolder that matches the following Identity: ‘\’.” although Get-PublicFolderStatistics shows the folder items that got migrated and are still stuck on this machine (the storage group and database are the same as before and on the other server it shows the owner). How would you delete these remaining items? I’m assuming this is what’s keeping the DB from being removed.

  43. Prabhat Nigam Says:

    Bad Items can be corrupted items which can only deleted or left like this.

    If you are able to see any access all PFs from 2013 mailboxes then I would not mind removing it from ADSIEdit.

  44. TC Says:


    Great how-to!

    However under my V14\scripts directory, I don’t have Export-PublicFolderStatistics.ps1 or PublicFolderToMailboxMapGenerator.ps1.

    Can I get them from somewhere? #Stuck.


  45. Prabhat Nigam Says:

    Check on 2013

  46. TC Says:

    Thank you!
    All went through successfully and I can see my public folder mailbox, but I can’t see the Public folder itself…I don’t entirely understand it either…Any help would be great thanks.

  47. Prabhat Nigam Says:

    Where are you checking?

  48. TC Says:

    Under Public folders via ECP.

  49. Prabhat Nigam Says:

    Check in the shell

  50. Siva Says:

    Hi ,

    I am trying to migrate exchange server 2007 public folder to exchange online(office 365), actually I have tried many article to configure but I couldn’t able to do successfully. Can you please tell me how to do the migration for the same.


  51. Prabhat Nigam Says:

    Hey Siva

    This blog is not for O365 but it will be almost the same process.
    I am adding below technet links for you, I hope this will help.

  52. “Legacy Exchange Servers Decommission” Post Exchange 2013 Migration « Says:

    […] […]

  53. Cathy Allington Says:

    Thank you!! Does this process alsi migrate custom view on the Public Folder?

  54. Prabhat Nigam Says:

    I don’t see why will it not migrate but I recommend testing in lab before production.

  55. tony Says:

    Hi, i have a problem during public folder migration between exchange 2010 and 2013. It creates the hierarchy but stop at 26% and i have the status “StalledDueToReadUnknown”.

    Thanks for help

  56. Prabhat Nigam Says:

    Few things to check
    1. You had permissions
    2. On source side if there are item level permissions then clean it using exfolders.
    3. Any stall migration might need to be restarted.
    4. You might need to do the cleanup before restarting the migration.

  57. tony Says:

    Thanks for reply,the process had copied few messages so i think i have permissions but how can i verify this?
    how do you do the cleanup before restarting migration?



  58. Prabhat Nigam Says:

    For Verifying the permissions Please use Exfolders utility on 2010
    Download from here –
    How to use from here –
    Some Release notes –

  59. Exchange 2013: Cross Forest/ORG Migration from Exchange 2010/2007 « Says:

    […] Exchange 2013 PF Migration Guide – […]

  60. ttac Says:

    Hi there, thanks for your Manual, the Migration has worked but i ran into an issue. (From SBS Exchange 07 to Exchange 13 windows Server 12)
    I migrated all Public Folder and i can see them all in Exchange-Shell and ECP. On our legacy Exchange theyre gone (Toolbox -> Public Folders)

    Now my Problem is, when i connect my Administrator Mailbox in Outlook 2007, it only shows me 5 out of 10 Public Folders. Same with an other client.
    Whats my Problem here?


  61. Prabhat Nigam Says:

    You might need to verify the permissions!

  62. ttac Says:

    Thanks for your Reply, thats exactly what i found out. Sometimes you dont see the easiest solution.
    Thanks again for your manual!

  63. mike selman Says:

    I get an error migrating from 2010 to 2013.

    Version 14.3 (Build 123.0).
    Request processing continued, stage CreatingFolderHierarchy

    Fatal error MapiExceptionNoReplicaAvailable has occurred.

    ObjectState : New

  64. Prabhat Nigam Says:

    -You can’t replicate to 2013. You have to follow this article for the migration.
    -I would recommend to upgrade to 2013 CU2 if your servers are on CU1. This might resolve the issue.

    -Next check this forum link –

    -I also got the below Microsoft KB for the error you got. Make sure you have backup before following the resolution mentioned in this kb.

    Let me know if this helps.

  65. Mike Selman Says:

    I followed the steps in this article to the letter… Im not trying to replicate anything, that is the mystery. I will check the links though and report back.

  66. Mike Selman Says:

    CU2 fixed my issues.

    What gets me is that MS sent us this Action Pack of Exchange 2013 recently. We were only pushing Exch 2013 out this early to stay within MS Action Pack compliance requirements. They recently audited us and informed us we must roll out before Dec or we’d lose our 2014 Action Pack.

    As I pushed the initial install through it specifically asked if I wanted to check for updates which of course I did. Also, after install no updates were available via Windows Update, even as Server 2012 had the usual updates, patch day releases etc.

    It took scouring forums for a fix for our issue, to find a cumulative update is available. I hate it when I over look these things but MS are MS after all. Even when I called MS Support to use one of our Action Pack support session, they said not in this case, we’d have to pay the $260. In a nutshell, we’d have paid to have them tell us they have an update we should use. Typical.

    Thanks again!

  67. Prabhat Nigam Says:

    CU2 was suggested by me so you should have followed my suggestion as CU2 installation is always recommended.
    If there is an issue which is a bug and resolved by a service pack or cumulative update or hot-fix then Microsoft used to refund the case charges. Write to support Engineer’s manager.

  68. Mike Selman Says:

    Hi Prabhat, we didn’t actually go that route, instead I followed your advice. I had initially followed TechNet migration steps but after I found the error I discovered this page. Much more clear and concise steps here.

  69. Mike Selman Says:

    Did run into more issues further into the migration, but now I see that MS acknowledge them and will be releasing CU3 soon. This is why when we aren’t ‘forced’ we would wait for a Service Pack

  70. Prabhat Nigam Says:

    Hey Mike,
    Would you like to share the issues? I might be able to help you with any available work around.

    CU3 should be released soon. below blog is another place where you can comment and Microsoft team will have a look on your comments.

  71. Toby Says:

    I have completed most of the process but after kicking off the New-PublicFolderMigration, and getting no errors, the status has been stuck at QUEUED for 12 hours. We do have a large PF store (18GB). No events in any logs point to any problems. Checking status, or making token change like baditemlimit and then resuming the PFmigraiton has no affect. Can’t seem to find any information on what happens after QUEUED but before the process starts moving items.

  72. Prabhat Nigam Says:

    Try to check report after running the command

    Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl

  73. Toby Says:

    Still shows as being queued.

  74. Toby Says:

    I tried to paste the output of the command but it won’t post. Can I email that to you. Looks okay to me but maybe you’ll see something I’ve missed.

  75. Prabhat Nigam Says:

    email me –

  76. Prabhat Nigam Says:

    Update to the Toby’s issue.
    – There were 2 issues
    – All mailbox databases were removed so there was no system mailbox. I have reported this test case to Microsoft and they are testing this test case.
    – Space in the alias of the Public folders.

    After removing the space from the alias of the PF, migration is running.
    I assume space was the issue in Simon’s case as well.

  77. John Says:


    I migrated succesfully an ex2007 to 2013 with 85 mailboxes. Now, after the remove of the public Folder database in the EMC of the ex2007 i get now the following error:

    Eventid 2937 MSExchange ADAccess Process w3wp.exe FE_RpfHttp. Object CN Mailbox Database (ex 2013) ,… Property PublicFolderDatabase is on value Domain/configuration/deleted Objects/PublicFolderDatabase DEL:fxxxx-xxxx-xxxx-xx, set and Shows up to Container deleted objects into AD. You have to fix it asap..

    Ok, i figured out in the adsi edit the value. But, if i delete this value, -> if i look into the emc 2013 i the Primary Hierarchie and secondary and everything is working well and all users have their public Folder <- what happends? i readed a lot, to set it to the value of the CN Mailbox Database (ex 2013). Which value should i copy paste?

    Next, i have the publicfolder into the same database like the mailboxes.

    Would be happy to get a right answer, cause at this time everything works 101% perfect! :)

    Thanks, John

  78. Prabhat Nigam Says:

    Don’t worry. Exchange 2013 does not use this property. Alternatively you can run the below cmd to remove this configuration

    Get-mailboxdatabase | set-mailboxdatabase -PublicFolderdatabse $null

    I will not recommend using Adsiedit.
    Let me know.

  79. Jay Says:

    Hello Prabhat Nigam,
    I am getting the below error while migrating PF from Exch 2010 to Exch 2013 pls advise

    WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an instance
    of an object.
    Object reference not set to an instance of an object.
    + CategoryInfo : NotSpecified: (:) [New-PublicFolderMigrationRequest], NullReferenceException
    + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.RecipientTasks.NewPublicFold
    + PSComputerName :

  80. Prabhat Nigam Says:

    It seems you are running the 6th step. Correct me if it is not the case.
    Make sure your legacy PF replication has finished, there is no -,\ or some unexpected characters in the legacy PF name and alias.
    Give me the command which you are running. Let me know more about your environment.

  81. Jay Says:

    Hi Prabhat,
    Yes I am running 6th step. how can I check the legacy PF replication?
    my environment is
    Single exchange server with 100-150 mail boxes and an public folder DB, it is exch 2010.
    I installed Exch 2013 as CAS, Mailbox in a single server and moved all the mailboxes, including arbitration mailboxes.
    now I try to move the publicFolders as per the steps which you mentioned…
    and While doing 6th step I am getting this error…
    please I need help to move PF successfully

  82. Jay Says:

    Hi Prabhat,
    the below is the size.csv export
    “\IPM_SUBTREE\Internet Newsgroups”,”0″

    and Map.csv is below

    Creating PF mailbox using the below cmdlet
    New-Mailbox -PublicFolder Mailbox1 -HoldForMigration:$true -Database “Mailbox Database 0039810732”

    Then running PF migration cmdlet as below (6th step)
    New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -Server hitexch-2010) -CSVData (Get-Content c:\pfimport\PF-mailbox.csv -Encoding Byte)


  83. Jay Says:

    Hi Prabhat,
    Also I checked the the legacy PF replication as below cmdlet
    Get-OrganizationConfig | select PublicFoldersLockedforMigration, PublicFolderMigrationComplete

    PublicFoldersLockedForMigration PublicFolderMigrationComplete
    ——————————- —————————–
    False False

    Please Advise,

  84. Prabhat Says:

    Do u see any data in the PF?
    If yes then you need to get permissions. It does not seems you have access to it. You can see the size is showing zero in the size.csv

  85. Jay Says:

    Hi Prabhat,
    There were no any data on the PF and we are not using it also, Just I migrated from Exch 2003 to exch 2010 and now I would like to move to Exchange 2013 that’s all. In this case how do I migrate?

    If I remove PF without migrating to decommissioning exch 2010 server will affect any ting to the outlook users, or AD environment, or I will face any serious problems in feature?

    Please Advise,

  86. Prabhat Nigam Says:

    Exchange 2013 does not use the PF the way it was used in the 2010 and 2003.
    So if it is blank then no need of migration. User will not loose anything as there is no data.

  87. Jay Says:

    Hi Prabhat,
    Thanks a lot…for the advise


  88. dean132 Says:

    Hi would it be possible to use this process to migrate my Exchange 2007 Public Folders to Exchange 2007 Resource Mailboxes? We are trying to get out environment ready for an O365 migration and we have around 1000 public folders most with public calendars in. We are looking for a way to automate the process.

  89. Prabhat Nigam Says:

    Export the data to pst then create resource/shared mailbox and import the data.

    I would recommend a test before Production data.

  90. Exchange 2007 to 2013: Public Folder Migration Issue « Says:

    […] Public Folders migration is not moving forward after step 6 in the migration blog here […]

  91. Zarky Says:

    Hey all
    So I’ve been stuck on this PF migration for some time, AD permissions and am running out of ideas
    What I’ve tried
    user migrating PF can access all the pf’s
    user is Org Admin and PF admin on 2007 and 2013 groups.
    User has full access to the root PF
    This is the error…
    I’ve repeatedly deleted the PF on 2013 and recreated for migration

    Any assistance would be appreciated.

    FailureCode : -2146233088
    FailureType : ADOperationException
    FailureSide : Target
    Message : Error: Active Directory operation failed on This
    error is not retriable. Additional information: Insufficient access rights to
    perform the operation.
    Active directory response: 00002098: SecErr: DSID-03150BB9, problem 4003
    –> The user has insufficient access rights.
    FailureTimestamp : 2/26/2014 3:21:07 PM
    IsValid : True
    ValidationMessage :
    OrganizationId :
    RequestGuid : 168498fe-cc9e-4d25-a7ff-b2e376c9f2cd
    RequestQueue : DB01
    ExchangeGuid : 3824a2c8-6597-4cd4-a28e-f06b3aa137c1
    Identity : 6d80a38a-f7e0-4589-bf76-c6ae64ae1097\168498fe-cc9e-4d25-a7ff-b2e376c9f2cd
    DiagnosticInfo :
    Report : 2/26/2014 3:20:59 PM [CORP2013EX01] ‘ Accounts/Exchange
    PublicFolderAdmin’ created request.
    2/26/2014 3:21:06 PM [CORP2013EX01] The Microsoft Exchange Mailbox Replication
    service ‘’ (15.0.775.35 caps:3F) is examining the
    2/26/2014 3:21:06 PM [CORP2013EX01] Connected to target mailbox
    ‘3824a2c8-6597-4cd4-a28e-f06b3aa137c1’, database ‘DB01’, Mailbox server
    ‘’ Version 15.0 (Build 775.0), proxy server
    ‘’ 15.0.775.35 caps:07FFCB07FFFF.
    2/26/2014 3:21:06 PM [CORP2013EX01] Connected to source mailbox ”, database
    ‘CORP2007MBX01\Second Storage Group\Public Folder Database’, Mailbox server
    ‘’ Version 8.3 (Build 330.0).
    2/26/2014 3:21:06 PM [CORP2013EX01] Request processing started.
    2/26/2014 3:21:07 PM [CORP2013EX01] Stage: CreatingFolderHierarchy. Percent
    complete: 10.
    2/26/2014 3:21:07 PM [CORP2013EX01] Initializing folder hierarchy from mailbox ”:
    340 folders total.
    2/26/2014 3:21:07 PM [CORP2013EX01] Folder creation progress: 0 folders created in
    mailbox ‘3824a2c8-6597-4cd4-a28e-f06b3aa137c1’.
    2/26/2014 3:21:07 PM [CORP2013EX01] Fatal error ADOperationException has occurred.

  92. Prabhat Nigam Says:


    I hope this is single forest migration.
    This looks like AD issue, the user should have org management and domain admins. check if this id has inheritance check.
    Also check your AD is healthy. IF it is not healthy then on one of the DC we might miss this user permission.
    After adding the permissions you need to log off and login back to make it effective.

    On 2007 use PFDAVAdmin and remove item level permission. This is another option if nothing works.

    Let me know if this helps.

  93. Zarky Says:

    Thanks for looking at this.
    I did find that when the user is both Domain admin, org management and exchange org management the the “inheritance check” gets unchecked after a while.
    if I omit the domain admin the inheritance stays checked.
    I’ve been at this for 3 weeks and its looking ridiculous. Microsoft exchange says it and AD issue open a ticket with them and AD says its and exchange 2013 issue.
    I just need to know where exactly the permission is failing? Is it on the 2007 side or on the 2013 side? are there logs I can enable to follow step by step what exchange is doing and where it fails?

  94. Prabhat Nigam Says:

    could you rerun the command just after you add the inheritance permission on verify. Looks like AD issue.

    Are you saying you have a Microsoft ticket open? You need to make both of them discuss.

    By the way got any chance to try pfdavadmin.

  95. Zarky Says:

    Hi Prabhat
    I looked at PFVDAdmin, really stopped using that when 2007 exchange came out. Feel more comfortable with powershell.
    Going back to PFVDAdmin feels “clunky”. all the permissions on the legacy public folders is ok.
    Microsoft saying it looks like the Databases within the DAG are causing the issue. Normal mailboxes are ok but the public folder mailbox creation is not ok.
    They suggest to create a new database and not add it to the DAG then see if the public folder to mailbox works, after move the mailbox into the database within the DAG.
    working this…

  96. Prabhat Nigam Says:

    Possible to have an issue within the database but I have never heard that Dag will be a problem.

    What is your exchange 2013 level.

    I think I would have asked for a Microsoft link which says migrate PF on a non-dag database.

    If it works for you then the next worry is to replicate the Hugh database file to 2nd server of DAG.

  97. Zarky Says:

    An update to this case.
    Im hoping this thread will be searchable for others as the answer is simple but undocumented and very misleading.
    Run get-mailpublicfolder on the 2007 exchange server, look for YELLOW warnings similar to those you get on Get-mailbox and get-distributionlist.
    Yellow warning saying something like this:

    WARNING: Object Exchange System Objects/Research & Technical Service has been corrupted
    and it is in an inconsistent state. The following validation errors have occurred:
    WARNING: “Research & Technical Service” is not valid for Alias. Valid values are: Strings formed with characters from a
    to z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or
    more periods may be embedded in an alias, but each one of them should be preceded and followed by at least one of the
    other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a
    best-fit US-ASCII string in the email address which is generated from such an alias.

    Do a
    get-mailpublicfolder “warning PF here” | select identity, alias (on the exchange 2007 box)

    Verify that Alias has no spaces or any other special characters not in the warning list…..

    3 weeks of this! WOW ms…. no KB for us? oh yes a $2500 support bill.

    This environment came from exchange 2000 hence this kind of show stopping error.


    Exchange 2013 is CU3
    The Create new DB and PF on that DB also failed (not in the DAG).

  98. Prabhat Nigam Says:

    I think I said the same thing.

    Anyways, let us see what we can do.

    1. Check if setup.exe /preparedomain fix this issue. If not then try the next 2 steps.
    2. Use PFDavadmin and propagate the permission of your id to all PFs. Take the owner or editor permission at the root.
    3. Add full access and send as to your id on the 2013 PF mailbox. Now restart “Exchange mailbox replication service”.

    Meanwhile ask for the escalation in MS for the escalation Engineer to come and help you.

  99. Zarky Says:

    The case is resolved

    ./setup /pd and ./setup /pad did not work, this was MS’s first troubleshooting step.

    The permissions were perfect what was wrong was the “Alias” field for mail enabled public folders has a “space” in it. This threw an AD error looking like a permissions issue when attempting to do a PF migration.

    I got an escalation out of India to Dallas TX. This 3rd lvl support drilled to the issue within 5 min.
    Case Solved

    Thanks All

  100. Prabhat Nigam Says:


    Happy to see you are in happy zone and moving.
    But unhappy to see this solution. I assumed that you have checked this. Updating the blog as a pre step.
    At 76 number comment I have shared the solution of other person. Which has mentioned alias space as a solution.
    I think MS also suggested you earlier to check the space. Space and special characters are the basic configurations

    By the way TX support always takes 5 minutes. They are the best and last level so only look for them when nothing else left.

  101. Wes Says:

    Hey Man,

    I’m getting error “StalledDueToMailboxLock”. I’ve tried everything from restarting services, mailbox servers and dismount databases. It’s still give the same error after initialization. Do you have any idea of what could be the error.


  102. Prabhat Nigam Says:

    This is a very common issue. Are you stuck on step 7. If yes then Try the following:

    1. Try to restart the Information store on the source PF mailbox servers. This can be coming because of this command has not replication to all other PF replica servers

    2. Run the step 7 on Source PF Server.

    3. Restart information store on Exchange 2013 server.

    4. Verify your permissions, you should be org management and domain admin.

  103. Wes Says:

    I’m stock on Step 5. When I did step 5, it upload 95 GB of data. I had to suspend it for about a month due to change freeze.
    When I tried to resume it to upload the current changes, it immediately gave me the error “StalledDueToMailboxLock”.
    I do have org management and domain admin.
    I tried restart the Information store on the source PF mailbox servers and information store on Exchange 2013 server.
    It took a week for that much data to upload, I’m trying not to remove it and restart over.


  104. Prabhat Nigam Says:

    Normally this issue comes of step 7.
    Step 5 is mailbox creation so I assume you are at step 6.
    We have also heard that resume worked for some people but in your case I would recommend to do it from start because we hold it for long.
    I think 95 GB in 1 week is too slow.

    Could you check the network and load balancer? Load balancer has also caused the issue for few customer.

  105. Samuel Fossett Says:

    This is really interesting, You are a very skilled blogger.

    I have joined your rss feed and look forward to seeking more of your great post. Also, I have shared your web site in
    my social networks!

  106. Prabhat Nigam Says:

    All – Watch for this attribute

    This parameter prevents users from accessing the public folder hierarchy on the specified public folder mailbox. For load-balancing purposes, users are equally distributed across public folder mailboxes by default. When this parameter is set on a public folder mailbox, that mailbox isn’t included in this automatic load balancing and won’t be accessed by users to retrieve the public folder hierarchy. However, if you set the DefaultPublicFolderMailbox property on a user mailbox to a specific public folder mailbox, the user will still access the specified public folder mailbox even if the IsExcludedFromServingHierarchy parameter is set for that public folder mailbox.

  107. Prabhat Nigam Says:


    To do a hierarchy sync the PF mailbox use the command below:
    Update-PublicFolderMailbox –Identity ‘PFMBX2’ –InvokeSynchronizer –FullSync (where PFMBX2 is the name if the PF mailbox you want to synchronize)

    You can also use the below cmd to troubleshoot or check the syncinfo of the PF hierarchy. Run the command and look for Syncinfo


  108. Joe Says:

    I am in the middle of a 2010 to 2013 Exchange Migration. I have the VIPs of the company left to migrate, if I migrate the Public Folders from 2010 to 2013 will the 2010 mailboxes be able to access the Public Folders on 2013.

    Thanks in Advance,

  109. Prabhat Nigam Says:

    Answer is No.
    This is mentioned in the Assumptions.

    You need to move VIPs before Completing the PF migration.
    You can complete till step number 6 anytime because it just moves the data to 95%.

  110. Joe Says:

    That was what I was assuming from the documentation I had read, but wanted confirmation. So if I did complete through step 5 and it was a couple more business days before the VIPs were moved would I have to repeat the process? This is my first Exchange 2013 migration so I’m being extra careful.


  111. Prabhat Nigam Says:

    No Worries Joe

    Hope you got the answer. :)

  112. Joe Says:

    So I kicked off the migration but it looks like the Public Folders are in a stalled state due to HA. The Exchange 2013 is in a DAG, I have done a fair bit of looking around for a solution. So does anyone have any idea how to get this data to migrate as part of step 5?

    My thought is postpone database replication for a try, but I’m looking for a little insight from someone more knowledgeable than I.


  113. Greg Says:

    If a Public Folder on Exchange 2010 has no information stored in it, is it safe to delete it and create a new Public Folder on Exchange 2013? Avoiding the long migration process?

  114. Ratish Nair Says:

    @Greg – Absolutely.

  115. Prabhat Nigam Says:

    If empty then just delete it, no need to create new one from exchange requirement point if view.

  116. Greg Says:

    Thats great, I know it sounds like an obvious question but though I would check first.

  117. J.D Says:

    Good Job, thank you !

  118. Jean-Luc Says:

    thank you for this article, great!
    Do you know if it exist a transition befor the migration.
    When you migrate your mailboxes on the other organization, how can you access to public folders on the old organization? Thx

  119. Prabhat Nigam Says:

    During transition exchange 2013 points to Legacy PF DB.
    Run the following command on 2013 shell to see the PF DB on 2013 database.

    Get-mailboxdatabase | FL Name,PublicFolderDatabase

    But this is for the same org upgrade.
    In case of Migration from one forest to another you might need to share a old forest common mailbox to access PF.

  120. Jean-Luc Says:

    I understand thank you.
    Is it possible to share PF from Exchange 2010 from another organization?…
    I think we must use OWA links…

  121. Prabhat Nigam Says:

    Yes OWA link is the only option. It can’t connect in same outlook.

  122. Prabhat Nigam Says:

    You need to give the url and keep user account active.

  123. LeBricoleur Says:

    Hi Bonjour

    I m migrating public folder 2010 to 2013

    When i do :

    Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics -IncludeReport | Format-List

    I have a lot of line like this

    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-18-33-94-00-00 ». Ce dossier peut être
    lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
    23/05/2014 19:18:02 [serveur] Avertissement : échec de recherche ou de liaison de l’objet destinataire « 96-7D-85-6C-DC-A6-83-42-AC-77-A4-5E-BD-CD-52-9B » dans
    Active Directory pour le dossier public à extension messagerie « Public Root/IPM_SUBTREE/Secrétariat RC/PAYS/VENEZUELA/2006/SINCOR » avec l’ID d’entrée «
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-13-4D-8A-00-00 ». Ce dossier peut être
    lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
    23/05/2014 19:18:52 [serveur] Avertissement : échec de recherche ou de liaison de l’objet destinataire « 25-86-EC-2D-ED-25-C6-49-83-B6-5F-E9-8C-2E-34-A4 » dans
    Active Directory pour le dossier public à extension messagerie « Public Root/IPM_SUBTREE/Secrétariat RC/Repertoire 2007 » avec l’ID d’entrée «
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-11-F5-9D-00-00 ». Ce dossier peut être
    lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.
    23/05/2014 19:18:57 [serveur] Avertissement : échec de recherche ou de liaison de l’objet destinataire « ED-80-51-1F-67-6A-B9-41-AA-B8-0C-14-C4-BF-07-A3 » dans
    Active Directory pour le dossier public à extension messagerie « Public Root/NON_IPM_SUBTREE/EFORMS REGISTRY/Organization(409) » avec l’ID d’entrée «
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-00-1F-49-00-00 ». Ce dossier peut être
    lié manuellement en exécutant la cmdlet Enable-MailPublicFolder une fois la migration terminée.

    it scared me, what does it means ? Do i do something wrong?
    I have let it work
    And when i check status i have this :

    Statut: Failed
    Détails status : Failed other
    Syncstages : Copying message
    Estimed transfert size : 0
    Pourcentcomplete : 95

    What do i do? Can You help me? I m a little scared right now


  124. Chonta Says:


    i have run the Migration as Posted here and all Folders migrated from 2010 to 2013.
    But since then the Exchange 2013 try to deliver mails for the Publicfolder to the old exchange 2010.
    I dont know why.

    Pls Help

    Servers ar restartet, all adresslists are updatet, but new Mails wont arrive the Folders and the Exchange tryes to send them to the old one.



  125. Chonta Says:

    Ex 2013
    Get-Mailbox -PublicFolder | Set-Mailbox -PublicFolder -IsExcludedFromServingHierarchy $false

    Set-OrganizationConfig -PublicFolderMigrationComplete:$true

    Must be done and than it works

  126. Prabhat Says:

    Sorry I am running extremely busy so could not answer in time.

    Great to see you got a fix.

  127. LeBricoleur Says:


    Can You help me for my problème please?


  128. Prabhat Nigam Says:

    I am trying to help everyone but 24hrs days is short for me.
    I converted your text to English so when ever you post any error next time then please convert to english.
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-18-33-94-00-00 ” . This file can be
    manually linked by running the cmdlet Enable- MailPublicFolder once the migration is complete .
    5/23/2014 7:18:02 p.m. [ Server] Warning: Failed to link research or the recipient object ” 96 -7D -85- 6C -DC- A6 -83 -42- AC- 77 -A4 -5E -BD- CD -52- 9B ” in
    Active Directory for mail-enabled public folder ” Public Root / IPM_SUBTREE / Secretariat RC/PAYS/VENEZUELA/2006/SINCOR ” with the entry ID ”
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-13-4D-8A-00-00 ” . This file can be
    manually linked by running the cmdlet Enable- MailPublicFolder once the migration is complete .
    5/23/2014 7:18:52 p.m. [ Server] Warning: Failed to link research or the recipient object ” EC – 25-86 -2D -ED -25- C6 -49 -83- B6- 5F -E9 – 2E- 8C- 34 -A4 “in
    Active Directory for mail-enabled public folder ” Public Root / IPM_SUBTREE Secretariat / RC / Repertoire 2007″ with ID input ”
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-11-F5-9D-00-00 ” . This file can be
    manually linked by running the cmdlet Enable- MailPublicFolder once the migration is complete .
    5/23/2014 7:18:57 p.m. [ Server] Warning: Failed to link research or the recipient object ” ED -80 -51- 1F -67- 6A -B9 -41 -AA- B8- 0C- 14 C4 -BF -07- A3 “in
    Active Directory for mail-enabled public folder ” Public Root / NON_IPM_SUBTREE / EFORMS REGISTRY / Organization (409) ” with the entry ID ”
    00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-36-B9-C6-5D-38-99-D6-11-9B-D6-00-08-02-55-A6-70-00-00-00-00-1F-49-00-00 ” . This file can be
    manually linked by running the cmdlet Enable- MailPublicFolder once the migration is complete .

    it scared me , what does it means clustering ? Do i do something wrong?
    I have let it work
    And when i check status i have this:

    Status: Failed
    Details status: Failed other
    Syncstages : Copying Message
    Estimed transfer size: 0
    Pourcentcomplete : 95


    Looks like you have very big names of PFs. Here is my recommendation
    1. Remove any space from legacy PF
    2. Remove \ from legacy PFs
    3. Also try to keep alphanumeric name of the PFs
    4. If you have some names like these then change them to a meaningful name.

  129. LeBricoleur Says:

    Thank You @Prabhat Nigam

    Do You have any script for do all of change?

  130. Prabhat Says:

    I don’t have any script. I have always done it manually. I know it’s time taking and very boring.

  131. LeBricoleur Says:

    Ok thank You for help
    I do not known how i Will do That because There is a looooot of folder/files like who have the problem
    I Will try and i come back later

  132. LeBricoleur Says:

    i have launch again the script with -AcceptLargeDataLoss true -BadItemLimit 100000

  133. Arvind Says:

    I have two public folders between two AD sites and they are replicated. When I do the migration (from 2010 to 2013), should I do the migration in both sites or just one site? If I need to migrate in both sites, can I start it simultaneously or should I wait for one to finish before I start second? Also, after migration the replication need to be started manually or it will start automatically?
    Thank you for your help.

  134. Prabhat Nigam Says:

    Hey Arvind,

    PF migration will read all PFs so only one PF server database is good enough. You will see the PFd in the input file.

    Exchange 2013 is changing PF DB to a mailbox which will replicate with DAG.

  135. Arvind Says:

    Thanks Prabhat for quick reply. Yes it retrieves all PFs, I guess my confusion is- what will happen in the second site and how the PF mailboxes will be created in second site Exchange servers? will it be created automatically on the Exchange server available in the second site or I will have run the same process to create the PF mailboxes and do migration?

  136. Prabhat Nigam Says:

    DAG will replicate to the 2nd site. Make sure you have copy of this mailbox database on the other side.
    There is no other way to replicate in the 2nd site.
    Over all I think you need a consultant to explain the Exchange 2013 PF design and workflow.
    Check out my youtube video to learn more. Youtube tab has links.
    mail me at if you are interesting in hiring a consultant.

  137. MX Says:

    Hi Prabhat,
    I’m facing a weird error when migrating public folders from 2010 to 2013SP1:

    7/11/2014 5:08:20 PM [E2013] Stage: CreatingFolderHierarchy. Percent complete: 10.
    7/11/2014 5:08:20 PM [E2013] Initializing folder hierarchy from mailbox ”: 122 folders total.
    7/11/2014 5:08:20 PM [E2013] Folder creation progress: 0 folders created in mailbox
    7/11/2014 5:08:30 PM [E2013] Folder hierarchy initialized for mailbox
    ’48f5020f-4185-4d4f-9640-4eb31fa590bf’: 100 folders created.
    7/11/2014 5:08:31 PM [E2013] Warning: Failed to find or link recipient object
    ‘2A-5C-8C-67-00-C2-F8-47-A5-7B-61-7B-F9-61-F0-BA’ in active directory for mail enabled public folder
    ‘Public Root/IPM_SUBTREE/eigedomsskatt.(postmottak)/Feil.oppdaget’ with EntryId ’00-00-00-00-1A-44-73-90
    4-22-00-00′. This folder can be linked manually by running Enable-MailPublicFolder cmdlet after the
    migration completes.

    7/11/2014 5:08:40 PM [E2013] Folder hierarchy initialized for mailbox
    ’79dd4f2a-6e91-4adf-ba86-843cef641cff’: 4 folders created.
    7/11/2014 5:08:40 PM [E2013] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
    7/11/2014 5:08:40 PM [E2013] Initial sync checkpoint progress: 0/122 folders processed. Currently
    processing mailbox ’48f5020f-4185-4d4f-9640-4eb31fa590bf’.
    7/11/2014 5:08:41 PM [E2013] Transient error MapiExceptionJetErrorTableDuplicate has occurred. The
    system will retry (1/60).

    I can see a number of such lines with MapiExceptionJetErrorTableDuplicate.

    7/11/2014 5:15:06 PM [E2013] Connected to source mailbox ”, database ‘pf2010dbnamehere’, Mailbox server
    ‘fqdnhere’ Version 14.3 (Build 181.0).
    7/11/2014 5:15:06 PM [E2013] Request processing continued, stage CreatingInitialSyncCheckpoint.
    7/11/2014 5:15:07 PM [E2013] Transient error MapiExceptionJetErrorTableDuplicate has occurred. The
    system will retry (3/60).

    [PS] C:\PF>Get-PublicFolderMigrationRequest

    Status : InProgress
    StatusDetail : TransientFailure
    SyncStage : CreatingInitialSyncCheckpoint
    ItemsTransferred : 0
    PercentComplete : 15

    It stalls at 15% and doesn’t seem to move forward. How to fix this issue?

  138. lee Says:

    Evening All
    I am stuck on the PF migration process.

    Step 5 create the public folder mailbox. I seem to get some AD permissions/insufficient rights – access denied error, although I can create a “normal” mailbox.
    Seems to be the same issue as comment 91 INSUFF_ACCESS_RIGHTS. I know any account that is or has had domain admin permissions etc. gets flagged and inheritance removed automatically. I don’t think its the account that is causing the issue more likely Exchange trusted system related but I have hit a brick wall.
    Any help at all would be greatly received.

  139. Prabhat Nigam Says:

    @ Lee
    Could you share the group membership. Did you follow this blog from the top? if not could you review the steps to make sure you have not missed any step.

  140. Genia Rayburn Says:

    Wow that was odd. I just wrote an very long comment but after I clicked submit my comment didn’t show up. Grrrr… well I’m not writing all that over again. Anyhow, just wanted to say wonderful blog!

  141. Heni Feinberg Says:

    We have an E2010 PF of a 10GB size, when I run the script it suggest a single Mailbox 1, I will need a future expansion of about additional 10GB space of PF.
    How can I specify space for expansion ?
    Is it better to go with a single PF Mailbox of that size or manually create multiple PF Mailboxes and how many ?

    Thanks in advance,


  142. Prabhat Nigam Says:

    Go with the mailbox database limit for the mailbox.
    you can decide how big a mailbox you wish to keep. I would suggest not more than 5GB and I will configure 2-5 PF mailboxes but again it depends on number of mailbox databases we have in your exchange 2013.

  143. Heni Feinberg Says:

    Hi Prabhat,
    As you suggested I used :
    PublicFolderToMailboxMapGenerator.ps1 5000MB c:\pf\PFmapNameToSize.csv c:\pf\PFmapFolderToMailbox-5GB.csv
    And I get an output of only two mailboxes Mailbox1 and 2. So in this case each Mailbox will be limited to 5GB each so total of 10GB and no room to grow.

    When I use PublicFolderToMailboxMapGenerator.ps1 2000MB then I get 5 Mailboxes, each 2GB again no room to grow. I am left with the only option, using PublicFolderToMailboxMapGenerator.ps1 20000MB which creat a Single Mailbox1, but room to grow.

    What other options do I have?

    As always,thanks in advance Henri

  144. Prabhat Nigam Says:

    when you specify the size with the map generator command, Exchange decides the number of mailboxes you need to accommodate this data if the PF mailboxes are of that size and it does not configure the mailbox size.

    PF mailbox adapts a normal mailbox size property you have configure on mailbox database limits or on the properties of the mailbox.

    So create 5 PF mailboxes and configure the size on mailbox property after you create a PF mailbox.

  145. Henri Says:

    Thanks again for the quick reply,
    Now i get it!
    One additional thing, when i select a 2GB size i get 5 mailboxes but the path of these mailboxes does not reflect our PF tree, the suggested path created by the PS are relative to size. So it cerats mailboxes with same parent folder with child path. Say i have a 2010 PF pare path root/HR that has 1GB and a sub folder root/HR/Deptmt/users that mesure 2 Gb, tthen the output of the PS file will be of 3 mailboxes One for the root one for the root/HR and another mailbox for the root/HR/deptmt/users. The PS output will includ all small sizes folder in the root folder itself an not spartely like we want.
    What can be done ?

  146. Prabhat Nigam Says:

    Post the output of Mapgen.csv. I am not clear right now until I see your output file.

  147. Henri Says:

    Ok, I will Mondy as I am out of the office right now.

  148. Heni Feinberg Says:

    Hi Prabht,
    here is the output for a size of 1.5GB:
    “Mailbox3″,”\IPM_SUBTREE\Rapports\Rapports de consommation NG”
    “Mailbox5″,”\IPM_SUBTREE\VTES-SC-MKTG\Service Conseil\Canada\Demandes entrantes\Archives SAC\Cas r gl s\Archives\2002 2009”
    “Mailbox6″,”\IPM_SUBTREE\VTES-SC-MKTG\Service Conseil\Canada\Demandes entrantes\Archives SAC\Cas r gl s\Archives\2010”
    If I select a size smaller than the largest existing folder say 1GB I get the following message:

    The size of the folder @{FolderName=\IPM_SUBTREE\VTES-SC-MKTG\Service Conseil\Canada\Demandes entrantes\Archives SAC\Cas r?gl?s\Archives\2010; FolderSize=1256229463} (1256229463)is greater than the mailbox size 1048576000
    Unable to load public folders…

    As you can see from the PublicFolderToMailboxMapGenerator.ps1 the largest folder size is: “\IPM_SUBTREE\VTES-SC-MKTG\Service Conseil\Canada\Demandes entrantes\Archives SAC\Cas réglés\Archives\2010 1256229463”

    Thanks for letting me know

  149. Heni Feinberg Says:

    Hi Prabht,
    I discover a strange issue: I created a Master Hierarchy Mailbox1, when a user send a mail to a Dynamic Distribution List based on a OU where the mailbox is, he get an autoreply from:
    The mailbox of the recipient is a problem. Try sending the message. If the problem persists, contact technical support for your organization.

  150. Prabhat Nigam Says:

    If this is a PF mailbox then You can’t receive email on PF mailbox. You will receive the email for multiple PFs inside.
    If it is something else then you can post issue in MS forum here –

    Lets talk about the PF issue here:
    1. In the PF output I can see some PF have space, could you remove space from their name and alias.
    2. If you see the defined mailbox size is smaller then the actual PF size then we can define higher size but it does not matter as far as your actual mailbox size is higher than this PF. So this is a warning to explain if you keep the mailbox size as defined in the command then you will not be able to move this PF.

  151. Henri Feinberg Says:

    Thanks Prabht,

    As for the spaces, there are spaces Only on display names (General Tab), not on the aliases.

    As per MS, they talk Only about backslashes:

    2.If the name of a public folder contains a backslash \, the public folders will be created in the parent public folder when migration occurs. Before you migrate, we recommend that you rename any public folders that have a backslash in the name.

    a.In Exchange 2010, to locate public folders that have a backslash in the name, run the following command:
    Get-PublicFolderStatistics -ResultSize Unlimited | Where {$_.Name -like “*\*”} | Format-List Name, Identity

    I run this command and no backslashes appears on any of our PF.
    Can you please confirm that spaces in display name are a problem?.

    Thanks again,


  152. Prabhat Nigam Says:

    You have to remove the space in alias as well else migration will fail for those PFs.
    I would prefer to remove space from displayname as well because every PF might not be a mailenabled PF so no alias. Just to be on the safer side.

    By the way, I get the MS technet link corrected in April and I closely work with MS PG who is responsible for PFs.

  153. Henri Feinberg Says:

    That will be a huge problem for us as we have so many folders\subfolders with display name with spaces. When I did the E2003 to E2010 migration, I had run into problems with Aliases spaces for mail enable, so I did correctd it back then so for sur they have no spaces.
    Do you know a script that could remove the spaces ?
    I run the followings to show spaces but I do not know one that will remove them:
    Get-PublicFolderStatistics -ResultSize Unlimited | Where {$_.Name -like “* *”} | Format-List Name, Identity
    By the way do you have the corrected April MS TechNet link ?

    Thanks again.


  154. Prabhat Nigam Says:

    The other option is to try and fix only if you get into the issue. I am not sure about the script but someone used a script check comments.
    Link is here –

  155. Scot Says:

    What’s up everyone, it’s my first pay a visit at this site,
    and article is truly fruitful in support of me,
    keep up posting these articles.

  156. Ninad Says:

    Hi prabhat
    In my test LAB I migrated PF from 2007 to 2013 and it went ok, not I tried rolling back. All steps were done, but cannot access PF on 2007 for users. All users show “defaultpublicfoldermailbox” as blank. The DB shows that it is pointing to 2007 publicfolder (publicfolderdatabase)
    Get error – cannot expand folder – attempt to log on to Microsoft exchange has failed.
    Any advice

  157. Prabhat Nigam Says:

    You have to migrate all mailboxes to 2013 before migrating Public Folders. I have mentioned in assumptions.

  158. Ninad Says:

    ignore comment. It took some time and then it started opening. Yes I had moved all mailboxes.

  159. Karim Says:


    I have done the steps you’re mentionning and all steps went smoothly except that the access rights are all the same: a custom access right granted to the admin user that has done the migration !

    Any thoughts

  160. Prabhat Nigam Says:

    Item level permission might have caused the issue. you could have removed item level permission using pfdavadmin in your legacy Exchange.

  161. Karim CAMMOUN Says:

    To the point to replace acces rights on all folders ? Microsoft will always surprise us !

  162. Nikhil Says:

    @ All,

    If any one is looking to migrate PF to O365 follow the MS article.

    I managed to migrate PF’s to O365 using the below MS article.

    MS should have included PF migration like on boarding mailboxes from On prem- O365 which works flawlessly, have to run hell lot of commands. Anyways… Good Luck…

  163. Prabhat Nigam Says:

    Good to hear Nikhil. I understand your concern but Public folders are not mailboxes. They way they are written in the database you can migrate with many commands. Scripting all scripts into one will cause more issue because a lot of things depends on the PF Hierarchy and data replication.

  164. Pascal Schröder Says:

    Hello, does anyone know how to speed up the process of migrating the Public Folders? I started the request yesterday and now, after 16 hours, only ~600mb were migrated. Already searched the web but there was nothing that helped me speed up the process.
    Thank you for this article!

  165. Prabhat Nigam Says:

    I can think of increasing thread count in one of the config file.
    1. Open the file C:\Program Files\Microsoft\Exchange Server\V14\Bin\MSExchangeMailboxReplication.exe.config;
    2. Increase the values to a number of simultaneous active moves that you want.

    MaxActiveMovesPerSourceMDB = “50”
    MaxActiveMovesPerTargetMDB = “50”
    MaxActiveMovesPerSourceServer = “50”
    MaxActiveMovesPerTargetServer = “50”
    MaxTotalMovesPerMRS = “100”
    3. Save and close the file;
    4. Restart the Microsoft Exchange Mailbox Replication service.

  166. Dan Says:


    I’ve migrated the PFs over from 2007 to 2013 but now, no users can see the public folders. There is no public folder options displayed within Outlook. Strangely, some users do have access to the public folders but I’m not sure why.
    I’ve ended up with two public folder mailboxes (PF-Hierarchy and PublicFolder) and the migrated PFs are in the PF-Hierarchy mailbox.

    Any idea what’s gone wrong?
    Thanks so much for running your website! It’s really really helpful!

  167. Prabhat Nigam Says:

    Make sure all mailboxes are on exchange 2013. 2007 users won’t be able to access PF.

  168. Dan Says:

    I had uninstalled 2007 and installed 2010. Looks like the profile remembered something. PF came back when I made a new profile.

    Thanks for the help and confirming that 2007 can’t access PFs on Exchange 2013.

  169. Aleksey Says:

    after migrating PFs to 2013, option of PF assitant(autoreply) stopped working.
    i deleted and recreated the rule but still no luck.
    any suggestions?

  170. Prabhat Nigam Says:

    So are you saying you had a public folder rule in your outlook which has stopped working?

    Have you moved this mailbox?

  171. Aleksey Says:

    yes a migration was of all components to 2013 and it was made about 4 month ago.
    i have a few users with PF assistant enabled that worked ok before migration.
    and recently they noticed that autoreply stopped to work after migration.

  172. Vishal Says:

    Hi Prabhat,

    I followed your article to migrate public folders from Exchange 2010 to Exchange 2013. Migration got completed successfully after lot of effort, but then when users tried to click on Public Folders in Outlook 2007 – they were getting an error message – “Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.”

    I then rolled back the migration as per this link –​.

    But after this – cannot see the public folder in Outlook 2007. Can you point me in the right direction, please?

    Await your response.

    Kind regards,

  173. Prabhat Says:

    You should not have rolled back and we could have fixed the issue. I have mentioned the simple roll back step in the blog.

  174. Vishal Says:

    Hi Prabhat,

    Thanks for your reply. I’ve read the roll back steps on your blog later on. How do I go about fixing it – the stage it is in now? Appreciate your help.

    Kind regards,

  175. Vishal Says:

    Hi Prabhat,

    I managed to get the public folders back in Outlook 2007. I had to reset my outlook profile and they re-appeared straight after that.

    Many thanks though.


  176. kjstech Says:

    Hi I have the same event ID 2937 as the poster John above, regarding the PublicFolderDatabase is pointing to the deleted objects container in active directory.

    I tried your command you responded to John with and got an error. You said to run:
    Get-mailboxdatabase | set-mailboxdatabase -PublicFolderdatabse $null

    But it returns
    Cannot validate argument on parameter ‘PublicFolderDatabase’. The argument is null or empty. Supply an argument that is not null or empty and then try the command again.

    But Prabhat, you told us to use $null after the argument -Publicfolderdatabase. EX2013 CU6 is not accepting it.

  177. Exchange 2016: New Features in compare to Exchange 2010 « Says:

    […] out my Public Folders Then Public Folders Migration blog. There is a PF migration video on YouTube channel as […]

  178. Prabhat Nigam Says:

    -PublicFolderDatabase switch has been removed.

  179. SSK Says:

    Dear Exchange guru,

    I face the problem during uninstall exchange 2007. i have migrate it to 2013, and i have remove exchange 2007 database already. when we try to remove public folder it show us that public folder contains folder replica. the existing public folder doesn’t contain any folder inside, even we try to do as instruction of the link “” it is still not working. if you have face the problem before could you please feedback to me. Thank in Advance.

  180. Prabhat Nigam Says:

    There would be some replica left. if not in PF, it might be in system folders. Have a look from the PF management.

Leave a Reply

Notify me of followup comments via e-mail. You can also subscribe without commenting.