Public Folder Migration Issue (Exchange 2013 to Exchange Online)

Question

Hi There

I'm having a problem migrating Public Folders from Exchange 2013 to Exchange Online. Following the guide here: https://learn.microsoft.com/en-us/exchange/collaboration/public-folders/migrate-to-exchange-online?view=exchserver-2019

I ran the sourcesidevalidation.ps1 script first which found some public folders with invalid characters in their name. Using the command supplied by MS I renamed those folders.

When continuing through Step 3 (generating the .CSV files) I get the following error:

These are the folders that the script renamed and looks like it has moved the old ones to some sort of recycle area.

The script will not continue until these folders are renamed.

Can I either A) rename these folders here ? or B) Purge the dumpster area to get ride of them?

Thank you

Answer 1

Hi @AM_ADM ,

---

NON_IPM_SUBTREE contains system folders and dumpster area which stores folders that are deleted by the end users or admins.

Please run below command to check the problematic folder path (i.e. /NON_IPM_SUBTREE/DUMPSTER_ROOT/PFName-GUID) exists or not:

Get-PublicFolder \NON_IPM_SUBTREE\DUMPSTER_ROOT -Recurse | ?{$_.FolderClass -ne "$null"} | FT Name,FolderSize,Identity  

If you find it, run below command to remove it:

Get-PublicFolder \NON_IPM_SUBTREE\DUMPSTER_ROOT -Recurse | ?{$.FolderClass -ne "$null" -and $.Name -eq "Name you find"} | Remove-PublicFolder

If you don’t find it in the first command ,please run the below command to check the folder exists or not:

Get-PublicFolder \NON_IPM_SUBTREE\DUMPSTER_ROOT -Recurse

If it is in the list, please refer to the following command to change the folder name, and then generate .CSV again to see if the error persists.

Set-PublicFolder -identity "\NON_IPM_SUBTREE\DUMPSTER_ROOT\Office/f1f3376f-34a1-410d-8358-23ab7824cd2e" -name "fold"

(Kindly note:You can use the third command to check whether the modification is successful)

---

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 to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I would suggest you try to connect to Exchange Online with PowerShell and check whether there exists issue with it: Basic auth - Connect to Exchange Online PowerShell (Check with prerequisites before connecting)

Suppose you could connect to Exchange online successfully. I would suggest trying again with that script.

If you cannot connect to Exchange online, I suggest you temporarily disable the firewall. Based on my search, this issue may be related to the firewall blocking the connect request.