cannot delete dumpster files from public folders - PF migration process

Semjon Paul 0 Reputation points
2025-03-24T13:11:16.3966667+00:00

Hey, I want to migrate my Exchange 2013 public folders to Exchange online. I noticed that I had a few folders that contained characters that were not allowed in the migration, so I renamed them. After running the Export-ModernPublicFolderStatistics.ps1 script again, i saw that the folder names are still in the dumbster_root folder present and causing an error. So I tried to use MFCMAPI to delete these files, but could not. Every time i click on deleting folders, nothing happens (no even the pop-up menu to force delete is showing). Is there any workaround for dumpster files in the Export-ModernPublicFolderStatistics.ps1 script? I appreciate any thoughts.

Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
2,270 questions
0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Sharon Zhao-MSFT 25,746 Reputation points Microsoft External Staff
    2025-03-25T08:27:05.7466667+00:00

    Hi @Semjon Paul,

    Welcome to Q&A! 

    To help us better understand your problem, please kindly share some screenshots:

    Screenshots of the error message encountered when executing the Export-ModernPublicFolderStatistics.ps1 script

    • Screenshots of the MFCMAPI interface when attempting to delete the problematic folder

    I’ve replicated this scenario in my test environment (Exchange server 2019) with the following results.

    a. Created two test folders: PFSUB01 (valid naming format) and PFSUB\02 (invalid format with backslash).

    Both folders appeared in the dumpster_root immediately after deletion. Manual deletion attempts were unsuccessful.

    User's image

    b. Successfully executed the export script.User's image

    c. The generated CSV only included the valid folder (PFSUB01), with no data for the invalid folder (PFSUB\02). It indicates the export script automatically filters out folders with invalid naming conventions.User's image

    Since Exchange Server 2013 is now out of support, we'd like to understand whether you plan to maintain a hybrid environment or transition to a pure cloud solution.

    If you choose to keep the hybrid environment, we recommend first upgrading your Exchange Server to the 2019 version before migrating public folders to Exchange Online.

    Alternatively, if you prefer a more immediate solution, you can migrate public folders directly using Outlook PST export. Detailed steps for this approach are available in Microsoft's official documentation: Batch migrate Exchange Server public folders to Microsoft 365 or Office 365 | Microsoft Learn.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

     

    Note: Please follow the steps in our documentation](https://aka.ms/msftqanotifications)) to enable e-mail notifications if you want to receive the related email notification for this thread.



  2. Semjon Paul 0 Reputation points
    2025-03-25T11:32:15.1866667+00:00

    Hello and first of all, thank you for your detailed answer.

    This is what my Exchange server is showing:

    User's image

    These folders are located in the DUMPSTER_ROOT folder, while your deleted folders are located in the DUMPSTER_EXTEND folder.

    User's image

    After I failed trying to delete this entry, I moved on to the other error entries, and somehow I was able to delete all of them except for two ("Bündnis90/Die Grünen" and "Radabeul/Coswig"). But after refreshing the view all folders were back, so I guess they are not deletable.

    For context:

    I am aiming to shift completely to the cloud after this migration and a batch migration is not an option for me, because my PF is like 80gb large.


  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.