I agree with Gjstewart. This is the way I have done it, and it works very well. I have two images, 32-bit and 64-bit, and I use a provisioning task to wipe the drive, load the image, run HII, then run a batch file that calls WMI to find make and model. I then pull down any other drivers that HII cannot pick up (mostly setup.exe). I then map a drive to a share that contains all of my installs, along with a custom script that processes registry settings, and other settings that I require. I found that everything I need can be done through simple batch files. I then call a secondary script that installs applications that I require on all devices (Antivirus, LDMS). I have also created these batch files with the ability to receive command line parameters, from which I pass from the provisioning task. These parameters tell which share (many locations, so many different shares) to pull from, and whether or not to install Office, or just the Viewers.
It all works very well, and I find managing the batch file(s) is mush easier than the Provisioning Task. I can change it on the fly without having to modify anything in Landesk.