What to do when K2000 driver feed falsly cannot find the drivers path for Dell Lat 5530, although the drivers for this model are loaded
After sending the image to the particular laptop (lat 5530), it fails during the third step "Apply Image" where it gets to about 40% - after several hours, but the "Driver Feed Advisor (v. 22.214.171.124) states "The driver path does not currently exist on the SDA"...
and, of course, the 'OS: >OSNotFoundlocalDrive< as it's deleted during the very first step - formatting...
Any fix to it?
an usual error is that the SDA expects the driver in another folder than it is saved. This is caused by changes in BIOS of the vendor.
To verify this, you simply login into your PC (in this case a 5530) and go to:
run then copy_drivers_debug.vbs manually.
Compare the lines Driver Feed Path with the actual location ( instead of y uses \\sda\drivers_postinstall)
Ignore the error that it cannot write to the location.
If there is a difference, open a case with KACE support and add the screenshots of the tool and also notify the BIOS version, Vendor, Make, OS you want to install and the filter version.
KACE will then modify the filter for this system (which is an automated process you don't need to do much here then)
You can find the filter here: \\sda\drivers_postinstall\feed_tools\drvstr.cfg
As of today the filter version is:
# Driver Feed Exception File
# Supported Versions 4.1.SP1-9.1
# Last Revision 01.23.2023
# Comments need to start with character '#' strictly on a new line ONLY
# Comments are NOT supported on the same line containing configuration data
(do not modify the file since it us updated regulary during check in to solve such issues you reported and will roll back your manual changes)
Your knowledge is greatly appreciated! I'm a K2000 novice, learning as I go. :-) I copied the \\sda\drivers_postinstall\feed_tools folder to the desktop of a non-domain Latitude 5530 (per Step 1: at https://support.quest.com/kace-systems-deployment-appliance/kb/4306536/drivers-are-not-installing-during-deployment), then ran the copy_drivers_debug.vbs manually. I receive an error, "Windows Script Host - No Registry entry found." I do have an open case with KACE, so I can wait for help. I just wondered if you have an easy fix for this error. :-) Thank you! - JessiS 3 months ago
the first error message No Registry Entry Found is not that important (it is because you run it outside the environment it is made for)
It seems (I have no 5530) that the latitiude reports wrongly from the BIOS than the amounts it awaits, therefore the filter needs to be modified. If you are unsure, feel free to contact support. And if you are unhappy with support contact me and I do my best to improve the experience. - Nico_K 3 months ago
As per Q.T. Support recommendation "you will need to create a new KBE with the latest PE drivers - A029", I started it with using a VMBox virtual Win10 image, and downloaded ADK (for Win11 as all my Win10 PCs are 22H2 version, and I need to start deploying Win11 soon) and Media Manager, but hit a stumble block where the path of the installation file "C:\Program Files (x86)\Windows Kits\10..." shows as invalid - no matter which folder under "10" I choose. Not sure what's wrong here... Any idea?
Thank you again... - bambus011 3 months ago
The issue is not related to the driver feed unless its actually at the task where its called to inject drivers into an image. The apply image is just taking the image from the SDA and placing it onto the hard drive of the target system (in this case the 5530).
The driver feed builder is a utility to use on an existing model with the drivers up to date to gather and then upload those to the appliance for the driver injection task after the image is deployed. It is used when that model is not showing in the driver feed.
The image deployment issue could be due to several factors and depends on what type of image is being deployed, scripted install or syspreped image that was captured and uploaded.
If you haven't submitted already, these are the things they asked me, which might speed things up for you if you provide them upfront: :-)
"Let's check the following:
1. Make sure the SATA operation in the Bios is set as AHCI (not Raid).
2. Boot up the Latitude 5530 in the main KBE menu, click recovery> command prompt and type the command: diskpart Then type the command: list disk and press Enter. This is to confirm if the hard drive is being detected. Please send me a screenshot.
If no hard drive is detected, that means the KBE you are using needs newer storage drivers, so we will need to create a new KBE with the latest PE drivers.
Could you please send me screenshots of the error(s)? Also a screenshot of the system image options (e.g. https://prnt.sc/8PmyH9bBEp3p), and a screenshot showing the current image Deployment Plan (PRE and MID level tasks in use).
Please also send me the Deployment logs located in \\SDA\petemp\ look for the date of the log file. The file also has the Laptop's MAC address and image ID. You can find the Image ID of an image by navigating to its Image Detail page in the web interface, the number at the end of your internet browser's address bar is the Image ID." - JessiS 3 months ago
Quest Customer Support helped me to resolve the issue with failed images for the Latitude 5530. (We are currently on K2000 SDA v9.0.146.)
Per their Support recommendation, I built a new KBE with the latest Dell PE driver pack A29. He advised against using the A22 driver pack, as is noted in their KB 4321348. I pasted his notes below:
"I would definitely recommend you create a new KBE with the latest driver pack A29.
Dell PE driver Pack A29 download link: https://www.dell.com/support/kbdoc/en-us/000108642/winpe-10-driver-pack
How to create a KBE for Windows 10: https://support.quest.com/kb/4321348/how-to-create-a-kbe-for-windows-10 (please don't use the pack A22 from this article)
Make sure to delete pack A22 before copying the A29, this is important."
I hope this helps! - JessiS 3 months ago
- However, following the steps for creating and uploading the KBE, I hit a stumble block at the point where the "path" I'd enter into that required field rendered as incorrect... Have you used a VM, or did you install the ADK and Media Manager on a regular PC?
Thanks again for sharing,
Bambus011 - bambus011 3 months ago