Skip to main content

Using the Reliability Monitor as a Lie Detector

There are some days that we feel like parents. Our kids come back with something expensive that we gave them and it is broke. They have no idea what happened to it. All they know is that they want you to either fix it or get them a new one. Being the superior support personnel we all are, we ask our usual round of questions only to get vague answers in return. What if I could tell you that you could eliminate the “What did you install/uninstall” question? How about even getting rid of the “Did anything crash” question? With the Reliability Monitor, you can.

Your start the reliability monitor by opening it as an MMC Snap-in. You can also click Start and type rel. At the top of the search results, right mouse click Reliability and Performance Monitor and select Run as Administrator. If you right mouse click Reliability and Performance, you can connect to that other user’s computer. Using the Reliability monitor, you can see when things went south on that client. You can see what crashed, what was removed and what was installed.




In this image of the System Stability chart, you can click on each day to see what went on. We had a pseudo way of doing this in XP with the System Restore Points. What you click through the System Restore calendar you got a little detail about what was changed that caused the restore point to be created. My personal record for dealing with a user who was not truthful is 2.5 days. Once I uncovered the truth, the problem was resolved in 20 minutes. Image the time, money and frustrations that we could have saved with this tool.

Comments

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.