In November 2005 I posted an article on the DSProxy referral changes that are included in Exchange Server 2003 Service Pack 2. For the full article, please see http://blogs.technet.com/exchange/ar...
Updated Jul 01, 2019
Version 2.0
Blog Post
I posted something a while ago "We actually prefer the old algorithm, when we migrated to Exchange 2003 we planned ahead and put all the DLs in the same site of our Exchange servers (they are all in the same domain), users are scattered across 5 other domain. This way the DL update issue is negated, as for the delegate problem we had no way to design around it. Now we are swapping problems. Any chance that we can at least control the algorithm? BTW: Why don’t you guys get together with the Office team and fix the problem for real, this is a know problem since 1999, there is no reason other than motivation for this problem to exist?."
Your response was "Stay tuned...I will be posting an update in the Dec/Jan timeframe that answers your issue. "
If you were talking about the "RFR Prefer In-Site GCs" it doesn't do anything to help us since we have overlapping Domains in the same site. So even with this switch our client’s still get "permission denied" Popups when trying to modify DL that they in fact have permissions for. The only alternative that was given to us with KB 912584 is to created a dedicated site for Exchange and our ExDomain GCs.
Alternatively, we are looking into using the "NO RFR Service" switch and having all DS requests proxied by the Exchange servers. Our lab testing is showing that it prefers using a ExDomain GCs even if a UserDomain GC is in the same site, but I can’t find any documentation on how the GC is selected in that case.
Your response was "Stay tuned...I will be posting an update in the Dec/Jan timeframe that answers your issue. "
If you were talking about the "RFR Prefer In-Site GCs" it doesn't do anything to help us since we have overlapping Domains in the same site. So even with this switch our client’s still get "permission denied" Popups when trying to modify DL that they in fact have permissions for. The only alternative that was given to us with KB 912584 is to created a dedicated site for Exchange and our ExDomain GCs.
Alternatively, we are looking into using the "NO RFR Service" switch and having all DS requests proxied by the Exchange servers. Our lab testing is showing that it prefers using a ExDomain GCs even if a UserDomain GC is in the same site, but I can’t find any documentation on how the GC is selected in that case.