Hello, You probably ran a mile when public folders was the topic, but please bear with me. (I have posted a similar question in the Exchange section as I am unsure of where the problem sits, it could be client or server side) My client is using a huge public folder exchange to "share" their e-mail related to various projects. This was killing their old server and their outlook clients with over 30GB of shared e-mail. I have persuaded them to start archiving e-mail into .PST files they can keep on their server and open if and when they need to. I have shown them how to move folders from the public folders to a local (or network) .PST to reduce the load on their systems and it works fine with some users. They recently had a work experience student start who they are trying to get to do a whole load of filing and organizing for them. They first got in touch regarding the problem last week and I instantly assumed that it was due to the user not having permissions. I granted Publishing editor rights to every folder and sub folder to the user however the move, delete and copy options are greyed out in Outlook. I was unsure if the rights needed to filter through to outlook first however a week later and the work experience student is in the office again and they are still having the same problem. They are using Win 7 32bit with Outlook 2010 clients and the server is SBS2011 64bit with Exchange 2010. If anyone can offer any help it will be gratefully received. Thanks in advance, Rob

Hello, You probably ran a mile when public folders was the topic, but please bear with me. My client is using a huge public folder exchange to "share" their e-mail related to various projects. This was killing their old server and their outlook clients with over 30GB of shared e-mail. I have persuaded them to start archiving e-mail into .PST files they can keep on their server and open if and when they need to. I have shown them how to move folders from the public folders to a local (or network) .PST to reduce the load on their systems and it works fine with some users. They recently had a work experience student start who they are trying to get to do a whole load of filing and organizing for them. They first got in touch regarding the problem last week and I instantly assumed that it was due to the user not having permissions. I granted Publishing editor rights to every folder and sub folder to the user however the move, delete and copy options are greyed out in Outlook. I was unsure if the rights needed to filter through to outlook first however a week later and the work experience student is in the office again and they are still having the same problem. They are using Win 7 32bit with Outlook 2010 clients and the server is SBS2011 64bit with Exchange 2010. If anyone can offer any help it will be gratefully received. Thanks in advance, Rob

BAD BAD IDEA to use PST files. PST files on a network share are not supported. PST files are almost impossible to backup. If you need to retain the data, then don't use PST files. As far as I am concerned, storing content in a PST file and deleting it is the same thing, both will provide the same result - loss of the data. Public folders would be fine, 30gb is peanuts. Just ensure the clients are configured NOT to download/cache public folders locally. When you look at the properties of a public folder you should be able to see what permissions the user has on the folder. However it sounds like the permissions are not taking effect correctly. That could be a sign of corruption in the public folder database. If you create a new public folder, do the permissions work then? Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Duplicate. http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/1dc6350c-c1c5-4f3f-a657-18fc3aa05610/#1dc6350c-c1c5-4f3f-a657-18fc3aa05610Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

The reason for using PST storage is to try to get them to delete things, they have 10 users and are always saying how slow outlook is and the infrastructure in the building is not set up for high network traffic unfortunately. They are aware that the PST files can only be opened by one person at a time and must be removed from outlook to avoid corruption. The folder actions do work on a new folder, but do not work on existing folders even though the permissions appear the same. The user has Publishing editor rights on the folders (and is owner on the one they made). I have logged on to a different machine on the domain to check to see if it was localized but this made no difference. The local permissions state the the user can delete and edit all mail. Thanks, Rob

It isn't about the one person being able to open the PST file, it is that they corrupt: http://support.microsoft.com/default.aspx?kbid=297019 More on the same subject: http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx You are just asking for trouble. Outlook with large mailboxes isn't an issue either, just keep the number of items in the key folders below 5,000 (use subfolders). Public Folders with many items isn't a problem, I have one with over 500,000 items in it that I use every day. The size of public folders shouldn't make a difference - I am aware of at least two clients with public folder databases well in excess of 750gb, no performance issues at all. Sounds to me like the folders are corrupt. Find someone who can maipulte the content and move everything in to new folders. Fairly frequent occurance. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thanks for the suggestions I will give them a go and let you know the results. Many thanks, rob

any updates? If your question is answered it would be nice if you mark it accordingly. Thanks. Fiona Liao TechNet Community Support

Hello, On closer inspection we have found that the only permissions that allow you to move the folders is owner, publishing editor allows you to move individual e-mail however only owner will allow you to move and delete folders. This change of permissions seems to have fixed it however the actual granted permissions would not suggest that this should make a difference; Owner | Create, read, modify, delete all items and files,create subfolders, and change permissions. All rights in the folder. Publishing Editor | Create, read, modify, delete all items and files, and create subfolders. The only differences are "change permissions" and "all rights". This may have remade the folders or the permissions on the folders that fixed the issue however it all seems to work now. Thanks for your help. Rob