戻る
-
タイトル
Drivers are not installing during deployment -
説明
Drivers not installing during a Scripted Installation or System Image Deployment usually indicates a problem with the Driver Injection Process or folder name where drivers are installed. -
対策
Quest Kace always recommends upgrading to the latest version of KACE System Deployment Appliance (KACE SDA). Known issues with driver injection were experienced by users of versions 3.7.110284 and earlier.
- Verify the image is built and sysprepped with System Image Best Practices KB 121734
- Verify (for system image only) that "Use Driver Feed" is checked in your System Image Details page for the image.
- For Dell Model systems, verify the drivers for the model/OS are installed into the Driver feed for the OS and architecture of the model.
- For Non-Dell Systems, use the test below to determine if the drivers are in the correct location in the Drivers_Postinstall Driver Share.
Troubleshoot Driver Location
Step 1: Determine the location where the drivers should be located
On a computer of the same Model, OS Version, and Architecture as you are deploying to, copy the entire feed_tools folder in the drivers_postinstall share to the desktop and run the driver_feed_discovery_tool.VBS script. It will return a dialog box showing a folder path where the KACE SDA will look for drivers. Take note of this, to include the case of the path name.
Step 2: Drive Placement
- If you already have drivers for the model, ensure that the drivers are in the folder path returned in step 1.
- If you do not have drivers for the model:
- if the driver exists in the KACE SDA Driver Feed, go to Library > Driver Feed and download/install the drivers from there.
- if drivers do not exist in the KACE SDA Driver Feed, either place the raw driver files in the path returned in step 1 or leverage the Driver Feed Builder (http://www.itninja.com/blog/view/driver-feed-builder) to upload the files for you. Compare the location to the path returned in step 1.
Step 3: Testing Driver Injection- Boot a system into KBE
- From the main menu, click on Recovery > Command Prompt
- Run this command:
y:\hta\copy_drivers.VBS - At this point, the command should run; another command window should open and start injecting drivers. Watch the process to see if the drivers are injecting successfully and take note of any errors.
If the drivers inject but there are still some missing drivers in the device manager when booting into the OS, test out a full deployment and check the device manager to verify that all of the drivers are installed. If drivers still missing at this point, please open a Service Request as outlined below.If it just blinks and closes the second window:
- Double-check the driver path against the driver_feed_discovery_tool.VBS results
- Make sure you are using a KBE built on the proper version of WinPE. The best practice is to use a KBE built with WinPE 10 to deploy Windows 7, 8.1, and 10.
If it is still not working, please create a Service Request adding the following information:- The KACE SDA version
- A screenshot or log of the driver_feed_discovery_tool.VBS output
- The DISM.log is located in the Windows directory from a deployed system (e.g. C:\windows\DISM.log)