RE: [ActiveDir] Exchange/AD bug or poor design?

[Kern, Tom]

Title: Message

can't you just set up a expansion server in the DL properties and use a global DL?

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 18, 2004 2:04 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange/AD bug or poor design?

If I am not mistaken,  'Changes' to DL Memberships happen on a domain controller within AD.  That information is replicated to the Global Catalog servers as a Read-Only Copy.

 

To be sure Global Catalogs that are queried maintain a complete list of Distribution List Members, all DLs must be Universal DLs  (in a multiple domain environment)

http://support.microsoft.com/default.aspx?scid=kb;en-us;271930

Kills the idea that you should limit the amount of Universal Groups in an AD domain / forest.

 

 

I probably missed the point below..

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken Cornetet
Sent: Thursday, March 18, 2004 1:17 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange/AD bug or poor design?

We handled it by writing a perl CGI program to do DL management. Our environment is fairly simple, though - all users in one domain, DLs in another.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thommes, Michael M.
Sent: Thursday, March 18, 2004 11:57 AM
To: Active Directory Mailing List (E-mail)
Subject: [ActiveDir] Exchange/AD bug or poor design?

Hi All,

    I know that some of you think the Exchange/AD is the best thing since "sliced bread" <wink> based on past exchanges/rants on this mailing list, and I wonder about the following:

 

In multi-domain environments, the global catalog server that you select may not be in the same domain as Active Directory group objects. Therefore, users cannot update group membership because the local global catalog server has a read-only copy of the group.

 from: How to configure a specific GC: http://support.microsoft.com/default.aspx?scid=kb;EN-US;319206

 

Since an Outlook client can choose any of the available GCs in the enterprise, when a user tries to update a group membership, obviously it's going to fail if connected to a GC that has a read-only copy.  So the fixup, according to the KB article, is to specify a particular GC.  But by specifying a particular GC, all of a sudden I have lost the redundancy that AD gives me!  Catch-22!  Is this an Exchange design flaw?  How are others handling this problem?  TIA!

Mike Thommes