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

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.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all. Take a look at the drive mapping below. The red triangle is what threw us off. It is not an error. It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle. This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the

Jason Yoder, MCT

Search This Blog