Recipe 3.8. Troubleshooting DSAccess Topology DiscoveryProblemYou notice that DSAccess is using a DC or GC that is out of site, or otherwise not optimal, and you want to know why. SolutionUsing a graphical user interface
Figure 3-3. Event ID 2080 gives you detail on the topology discovery processDiscussionWe 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 which DCs and GCs are most suitable for it to use. Sometimes changes in the AD environment, either planned or unplanned, can impact the DCs and GCs selected by DSAccess. For example, if your AD team removes the only GC from a site, or if that GC is unavailable due to a problem, Exchange will start to use an out-of-site GC, which can severely degrade Exchange performance. Setting Diagnostics Logging for DSAccess Topology discovery will help you to identify the problem quickly. See AlsoMS KB 316300 (Event ID 2080 from MSExchangeDSAccess), Exchange 2003 Technical Reference Guide:
and the Understanding and Troubleshooting Directory Access white paper:
|