Win 7 Drivers using DPINST 64 bit??

Discussion in 'Windows Problems' started by andyroo54, Jan 19, 2012.

  1. andyroo54 Community Manager

    Hi,

    So I'm still fairly new to Fog. Everything was setup by the last guy prior to my arrival. I've learnt a fair amount, however currently we only have XPSP3 image in Fog. Now from what I've seen the drivers are on a shared network location where SAD is with some drivers.

    Look basically I'm looking for the best way to have win 7 pro X64 install by itself, scan the hardware and install appropriate drivers from a network location. I read somewhere that DPISNT may have to be 64 bit version?

    Can someone please point me to some documentation that details how to configure 7 to get these appropriate drivers? I was going to point "MW pnp customizationsWinPE" Driver paths, PathandCredentials, then point it to the network share location? Would that work? Or should I use this DPINST tool?

    Any help would be much appreciated, thankyou.
  2. andyroo54 Community Manager

    I would rather use the xml file to point to the server share location, but how does it scan the hardware? Does it do this without any add ons?
  3. dugjones New Member

    I have not had success with getting drivers to install using the DriverPaths option in the unattend.xml. Admittedly, though, I have not spent a lot of time trying to get it to work. I do have my fog installation modified to copy the specific drivers for the computer build down to a folder on the c: drive after imaging but before booting. It wasn't a simple thing to configure so unless you are already skilled at writing bash scripts or are very determined to learn you may want to find another way to get the drivers on the pc.

    The way I am currently handling driver installation is that I put a Windows-Shell-Setup / LogonCommands entry in the oobeSystem to launch an AutoItv3 executable which launches the dpinst.exe (which points to the folder previously mentioned). There is probably a better way to do it but I had my Windows XP installs doing something similar so I just modified it slightly. I have only tried it with a couple of different builds so far but it works well. One nice thing about dpinst.exe is that it has a force option (/F) which forces your specified drivers to install even if they are not considered "better" by Windows.

    Dpinst.exe is part of the Microsoft Windows Driver Kit (WDK) and it does include 32bit and 64bit versions. Below is a link to a technet article that should get you started.

    http://blogs.technet.com/b/svengrue...lation-and-updating-made-easy-dpinst-exe.aspx

    Doug
  4. Nate Baker New Member

    I know this thread is old, but wondering if anyone else has had success with this?

    Doug, your method sounds like it would work great, but I'm wondering if that would work with critical drivers such as storage and network? Or do you need to have the storage and network drivers in the image already, and install the rest of the drivers using that method? It seems like since that oobeSystem pass is the last pass, it would need the storage and network drivers by that point.

    Thanks,
    Nate
  5. andyroo54 Community Manager



    Check out the guide I made here:

    http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/
  6. Nate Baker New Member


    Thanks Andy, that is a great guide. I guess the question I had was similar to reply #53 on that guide: http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/page-3#post-3147

    You replied (to him):

    I was thinking that you needed the critical drivers (at least the mass storage controller) before the SAD tool is run, or it wouldn't even be able to boot, execute the SAD script, and install the remaining drivers. If Windows doesn't recognize some new mass storage controller hardware ID, how will it even get to the OOBE stage? I'm still not 100% clear on that, can you just have ALL drivers including the critical ones installed in the OOBE stage?

    Also, what I'm looking into doing is something like Doug posted above, having a directory that you can keep all your drivers in, and then having FOG (after deploying image) or Sysprep (during setup) copy the drivers from the network, and then run SAD / DPInst. That way I could add drivers for a new model to the network share and not have to update & re-create the image.

    Thanks!
  7. dugjones New Member


    Sorry for the late reply. You are correct, Nate. I inject mass storage and LAN drivers into my base image for all the models of computers we deal with here before sysprep.

Share This Page