I completed the public folder migration over the weekend from Exchange 2007 to 2013. I ran the scripts to compare public folder structure, permissions, etc. at the end and everything seemed ok. I even logged in and tested things like creating folders, deleting them, and adding items.
Now it's the start of the work week and users are in and out of public folders, adding content, etc. The issue we seem to be having is that it appears that we cannot create new public folders in Outlook. We get an error that just says "cannot create folder". The folder then appears in EAC but if you highlight it a yellow banner appears on the left saying "the process failed to get the correct properties". I will get this banner for public folders I try to create directly in EAC as well. Folder permissions are correct, and I'm owner of the public folder and parent folder. The only solution I've been able to find on the net is to put the Primary Hierarchy public folder in it's own database. Seems excessive especially when I'm running standard and would like to distribute all of my user mailboxes into four databases.
Our public folders are quite large. We have over 75,000 public folders and about 13 million email items. The database that has all of the public folder mailboxes is 134GB and there are 32 public folder mailboxes total. Right now I have 2 Exchange 2013 servers in a DAG locally and one DAG member off-site. All four databases with user mailboxes are on one server and the database with all the public folders is on the other local server. Each server has 40GB of RAM. The off-site DAG member has no active DBs and is just for DR purposes. Any suggestions?