3.8. Troubleshooting DSAccess Topology Discovery
Problem
You notice that DSAccess is using a DC or GC that is out of site, or otherwise not optimal, and you want to know why.
Solution
Using a graphical user interface
Launch the Exchange System Manager (Exchange System Manager.msc).
In the left pane, expand the appropriate Administrative Groups container, and then expand the Servers container.
Right-click the target server and select Properties.
Click the Diagnostics Logging tab.
In the Services pane, scroll down and select MSExchangeDSAccess.
In the Categories pane, select Topology and change the Logging Level to Maximum. Click OK.
Open the Application event log and look for recent event with the ID 2080 from the source MSExchangeDSAccess, similar to that shown in Figure 3-3.
Use the MS KB 316300 to interpret the information from the ten columns shown in the 2080 event.
When finished, reset the diagnostics logging level for MSExchangeDSAccess Topology back to a lower level (e.g., none).

Figure 3-3. Event ID 2080 gives you detail on the topology discovery process
Discussion
We know from the description of the role of DSAccess earlier in this chapter that it is central to the smooth running of Exchange. Hence, when things go wrong it is useful to know what view of AD Exchange has. Setting diagnostics logging for DSAccess Topology lets us do this. DSAccess uses a wide range of criteria to determine ...