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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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 .

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne. I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10. This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit. In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate. I needed to make sure the environment is set up for me to be able to utilize this cmdlet. If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place: Remote Scheduled Tasks Management (RPC) Remote Scheduled Tasks Management (RPC-ERMAP) Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Jason Yoder, MCT

Search This Blog