SysAdmin Tools

Dcdiag Overview: The Essential Domain Controller Diagnostic Tool

Posted on April 11, 2015 Updated on April 15, 2026

If you suspect issues with Active Directory—whether it’s slow logins, replication failures, or DNS errors—the first command you should run is Dcdiag. This command-line tool analyzes the state of your Domain Controllers (DCs) across a forest or enterprise and provides a detailed report of abnormal behavior.

Why use Dcdiag?

In a Windows environment, all DCs are peers. Any DC can update the directory, and those changes must replicate to all other peers. If the replication topology is broken or the DC Locator service has inaccurate DNS information, your environment will quickly fall out of sync.

Dcdiag identifies these “silent” failures before they become major outages.

Key Functional Areas Tested

Dcdiag doesn’t just run one check; it executes a series of specialized tests:

Connectivity: Verifies if DCs are reachable and have the necessary services running.
Replication: Checks for latent or failed replication links between peers.
Topology: Ensures the Knowledge Consistency Checker (KCC) has built a valid path for data to travel.
Advertising: Confirms the DC is properly announcing its roles (Global Catalog, KDC, etc.) so clients can find it.
DNS: Validates that the necessary resource records are present in DNS.

How to Run Dcdiag

To get the most out of the tool, you should run it with administrative credentials.

To test a single server:

DOS

dcdiag /s:DC_Name

To identify and automatically fix minor DNS/Service record issues:

DOS

dcdiag /fix

Understanding the Scope

Dcdiag is flexible. You can target:

A Single Server: For local troubleshooting.
A Site: To check health within a specific physical location.
The Entire Enterprise: To ensure forest-wide health.

The LazyAdmin Lesson: Make dcdiag a part of your weekly routine. Catching a replication error on Monday is much easier than fixing a fragmented database on Friday afternoon!

#ActiveDirectory #Dcdiag #SysAdmin #WindowsServer #ITPro #TechSupport #ServerHealth #LazyAdmin #ADTroubleshooting #DataCenter

This entry was posted in Windows and tagged Active Directory, dcdiag, DNS, Domain Controller, Health Check, Replication, SysAdmin Tools, Troubleshooting, Windows Server 2003.

Troubleshooting Storage Latency with esxtop: The Admin’s Guide

Posted on April 11, 2015 Updated on April 15, 2026

When “the server is slow,” the storage subsystem is usually the first suspect. While vCenter performance charts are great for history, esxtop gives you real-time data from the heart of the hypervisor.

🛠️ How to Configure esxtop for Storage Monitoring

You can monitor performance at three different levels depending on where you suspect the issue lies.

1. Per-HBA (Host Bus Adapter) Mode

Command: Type esxtop, then press d.
Tip: Press Shift + L and enter 36 to see the full device names.
Fields: Press f and ensure b, c, d, e, h, and j are selected.

2. Per-LUN (Device) Mode

Command: Type esxtop, then press u.
Why use this? To see if a specific volume on your SAN is being hammered.

3. Per-VM (Virtual Machine) Mode

Command: Type esxtop, then press v.
Why use this? To identify the “noisy neighbor”—the specific VM that is consuming all the IOPS.

🔍 Analyzing the “Big Three” Latency Columns

To understand storage health, you must look at these three columns. They tell you exactly where the delay is happening.

Column	Name	What it represents	Threshold
DAVG	Device Latency	Time spent at the hardware level (HBA + SAN).	< 10ms
KAVG	Kernel Latency	Time spent inside the VMware VMkernel.	< 1ms
GAVG	Guest Latency	Total latency perceived by the Guest OS (DAVG + KAVG).	< 10ms

What the numbers are telling you:

High DAVG: The problem is external to ESXi. Check your SAN controllers, disk spindles, or fabric switches.
High KAVG: The problem is inside the host. This usually means the host is overloaded or there is a queueing issue (e.g., Disk.SchedNumReqOutstanding is too low).
High GAVG: Your users are feeling the pain. If this exceeds 10–15ms consistently, application performance will suffer.