Is there any info on the native imaging and injecting 3rd party drivers anywhere?  I checked the Admin manual and I'm not finding what I need.  I am currently using the info from my older 3.4 build, but the documentation does not mention if I keep using the old templates or the new checkbox for adding drivers.

Thanks for any info!


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



If you are imaging non-Dell systems then you can use the driver feed builder found here http://www.kace.com/hk/support/resources/kb/article/Driver-Feed-Builder to "inject" your drivers. The Driver feed builder will work with the new native imagin in version 3.5.

Answered 03/22/2013 by: Timi
Seventh Degree Black Belt

Please log in to comment

You'll use the new "Use driver feed (only with Sysprep'd images)" if you want to use the Driver Feed with your system images, whether they be kimage or native. 

You will no longer use the WIM templates from 3.4 as native imaging has been completely integrated. When capturing an image you will see a radio button to choose kimage or native format. Here is some info on getting 3.4 native images integrated into 3.5: http://www.kace.com/support/resources/kb/article/K2000-Convert-knit-wim-to-integrated-wim

New release information can always be viewed in the release notes. For 3.5 they are located here: http://downloads.kace.com/support/customer/release/K2000/3.5.76460/ReleaseNotes.zip

Answered 03/20/2013 by: mpace
Red Belt

  • We use non-Dell systems in our environment and some of the drivers are stored in \\k2000\drivers_postinstall.

    Does the new checkbox "Use driver feed (only with Sysprep'd images)" look at that folder?
    If that checkbox is checked, do we need to remove the mid-level task "Driver Feed Mid Task" aka Driver Feed Workaround from 3.4?
Please log in to comment