I have created a top levelpublic folder called "marketing" , i didn't add permissions yet.Then i created some subfolders under marketing\ marketing \ \ folder a \ folder b When i know add the owner permission on the marketing folder, for user "peter"he doesn't have owner rights on the subfolders a and b.What can I do to let all folders inheritance the rights from the top level folder ?

a get-publicfolder -"marketing" -recurse | set-publicfolder would do the job for you http://technet.microsoft.com/en-us/library/aa998596.aspx

The "-recurse" flag is the thing I was looking for to get all the subfolders.But the command "get-publicfolder -"marketing" -recurse | set-publicfolder" doesn't set all the rights from "\marketing"on all the subfolders. It does say : WARNING: the command completed succesfully but no settings of "\marketing\folder a" have been modified. I can create a work-arround with the command: get-publicfolder -"marketing" -recurse | add-publicfolderclientpermission -accessrights "rights"-user "user" But that's not the way an admin should administer the accessrights. I would like to add the rights on the top folder, and then use an command to set it on all subfolders.

nice work around. If you add the permission to the top level folder before you create the subfolders are you seeing proper inheritance?

If you add the permission to the top level folder before you create the subfolders are you seeing proper inheritance?I would imagine he is, but that's kinda besides the point isn't it? The complete lack of administration folder propagation via the UI makes simple administrative tasks (such as you would carry out on a filesystem) an excercise in frustration. eg. One of our divisions has it's own sub tech support group for special business software. The decision was made recently to xfer administration rights for their public folders (~60 of them) to 2 staff members. We cannot just add them to a top level permission group like the exchange admin group. So, we are left with manually applying a group with 2 ppl in it to each and every folder (time consuming as hell and prone to mistakes) or find a way to push the permissions down from the top of their particular folder tree. It's almost as if you are supposed to have the foresight to create dummy admin groups for each division just in case they do eventually require this. Or say for example you reshuffle/restructure your support dept. etc etc.

When i create a new subfolder it gets it rights from the top-folder, so that is working correctly.The problem is that i have about 100 sub-folders so i don't like to add permissions manually everytime something changes in the rights of the top-folder. The only working thing on this moment is my work-arround which isn't a nice one, but it's working. Until the time i find a command to let all subfolders get the proper rights from the top-folder i have to do it with the work-arround.

Hi Peter, I know this post is quite a bit later than your initial request, but I thought it relevant. It is a misnomer to think of your cmd as a work-around. It is in fact, THE proper way to do permissions in Exchange 2007. Public Folders are not NTFS directories, and do not (by design) inherit permissions from parent folders. When they are created, by default they will get the parent folder permissions. But once created, it is a manual process, folder by folder, to manage the permissions. In Exchange 2003 SP2, they added special functionality in the GUI to be able to recursively manage public folder permissions. With Exchange 2007, they finally just added the GUI for basic management of public folders that was left out of the RTM version. They still do not have a way in the GUI to manage the permissions... it must be done from the shell. By design, the public folders will never be able to "Inherit permissions from parent" like NTFS does. There is a utility out there, you have already probably found. It is called PFDAVAdmin. It was created to help manage PF in Exchange 2003, but the latest version (2.8 as of the writing of this) supports 2007 PFs as well. It has many features built into it to help automate lots of PF tasks. Check out the links below to get the tool. It is free from MS, and was created by their PSS staff, so it is supported by the vendor to a certain degree. http://www.microsoft.com/downloads/details.aspx?FamilyID=635BE792-D8AD-49E3-ADA4-E2422C0AB424&displaylang=en http://www.msexchange.org/articles/PFDavAdmin-tool-Part1.html Good Luck,Ed

It would have been a dam site easier for those of us operating in the real world if MS had simply left the GUI in place instead of making Public folders such a pain in the backside to work with that we in the end just give up and move everyone on to sharepoint.