Scripting

We have a K1000 and K2000 the recent update to 3.6 on the K2000 changed a lot of how we used to do things.

The largest is no longer do we have an image for each computer model (that contained all the software & drivers) now we are using a sysprep image free of drivers and pulling down drivers via the driver feed.

Problem here is that often some drivers just do not pull down properly, I suppose its missing elements needed to function properly that are only installed if done via the installer instead of from a double driver rip.

What I am seeking is the most automated way to run the installers for drivers not installing properly in a way that is basicaly hands off to the techs imaging the machines so that I know once I set it up it happens with no interaction on their behalf.

So what I have ruled out is post install tasks for each machine that need to be manually applied since I would have to rely on a person to look at the current tasks and change as needed for the machine model being imaged.

I am thinking I may need to use some sort of smart label in the K1000 to do this, but I would need it to happen right at the deployment time of the image not a week later when the label decides to catch and the automatic job runs.

I imagine people probably embede a forced checkin as a post install task to remedy this, if that is the case just looking for steps and guidance on how to get that far and how I should og about setting up my labels and there associated scripts.

One extra piece of info, what I started to do today is find a way to "silently install" the exe files and I did this via AutoIT I have already written a script to install several drivers from start to end and was able to compile those into an exe.  So I think this will help with my request as I can just have the AutoIT script do the installing I just need the KBOX systems to recognize the proper system and push out the installers and run the scripts.

Thanks for the feedback,

Edit: Just recalled I can't do a forced check in right after the K2000 is done because we have not given the PC the proper name or description yet so it would check in incorrectly.  The few times I checked in a computer early it was difficult to get it to refresh with the new info even with a forced updated.