I am frequently troubleshooting problems in a Windows Command Prompt.  There are some functions which can be tested at a very basic level.  For example, if I am unable to connect to a server via Windows Explorer, I might jump into a command prompt and try to ping the server. 

ping [servername]

Read more: Enable Windows Telnet Client

Have you ever looked in Active Directory Users and Computers and wondered whether or not the list of computers is a list of every computer that has ever existed since the beginning of time?  Me neither.  ;)

The following command will return a list of computers that have been inactive for X weeks.  In the example below, I'm looking for computers that have been inactive for more than 4 weeks.

Read more: Active Directory -- Identifying Old Computers

The screen turns black, a popup appears and in the center of the screen you see: 

"You may be a victim of software counterfeiting."

Down in the bottom right hand corner, you see:

"This copy of Windows is not genuine."

Read more: This Copy of Windows is Not Genuine

Lots of applications for this simple command.  Yesterday, I was troubleshooting a SQL connection issue and even though I had enabled TCP/IP in protocols, I was still unable to make a connection.  As a sanity check, I ran a shortened version of the command below which showed me that 1433 was not open and ultimately brought me to the source of the problem. 

Launch a Command Prompt as the administrator (right click, CMD, select Run As Administrator).

Enter the following command:

Read more: List Ports in Use

In a previous post, I explained how to disable the Windows 7 firewall and leave it to Microsoft to change how an operation is performed.

Like the previous post, there are times when I don't want the firewall in the way of troubleshooting a problem.  The following is how to disable it.

From a Command Prompt run as the administrator, enter the following:

Read more: Disable Windows Server 2012 Firewall

Life was simple with Exchange 2003 but as life goes on, newer versions of Exchange have appeared and what was once simple has become a bit more complicated.

One of the first gotchas you notice with Exchange 2007, 2010 and 2013 is the increased security and the challenges of connecting to Exchange remotely.  One tool that I find to be invaluable is the Microsoft Remote Connectivity Analyzer which can identify various issues with your configuration.

Read more: Microsoft Remote Connectivity Analyzer