Only use win10 drivers- MDT

[kidpressingbuttons]

I have a win10 image set up on the latest version of mdt. I also have windows 7 on here.

I would like to only inject windows 10 drivers when installing win10- how can I set up mdt to differentiate?

[Davit2005]

It should pick a suitable driver, I don't think you can differentiate for drivers and different OS, well you can't seem to in MDT 2012 Update 2

 

We do our drivers via selection profiles and then doing a BIOS query at deployment so it picks the relevant driver for the hardware. TBH we normally use the same OS family for a specific hardware i.e. Tablets get 8.1.

[MYK-IT]

Yes, should be able to (well on, and up to MDT2012 you can...)

 

MDT Share > Out-of-Box Drivers

Create folder for OS (e.g. Windows 7 x64)

(Optional) Create folder for Manufacturer, and sub-directory for Model

Inject drivers into folder

 

Task Sequences

For your Task Sequence, under Preinstall > Set DriverGroup001 with value (e.g. Windows 7x64\%MakeAlias%\%ModelAlias%)

 

Sorry, I'm short on time.. and I know the above is incomplete (missing some other steps and scripts etc). but if you have no luck I'll dig out more information during tomorrow for you; or beter still go to Deployment Fundamentals > Home. Everything was setup following the various MDT Deployment books on there.

[KevinH]

The MDT driver management bible:

 

Deployment Research > Research

[MYK-IT]

The MDT driver management bible:

 

Deployment Research > Research

 

That's the one!

[SHimmer45]

Yes, should be able to (well on, and up to MDT2012 you can...)

 

MDT Share > Out-of-Box Drivers

Create folder for OS (e.g. Windows 7 x64)

(Optional) Create folder for Manufacturer, and sub-directory for Model

Inject drivers into folder

 

Task Sequences

For your Task Sequence, under Preinstall > Set DriverGroup001 with value (e.g. Windows 7x64\%MakeAlias%\%ModelAlias%)

 

Sorry, I'm short on time.. and I know the above is incomplete (missing some other steps and scripts etc). but if you have no luck I'll dig out more information during tomorrow for you; or beter still go to Deployment Fundamentals > Home. Everything was setup following the various MDT Deployment books on there.

 

that only works if the OEM actually populates that information, i found that out when trying to use it for our Stone / Novatech pc's as they dont add this information so WMIC can pick it up.

i ended up doing something similar using other WMIC query fields but i am still not 100% happy that the selection works as it should, (have had a funky issue with an intel gfx / sound driver not being injected when adding more control to the driver injection, even though it is the correct driver in the folder...)

[MYK-IT]

@SHimmer45 I've not personally come across that, due to using all Dell computers etc; but at the very least @kidpressingbuttons should be able to separate Windows 7 & 10 drivers into their respective (Out-of-Box) Drivers folders...

[SHimmer45]

being Dell's the method described will work without any mucking about

 

didnt mean the reply to come across as being sharp apologies

[MYK-IT]

No problems at all @SHimmer45 It never crossed my mind at all, or did it come across as you/r reply as being sharp. Only helpful!

[KevinH]

that only works if the OEM actually populates that information, i found that out when trying to use it for our Stone / Novatech pc's as they dont add this information so WMIC can pick it up.

i ended up doing something similar using other WMIC query fields but i am still not 100% happy that the selection works as it should, (have had a funky issue with an intel gfx / sound driver not being injected when adding more control to the driver injection, even though it is the correct driver in the folder...)

 

That's interesting, and a new one on me. Never saw WMIC conputersystem get model fail - but I'll take your word for it.

 

BTW - Dell has changed the format of WMIC names recently, so if you get new Dell kit, be sure to run the command on them. Was reported over on Spiceworks when a guy couldn't get drivers to inject on a new series recently.

 

My first two Lenovos broke MDT when a few of my Dells decided they liked a Lenovo video driver better than the Intel one a few years back, went total control the very next week. That was an ugly scene ...

[sted]

you can always create a selection profile and point it at your windows 10 drivers folder then in a new task sequence instead of letting it search all drivers set it to only search ones in your selection profile

[SHimmer45]

That's interesting, and a new one on me. Never saw WMIC conputersystem get model fail - but I'll take your word for it.

 

BTW - Dell has changed the format of WMIC names recently, so if you get new Dell kit, be sure to run the command on them. Was reported over on Spiceworks when a guy couldn't get drivers to inject on a new series recently.

 

My first two Lenovos broke MDT when a few of my Dells decided they liked a Lenovo video driver better than the Intel one a few years back, went total control the very next week. That was an ugly scene ...

 

ended up using WMIC W32_baseboard get product like %mobonamehere%

 

as @sted has said you can use a selection profile as well (like everything there multiple ways of doing it) i have added a step for each mobo make we have with this query and then that step installs from a selection profile - a little long winded to setup but for the most part works (niggles apart).