MDT - Driver manager - profile - if

Hi,

How about to configure the Inject Drivers task sequence step action with the following settings to use dynamic DriverGroup001:
Choose a selection profile: Nothing
Install all drivers from the selection profile

The configuration above indicates that MDT should only use drivers from the folder specified by the DriverGroup001 property, which is defined by the "Choose a selection profile: Nothing" setting, and that MDT should not use plug and play to determine which drivers to copy, which is defined by the "Install all drivers from the selection profile" setting.

A similar thread for your reference:
MDT - deployment fails when out-of-box drivers are enabled

Hope it helps. Thanks for your time.

Best regards,
Simon

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

I'm not sure if I follow you completely, but I'll try and answer.

To map a network drive from a task sequence, create a new Run Command Line: net use h: \IP or Host>\DeploymentShare\some\folders\ /user:computername\username your-password
You probably don't need this since the deploymentshare would automatically mount this as Z: drive and read everything from there, or do you wish to copy files to the X drive (WinPE)?

When it comes to drivers and injections. I have created three folders based on manufactures, you need to type the following on each computer.

wmic computersystem get manufacturer
wmic computersystem get model

Each folder of manufacturer have their own models like "Latitude 5410". Then download the .CAB files from Dells webpage and insert the drivers for each model.
You can also manually download the drivers manually and then add them.

Under Preinstall, create a new Task Sequence Variable
Task Sequence Variable: DriverGroup001
Value: Windows 10 x64\%Make%\%Model%

I have mine right after Enable Bitlocker (Offline).

Note that the Out-of-Box Drivers and Windows 10 x64, you can have a different name rather than Windows 10 x64 if you like, but it has to match the same name in the task sequence.

Under the pre-defined Inject Drivers:
Choose a selection profile: Nothing
Install all drivers from the selection profile

Go to Advanced Configuration and select Selection Profiles and create or edit DriverGroup001 and select all your brands

Hello,

I managed to do what I wanted thanks to Johan Arwidmark who created a documentation :
https://www.deploymentresearch.com/add-driver-fallback-to-mdt-lite-touch/

Maybe it will be useful for some.

Thanks for your help,
S. Hepperle

Hi,

Thanks very much for your feedback. We're glad that the goal is achieved now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.

Problem/Symptom:
Look for a way to check if the driver folder exists for a specific device in Out-of-Box Drivers, otherwise it installs all the drivers.

Solution/Workaround:
Add a fallback driver script to the task sequence. The script looks for the drivers folder used by MDT during deployment, and if no folder is found the scripts set the DriversFallback variable to True.

Reference Link:
Add Driver Fallback to MDT Lite Touch

Thanks again for your time! Have a nice day!

Best regards,
Simon

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Hi,

Thank you for your reply.

That's what I did but sometimes I get a blue screen after installing Windows, when the drivers weren't exported and the folder didn't exist in out of box drivers.

In fact I'm looking for a way to check if the folder exists in Out-of-Box Drivers, otherwise it installs all the drivers.

Best regards,
S. Hepperle