Skip to main content

Configure Windows to Search Additional Folders for Device Drivers

By

Over the years, one of the things I dreaded doing was rebuilding clients. Almost always I would have to go to the internet to hunt for drivers. The client installation process has greatly improved over the past several years to include image deployments. The problem with images are that you need to service them be able to use them on different hardware platforms. This is because of the device drivers. Now there is a different method that will allow you to use your images on multiple hardware platforms without having to service the image to add new plug-and-play drivers.

When a client boots, it enumerates the plug-and-play devices that are connected to the client. The client then searches its central store and installs the appropriate drivers. If a driver is not found, we then have to provide one. An easy way to make sure the drivers you use are available to all your clients is to store them in a central location.

Be careful whenever you edit the registry. An incorrect setting may require a reinstallation of the operating system

1) Create a shared location on your network that has READ permissions for the Everyone group. In class I discouraged the use of this group but if we are working with a client that has not been added to the domain, you will want the client to get anonymous access to this share. For a more secure method, use the Authenticate Users group

2) Place all you Plug-and-play drivers in this share.

3) Complete the rest of this procedure on the source computer for you deployment image.

4) Start Registry Editor. Click Start, and in the Start Search box type regedit.

5) If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.

6) Navigate to the following registry key:

HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version

7) In the details pane, double-click DevicePath.

8) Add additional folder paths to the setting, separating each folder path with a semi-colon. Ensure that %systemroot%\inf is one of the folders included in the value.

Reference: http://technet.microsoft.com/en-us/library/cc753716(ws.10).aspx

Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
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 .
6 comments
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more