User's unable to create folders in Public Folders after migration from SBS2011 to Exchange 2019

Question

Hi everyone, would appreciate some Exchange expertise and advice into a weird problem we are facing post migration.

We recently migrated users from SBS2011 to Exchange 2019. Everything is working except when users try to create subfolders within Public Folders. The error is

There is no error or issue if we try to move an email into the Public folders or any of the subfolders.

We also noticed that sometimes when we try to browse into the Public folder, we would be greeted with another error:

• First thing we checked was permissions - users had "Owner" rights to the public folders. We tried removing and re-adding the permissions via GUI and Powershell but that made no difference
• Made sure that users were using latest version of Outlook, which they were.
• Created new Outlook profile, but made no difference.
• We created a new user, granted the user "Owner" rights and tried to create subfolders - but same issue. However, we did notice that sometimes the subfolder would be created, even if we received an error.
• Followed steps listed in Can't expand or add public folders in Outlook or OWA but was not relevant.
• Followed steps listed in How to diagnose and fix public folder permission issues , but at step 2c, there was no error, and all commands worked, showing that the user had Owner rights.

If anyone has any idea what is going on or how we can isolate the problem, that would be great. Some information about the PF and structure below:

Answer 1

@Nimal Sirimanne

How do you migrate public folder from Exchange 2010 in SBS 2011 to Exchange 2019? Exchange 2019 cannot coexist with Exchange 2010, it only suggested migrate public folder from Exchange 2013/2016 to Exchange 2019.

I think this issue may related with the way that used to migrate public folder.

---

If the response is helpful, please click "Accept Answer" and upvote it.
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

Hi KyleXu,

We migrated everything including PF from SBS 2011 to Exchange 2016, then from Exchange 2016 to Exchange 2019.

SBS2011 and Exchange 2016 servers have been shutdown and removed from network, so only the Exchange 2019 is live.

Do let me know if you need any further information.

Answer 3

Hi Kyle - this was the first thing i tried :) Did this using powershell as well, but no change in user experience.