With a windows 7 syspreped image I can found a method that has not failed yet. I have only 2 admin images, one 32bit and one 64bit and one base 32bit academic image. I discovered by placing any missing drivers I have to install post sysprep back on my master machine in the windows\inf structure that model computer will then find the driver by itself next time.
Under windows\inf I created on subdirectory called tmccdrivers and then created subdirectories for each model. I put only the drivers I had post install in here to keep it's size down. Under most of the models I have audio, video. then some I need mei heci tpm. I even have 10 models of laptops this works for. currently my images suppport 18 pc/laptop models from gateway, dell, hp and lenovo.
When we get a new model staff deploy's a image to it. They find the missing drivers and place them on a share named imagedrivers by model\type directories. I have a midlevel task that copies this directory structure to c:\windows\inf\tmccdrivers. They deploy the image again to that model and the drivers are found without me having to create a new master immediatly. When I update the master (usually monthly) I move the drivers from the share to the master to save copy time during imaging.
Once I did have to copy the drivers for a video card from the temp folder vs the install folder, something to do with compressed files if I remember.
Because our master is hardware independant I now base all my images on software/licensing and they work in any classroom even if all the machines are not the same model.
Your method above works fine except when using an image with the 100MB system partition and deploying to HW that has a different sized Disk 0 to the Master Image PC. Under these circumstances it appears the bootsector code does not get copied across correctly or even at all. - squashedrex 12 years ago
What is the right way ?
10X - avishalomf 9 years ago