KACE Product Support Question
Driver feed using 3.4 KNIT process
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?