Step 8: Drivers- SAD2
This topic is one that will no doubt cause some to interject with their own way of doing drivers. That's fine, however I spent quite some time trying to find the best way to inject drivers to win 7 installs. Most ways are clumsy and require more work than it's worth. I've settled on this path and it works great for our situation, across any machine.
Essentially after install on first logon, the "setupcomplete.cmd" script will call the "SAD2" driver tool to run. The SAD2 driver tool was made by community members of the driverpacks.net forums.
Stand Alone Driverpack utility for all OS (XP, 2k3, 2k8, Vista, Win7) (Page 1) - Windows 7 tools - DriverPacks.net Forum
You can download it from the above forum link. I'm using version 111118.
You need to create and then save the folder to:
or else you need to adjust the setupcomplete.cmd script in step 7 to where you place the tool.
Now for the drivers you need to go to driverpacks.net:
Latest DriverPacks | DriverPacks.net
And download all of the packs you want for win 7/vista x64. Do the same for x86 vista/7.
Once you have downloaded the driver packs (you don't need to extract them), place them in the respective folders for each image:
So in the x64 image you only put the 64 bit drivers into the x64 folder, and for the x86 image you only put the 32bit drivers into the x86 folder. This will add only approx 1gb to the final size of the OS partition if you use all packs. We only use core driver packs.
I made a few changes to the "DP_Install_Tool" to make it fully unattended, and also so that it restarts after the drivers have been installed, and deletes the driver packs from the image. I will attach the modified tool to the original post in this thread, so you can just download and replace it in your SAD2 folder, but essentially I just removed the prompt that asks you if you want to proceed, and removed and pauses after that also. Then I just added: **I have attached the modified DPinstall tool, but I had to change it to a .txt in order to upload to this post. You will need to modify the file extension back to .cmd.
shutdown -r -c "Drivers Installed! Machine will now restart.."
..to reboot the machine after drivers have installed, and delete the drivers. You will need to create a "RemoveD.cmd" script in the location as specified above. The SAD2 tool creates a folder called "D" in the C:\ root , so I added this script to both delete the "D" folder, and the drivers to clear up some room. The .cmd script is below:
rd /s/q C:\D
DEL /F /S /Q /A "C:\Drivers\SAD2-111118"
rd /s/q C:\Drivers\SAD2-111118
I suggest creating another snapshot and testing that the tool runs correctly. You can also try the tool out on a physical machine to make sure it is working for you. I have fully tested this and it works every time. This is also the reason why it's good to have a x86 version of your image, because as I mentioned although even an old P4 processor can handle x64 OS, if you try to inject x64 drivers it can cause big problems. So I suggest if the machine you are imaging is less than 12-24 months old, then go for x64, if it is any older then use x86. Really the only reason you might want x64 is for the machine to use more than 4gb of ram, and most machines that have 4+gb ram are less than 24 mths old anyway.