Hello, can you please address an additional issue that does not seem to be mentioned in the workarounds?
Our AD Site Topology is very hub/spoke. We have 13 domains, 1 of which is where Exchange lives, and it has a dedicated Exchange Site in AD. There are around 23k mailboxes and around 120 GCs. None of the users live in the domain that Exchange is in.
We have experienced the following, preventing many (thousands) of our users from being able to Edit DLs and Delegates.
If there is no UserDomain GC in the Exchange Site or a Site directly connected to the Exchange's site via an AD Site link, that User's Outlook client will NEVER get a GC in their domain. Outlook is referred to a GC in Exchange's domain in the Exchange AD Site even though it scores 27 points instead of 28 points for a GC in the User's domain.
Can you please explain why even if a GC is sitting on the same subnet as the user, Exchange will still tell Outlook to use a GC in Exchange's site even though it is not a member of the user's Domain. I guess it confuses us why Exchange will only refer Outlook to GCs in its own site, or one directly connected to its own site. From our point of view it seems to makes load balancing GCs a bit trickier and introduces unnecessary WAN traffic.
We have many perfectly good GCs sitting on the same subnets as users, but they're never used by Outlook for this reason. Many times the sites directly connected to the Exchange Site only have UserDomain DCs, not GCs for these domains. We could put UserDomain GCs in the Exchange site, but that could create an enormous amount of WAN traffic that seems to be unecessary.
We'd prefer not to use Glosest GC reg keys so that we can retain dynamic GC selection in the event of that GC ever being offline.
Thank you very much, I hope that made sense.
Microsoft
