Skip to main content

Upgrading Dynamic Distribution Groups

Dynamic distribution groups These are distribution groups for which membership is based on specific recipient filters rather than a defined set of recipients. Dynamic distribution groups were called query-based distribution groups in Exchange 2003.

Source: Microsoft Exchange TechNet library

If you created query-based Distribution Group in Exchange 2003 it was filtered by using LDAP query language. Exchange 2007 is using OPATH as query language which is simpler to use than LDAP. During transition from Exchange 2003 to Exchange 2007, now called dynamic distribution groups, are not automatically converted to OPATH query-language. Query-based distribution groups work but if you want to see members from Exchange Management Shell or do something else with the group within Exchange 2007, you simply can't or the use is limited.

So, you need to convert LDAP query language to OPATH. When creating new Dynamic Distribution Group in Exchange 2007, there are some conditions (filters) you can choose from. But as you will see there are only few.


For example, if you have a query based distribution group that uses City as a filter point, then, if you check your conditions options, you will see that City is not included in the GUI. You can still use Exchange Management Shell though. To query users for dynamic distribution group that have City attribute assigned, you need to enter the opath query through Exchange Management Shell.

To change existing Dynamic Distribution Group which uses LDAP filter to use OPATH filter you use:

Set-DynamicDistributionGroup -Identity "GROUPNAME" -RecipientFilter {(Alias -ne $null -and City -like 'Ljubljana') -and -not(Name -like 'SystemMailbox{*') -and -not(Name -like 'CAS_{*')}

In this case all the users that have Ljubljana as the City attribute will be members of this Dynamic Distribution Group.

Lists of Active Directory group attributes can be found on Microsoft's web site for different operating systems but I suggest that you try the name as it is written in AD properties. For example, City in LDAP is l (L in small letters) but in OPATH you just write City (see example).

Comments

  1. Were are running Exchange 2007...We have created two new Dynamic Distribution groups, but they are only visible and functional for DOmain Admins. When the staff opens their Address book > All Groups, there appears blank lines where the groups should be displayed. It's like they are there but not accessible. Is there something in AD (running WIndows Server 2003) that we need to change?

    ReplyDelete
  2. Out of the head, I would think of something like Inherited permissions problem. It looks like default settings are somehow changed. Unchecked permission inheritance on user object can sometimes have unusual consequences.

    ReplyDelete
  3. Thank you, this was a great help.

    ReplyDelete

Post a Comment

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.