The Basic IT Toolkit
Published: 09/18/2009
IT shops are about one fire after the next, and if you're in IT and can honestly say otherwise, then you're the rare exception. Helpdesk tickets, unscheduled Exchange outages, someone in marketing testing out a new "P2P screensaver," and the self-important guy with the "C" in his title from the executive suite calling down for immediate assistance because his Internet is broken and it's preventing a sales meeting, thus "impacting the bottom line!"
And since you can't access his machine remotely, you have to make a house call. Time to grab your fix-it gear.
It always amazed me when I worked in IT when co-workers would run to users' cubes, twiddle with their machines, find the cause of the problem, then run back to the MDF to grab a driver CD, cable, or something else equally trivial. Early in my career, I decided I wasn't going through that inefficiency. I wanted to assign a ticket to myself, read the problem description, and make the cube visit (if necessary) and fix the problem on the spot. Done. Ticket closed.
It's never that simple, obviously, but when you have laptop connectivity issues, the last thing you want is an impatient user tapping her heels behind you with that, "Are we there yet?" look on her face. Look, lady, I'm not Santa Clause. You need to stop spending your day composing joke e-mails with that Comic Sans font and get to work.
Every organization should have some basics down. For example, all IT-owned hardware should be properly inventoried and documented. Sometimes this is a pipe-dream, but usually the department at least knows what kind of hardware is commonly assigned. Therefore, a USB flash drive with all the drivers, common corporate-approved software installers, and other administrative utilities should be handy in your pocket. Preferably, the flash drive should also have a physical write-protect switch just in case the user's machine has a malicious process in memory that wants to get its dirty hands on your portable file system. I've used specific model drives from Imation and RIDATA for this purpose.
While every IT shop has different needs, here are some of the basic tools that I find myself reaching for.
The entire Sysinternals suite
More Information
I've been using various third-party utilities since I've been working with NT 4.0 networks. Somehow, the available executables on a client OS always just happens to fall short for my diagnostic needs. A long, long time ago a co-worker of mine introduced me to the PsTools suite. This was back in the day when we still had a licensed copy of Winternals ERD Commander.
Windows Sysinternals
The scope of these tools is impressive, especially for being lightweight and free. Many are command-line only, but some are natively GUI. Some of the more prominent examples that I like are:
- Process Explorer
- Process Monitor
- PsTools collection
- TCPView
- AutoRuns
- NewSID
- Handle
and if you give presentations a lot, ZoomIt is great. There are more that I use, but these seem to be a starting point which address a wide variety of potential problems. If you really want to make someone worry, install the BSOD screensaver on their machine.
Wireshark
More Information
If you're in IT, you're going to eventually need to trace network traffic. It's a fact of life. If you don't know how to do basic packet analysis, now's a good time to pick this essential skill up. Many times you can narrow the problem down immediately just by looking at what is or isn't happening on the wire when the machine is trying to communication with the server.
Wireshark
Install Wireshark and you also get tshark.exe which you can script so users can double-click on a batch file and run a capture whenever they're experiencing that odd intermittent problem that never happens when you're making a cube visit.
Scripts
More Information
Sometimes there are common problems or scenarios which require multiple, predictable steps to troubleshoot. Usually these can be scripted so initial diagnosis can be as easy as running a single batch file. AutoIt is a very handy tool to make your own compiled script executables when you need to manipulate GUI objects such as buttons on a software installer:
AutoIt v3
WMI scripts are really handy to have at your disposal. Take some templates and modify them to meet your own:
TechNet Script Center
Resource Kit utilities
More Information
Unix utilities (Win32 ports)
More Information
Wouldn't it be nice if you could grep in Windows? How about sed or awk? When's the last time you were able to wget a file from some web server and preserve its original date stamp? How about creating an MD5 or SHA1 digest of a file? Now you can have a partial excuse to wear that hacker-trendy "got root?" t-shirt while being a Windows admin.
GNU utilities for Win32
Putty
More Information
Because HyperTerminal sucks, even if it comes with Windows.
Putty
Beyond Ring 0
More Information
Windows Service Packs
More Information
Some loose ends...
More Information
There's a lot more out there, but here a few notables that for some reason have always had a place in my toolkit.
Fport
Port Reporter
Recuva
Go back to the main articles list.