I have been using the k2000 for a couple months now and have done a few images. I always sysprep and use the driver feed in my images.
My Kbox is at 3.6.98680 

I took a functioning image and exported it to a USB key.
That key is successful in imaging but never loads the drivers fro the machines.
I have copied the post install driver folder from the kbox to the usb key as well.

Is there a particular process I need to follow to build a fully functioning usb key for image deployment?

0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


This content is currently hidden from public view.
Reason: Removed by member request
For more information, visit our FAQ's.

I found the solution is to copy the post install driver to the usb drive under the kace folder
Answered 10/30/2014 by: Duncan
White Belt

Please log in to comment
If these are sysprep'd images you are putting on the key, place the drivers in c:\windows\inf\SomeFolderYouCreate\subfolders.  Then the driver feed is not needed

windows 7 has a undocumented feature. When a machine comes out of sysprep the discovery engine looks at c:\windows\inf for drivers. I created a subdir under that on my master called tmccdrivers and under that I create subdirs for every model of computer we have and put that models drivers there. Currently about 6 desktop and 6 laptop models.


Answered 10/30/2014 by: SMal.tmcc
Red Belt

Please log in to comment