locked
Outlook Client in the Subdomain connect to the GC in der Root Domain RRS feed

  • Question

  • My problem is simlar to this.

    I have Exchange 2007 in the Root Domain A and 1 Sub Domains. The Outlook Client in the Subdomain connect to the GC in der Root Domain. The users problem is, that the modification of a Distribution List does not work, because the OL Client have to use the GC in the Subdomain.

    I have found the KB of the RegKey with Closest GC, than the problem is resolved. But is there a way on the Exchange Server to fix this problem?Strange is, that this problem occurs since we have installed SP3 RU6 for Exchange 2007. And only some clients, not all connect to the wrong GCs.

    any ideas?

    Sunday, April 1, 2012 3:21 AM

Answers

  • On Sun, 1 Apr 2012 03:21:48 +0000, Elvis Zhang wrote:
    >I have Exchange 2007 in the Root Domain A and 1 Sub Domains. The Outlook Client in the Subdomain connect to the GC in der Root Domain. The users problem is, that the modification of a Distribution List does not work, because the OL Client have to use the GC in the Subdomain.
    >
    >I have found the KB of the RegKey with Closest GC, than the problem is resolved. But is there a way on the Exchange Server to fix this problem?Strange is, that this problem occurs since we have installed SP3 RU6 for Exchange 2007. And only some clients, not all connect to the wrong GCs.
     
    That problem's been around for at least a twelve years. It's an
    Outlook/AD problem, not an Exchange problem.
     
    >any ideas?
     
    You can try placing the root (or child) domain in a different AD site.
    But, even then, there are no guarantees that the client will select a
    GC with a writeable copy of the data.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Xiu Zhang Wednesday, April 4, 2012 6:24 AM
    • Marked as answer by Xiu Zhang Monday, April 9, 2012 2:52 AM
    Sunday, April 1, 2012 4:51 AM
  • Hi,

    That is by design.

    We recommend to have GC in each domain when we have Exchange installed.


    Xiu Zhang

    TechNet Community Support

    • Marked as answer by Xiu Zhang Monday, April 9, 2012 2:52 AM
    Wednesday, April 4, 2012 6:25 AM
  • As Rich mentioned thats been around for ever its by design.

    "This poses a few issues in multi-domain environments where DomainPrep has been executed against the domains.  Specifically, if an Outlook client is referred to a global catalog server that doesn’t reside in the same domain as the mailbox-enabled user, then that user will be accessing data that is in a read-only fashion.  This means that updates to certain objects (whether it be updates to the mailbox-enabled user like delegate access, or distribution group membership) may fail."

    Exchange Server 2003 Service Pack 2 DSProxy Referral Process Changes
    http://blogs.technet.com/b/exchange/archive/2005/11/04/413669.aspx


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    • Marked as answer by Xiu Zhang Monday, April 9, 2012 2:52 AM
    Wednesday, April 4, 2012 2:56 PM

All replies

  • On Sun, 1 Apr 2012 03:21:48 +0000, Elvis Zhang wrote:
    >I have Exchange 2007 in the Root Domain A and 1 Sub Domains. The Outlook Client in the Subdomain connect to the GC in der Root Domain. The users problem is, that the modification of a Distribution List does not work, because the OL Client have to use the GC in the Subdomain.
    >
    >I have found the KB of the RegKey with Closest GC, than the problem is resolved. But is there a way on the Exchange Server to fix this problem?Strange is, that this problem occurs since we have installed SP3 RU6 for Exchange 2007. And only some clients, not all connect to the wrong GCs.
     
    That problem's been around for at least a twelve years. It's an
    Outlook/AD problem, not an Exchange problem.
     
    >any ideas?
     
    You can try placing the root (or child) domain in a different AD site.
    But, even then, there are no guarantees that the client will select a
    GC with a writeable copy of the data.
     
    ---
    Rich Matheisen
    MCSE+I, Exchange MVP
     

    --- Rich Matheisen MCSE+I, Exchange MVP
    • Proposed as answer by Xiu Zhang Wednesday, April 4, 2012 6:24 AM
    • Marked as answer by Xiu Zhang Monday, April 9, 2012 2:52 AM
    Sunday, April 1, 2012 4:51 AM
  • I am so regretful that MS could let this problem be as so long time. we expect that MS explain the root cause and give a solution not workaround.
    Sunday, April 1, 2012 6:29 AM
  • Hi,

    That is by design.

    We recommend to have GC in each domain when we have Exchange installed.


    Xiu Zhang

    TechNet Community Support

    • Marked as answer by Xiu Zhang Monday, April 9, 2012 2:52 AM
    Wednesday, April 4, 2012 6:25 AM
  • As Rich mentioned thats been around for ever its by design.

    "This poses a few issues in multi-domain environments where DomainPrep has been executed against the domains.  Specifically, if an Outlook client is referred to a global catalog server that doesn’t reside in the same domain as the mailbox-enabled user, then that user will be accessing data that is in a read-only fashion.  This means that updates to certain objects (whether it be updates to the mailbox-enabled user like delegate access, or distribution group membership) may fail."

    Exchange Server 2003 Service Pack 2 DSProxy Referral Process Changes
    http://blogs.technet.com/b/exchange/archive/2005/11/04/413669.aspx


    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    • Marked as answer by Xiu Zhang Monday, April 9, 2012 2:52 AM
    Wednesday, April 4, 2012 2:56 PM