Health Check for Domain Controller

Hi All,

I have an AD Domain Controller (single domain controller), of which I need to come up with a health checklist to make sure that the DC is running fine and basically healthy.

I'm lost as to what should be checked.

I'm thinking the basics would be like disk space. What else can I check to confirm that the DC is in a healthy state?

I also have DHCP running on this server. Its a File and Print server as well.

What can I check on a daily basis to ascertain that the DC is in a healthy state and how would I do this please?
Who is Participating?
Krzysztof PytkoConnect With a Mentor Senior Active Directory EngineerCommented:
Run in command-line

dcdiag /v

and review output
That's the most important tool of checking domain and DNS health :)

for DHCP you can use to check

netsh dhcp server \\ServerName show all
and review output :)

ben1211Author Commented:
Its a Windows 2003 Server
Neil RussellTechnical Development LeadCommented:
Run DCDiag.exe and read the results :D IF all tests pass its healthy
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

SommerblinkConnect With a Mentor Commented:

The first thing that you need to do is to watch over events in the event logs.

You should look at all the warning and errors and even some of the informational alerts. This will give you a good baseline for how your server should behave.

You should download Server 2003 Support Tools (

My two most favorite commands in there are repadmin and dcdiag.

But,  I am getting ahead of myself.

To be honest, the greatest thing you need to do to keep AD perfectly healthy.... is to make sure that DNS is configured on every server and every client, correctly.... You should make absolutly positive that there is NO domain member or domain controller, who has a DNS entry listed in the TCP/IP v4 properties, who isn't a AD-DNS server. Period.

Even other AD-DNS servers should only reference another AD-DNS server (and/or themselves).

The only place that you will find your ISP's DNS servers are in the conditional forwarders, in the DNS service settings.

With that, you will have prevented about half the problems I run into, both with real life clients and on EE.
ben1211Author Commented:
Guys, do i need the windows server 2003 tools to run dcdiag? Where do I run this from?

What does netsh dhcp server \\ServerName show all do?

It won't disrupt the DC right?

Apart from these, whatelse can I check for a server health check?

Krzysztof PytkoSenior Active Directory EngineerCommented:
dcdiag should be run on a DC or on a workstation with Windows 2003 Support Tools installed.
netsh dhcp \\servername show all displays all information about DHCP server, issued IPs and free IPs. It works only in read-only mode, don't worry :)

ben1211Author Commented:
Guys....would you have a health checklist to perform for servers? Other than DCDIAG and netsh dhcp, what else can be checked?

Assuming, I check on disk space, event logs, what else can be checked to make certain that the server is healthy?
ben1211Author Commented:
Guys, how do i get this DCDiag and netsh dhcp tools? Where can i find it on the server and how do I run it? From the command prompt window?
Krzysztof PytkoConnect With a Mentor Senior Active Directory EngineerCommented:
dcdiag and netsh with dhcp context are available on a dc or you need to install Windows 2003 Support Tools to use them from other workstations :) And yes, they have to be run in command-line :)

Krzysztof PytkoSenior Active Directory EngineerCommented:
sorry, forgot to mark that netsh dhcp context is only available on server :)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.