/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


Driver feed using 3.4 KNIT process

03/03/2014 1674 views

I recently upgraded to 3.6 and have decided to start using the driver feed instead of injecting the drivers directly into the WIM.  All of my WIMs were captured using the 3.4 KNIT process.  Will the driver feed work for me?  Also is there a bare minimum set of drivers that need to stay in the WIM or can I remove all drivers?  Last I have a few scripts that rewrite the unattend.xml as the final Mid level task.  Will this mess with the driver feed?

0 Comments   [ + ] Show comments

Comments


All Answers

0

I am 3.5 still, but I never had an issue using the driver feed with my KNIT-captured images.

Answered 03/03/2014 by: nheyne
Red Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ