Hi,
We do not use public folders for our customers, but we had a Default Public Mailbox.
The Default Public Mailbox has been removed thru ECP, but is still visible in CloudPanel under Features – Microsoft Exchange – Public Folder Mailboxes.
How can we remove the Public Folder Mailbox from CloudPanel?
Manually removing the public folder mailbox from the database and updating CloudPanel resolved the issue.
An article was written on how public folders are supposed to be setup and how they function was written:? http://knowmoreit.com/kb/installation/configuring-and-using-public-folders/
There is a refresh button at the top right. Are you able to click that and refresh? It should go away then.
Jacob Dixon 2016-06-07 06:27
Also once you do that make sure you uncheck public folders under the settings if you don’t want to use them in CloudPanel or it will cause problems.
Jacob Dixon 2016-06-07 08:43
If you are not going to use public folders in CloudPanel you can simply uncheck it in the settings and it doesn’t matter if that default is still in there. Otherwise it will need to be removed from the database.
dbaljet Topic starter
2016-06-07 08:46
Hi Jacob,
Thank you for your time.
So a sales guy just asked me to deploy public folders again… For a new customer who will be migrated in a few days.
So I think I need to remove the public folder mailbox from the database.
Please advice.
Jacob Dixon 2016-06-07 09:09
Those sales guys!!
Open SQL Management Studio, select the CloudPanel database, click New Query and type in:
DELETE FROM exch_PublicFolders
DELETE FROM exch_PublicFolderMailboxes
That should wipe out the public folders and public folder mailboxes database. Then create your default public folder mailbox (make sure the email domain on it works via autodiscover externally) and refresh on the CloudPanel screen.
I’m assuming your on one of the three latest versions of CloudPanel or the command may not work.
dbaljet Topic starter
2016-06-07 09:51
So everything worked. I created the PF mailbox. Then I created the new customer and succesfully added a Public Folder to this customer.
However, creating a Public Folder for an existing customer gives:
500 ERROR
An internal server error occurred.
00000000-0000-0000-0000-000000000000
Jacob Dixon 2016-06-07 09:52
What version were you on? There were some fixes in the last two versions. Also can you email the logs to support@knowmoreit.com
Jacob Dixon 2016-06-07 10:32
I looked over your logs… please update to 3.1.1005. This was fixed in this version. If you don’t want to upgrade then try to delete the two security groups it created called PublicFolderAdmins@MIR and PublicFolderUsers@MIR and try again.
the @MIR is the company code of the company you are created it for.
dbaljet Topic starter
2016-06-07 10:41
Hi Jacob,
I just did the upgrade to 3.1.1005.
I now lost our branding. What files and folders did I need to restore from the CloudPanel backup folder on my desktop?
Jacob Dixon 2016-06-07 10:47
You shouldn’t of lost your branding. Recycle the application pool or refresh the browser (make sure its not cached)
dbaljet Topic starter
2016-06-07 10:51
Oops, my bad. Branding is working again.
I just created the Public Folders just fine.
I going to test Outlook tomorrow and see if there are any permission problems.
Perhaps you can give some more info on how to successfully create public folders and good permissions for non-admin users?
Thank you for solving our issue! Great and fast response.
Jacob Dixon 2016-06-07 10:52
You can create public folders (only folder type) with CloudPanel but most of the time people just create public folders using Outlook and you can modify permissions using Outlook as well.
dbaljet Topic starter
2016-06-07 11:07
When I lookup the autodiscover settings for a user in the tenant MIR, I receive the Public Folder SMTPaddress from the tenant JDH. This is wrong. What can I do?
Jacob Dixon 2016-06-07 11:09
Your default public folder mailbox should have the autodiscover record pointing to your hosting domain which autodiscover should work for. Every public folder mailbox you create should have the tenants domain in it and autodiscover must work.
Check the mailbox you are testing to see what DefaultPublicFolderMailbox is pointing to.
I’m migrating from Exchange 2010 to 2016. The current step in is the public folder migration. After reading about batch migration I think that will not work correctly with the cloud panel because it will create a single public folder mailbox. Does anyone have any advice on how to handle this so it will work properly with cloud panel? The isn’t a lot of data but there are about 5 different companies with public folders. I appreciate any advice anyone can offer.
Jacob Dixon 2019-02-18 09:41
What I would do is migrated the data to the single public folder mailbox and then create new public folder mailboxes for each company. Then you can follow this to move the data to the correct mailbox: https://docs.microsoft.com/en-us/exchange/move-a-public-folder-to-a-different-public-folder-mailbox-exchange-2013-help
By default CloudPanel assigns everyone to the master public folder mailbox unless they have their own. So it will probably still work but it isn’t how we recommend setting it up. Just import the master public folder mailbox after you migrate.
