How do I download driver updates from Windows Update into SCCM?

[ukskydiver]

Hi guys

Hopefully you can point me in the right direction with this one... Please note this is not a question about Driver Packages that would normally be deployed as part of an OSD Task Sequence.

 

Scenario: We are using SCCM (1511) to deploy a Windows 10 OS upgrade to existing Windows 7 clients.

 

The upgrade all works ok and I can deploy the cumulative update from SCCM during the upgrade. I also appreciate I could patch the WIM with this cumulative update (when I upgrade to 1602), but that's a job for another day.

 

I have a number of Dell and Lenovo laptops. Invariably there are a couple of drivers that need to be installed post upgrade.

When I connect to Windows Update on the internet, the drivers are downloaded and installed without issue.

 

What I am trying to do is download them from the 'net into SCCM so that 30,000 clients

1. Don't need to go to to the internet for driver updates and...
2. Are ready to go straight after the upgrade.

I have configured the software update point component to download the metadata for all classifications and all products.

 

I have configured an automatic deployment rule like this: Properties / Software Updates / Product / Search Criteria / Windows 10 and later Drivers.

 

When I do a preview, there are no driver updates to display.

 

My questions are:

• Is it possible to download the drivers that Windows Update finds and subsequently host and deploy them from SCCM?
• If so, am I doing it correctly?
• If not, how can this be dome without having all clients go to Windows Update for the driver updates?

Thanks, Phil

[YPCC]

Try to get the Drivers showing in All Software Updates. Ive never enabled meta data collection for drivers so couldnt tell you how it works. This would be easiest solution.

 

Or... Build a machine as normal using your Taskseq. Then run Windows Update and install the drivers. Then browse to c:\windows\software distribution\. This folder is where WU downloads and stores content. Do you see the drivers there? If so, copy these files and import into sccm as drivers, voila! This would require a little more work as youd need to regularly ensure youve got all the drivers you need.

 

Out of curiousity, why are you missing drivers after imaging? I usually download CAB files which contain all the drivers for a specific model.

[ukskydiver]

Try to get the Drivers showing in All Software Updates. Ive never enabled meta data collection for drivers so couldnt tell you how it works. This would be easiest solution.

 

This is exactly what I am trying to do but the drivers do not show in 'All Software Updates', even having selected the relevant Products and Classifications.

 

Or... Build a machine as normal using your Taskseq. Then run Windows Update and install the drivers. Then browse to c:\windows\software distribution\. This folder is where WU downloads and stores content. Do you see the drivers there? If so, copy these files and import into sccm as drivers, voila! This would require a little more work as youd need to regularly ensure youve got all the drivers you need.

Out of curiousity, why are you missing drivers after imaging? I usually download CAB files which contain all the drivers for a specific model.

We are upgrading to Windows 10 from Windows 7. The drivers are loaded absolutely correctly during the existing Windows 7 TaskSeq in the usual way. After the upgrade to Windows 10, a number of workstations (in fact pretty much all workstations) have at least one, if not more, devices that show up with the yellow exclamation mark.

I'd like to install the relevant drivers during the upgrade process, rather than have each workstation have to go to Windows Update after the upgrade.

[YPCC]

I see. So this is where it gets a bit tedious. Try this:

Obtain a file called dpinst.exe (x64 version if your clients are x64). Download the Windows 10 drivers for your hardware and extract any zip or exe files to obtain the inf's and supporting files. You need to then place all your drivers into a single folder (can use multiple but never tried or needed to).

Now i dont remember the exact syntax but if you google dpinst xml, youll see examples. Basically in the .xml file you specify the drivers you want to install. In your case you can set the parameter which basically installs all the required drivers. Deploy this as a package.

I did something similar when a few of my clients had missing drivers. Works a treat but just a bit more effort required.

Edited April 12, 2016 by anyweb
fixed typos

[YPCC]

Typo!! Its dpinst not drvinst.

 

http://blogs.technet.com/b/svengruenitz/archive/2008/07/02/driver-installation-and-updating-made-easy-dpinst-exe.aspx

 

That should get you started.

[ukskydiver]

Thank you

 

Obtain a file called drvinst.exe (x64 version if your clients are x64). Download the Windows 10 drivers for your hardware and extract any zip or exe files to obtain the inf's and supporting files. You need to then place all your drivers into a single folder (can use multiple but never tried or needed to).

 

If I'm doing this, then I might as well download the drivers from the vendor and deploy a driver package as you would as if you were doing a bare metal build. So it's _an_ approach, but not one I'd expect to have to do, considering the existence of the 'Windows 10 and Later Drivers' option in Software Updates.

 

Can anyone give a definitive answer as to whether what I'm doing is possible, if it is, why it's not working, and / or what is the recommended way of doing this?

Thank you

[anyweb]

drivers were present in the SUP in SCCM back in SCCM 2007 however, that Update Classification was removed in SCCM 2012 due to filling up the database with loads of duplicate info that was difficult to filter...