Driver Deployment - Quick Fix?

[CHR1S]

Its Friday and I have reduce mental ability!

 

Is there a really easy way of deploying new drivers to clients?

 

GPP or WDS or anything?

 

Thanks

[free780]

If it has a exe you use psexec to run it silently. You can copy drivers to the driver store and use pnputil.

[sonofsanta]

You can do it with script or SCCM using dpinst.exe. From the guide I wrote myself however many months ago:

Copy the relevant folder with the inf/sys/cat files into this directory and name it appropriately.

 

If there is more than one inf file, search them all for the short Hardware ID (Device Manager > Properties of device > Details > Hardware IDs). Only one should turn up a result, so delete the rest.

 

_Copy_ the dpinst.exe file from here into the _same_ folder as the driver files.

 

In SCCM, create a new package. Point it at the driver folder for source files.

 

The command line should be

dpinst.exe /q /se /sw /f

which is /quiet, /suppressEULA, /suppressWizard, /forceInstallation (i.e. even if a better match is found)

Can also use /sh to /scanHardware, which only installs the driver if the device is present.

 

More installation flags: DPInst Command-Line Switches (Windows Drivers)

 

When deploying, try and target at computers with the relevant hardware. Collections can be created based on hardware. From Assets & Compliance, go to Device Collections, and add a new collection. Title it "Hardware - " and the relevant hardware (e.g. Hardware - Via 1708S).

For membership, use a query rule. Edit Query Statement, Criteria tab, Simple Value, click the Select button and choose the relevant hardware type with Device ID (e.g. Sound Devices, Device ID), operator Is Like, value = the short hardware ID from device manager, with % at the start and end of the string e.g. %HDAUDIO\FUNC_01&VEN_1106&DEV_0397&SUBSYS_10438415&REV_1000%

Continue setting this collection up as normal then deploy the driver package to this collection.

 

That's written for SCCM but you can push a folder to the local machine with GPP then use a startup script to run dpinst on startup.

 

This is based on @localzuk's answer to me when I asked the same question a year ago

[CHR1S]

Is there anyway you can ensure the script only runs once?

[sonofsanta]

Is there anyway you can ensure the script only runs once?

 

SCCM only runs it the once anyway so I don't have an answer off the bat for you (buddum-TSH! Off the bat? The *.BAT? God I'm good) but I imagine you could do a version check against a particular file or reg key?

[CHR1S]

I will have a play, thanks.

 

Well once GPP decides to deliver the files! grrr