Hi All,

Wonder if any of you can assist with a public folder issue I am having with Exchange 2013. We have migrated from Exchange 2010 to 2013.

I have followed the guide for public folder migration here http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

Everything went fine and as per the document - except I had to use the "largeitemlimit" parameter to get the public folder migration to complete.

We tested the public folder migration by adding content to public folders and creating public folders and it all appeared to be OK, we completed the migration and removed our old public folder databases from Exchange 2010.

However we noticed later that users cannot CREATE folders in SOME public folders. It appears from some testing that any folder that does not lie in the first public folder mailbox, end users cannot create public folders.  Administrators can create them fine from the ECP - just not from outlook.

It also appears some users cannot see some folders that they have permissions to.

Can anyone assist with some ideas to resolve ?

Thanks.

Hi

Have a look at this article, perhaps some of the steps might help. it is for Exchange 2013 preview but the concept applies:

http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-preview-public-folders-part1.html

Hi,

We can access Outlook client and check the related public folder permission settings as below.

If the permission settings are correct, members of SG should be able to create/delete items.

Generally, it will take several minutes after changing the folder permission.

When we cannot create public folder in Outlook, is there any error messages poping-up?

Thanks

Mavis

Hi,

Any update?

Thanks

Mavis

Mavis,

We have double checked the permissions are corrrect.

The users can create items, just not create folders (and sometimes not move them).

M.

Hi,

Please trying to run following command:

Set-OrganizationConfig -PublicFoldersLockedForMigration:$true

Hope it is helpful

Thanks

Mavis

Hi Mavis,

This did not solve our issue - why would you say that command would help us ?

M.

Hi,

Sorry for the neglect on " Administrators can create them fine from the ECP - just not from outlook".

We can perform creating from ECP but not from Outlook.

It seems like an issue on the Outlook Client side.

Please run Outlook under safe mode to avoid some AVs, add-ins and firewall.

Please trying to re-create a new profile to refresh the caches.

Feel free to contact me if there is any problem.

Beg your pardon again.

Thanks

Mavis

You still havent read through my description properly.

Users can create folders in SOME folders - but only the ones that are stored in the first public folder mailbox.

This is affecting all users across Outlook 2010 and 2013 clients so I dont think this is the issue.

Yes we have tried a clean outlook client install to no avail.

M.

i can confirm EXACTLY the same issue in our enviroument. Publics migrated, everything works fine, but users (including exchange administrators) cannot create new public folders in case of root folder is hosted in the "secondary hierarchy" mailboxes, althrought have ownership permisions. -IsExcludedFromServingHierarchy set to $false. Specifying Primary hierarchy mailbox by -DefaultPublicFolderMailbox for users doesn't change anything either.  can't see meaninful errors in exchange server log. Creating folders thru ECP works fine in all cases. Exchange is the 2013 CU3 on Win 2012 (non-R2). Anyone could came-up with solutions?

• Edited by Vladimir Usov Saturday, January 11, 2014 6:17 AM

Question?
Are you able to create the Folder in OWA?

Question?
Are you able to create the Folder in OWA?

Hi Gulab! Any update you might have? Or should we escalate this as a support case to Microsoft support? I'm wondering if this is common known bug or installation-specific issue..

My Apologies, hasn't been able to test it yet.
Being busy in one of the Exchange 2010 Migration Project.

I have a question. Are these Public Folders are MailEnabled or Mail Disabled?

Hi Everyone,

We have had an MS Support case open on this issue since January.

We have been escalated all around the world inside Microsoft.

Microsoft have admitted that there is an issue and they have no fix (nor will it be fixed in SP1 they say).

Their solution was to put ALL our public folders in the primary mailbox (we have 250gb+). Not sure how I feel about this!

Exceptionally poor effort - clearly this wasn't tested properly - surely if you put out a document saying you need to spread your public folder items into different mailboxes (and provide scripts etc to work out how many to create) and then it doesn't work - it cant have been tested too thoroughly!

Exchange 2013 also appears to require significantly more resources - our previous single server Exchange 2010 was 4vcpu 12gb ram. We have assigned 8vcpu and 32gb ram to the current exchange 2013 server and it still seems to struggle at times.

Moral of the story - it would be prudent to have removed public folders from your organisation before migrating to Exchange 2013. However you might be OK if your usage of public folders is limited/small.

Thank you all for your attempts to assist, it is appreciated!

M.

• Marked as answer by SubMegabyte Friday, March 14, 2014 4:06 AM

We are also getting this issue and I have raised some of this on spiceworks at:

http://social.technet.microsoft.com/Forums/en-US/2d4e92ce-7aea-4163-aa20-39f24eb868dd/exchange-2013-public-folder-migration-problem?forum=exchangesvrdeploy