/build/static/layout/Breadcrumb_cap_w.png

DIY Driver Feed

We have lots of Dell machines that don't seem to pick up all their drivers from the K2 Driver Feed.  The typical solution posted here seems to be to create post-install tasks that install specific drivers.  That's well and good if you want to manage a dozen different image options.  I don't want to do that, I want to have a single image option for our gold master image that will always install every driver for any model.

So I have devised a way that accomplishes this.  I have this script setup as a post-install task:

@ECHO OFF

title Installing any missing drivers, please wait...

FOR /F "tokens=2 delims==" %%A IN ('WMIC csproduct GET Name /VALUE ^| FIND /I "Name="') DO SET machine=%%A

ECHO Computer model: %machine%

net use w: "\\servername\share\%machine%" password /user:domain\user

call w:\install.cmd

net use w: /delete

The script uses the computer model as a variable to map to specific folders on a server share. Inside of these folders I have placed the drivers for each particular model that the K2 doesn't install (for whatever reason).  I have also placed a "install.cmd" file at the root of each folder with variations of the following commands:

@echo off

echo Installing video...
start /wait w:\video\setup.exe -s echo Installing chipset...
start /wait w:\chipset\setup.exe -s echo Installing USB 3.0...
start /wait w:\usb3.0\setup.exe -s echo Installing freefall sensor...
start /wait w:\freefall\setup.exe /s

When this post-install is used in conjunction with the RunOnceEx Convertor, the install.cmd file will be called during the first logon and will map to the share with the drivers.  Because the variable will change which folder gets mapped, I only need this one post-install task regardless of what model is being imaged.  As long as I have a "install.cmd" file inside of each folder, I can edit them separately and never touch the post-install task


Comments

  • This is exactly what I've been looking for! Thanks! One question though, the method the K2 uses by default to name folders and subfolders (ie \\k2200\drivers_postinstall\Brand\Model\driver files) how would you allow for it to find the Brand as well as the machine? Whats the %tag% for manufacturer? - aaronr 10 years ago
    • I believe instead of NAME it is actually MANUFACTURER. It should be entirely possible. - nheyne 10 years ago
  • So something like:
    <code>FOR /F "tokens=2 delims==" %%A IN ('WMIC csproduct GET Name /VALUE ^| FIND /I "MANUFACTURER="') DO SET machine=%%A</code> - aaronr 10 years ago
    • You would also have to say "GET Manufacturer" instead of get name. - nheyne 10 years ago
    • Just figured it out, it's "wmic csproduct get vendor" - nheyne 10 years ago
  • I also found a caveat, the NIC driver can't be done this way due to it being postinstall. DOH! - aaronr 10 years ago
    • Whoops hit delete accidentally... Email me for a detailed way to set this up and get the nic installed. - nheyne 10 years ago
      • I think your email is set to private. I made mine public if you'd like to send me the info. And thanks btw. - aaronr 10 years ago
This post is locked

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ