I have several users that can be members of multiple "departments" or "roles" and to acommodate this we long ago started using the departmentNumber attribute to store those nonprimary departments. Exchange 2003 was able to send to these just fine using the old LDAP syntax but I cannot seem to find a way to make OPATH do the same. Does anyone know a way to do this? It is NOT practical for me to use 1 field per additional role/department because some users may have 2 or 3 extra and i'd have to then account for each of those in about 30 distribution lists. Even if I did then what happens when I have someone who needs a 4th a year down the road. I know how to make 2007 use the old syntax using ADSIEdit which I will do if I absolutely have to but to me this is a kludge and I should not have to do this. Plus it worries me that these would not be supported anymore in Exchange 2010.

Not sure if the below links do help to solve any of your issues:Filterable Properties for the -RecipientFilter Parameter in Exchange 2007 SP1 and SP2http://technet.microsoft.com/en-us/library/bb738157(EXCHG.80).aspx Set-DynamicDistributionGrouphttp://technet.microsoft.com/en-us/library/bb123796(EXCHG.80).aspxMCTS: Messaging | MCSE: S+M | Small Business Specialist

I have already reviewed those links and they only somewhat helped but did not truly answer my question. I found some references to multivalued fields in some of the documents I reviewed on technet but no examples and when I looked at the fields in adsiedit they don't actually appear to be multivalued fields... It's hard for me to believe (ok maybe not..) Microsoft would remove what I would think would be basic functionality regarding dist lists/the selection of users. But then again they did put in OPATH.. Does anyone have a better way to do what I want? To recap I have a user that users primary job is "Receptionist" that user also acts as a "Dispatcher" we have mail lists for both of these jobs and the user needs to be able to get both without manually adding them. Right now I use a multivalued field (departmentNumber) to list extra job functions and it works great with the old LDAP syntax. If there was only 1 possible extra job function I would gladly just use one of the customvalue fields but some users have 2 or 3 extra jobs.

I believe departmentNumber is not valid for use in recipient filters. For the exact problem you have (mapping job function to dynamic distribution groups) you may want to consider using the ConditionalCustomAttribute* flags and use the CustomAttribute* fields on the mailbox to denote the user's job function(s).

I think your right about departmentNumber since its not in the list. I explored using the ConditionalCustomAttribute* flags and the CustomAttribute* fields but those don't appear to allow multiple values (although technet does say multivalued by the field...) if I am completely missing something thats great please let me know but as it appears now I see no way to have a single field contain more than 1 value. This is what I need since I don't have a set number of job functions a user can have.

The more I think about it you can do something like this: set-mailbox user -CustomAttribute1 "Receptionist,Dispatcher" Then for your DDGs you have: new-dynamicdistributiongroup -Name Receptionist -RecipientFilter { CustomAttribute1 -like "*Receptionist*" } new-dynamicdistributiongroup -Name Dispatcher -RecipientFilter { CustomAttribute1 -like "*Dispatcher*" } And so on for all of the job titles that you want DDGs for.

Ok I think you are my hero. That seems to be working. I need to test a little bit more before marking as the answer but that looks like it will work. The only other part to it is making sure that the primary department attribute works with it as well which I expect it should. Tested and working as a workaround. I wish the multivalued attributes still worked since we are using a program called namescape to enter user accounts and manage our company directory and it handles the "subdepartments" as multivalued attributes. Maybe I can rig up some kind of script that will copy the multivalued attributes out of department number int a string in CustomAttribute1.