How do you know which hardware ID the client used to match a driver to?

To find out which hardware ID was used in driver selection, we need to take a look at two properties of the driver. The Hardware ID and the Driver Node Strong Name.

Every PnP device has a set of hardware Ids that are set by the manufacture. They range from specifically identifying the device. The manufacture will also include some IDs that are a close match. When Windows starts up, it enumerates all devices in the computer. It ranks them with the most specific hardware ID with a rank of zero. It will then try to match a driver in the driver store to the hardware ID with the lowest rank. If a driver is not available for the ID with the lowest rank, it tries to match a driver to the next ID in the list. The question is, which hardware ID was used?

· Open your Device Manager.

· Select a device. (It must be one that does not have any issues.)

· Go to its properties.

· Click Details tab.

· Select Driver Node Strong Name from the drop down list. This attribute is populated with a string that identifies the driver used. At the end of the string is the Hardware ID used.

· Select Hardware Ids from the drop down list and compare.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog