By writing the article, I hope that you will be able to understand the criteria considered by DS Access to list GCs in Event ID 2080. The article will allow you to ensure continuity in case of a server failure.
I will start by listing how DS Access/AD Access identifies the topology by using the following steps for the benefit of Exchange administrators:
There are situations when Exchange DS Access/AD Access does not show the GCs from other AD Sites in Event ID 2080. As an Exchange administrator, you may be wondering why the event 2080 does not list all GCs in the domain even though the GCs are healthy. To save you a lot of production downtime and effort, I will discuss the following aspects.
Exchange DS Access/AD Access uses AD Site Link details while listing GCs in Out-Of-Site in Event ID 2080. If there is no direct site link between AD site where Exchange exists and other AD sites, the AD sites' GCs will not be considered to be listed in Event ID 2080.
I thought that giving an explanation on AD site link criteria used by DS Access/AD Access will help you to manage the GC resource efficiently for better Exchange functionality.
Since a picture is worth a thousand words, I will explain the topic in question using examples and diagrams.
Let’s say we have the following lab setup:
The Site A, the Exchange site, has direct AD site link with other AD sites. All site links have the same site Link Cost i.e. 100. So, the Event ID 2080 on Exchange will appear like in the following snapshot, Picture 1A:
If I change my AD site Link Cost as shown in Picture 2, then Exchange will pick the GCs from the Site with lowest cost to list under Out-Of-Site in Event ID 2080 and will ignore other AD Site GCs.
Exchange will consider only the Site Link with lowest cost for the Out-Of-Site GCs. So, the Event ID 2080 will look like Picture 2A.
Other GCs in Site B and Site C will not be listed in Event ID 2080. Therefore, Exchange will not use the other GCs i.e. GC5, GC6, GC7 and GC8 in sites B and C.
If I change my AD site Link as shown in Picture 3 then Exchange will pick the GCs from the Site C to list under Out-Of-Site in Event ID 2080, and it will ignore other AD Site GCs i.e. GC3, GC4, GC7 and GC8.
This scenario may be a little odd and may not usually happen as there is no AD with multiple AD sites but no site link. Still, I wanted to talk about this scenario so that the logic can be clearly understood. If there are no site links for any site as in Picture 4, sites are not considered. It will only use local site DC/GC.
Now that you’ve gone over various scenarios, you may ask, what if I hardcode the GCs that are:
Will exchange use the GCs?
The answer is yes. It will use GCs, because if you hard code the directory servers, DSAccess bypasses the discovery process and checks only for server suitability. Similarly when you set StaticExcludedDomainControllers, the excluded DC will be listed in 2080 event, but scores for the DC in the event will be set to 0 for all except GC Capable.
Let‘s say, I run the following command, the exchange will get updated and will log the Event ID 2080 as in Picture 5:
Get-ExchangeServer MSX | Set-Exchangeserver –identity MSX – StaticDomainControllers GC3.CONTOSO.COM, GC5.CONTOSO.COM, GC7.CONTOSO.COM – StaticGlobalCatalogs GC3.CONTOSO.COM, GC5.CONTOSO.COM, GC7.CONTOSO.COM – StaticConfigDomainController GC3.CONTOSO.COM
In conclusion, you can ensure service continuity and minimize service downtime by setting a proper AD site link.
Microsoft Exchange Server 2010
Microsoft Exchange Server 2007
Microsoft Exchange Server 2003
Thanks for sharing
So in this case what is the purpose or main reason to do the hard coding of the AD site using the registry key HKLM\System\CurrentControlSet\Services\Netlogon\Parameters ?
Information very helpfull