Title: Message
I may be missing something, but why couldn't the NSPI be updated to chase referrals? Easy fix... no changes to Exchange or Outlook.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of GRILLENMEIER,GUIDO (HP-Germany,ex1)
Sent: Thursday, March 18, 2004 4:33 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Exchange/AD bug or poor design?

call it what you want - other programs handle group changes better, and you have one of them on every client: the people search function, where you query AD as the Address book.  You can use this to change groups and it will do true LDAP referrals to check for a writeable DC of the applicable domain when changing the group...  I'm sure this will be fixed in Outlook sometime in the near future as well (1-10 years). 
 
But whatever you call it, have to be fair to say it's not an Exchange problem - it's an Outlook client issue.


From: Thommes, Michael M. [mailto:[EMAIL PROTECTED]
Sent: Donnerstag, 18. M�rz 2004 17:57
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 

Reply via email to