Lenovo Drivers not installing after 3.6 upgrade
Hi All, I have seen some similar comments, but no suggested solutions have helped me.
I am running Windows 7 Scripted Install. Install is stable on Dell models e.g. E5440, however drivers are not installing on our Lenovo's (some of which were ok prior to upgrade). Drivers are in postinstall share. I have ran "driver_feed_discovery_tool.vbs" to confirm following path is correct. \\ikbox\drivers_postinstall\lenovo\windows7x64\20B7S0JW00. The only difference from the vbs output is that lenovo is in UPPERCASE but surely this is not the fix?
Install just skips through "Copy Drivers" step, it doesn' t appear to do anything.
I am totally out of ideas.. and time, before I get some serious grief! Any experts out there who can help me?
Answers (1)
We had the same issue. The Lenovo 'model' number needs to be replaced with the plain English model name. So if you had a model entry for 7360CTO ...which happens to be a ThinkCentre M58, then you need to change the driver directory name from 7360CTO to ThinkCentre M58.
Here's some additional notes I got from Kace:
Previously, all models were pulled via WMI from the win32_ComputerSystem path, but since Lenovo stores their "friendly" model name in the win32_ComputerSystemProduct path instead, we've changed it to reflect that in response to complaints about sub-models taking up large amounts of space due to duplicate drivers.
For example, what might be returned as the proper path in 3.5 (e.g.
\lenovo\windows_X_xXX\79858855) would be returned as the friendly model name in 3.6 (e.g. \lenovo\windows_X_xXX\Thinkpad T99)
I would recommend changing to the new directory structure. You can determine the proper path for 3.6 by running the driver_feed_discovery_tool.vbs (located in
\\k2000\drivers_postinstall\feed_tools) on one of the models in question and it will return the correct path and model name. If this is not feasible, I can change the behavior back to the 3.5 method, but it will only be in effect until the next upgrade.
Comments:
-
Thanks! Kace support came back with the new driver path tool, which resolved the issue. I don't understand why the new tool is not available for download, or why it was not in my feed tools folder. Thanks for your response! - ethel_winters 10 years ago
