I am not aware of any limits in the size of DLs specific to
Exchange. There is a recommendation to keep your DLs less than 1000 members.
However, I expect that this is due to attribute ranging which in Windows 2000
was 1000 attributes and in Windows Server 2003 AD that is now 1500 members. The
idea being that you can get all of the values in a single query instead of
sending back asking for more over and over again. I did notice that Exchange
does something odd when it has to start ranging to retrieve more members. It
doesn't appear to be using the normal WLDAP32 library to do it. I was using
Insight for AD from winternals and the additional calls to get the additional
members weren't being caught, yet I could see them over the wire with ethereal
meaning that the hooks that Insight puts into the WLDAP32 libs weren't seeing
the calls... hence they weren't using the standard library.
Breaking the users up into separate smaller groups and then
nesting the groups is exactly what any Exchange consultant that came in
would say.
joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Kern
Sent: Friday, May 12, 2006 11:15 AM
To: [email protected]
Subject: Re: [ActiveDir] Exchange queue(OT)
Well one thing I noticed is that the senders(and some recipients) are
members of a AD security DG that has over 3300 members.
I think the categorizer has a 1500 value limit for member?
I'm gonna seperate the members into multiple local groups and then nest
them into the DG.
Maybe that will help.
I'll let you know what I find.
Thanks
On 5/10/06, Al
Mulnick <[EMAIL PROTECTED]>
wrote:
