Hi, I have had a problem which I think relates to permission changes on the Public Folders - one of my guys haschanged permissions on "everyone" when using ESM and since that change I cannot see the public folders at all. I believe it is still there as if I try to recreate it ESM tells me it cannot as it already exists. Anybody any idea as to how I recover if it is a permissions issue? Best regards, John

Launch ESM, browse to Folders-->Public Folders. Here you should be able to see your PF hierachy. Right click on the folders you can't see in Outlook and select All Tasks-->Manage Settings (this is a new feature with E23 SP2). A wizard will launch allowing you to repush clientpermissions without changing existing ones. Very useful! Dan

Hi Dan, Problem is I cannot see the heirarchy. The pub files are visible so they are still there. So I tried running the problem through kb/823017/en-us guidelines. Modified the HKEY_CUURENT_USER key mentioned no problem and followed the procedure but no luck (although I will go into the office and try again tomorrow as I may not have followed the procedure fully). Tried method 2 using DSACLS but having trouble getting that to work - seems I dont understand how to get either the CN=Administrative Group Name right (I used "First Administrative Group") or I cannot get the Root_Domain right (I have used "secserv" which is the published server name when I look up when looking at my computer / entire network / microsoft network. The internal domain is secag.local...... Can you help with DSACLS perhaps - at least that way I can see if it's a permissions problem? My command line script is: C:\Program Files\Support Tools>dsacls "CN=Public Folders,CN=Folder Hierarchies,CN=First Administrative Group,CN=Administrative Groups,CN=secag.local,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=SECSERV" >c:\pfperms.txt C:\Program Files\Support Tools> The log file says: The specified domain either does not exist or could not be contacted. The command failed to complete successfully. Best regards, John

Hi Dan, Just an update, I have worked out how to use DSACLS so don't worry about that - I need to work on this a little more when I am in the office next. Will get back to you. John

Hi Dan, I have managed to restore the Public Folder thank-you. The fault was a permissions issue. The fault was repaired by using DSACLS as outlined in kb/823017. However for those not familiar (like me), It is hard to work out the inputs for method 2 which is described: DSACLS "CN=Public Folders,CN=Folder "Hierarchies,CN=Administrative_Group_Name,CN=Administrative Groups,CN=ORGANIZATION_Name,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Root_DOMAIN" >c:\PfPerms.txt Note In this command, replace CN=ORGANIZATION_Name with the name of the Exchange organization, replace Administrative_Group_Name with the name of the administrative group where the public folder tree is located, and replace Root_DOMAIN with your forest root domain (dc=microsoft,dc=com). Finally, replace C:\PerfPerms.txt with an appropriate name and location." So I found it very useful to use ADSIEdit.msc see and work in reverse order from the root domain, configuration, services, etal to work out the correct responses. see http://technet2.microsoft.com/WindowsServer/en/library/ebca3324-5427-471a-bc19-9aa1decd3d401033.mspx?mfr=true for ADSEdit.msc Once that was worked out correcting the permissions was a breeze.