Can anyone tell me how I can "Inject" drivers after I image a computer, like you do when you do a scripted install? I have all my preinstall Tasks and post install tasks setup the same.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Currently we do not offer slip-stream driver injection for K-imaging like we do with Scripted Installations. That is something we are currently experimenting with.

Right now, you will have to be sure the image has the correct drivers embedded in the image before capture or install drivers as post installation tasks.

Hope this helps.
Answered 01/26/2012 by:
Senior Purple Belt

Please log in to comment
If you know where the drivers go, you can use the imagebrowser to put them in, and then edit the registry of that comptuer to add the path.

However, it is much easier to use the driverfeed workaround in my opinion,, then you aren't adding a million drivers to one image.

Answered 01/27/2012 by: cserrins
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity