Windows 7 Thread, Driverpack problem in Technical; I use SAD2 to install drivers via a universal image for Windows 7 64bit but I'm having issues.
I have ...
27th March 2013, 10:29 AM #1
I use SAD2 to install drivers via a universal image for Windows 7 64bit but I'm having issues.
I have my image, and that works as expected, but I have an issue with a couple of devices and their drivers.
The problematic machine is an HP ProBook 6570b, and it refuses to install drivers for its USB3.0 root hub, for the 3D Drive Guard and for the Validity fingerprint sensor.
I have created a custom driver pack, which SAD2 is successfully installing the Broadcom Bluetooth driver from. But it ignores the other 3 drivers. However, if I go into device manager, and point the device at a folder containing the same contents as that USB3 folder in the driver pack, it installs!
So, can anyone give any insight into what on Earth is going on?
IDG Tech News
29th March 2013, 12:38 PM #2
Using MDT? Have you tried just dumping all the drivers into the repository, if they work it should install them. I think you can also provide a driver searchpath in the WDS sysprep stuff that you could point to a network share.
29th March 2013, 12:50 PM #3
29th March 2013, 01:21 PM #4
Oh, manually it is then. The bit about the driver search path is still valid just not sure how to set it all manually without any of the advanced tools like DSIM.
Originally Posted by localzuk
29th March 2013, 02:42 PM #5
That's what the SAD2 script does, it uses a directory with driverpacks in it, in 7z format, unzips them, and then uses DPInst to go through them all to see if any fit the devices that are on the machine.
29th March 2013, 02:57 PM #6
What stage of the process does it do it in though, could it be being blocked by something else running at the time.
Originally Posted by localzuk
29th March 2013, 03:14 PM #7
It does it on first reboot after the normal setup has finished. All other drivers install fine this way, on a bunch of different machines. Just not these few drivers on this specific machine.
Once it finishes this script, it reboots again, and the Fog client does its bit - renames and reboots the machine, joining it to the domain.
29th March 2013, 03:16 PM #8
There are issues with USB 3 driver installs using wds as well, it seems to be beacause the driver installs in two stages, the way we got round it was to inject the driver into the WIM image rather than deploying it as a driver pack using DISM Gui.
Windows 7 WDS Deployment - USB 3.0 Driver Package Won't Install
29th March 2013, 03:39 PM #9
You could install the driver as a FOG snap-in, using the silent install switch on the original installer. Or investigate the HP System Software Manager which looks like you are meant to hook it into your deployment somewhere to silently install all of the drivers you need.
The Admin Nexus: Installing HP Driver Packages and Software During a Task Sequence With HP System Software Manager
29th March 2013, 03:52 PM #10
I think I will be looking at the FOG snap-in route - keep it all centred around a 'universal' approach, rather than using system specific software.
Originally Posted by morganw
29th March 2013, 03:58 PM #11
I used to use the snap-ins to do some audio drivers on XP, but had to bundle them inside a 7zip self extractor to make sure that the FOG client wouldn't continue with the next snap-in or a reboot. Some silent installers just launch another process and then quit, but the self extractor will wait to clean-up after itself.
This is pretty handy too:
Unattended, A Windows deployment system: Unattended/Silent Installation Switches for Windows Apps
18th June 2013, 11:25 AM #12
A little help required please. When my machine reboots and runs the DP_install_tool.cmd it runs through all the drivers but does not install the drivers from the driver packs. I know the correct drivers are in there as I have pointed to them manually before and it's picked them up fine. Any ideas why this might be happening?
19th June 2013, 01:40 AM #13
You could try recursively deleting NTFS streams within your driver folder, just in-case access is being blocked.
streams -s -d directory
By alexknight in forum Wireless Networks
Last Post: 22nd August 2005, 05:01 AM
By mark in forum Wireless Networks
Last Post: 22nd August 2005, 04:52 AM
By Dos_Box in forum Educational Software
Last Post: 19th August 2005, 03:32 PM
By Rozzer in forum Windows
Last Post: 19th August 2005, 08:49 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)