Lenovo Models not matching SDA Driver feed path
Using version 9.0.146 of the SDA.
I have some Lenovo desktops that I am trying to image, but their driver paths are not matching up with the paths the Driver Feed is listing. For example, I am trying to deploy and image to a ThinkCentre M70s Desktop for Windows 10 21H2. The driver feed downloads the drivers to:
But when I run my scripted install, the drivers are not injected. I opened the log file on the SDA and see that the ThinkCentre M70s Desktop is actually being detected as 11t8 and the expected path should be windows/10/x64/21h1/lenovo/11t8 not 11db which is what the Driver Feed says and where it put the drivers.
In earlier version of the SDA there were some scripts in \drivers_postinstall\feed_tools that I could run that would show me the driver path, but they are no longer there. Also, the Driver Feed builder 3.0.0 that is available on the Quest site appears to only work for 8x and lower appliances because it still puts the drivers in the path of Make\Model and not the new 4-character model ID folder.
In order to get this to work with my Lenovo and HPs it seems like I am going to need 2 things:
- A utility I can run on a computer that will tell me the new machine type (4 character code)
- A reference table that will tell me exactly what driver feed matches the machine type because in the example I gave, I did pick the correct Model and OS, but the folder path was wrong for the lenovos.
I tried to find utilities on the Deployment Workbench - Tools page on the SDA, but that only links to old articles.
The first thing you probably need to understand is that this is not a KACE issue. For the driver share to work, the device type needs to match the name of the directory created in the driver share where that specific make and model device's drivers are stored. Over the years we have learned that the response that is given, when your SDA does WMI call to establish the make and model, is totally the responsibility of the hardware manufacturer. KACE is literally just reading the data they set.
So imagine if you will that Lenovo create a batch of BIOS that has the incorrect model code in, when trying to install drivers the WMI call gives wrong information and so drivers are not deployed.
It happens so you are best to run the Driver Harvesting utility where you can see the results of the WMI call and then ensure you have a directory in your driver share which is correctly labelled.
The ID 11T8 , is only for
Model": "ThinkCentre M70S Gen 3" (this is your computer per the Expected Path by the driver feed).
So... ThinkCentre M70S Gen 3 is different than
ThinkCentre M70S (the one in KACE's Catalog, and the one you are probably downloading)
Model: "ThinkCentre M70S",
Product ID: ["11EX", "11DB", "11DC", "11EW"]
So these are two different models, and unfortunately at first glance, I do not see the model ThinkCentre M70S Gen 3 available in KACE's Catalog.You may want to contact support.As a workaround you could manually build\create the PATH in drivers_postinstall:
And place the uncompressed driver pack there. Source:"Lenovo ThinkCentre M70S Gen 3 Win10 21H1"
I'm not fully in the loop, but what I can tell you is, Lenovo needs a lot of R&D to catch up to HP and DELL standards when it comes to organizing, tagging and distributing driver packs.
for Dell computers it is: wmic computersystem get SystemSKUNumber or Get-CimInstance -ClassName Win32_ComputerSystem | select Model,SystemSKUNumber
for hp it's different, I forgot. Use WMI-Explorer.
And Lenovo as I know Quest it's different, too and you have to look with WMI-Explorer for hours, because Quest don't tell you....