Choosing/creating correct drivers for driver package

[Silencer001]

Hi all,

 

On a couple of blogs, I read you need to import clean drivers in ConfigMgr and not just add all the drivers in the driverpack found on the OEM website (lenovo/HP/..).

 

I was wondering how this can efficiently be done and how you do this for customers?

 

I was browsing on the Lenovo website and saw that the driver packs mostly contain old drivers. The latest drivers can only be found on the website of the manufacturer (Broadcom, Intel,...). These website also advertise that it's best to use the drivers of the OEM since they may add additional fucntionality?!

 

Maybe the following method would be advised?

• Download the latest drivers of the generic devices (Intel NIC, RST, chipset, integrated gfx, nvidia/ati gfx, broadcom NIC)
• Install computer with these drivers (using ConfigMgr)
• After installation, download the latest drivers for all unknown devices (based on PNP Hardware ID).
• Use dpinst in combination with XML-file to load all the drivers of the driverpackage of Lenovo. If still better drivers are found, search for newer versions of this driver. (This step is used to check better drivers for the known devices. Since Microsoft also has standard drivers which will be used if no other are available)

 

Thanks in advance!!

[Silencer001]

Hi everyone, can someone enlighten me about the procedure they use at their customers?

I can't seem to find any other information than "use clean drivers", but the practical side of the implementation isn't really explained.

 

Thanks!

[Peter van der Woude]

Not sure what you mean with "clean drivers"... often the problem with the driver packs is that they contain too much drivers. They often contain drivers for multiple models and possible combinations on those models. Cleaner could be to make sure that you only use the drivers from a driver pack that your devices really need.

[spgsitsupport]

And for the ie Intel chipset you ONLY want to use the ones that are actually used on the very hardware.

Otherwise SCCM makes a mess of it. By default it can create 600Mb package from 11.4 Mb driver set (as it multiples 11.4 by as many inf as exists in the folder)

Awful beahviour!

Setup.exe –AONLY -OVERALL –p C:\temp\chipset

from this blog combats this behaviour