You may have had a computer in the wrong class a time or two before in which the wrong drivers came down and the computer would not boot.
In most cases, when this happens you would just go into HIIS, put the machine in the right class, then send the Image job back down to the computer from the DS Console again. While this method works, it also will take quite a while to wait again and you don't have to Re-Image the machine at all!
Here is a normal HIIS Image Job:
In order to Perform the "Run Script" Tasks after a failed Image attempt (since you can't boot into Windows on that machine now) you will have to create a new job to boot the machine into a PXE such as WinPE or whatever environment you used to Image with in the first place and then run the Tasks again.
So to get started, first; Put the computer in the correct Driver Class in HIIS. Once done, Create a new job in the DS. Copy the "Run Script" Tasks from your initial HIIS Imaging job and then Paste them into the new Job you had just created. I call my Job "HIIS Re-Inject Drivers". After you have copied the Tasks into your new Job it should look like so;
Now, you will need to create a new task above the first "Run Script" Task by clicking "Add" and then click "Wait".
Now, pick your Automation Environment (Usually left on your default automation) and click "Finish"
Use the Arrow buttons to bring this Task to the top of the Tasks list:
After that, your Job should work fine, run the Job on the failed driver injection computer and it will boot back into your PXE and reinject and should boot fine afterwards (considering the driver class the computer is in has the correct drivers).
Let me know if this works out for you (I sometimes get lazy with the classes I put machines into I guess so I use this job a couple times a week!). I always enjoy feedback so if you have any Q & A, go for it!