This command-line tool analyzes the state of one or all domain controllers in a forest and reports any problems to assist in troubleshooting. DCDiag.exe consists of a variety of tests that can be run individually or as part of a suite to verify domain controller health.

Let’s get back to clearing the errors, one might say that this is a difficult task. Not so much.

Just open up Eventvwr and clear the logs, re-run dcdiag and the errors should go away.

You could also try running dcdiag /fix to let it apply safe fixes.

For a full list of dcdiag commands, go here.

-NS

Click Start, click Run, type cmd in the Open box, and then click OK.

Type netsh dhcp server export C:\dhcpdatabase.dat all, and then press ENTER.

Note: While the export command runs, DHCP server is stopped and does not respond to clients seeking new leases or lease renewals.

At the end of this step, you will have the DHCP configuration as well as address lease information exported into the dhcpdatabase.dat file. You can now stop the DHCP service on the source server.

Install the DHCP server service on the server that is running Windows Server 2008

To install the DHCP Server service on an existing Windows Server 2008 computer:

1. Start Server Manager.

2. Click on Add Roles.

3. Select the DHCP server role and press Next.

4. Click through the next sequence for screens of the installation wizard to complete the DHCP server installation. You should not authorize the DHCP server at this point.

Import the DHCP database

1. Log on as a user who is a member of the local Administrators group or DHCP administrators group.

2. Copy the exported DHCP database file to the local hard disk of the Windows Server 2008 computer.

3. Verify that the DHCP service is started on the Windows Server 2008 computer.

4. Click Start, click Run, type cmd in the Open box, and then click OK.

5. At the command prompt, type netsh dhcp server import c:\dhcpdatabase.dat all

And there you have it, no manual entries needed!

Good Luck!

1.) Space Available; is there any space left where the Exchange Databases are? If not free up some space!
2.) Has the database hit its Limit? For Exchange 2003 its 75GB (with the registry modification)

If it’s neither of these you have to start looking at the domain as a whole.

Remember that EVERYTHING is tied together, if Exchange isn’t working, it could very well be a Domain Controller issue!

First thing to do would be to run a DCDiag, if this fails you have issues. The most likely cause would be the Netlogon service is paused or stopped. Restart it, and then restart the exchange Server. Re-run DCDiag to verify that all is well

If none of the above solutions help, the database could be corrupt, wherein you would have to utilize eseutil to find out of the DB is in fact corrupt. At that point let’s hope you have good backups be it Veeam, Backup Exec, or Windows Server Backups.

Good Luck

-NS

There is only one thing you can do, remove it forcibly.

Petri has an article that can help you do this.

When you try to remove a domain controller from your Active Directory domain by using Dcpromo.exe and fail, or when you began to promote a member server to be a Domain Controller and failed (the reasons for your failure are not important for the scope of this article), you will be left with remains of the DCs object in the Active Directory. As part of a successful demotion process, the Dcpromo wizard removes the configuration data for the domain controller from Active Directory, but as noted above, a failed Dcpromo attempt might leave these objects in place.

Good Luck!

You can cancel this process. If you cancel you will need to manually delete the temp files that the compaction was creating. Your original database is completely intact and can be mounted again until you reach the point where the ESEUTIL is copying the completed DB over the original or in your case after you have renamed the original.

I have canceled compactions with no negative consequences.

So the answer is a Big YES! You can cancel an offline defrag without consequence.

-NS

-NS

NetRouteView is a GUI alternative to the standard route utility (Route.exe) of Windows operating system. It displays the list of all routes on your current network, including the destination, mask, gateway, interface IP address, metric value, type, protocol, age (in seconds), interface name, and the MAC address.
NetRouteView also allows you to easily add new routes, as well as to remove or modify existing static routes.

Download NetRouteView here.

-NS

   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\

   add a DWORD “DisableBeep” with a value of “1″

You will have to restart the Terminal Services service for the change to take effect.

The above applies to Windows 2003 SP2 and Windows 2008. If you are running Windows 2003 SP1, you will need a hotfix first: 901115 – A Terminal Services client computer may make beep sounds after you connect to a Windows Server 2003 Service Pack 1-based computer

Double click on AddSystemRestoreEntries.reg (This will add some values to the registry). Click on Yes to continue

Then insert a Windows XP CD to your CDROM drive. Right click on sr.inf and click on install

Reboot the computer

Now you can find the System Restore utility from START–>All Programs–>Accessories–> System Tools –> System Restore

Process Monitor v2.7
This update to Process Monitor, a system monitoring utility, adds a new option to the process tree dialog that direct it to show just the timeline for displayed events, uses kernel-based thread profiling on Vista and higher for better performance, and includes a number of minor fixes and enhancements.

ProcDump v1.5
ProcDump now includes a new switch that enables the creation of a process dump upon process termination, which can help with troubleshooting unexpected process termination. It also fixes a bug where the -ma switch wouldn’t generate a full dump when combined with -r , the Windows 7-specific process reflection switch.

If you want to download these apps go to the Systinternals Live Site or go here for the whole updated package.

Posted in August that is Definitely worth a read.

Mark’s Blog: The Case of the Temporary Registry Profiles
In the latest post in Mark’s “Case of the Unexplained” series, he documents a perplexing case affecting many Microsoft and Citrix customers that Microsoft Customer Support Services solved with the use of Process Monitor’s boot logging and stack trace features.