Scripting Question

K2000 Driver Feed

01/11/2016 1508 views
My K2000 has been doing scripted installs to late model Optiplex's and Lattitude E7440 and E7450 systems.  This afternoon I got a new Dell Precision T3420. Of course it won't boot in my current KBE environment so I called KACE support and the tech recommended creating a WinPE10 based env.  Copied up the files, recached and created the environment.  System won't boot.  Bombs on iastor.  With the help of some other posts here in this form I created another environment using the Driver packs 4 and 5.  So now I have a working KBE boot environment that boots the T3420.  BUT...... I select my standard image of Win7_64 and the process immediately bombs on creating the 1st 2 partitions (C: and D:).  No problem, I'll just temporarily create them myself and move on.  Finally got that fixed the image is deployed and finishes.  When I login to the system afterward, the image is correct with all the application installed but their are no drivers installed.  Device Manager shows exclamations for all the drivers not installed.

So when I look at the driver feed in the K2, T3420 is selected and driver feed is enabled for that image.  What am I overlooking?

0 Comments   [ + ] Show comments


All Answers


to get the advantage of the Driver Feed during image deployments you need to check the following things:
  1. Check that you have downloaded the drivers in the Driver Feed menu.
  2. Check that the image that you deploy has been sysprepped (it is a requirement!).
  3. Check that you ticked the checkbox Use Driver Feed in the System Image that you're distributing.
Kind regards,
 Marco - StockTrader
Answered 01/12/2016 by: StockTrader
Red Belt

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