|
Jeremy- We have a threed aomin (empty root) structure, they’re all in the
same site as the exchange servers, but the exchange servers are all joined to
one of the domains… From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Burkes, Jeremy [Contractor] Do you have two domains in the same
physical site with Exchange servers in both domains? If so read on as we
had a very similar issue. Hope this helps. We had your 1st problem here
which possibly could be related to your 2nd problem. We have
two domains in the same physical site 3 Exchange servers in one domain and 1
Exchange server in the other domain. Whenever we sent out email
particularly to our ALL HANDS DL it would sometimes fail and no one would get
it, other times people would get it on the first try. It took me the
longest time to figure out why. When a DL is “expanded” any
server within the organization can technically “expand” the message
unless you set the expansion server usually an Exchange server within the site
does the expansion. We found that our 1 Exchange server in the other
domain was getting the expansion responsibilities sometimes (25% chance) for
our Domain level Distribution List. This server knows nothing about
Domain specifics so it would fail. As soon as we put that domain in a
separate site and reduced the site replication time to 5 minutes we no longer
had any problems. One of our 3 Exchange servers in the same domain would
always be responsible for the expansion of any DL we had in our domain.
I believe I eventually found a technet article on this, let me see
if I can find it. I hope this helps. Jeremy From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Grillenmeier, Guido did you compare the members of the
respective groups in AD on your 3 GCs? You could potentially have an
inconsistency between the DCs. /Guido From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Apparently we have had for the past three months a persistent but not
predictable issue with large and nested DL expansion. These are always DLs that
are nested usually three to four levels deep and ultimately expand to tens of
thousands of mailboxes. There are three global catalogs in the Exchange site,
and they sit all day around 3%. No load issues, all 2k3 SP1, have been built to
spec by yours truly in December I believe. Nothing weird going on with them
that I can see. There are two issues that crop up, one newer than the other. Issue #1
(original) is that quite simply it will take a couple tries of sending a
message to a DL to get everybody to get it – some folks get it twice,
some get it once. When you do a message tracking it just sort of falls off the
face of the Earth as far as delivery to the folks that don’t get it
twice. Now issue #2 is that as of late some DLs just hang up in the submission
to categorizer if you look in message tracking. Takes a couple tries to get the
categorizer to categorize. Everything but the OWAs is 2000 SP3 w/ the rollup. I just started looking at this today, and quite frankly I’ve gotten
to the end of my short list of things to check. I cranked up diagnostic logging
for DSAccess and SMTP on the gateways and the mailbox server hosting the
mailbox that blasts these DLs. Haven’t found anything useful. Thanks, c -
312.731.3132 |
