Pular para o conteúdo principal

Better troubleshooting capabilities with Windows 7 Event Viewer

Better troubleshooting capabilities with Windows 7 Event Viewer: "
If you had been holding on to Microsoft Windows XP and just recently made the move to Windows 7, you’ve begun to discover that a lot has changed in the operating system besides just the new user interface with all its new bells and whistles.

For example, chances are that one of the first places that you probably turned to when troubleshooting problems in Windows XP was the Event Viewer. Well, when you get to Windows 7’s Event Viewer, you are in for a new experience.

In this edition of the Windows Desktop Report, I’ll introduce you to some of the new features in Windows 7’s Event Viewer.

This blog post is also available in PDF format in a TechRepublic download.

An overview


As you know, Event Viewer maintains logs that record information about program, security, and system events that occur on your system. While XP’s Event Viewer is an effective tool that you can use to view and manage event logs, gather information about hardware and software problems, as well as monitor security events, it does have some shortcomings. Perhaps the biggest drawback is that XP’s Event Viewer does such a good job at logging events, that the number of items in the log can be staggering. As such, sorting through the logs can be a very daunting task. To add insult to injury, not all the events are documented very well and many aren’t documented at all — often leaving even the most experienced troubleshooter puzzled.

Another drawback in the system stems from the fact that Windows XP has other logs that are stored as text files on the hard disk. This means that when troubleshooting problems, you may have to scan through a bunch of text files in addition to scanning through Event Viewer.

Fortunately, Windows 7’s developers have spent a great deal of time and effort on improving Event Viewer. Let’s take a closer look.

The new Event Viewer


To begin with, the Windows 7 version of the Event Viewer has been completely rewritten with a new user interface that makes it much easier to filter and sort events as well as control which type of events are logged. In addition, you can now perform some basic diagnostic tasks right from within Event Viewer itself.

Microsoft has stated that they are going to impose stricter standards in order to ensure that events logged in Event Viewer are more meaningful, actionable, and well-documented, thus providing better information for troubleshooting. In addition, Windows 7’s Event Viewer will be the central point of inquiry for all the operating system’s logs. More specifically, those operating system components that store logging information in text files will add events to the event log in Windows 7.

Other new features in Event Viewer allow you to create and save custom views so that you can easily focus in on the problem you are currently troubleshooting, create event subscriptions that can collect information from other computers on a network, and allow you to more easily correlate problems that affect multiple computers and assign tasks that are to run when a certain event occurs.

A tour


Let’s take a look around the new Event Viewer in Windows 7. As you can see in Figure A, the new user interface provides access to more pertinent information than Windows XP’s Event Viewer, as shown in Figure B.

Figure A



Windows 7’s Event Viewer provides access to lots of information.

Figure B



The user interface for Windows XP’s Event Viewer looks pretty stark in comparison to the Windows 7’s Event Viewer.

As you look at Windows 7’s Event Viewer, you’ll notice that the left pane contains an expandable tree that provides you with easy access to all of Event Viewer’s logs. The two main categories are Windows Logs and Applications and Services logs. The Windows Logs category includes the logs that were available in Windows XP, such as the Application, Security, and System logs, while the Applications and Services logs are a new category of event logs that store events from a single application or component.

In the center is the View Pane that provides you with an easy way to view both the list of events as well as the information that each event contains, as shown in Figure C.

Figure C



The View pane does double duty, showing you both the list of events and details about the selected event.

On the right side of Event Viewer is a new area called the Actions pane, which contains a list of actions, or commands, that are associated with Event Viewer. As you can see by comparing the Actions pane in Figures A and C, the Actions pane changes to provide relevant tasks depending on what is selected.

To make focusing on specific events easier, you can create a Custom View that essentially allows you to create a very detailed event query that can span several logs. To help you create a Custom View, Event Viewer provides you with a very detailed form, as shown in Figure D. Once you have created a Custom View, you can then save it and reuse it later.

Figure D



Creating Custom View can be a real time-saver when troubleshooting problems.

Attaching tasks to events is also a great troubleshooting feature. To make this a simple procedure, Windows 7’s Event Viewer employs the Task Scheduler Wizard and provides you with several relevant actions to attach to the event, as shown in Figure E.

Figure E



You can configure a task that is to take place when a certain event occurs.

What’s your take?


In addition to providing improved performance and a new user interface, Windows 7’s Event Viewer gives you a whole slew of new features to make troubleshooting a much easier task. If you are a Windows 7 user who has recently moved from XP, what has been your experience with Windows 7’s Event Viewer? As always, if you have comments or information to share about this topic, please take a moment to drop by the TechRepublic Community Forums and let us hear from you.

Stay on top of the latest Microsoft Windows tips and tricks with TechRepublic’s Windows Desktop newsletter, delivered every Monday and Thursday. Automatically sign up today!



"

Comentários

Postagens mais visitadas deste blog

Improve Windows Security By Closing Open Ports

Improve Windows Security By Closing Open Ports : " A standard Windows operating system has a number of ports open after installation. Some of these ports are needed for the system to function properly while others might not. These ports can pose a security risk as every open port on a system might be an entry point for a malicious user. A port basically allows communication to or from the device. Characteristics are a port number, an IP address and a protocol type. This article will give you the tools at hand to identify and evaluate the open ports on your Windows system to make a decision in the end whether they can or should be closed or left open. Software programs and tools that we will use: CurrPorts : Available for 32-bit and 64-bit editions of Windows. It is a port monitor that displays all open ports on a computer system. We will use it to identify the ports and the programs that are using them. Windows Task Manager: Also used to identify the programs and link some p

Diagnosing a Blue Screen of Death Error in Windows

Diagnosing a Blue Screen of Death Error in Windows : For many years now the famous Blue Screen of Death (BSoD) has been the ultimate indication that something disastrous has happened to make your computer die, but how useful is the information in the BSoD and the respective crash dump file that Windows produces? The best article I ever found explaining the BSoD in depth is here on the Microsoft website, however it’s quite technical and doesn’t discuss how to actually troubleshoot a problem. The crash dump file is just technical details of what was being held in the computer’s memory at the time of the crash, and this will include details on every driver and service that was loaded, and every piece of software that was running. The most useful pieces of information are to be found on the BSoD itself and are highlighted on the screenshot below. These are the BSoD error name, the stop error code and the name of the driver or service that has failed (this last one might not always appea

Use BGInfo to Build a Database of System Information of Your Network Computers

Use BGInfo to Build a Database of System Information of Your Network Computers : " One of the more popular tools of the Sysinternals suite among system administrators is BGInfo which tacks real-time system information to your desktop wallpaper when you first login. For obvious reasons, having information such as system memory, available hard drive space and system up time (among others) right in front of you is very convenient when you are managing several systems. A little known feature about this handy utility is the ability to have system information automatically saved to a SQL database or some other data file. With a few minutes of setup work you can easily configure BGInfo to record system information of all your network computers in a centralized storage location. You can then use this data to monitor or report on these systems however you see fit. BGInfo Setup If you are familiar with BGInfo, you can skip this section. However, if you have never used this tool, it takes ju