I'm hoping to change the permissions for a user's inbox and LONG list of subfolders so that permissions are given to a few distribution lists, rather than discrete mailboxes. The mailbox in question is a partner, and his assistant/other staff come & go. So using a user group (ie distribution list) would make this more manageable over time. Unfortunately, when I attempt this using PFDAVAdmin, it returns an error: "unsupported object type". When I only select ACEs to be propagated that reference individual mailboxes, the propagation completes successfully. Is this a limitation of the current tool (v 2.7)? It sure would be nice to be able to use it for this permissions change to DLs - after all, assigning permissions by group rather that individual is a classic 'best practice'... um... practice :-)

Hi there, I am experiencing exactly the same problem. Did you find a solution for your problem? We need to configure permissions using groups on +- 300 so called resource mailboxes. Thx in advance!

Unfortunately, no, darn it. Very confusing to my how this could be overlooked/unimplemented. I wound up assigning rights to the one partner's mailbox folders by spec'ing the staff members' mailboxes rather then via groups. I consoled myself that at least the PFDAVAdmin tool would make it less painful to go back later & change them all again. (shrug)

Hi, I'm experiencing the same problem. I'm trying to migrate the public folders from one organization to another. I've exported the permissions from the source server and imported them in the destination server (after editing the export file to reflect our domain information) and everything works fine, except for the permissions which were given to distribution lists. The log file states unsupported object type, just as you mentioned. Iwas wondering if you managed to find another solution in the last two months since the last comment in this topic. Best regards, Aico

Ok, I found the solution to my own situation. The problem was that the groups were configured as distribution groups in AD. When I changed this to Security groups PFDavAdmin worked just fine.

Hi, the problem was caused by the fact that my groups were configured to be distribution groups in AD. When I changed this to security groups PFDavAdmin worked like a charm!

I actually had the exact same problem as well but my groups were already set as security groups. Turns out that when I changed them from Global to Universal security groups the tool worked. Greg

GregThank you for thisinformation, it helped me configure 400 mailboxes so that i can set group permissions instead of user permissions. You saved me a lot of stress :)Garry