Driver feed not working for SDA Offline/USB deployment
I have a scenario in which I need to use an offline deployment in the SDA, and I'm finding that the driver feed feature is not working. I am on version 8.2.158.
Using instructions from here: https://support.quest.com/kace-systems-deployment-appliance/kb/4230503/create-usb-offline-deployment
The drivers_postinstall directory structure is created but the drivers aren't actually there. That's fine as I can just copy them manually.
However, the drivers just aren't getting installed during the deployment process. It seems to me like DISM doesn't run, a command window never shows indicating that the driver feed tool is running and it just marks the copy drivers task as successful. In my experience, even if the tool doesn't find drivers for the model it will still show something.
Has anyone else experienced this and know what might be wrong? For now I'm working on just adding a mid-level task of my own to do the driver install as it's really just for one particular model that I need this image.
Thanks!
-
During the offline deployment wizard did you it give you a page where you can add drivers? Did you click the + to add them? It only includes drivers that were downloaded using the feed. In 8.2, there is a dism log created for this task in the windows directory (In 9.0+ that log was moved to programdata\quest\kace\logs I believe. This might help troubleshoot. - cserrins 1 year ago
-
Yes, the wizard allowed me to add drivers and I clicked the +, that was all pretty straightforward. The image included the folder structure (e.g. KACE\drivers_postinstall\dell\windows_10_x64\5430) but it was empty, nothing in the folder. I did check for that DISM log but it wasn't there, I don't think it ever reached the step of running DISM. - zberkowitz 1 year ago
-
So I just added this identical driver to my offline deployment in version 9.1 and all the files were there. I encourage you to upgrade to the recent version after making sure everything is backed up and snapshotted! - cserrins 1 year ago
-
That's good, I will plan on doing that soon. But can you confirm that the actual driver feed task is working, in that it will actually run dism to install the drivers? - zberkowitz 1 year ago
-
It is working for me in 9.1 with vmware drivers, I don't have hardware to test on. If the directory is empty, then it will seem like the task doesn't run, but it just didn't find anything to do. You could manually put the drivers in that directory as a workaround until you upgrade. - cserrins 1 year ago
-
@cserrins Thanks for testing, as I mentioned I did add the drivers manually but still nothing. I'm assuming you mean you have the vmware drivers in your local/offline drivers_postinstall and DISM is running successfully to install these drivers? If so then that would mean the issue I'm having is indeed fixed in 9.1. - zberkowitz 1 year ago
Answers (1)
Make sure it's a Sysprep = YES image, before initiating the KB process. (check the Image's detail page).
And make sure Use driver feed is enabled right there from the System Image's detail page.
Then proceed with the KB article.
Comments:
-
Thanks for the response! But yes, it is a sysprepped image with driver feed enabled. - zberkowitz 1 year ago
-
IIRC that was a known issue in 8.x
Could you update to 9.0 and try again? - Channeler 1 year ago-
I see! I will hopefully be updating to 9.0 in the near future but will need to coordinate that in my organization. In the meantime I added a mid-level task to run a script that uses Dism to install drivers from a hard-coded directory. It works well enough for me since this is a unique case for me and all of the machines we need to image are the same model. Shared that task here: https://www.itninja.com/file/view/125 - zberkowitz 1 year ago
