also if you are creating a “universal” image and can spare an extra 10gb or so then look at “snappy driver” for deploying drivers. That is what I use for my “universal image”.
for our Windows 7 image I did the following:
*set up our “unattend.xml” using a workstation.
*from within a hyper-v guest, install fresh W7 and boot into audit mode.
*install base software (office, serif, any other site licenced products).
*install FOG client
*copy snappy drivers and download the packs.
*configure setupcomplete.cmd to run my snappy driver .bat. This BAT autoruns snappy driver to install MISSING drivers, then deletes the folder of drivers when completed.
*copy the unattend.xml created earlier.
(I then “backup” my VM at this point so I can come back to it later)
*sysprep shutdown and generalise
*capture the image into FOG then restore VM from backup ready for the updates next time.
To get snappy drivers to install, simply open it, update the packs, then in your setupcomplete.cmd call
SDI_x64_Rxxx.exe -autoinstall -autoclose -license
The batchfile also cascades into an RD and shutdown reboot at the end of it so it is self cleaning. NOTE I also shutdown the FOGClient service in my setupcomplete.cmd as I DONT want it to join the domain as soon as it sniffs the network! It will join the domain (and rename etc) AFTER the drivers have been installed and rebooted. The batch file also ensures our KMS key is added and I run slmgr /ato. I also add the office KMS key and activate that at the end too, whilst there are default KMS keys when products are installed, I have other images with MAK keys as some of our machines are destined to be unplugged from the network (exam machines etc).
My image is a monster, weighing in at 40gb but works on every single machine I have thrown it on and they are pretty much ready to go (WSUS always has more updates on first boot)