Inject Drivers Into Winpe

• But unluckily that didn't work. I am not able to add the Intel® Rapid Storage Technology enterprise (Intel® RSTe) RAID Driver (x64 Bit) after loading into WinPE mode. And that's why Hard Disks are not getting detected. Drvload command still says that drivers are loaded but actually it didn't. I tried in WinPE 4.0.
• Aug 29, 2010  This is the shortest documentation I could create on how to inject drivers into Win PE2.0 (or Vista WIM file). The screenshot beside STEP 5 displays the 3 critical commands I used to load nVidia nForce 4 ethernet drivers to my WinPE boot.wim. Create a folder called C:TEMP.

-->

Navigate to the Preinstall Inject Drivers step. Click the drop down menu and choose “Nothing” for the selection profile. This will disable the pnp so we can take control of the driver injection. While the Inject Drivers step is highlighted look at the top and click ADD General New Task Sequence Variable. In this article, we will show you how to add the necessary device drivers directly into the Windows installation image. The integration of the device drivers into your offline Windows image is widely used when you need to deploy a large number of workstations and servers on the same hardware. The final step in this process is to go to the properties of your deployment share WinPE tab, choose your platform type, then click Drivers and Patches tab. Select the WinPE selection profile so MDT knows where to get NIC drivers for the boot image to inject.

Applies to

• Windows 10 versions 1507, 1511

Important

For instructions to deploy the most recent version of Windows 10 with Configuration Manager, see Scenarios to deploy enterprise operating systems with System Center Configuration Manager.Configuration Manager 2012 and 2012 R2 provide support for Windows 10 versions 1507 and 1511 only. Later versions of Windows 10 require an updated Configuration Manager release. For a list of Configuration Manager versions and the corresponding Windows 10 client versions that are supported, see Support for Windows 10 for System Center Configuration Manager.

In this topic, you will learn how to configure the Windows Preinstallation Environment (Windows PE) to include the network drivers required to connect to the deployment share and the storage drivers required to see the local storage on machines. Even though the Windows PE boot image and the Windows 10 operating system contain many out-of-the-box drivers, it is likely you will have to add new or updated drivers to support all your hardware. In this section, you import drivers for both Windows PE and the full Windows 10 operating system.

For the purposes of this topic, we will use CM01, a machine running Windows Server 2012 R2 Standard that is a member of the domain contoso.com for the fictitious Contoso Corporation. For more details on the setup for this topic, please see Deploy Windows 10 with the Microsoft Deployment Toolkit.

Add drivers for Windows PE

This section will show you how to import some network and storage drivers for Windows PE. This section assumes you have downloaded some drivers to the E:SourcesOSDDriverSourcesWinPE x64 folder on CM01.

1. On CM01, using the Configuration Manager Console, in the Software Library workspace, right-click the Drivers node and select Import Driver.

2. In the Import New Driver Wizard, on the Specify a location to import driver page, below the Import all drivers in the following network path (UNC) option, browse to the CM01Sources$OSDDriverSourcesWinPE x64 folder and click Next.

3. On the Specify the details for the imported driver page, click Categories, create a category named WinPE x64, and then click Next.

4. On the Select the packages to add the imported driver page, click Next.

5. On the Select drivers to include in the boot image page, select the Zero Touch WinPE x64 boot image. Also select the Update distribution points when finished check box, and click Next twice.

Figure 21. Add drivers to Windows PE

Note

The Updating Boot Image part of the wizard will appear to hang when displaying Done. It will complete in a minute or two.

Add drivers for Windows 10

This section illustrates how to add drivers for Windows 10 through an example in which you want to import Windows 10 drivers for the HP EliteBook 8560w model. For the purposes of this section, we assume that you have downloaded the Windows 10 drivers for the HP EliteBook 8560w model and copied them to the E:SourcesOSDDriverSourcesWindows 10 x64HP EliteBook 8560w folder on CM01.

1. On CM01, using the Configuration Manager Console, right-click the Drivers folder and select Import Driver.

2. In the Import New Driver Wizard, on the Specify a location to import driver page, below the Import all drivers in the following network path (UNC) option, browse to the CM01Sources$OSDDriverSourcesWindows 10 x64HP EliteBook 8560w folder and click Next.

3. On the Specify the details for the imported driver page, click Categories, create a category named Windows 10 x64 - HP EliteBook 8560w, and then click Next.

   Figure 22. Create driver categories

4. On the Select the packages to add the imported driver page, click New Package, use the following settings for the package, and then click Next:

   • Name: Windows 10 x64 - HP EliteBook 8560w

   • Path: CM01Sources$OSDDriverPackagesWindows 10 x64HP EliteBook 8560w

   Note

   The package path does not yet exist, so you have to type it in. The wizard will create the new package in that folder.

5. On the Select drivers to include in the boot image page, do not select anything, and click Next twice. After the package has been created, click Close.

   Note

   If you want to monitor the driver import process more closely, you can open the SMSProv.log file during driver import.

   Figure 23. Drivers imported and a new driver package created

How To Inject Drivers Into Winpe

Related topics

Learning has never been so easy!

This HowTo is how to control what drivers get installed per model when you deploy an image with Microsoft Deployment Toolkit.

Note: If using ADK10 then substitute the folder name WinPEx64 and WinPEx86 for WinPE10x86 WinPE10x64.

Note: If your using MDT 8443 then see the link below for fixing the capture bug.

https://community.spiceworks.com/how_to/138246-how-to-fix-mdt-8443-missing-capture-screen

Wedding invitation maker free download - Wedding Invitation Cards maker, Free Wedding Invitation Card Maker, Wedding Invitation Cards Maker, and many more programs. Wedding invitation video making software, free download. The kind of lettering you choose for your custom wedding invitations says a lot about you. Try on different typography styles and see which one fits. Download, print or share your invitation. If you plan to print your own wedding invitations or send them to a printer.

10 Steps total

Step 1: Gather You Drivers

Please visit the vendor's website for the drivers to your PC or laptop models.
I recommend never visiting these rogue sites for drivers. Make a driver repository on your network to keep them in a safe place so you will have a backup.

Step 2: The Boot Image

Navigate to the Out of Box Drivers node and create a folder called WinPEx86. If you use x64 then make a folder called WinPEx64. The only drivers we will need to this folder normally are the NIC drivers. But we need to structure things before we add in the nic driver.

On each model PC you have while you’re at the desktop click start and go to a CMD. Type in the command wmic and press enter. Now type computersystem (all one word). Scroll to the right side and what you are looking for is the maker/model of that computer. You need make a note of the maker/model exactly how it shows. Case sensitive and space sensitive.

To make the structure for the boot image you will want to make a structure with the exact Model name. I usually create a NET folder and put the driver in it. WinPEModel is a must.

Step 3: The Boot Image (Continued)

Here is another pic with all my models in it. Again this is only adding the NIC driver into the boot image so it can support all models.

Step 4: Setup A Selection Profile For The Boot Image

You will need to continue to structure your WinPE folder this way per model computer you have until all the nic drivers per model are in there. We need to create a selection profile for the WinPE folder or folders you made.

Navigate to the Advanced Configuration node. Right click on Selection profiles and create new selection profile. You will need the name of the folder WinPEx64 or WinPEx86. Whichever architecture your using. Select the WinPE folder as you see in the pic. Click next and finish.

Arcane Weapon, a free online Action game brought to you by Armor Games. Destroy the powerful bosses to gather Arcane Weapon. Arcane Online is a new heroic fantasy, free MMORPG game perfected for mobile devices. Immerse yourself in a magical world filled with thousand of players (Online MMO RPG game), monsters, and characters. Can you discover the secrets of the Spirits and vanquish the evil spreading across Eldine? ★ NEW IN UPDATE 2.2 - New Raid Dungeon, the Devildom - New Legacy items - New Heroic Buddies. Sep 18, 2019  Arcane Online is a new heroic fantasy, free MMORPG game perfected for mobile devices. Immerse yourself in a magical world filled with thousand of players (Online MMO RPG game), monsters, and characters. Can you discover the secrets of the Spirits and vanquish the evil spreading across Eldine? ★ NEW IN UPDATE 2.2 - New Raid Dungeon, the Devildom - New Legacy items - New Heroic Buddies. Jun 09, 2008  Kongregate free online game Arcane - Fight and earn your way to glory in this middle age style tournament using bows, boomerangs, k. Arcane online game season 1.

You have completed the structure and added the NIC drivers for the boot image. That is all there is to it there.

Inject Drivers Into Winpe

The final step in this process is to go to the properties of your deployment share > WinPE tab, choose your platform type, then click Drivers and Patches tab. Select the WinPE selection profile so MDT knows where to get NIC drivers for the boot image to inject. Close the properties windows and update your deployment share by right clicking your deployment share and choose Update.

The boot images will get created with the NIC drivers you specified in the selection profile. The boot images will reside at the deploymentshareboot folder. If you wish to PXE boot you can import the boot image from WDS to look at the boot folder.

Step 5: Adding Base Drivers

Now that you know the maker/model of your computers we need to setup the same structure so MDT will inject all the drivers for the computers when it needs it. Let’s setup the structure.

Navigate to the Out of Box Drivers node and create a folder called Dell Inc. (Just like the computer showed you when you ran the wmic> computer system command).

Inside the Dell Inc. folder create a new folder and call it the exact model (case sensitive and space sensitive) of your computer. (just like the computer showed you when you ran the wmic> computer system command).

https://cleversimple.tistory.com/10. The industrial person can take full advantage from this all-in-one Innovative Software solution to Increase engineering productivity. For educational purpose it can deals with electrical one-line circuit design and simulation, PLC control circuit design and simulation, digital electronics circuit design and simulation, Bill of material and report documentation and manufacturers catalogs for design and simulation and technical teaching and professional training. With the help of Automation Studio users can draw hydraulic circuit design and simulation, Pneumatic circuit design and simulation, electro-hydraulic and electro-pneumatic circuit design and simulation and Fluid Power component sizing.

Landesk Inject Drivers Into Winpe

At this point most people just dump the drivers into that model folder. You can do this as well. I avoid duplicates when it shows me duplicates.

Continue performing these steps for all dell models. The same procedures for the HP models as well. I think the maker for HP is spelled out as Hewlett-Packard when you run the wmic > computer system command.

After the above is completed the structure should be:
Out of box drivers > Dell Inc. (if you use HP then it would be Hewlett-Packard) > Models of computers. I am using Toshiba as an example in the pic.

Step 6: Setup Selection Profiles For All Models

Setting up Selection profiles for all models. The process is the same that you did for the WinPE. Here is a pic of my model with a selection profile. Name the selection profile the exact same name as the model. The important thing you select the correct maker/model and all is named correctly.

I have a good amount of Dell machines in my deployment share as you can see in the pic.

Step 7: End Result of Selection Profiles Once Made

See pic.

Inject Drivers Into Winpe 7

Step 8: Editing The Default Client Task Sequence

Open your task sequence that you have been using. Navigate to the Preinstall > Inject Drivers step. Click the drop down menu and choose “Nothing” for the selection profile. This will disable the pnp so we can take control of the driver injection.

While the Inject Drivers step is highlighted look at the top and click ADD > General > New Task Sequence Variable. At the top of the page you will need to move this new step right above the “configure” step as you see in the pic below. Name the step a name of “Set Driver Path” and for the task sequence variable to DriverGroup001 and the value to %Make%%Model% Click OK to save the change.

Step 9: Inject Driver Step Change

Look a couple steps down in the Task sequence and you will see the Inject Drivers step. We should change this to 'NOTHING' for the selection. At this point watch the deployment and you should see where it is install the drivers right after the format of the C drive. Do not forget to update the deployment share and add the boot file that MDT makes to the WDS server if you use WDS for PXE booting.

Step 10: Configure MDT to Create Boot Image

You should change the default for the boot image creation process to point to your selection profile called WinPEx64. This is located in the properties of your deployment share.

You should see the drivers that you specified per model being injected during the deployment. MDT will no longer need to take the time to try and figure out the best driver (PnP) because you have taken Total Control.

Published: Apr 29, 2015 · Last Updated: Apr 05, 2017

25 Comments

• Poblano
  Judopunch Jan 12, 2017 at 05:09pm

  Thanks for this! This is a great learning resource! I'm just starting in IT and this was very helpful!

• Habanero
  Jago Wu Jan 13, 2017 at 12:32pm

  I am glad the doc helped you out Justin. Thanks

• Anaheim
  AutumnBreeze Feb 3, 2017 at 04:55pm

  This was helpful for me as well. I have access to paid training, but nothing that explained how to practically apply this information. -Thank you!

• Habanero
  Jago Wu Feb 3, 2017 at 05:00pm

  You're welcome Autumn. I am glad the doc helped you out. Thanks

• Pimiento
  Jath Aug 30, 2017 at 05:49pm

  Question for you Jago. Using the Total Control method of driver injection with MDT, there is one model that is not getting it's drivers injected properly. The Dell Latitude 7480 is not. Now, on the laptop, we have ran 'wmic csproduct get name' and it comes out to Latitude 7480. Under the path for Out of box drivers, I have a folder with drivers in it named Latitude 7480.

  What could be the reason that? It looks like everything is setup just the same as other models and the other models work just fine.

  Boxhead 2 Play Rooms, Play in single or multi-player mode for more zombie blasting fun. Hone your skills and then take on your friends in this action packed shootout game. Boxhead download free.

  Thank you.

  Edit: Wanted to edit to add more information.

  It doesn't even attempt driver injection, which makes me think that it's not detecting the model the same as I have the folder named, even though the wmic command says it's that model.

• Habanero
  Jago Wu Aug 30, 2017 at 05:58pm

  I only injected some of those drivers in MDT from the .cab file from Dell. The rest of the drivers I downloaded the .exe packages and extracted them.

  Then created a batch file that calls for those setup.exe and install.exe and tested via CMD line. The batch file is in the root folder that was created from the extraction. Inside the batch is a simple command to call the silent install. Once completed I imported each into MDT as an application.

  Then edited the Rules as such for the injection:

  [Settings]
  Priority=TaskSequenceID,Model,Default

• Pimiento
  Jath Aug 30, 2017 at 06:18pm

  Ahhh, okay. Yeah, I did the total control where you import the .cab into MDT's out-of-box driver folder structure, E.G. Windows 10>x64>Latitude 7480, and then in the Task Sequence I did the Set Drivergroup as Windows 10>x64>%Model%. It works for everything but the Latitude 7480, so I didn't know if you knew anything about that or not.

  Alas, the search continues. Thank you!

• Habanero
  Jago Wu Aug 30, 2017 at 06:22pm

  Honestly the reason why I have noticed is some hardware need the full setup package and will not accept just the .inf files.

  You could turn on logging in the Rules of MDT and then review the log to see what happened.

  https://community.spiceworks.com/how_to/111518-how-to-enable-logging-of-mdt-deployments-for-troubleshooting

• Jalapeno
  MikeCS Jan 26, 2018 at 08:25pm

  This an awesome post. I have the task of setting up MDT in our infrastructure and definitely needed some tips and how-to's.

  I have a question about the selection profiles. I understand creating the WinPE10x64 selection profile with just the ethernet drivers, however, when we create selectopn profiles for the ret of the drivers for each model, do we need to create a separate boot file and save it to WDS as the specific model?

  Probably a stupid question but I am getting a little confused.

• Habanero
  Jago Wu Jan 26, 2018 at 08:38pm

  When you say 'the rest of the drivers' are you talking about the Windows drivers (Sound, Video, chipset, etc)?

• Jalapeno
  MikeCS Jan 29, 2018 at 01:38pm

  Sorry for the confusion and all the typos. It was Friday afternoon. ;-)

  In your post you created a WinPE10x64 folder in the Out Of Box Drivers section and added just the ethernet drivers, created a Selection Profile called WinPE10x64, selected the folder WinPE10x64 form the Out Of Box section with all the ethernet drivers for the boot file.

  You then updated the Deployment Share to only use the WinPE10x64 Selection Profile in the Drivers and Patches section within the WinPE section.

  I then created the secondary folder in the Out Of Box Drivers section for those remaining system drivers.

  I was confused on how the Sound, Video, chipset, etc drivers, get installed afterwards if we are only injecting the ethernet drivers during the boot process.

  But, after a little more digging, I think I needed to add those remaining system drivers into a new Selection Profile (for each specific model). Then in a install new image Task Sequence I created, I use that new Selection Profile within the Inject Drivers section.

  Does this make more sense and is this the correct process?

  Thank you for your help!

• Habanero
  Jago Wu Jan 29, 2018 at 01:44pm

  Correct. Add the remaining drivers and make selection profile for each model. For them to get injected in the TS follow step 8.

• Jalapeno
  MikeCS Jan 29, 2018 at 02:41pm

  Wow, how did I miss those steps..

  Sorry to bug you and thank you for clarifying my oversight.

• Habanero
  Jago Wu Jan 29, 2018 at 02:43pm

  No problem. Let us know if you got it working. Thank You

• Jalapeno
  henryarroyo Feb 23, 2018 at 09:52pm

  I have a number of Insprion models and noticed that Dell only provides the CAB packs for Optiplex, Precision, XPS, and Latitude systems. I know that I can just look up the models I have and individually import their drivers into MDT, but I was wondering if you might know of a quicker way to do this.

Inject Drivers Into Iso

• prev
• 1
• 2
• next