Hello all: I have an SBS 2k3 server running Exchange 2003 SP2. I am trying to setup a public folder for a shared job role (human resources) so that they can share an e-mail address/Inbox. I would like the permissions for this folder to come from security groups (universal) as the users and their access are already setup, and that's how users will be add/removed. I feel as if I've tried everything; and 3 hours later after much research and trial and error I'm pulling my hair out with no working solution. I tried using the universal security groups on the folder permissions, as well as a query driven distribution group that returned the security group (so that the group would still be dynamic and show up in client permissions). I know that this must be strait forward, however have been unable to figure it out. Could someone provide me with some direction, documentation, a step-by-step guide or something?? Hopefully this question is not redundant; however a search yielded thousands of results (first couple pages unhelpful). Thanks in advance,++++ Greg ++++

You can't use a QBD anywhere in the permissions set, as QBDs are for distribution only, not security. If you use a regular distribution group for permissions then it is changed in the background to a security group. A QBD wouldn't allow this to happen. You must use a mail enabled group for permissions, so that it is seen by Outlook. Therefore if you already have the group, mail enable it. You will then be able to use it for permissions. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Hi Simon, Thanks for the response. What is a QDB? I'm unfamiliar w/ the acronym (and so is Google).Greg

I agree with Sembee. QBD is nothing but Query Based DL. and which cannot be used to assign permission. The best thisng would be here to create a Security Group grant permission on PF and keep on adding the users to that DLVinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

QBDL is query based distribution list. I missed the L off. Also known as DDL - Dynamic Distribution List. Basically a list that doesn't have a static membership list. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources