Driver Feed - Anyone using it?
Hi all,
I upgraded our KBOX 2000 up to 3.3 over the slow holiday week and spent some time trying out the Driver Feed function. We are a Dell shop on the PC side, so I was interested to see if this would allow me to stop having to manually upload specific drivers needed to load Win 7 x64 on to our different Dell models.
To test this out, I removed all the custom drivers we had from the KBOX 2000 driver share, recached the drivers, enabled the driver feed for a Precision M4500 and then recached the drivers once more. I am able to PXE boot a test M4500, but when I deploy a scripted install to the M4500 it fails within a couple of minutes with the following error.
Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure the drivers are valid, and restart the installation.
I've since disabled the driver feed for the M4500, recached the drivers, restored my custom drivers back on to the KBOX 2000 driver share and recached the drivers once more. Scripted installs are working as they should now.
I'm going to read in to it a bit more before I take another stab at testing it again, but was wondering what other people's experiences with the Driver Feed were.
Thanks!
I upgraded our KBOX 2000 up to 3.3 over the slow holiday week and spent some time trying out the Driver Feed function. We are a Dell shop on the PC side, so I was interested to see if this would allow me to stop having to manually upload specific drivers needed to load Win 7 x64 on to our different Dell models.
To test this out, I removed all the custom drivers we had from the KBOX 2000 driver share, recached the drivers, enabled the driver feed for a Precision M4500 and then recached the drivers once more. I am able to PXE boot a test M4500, but when I deploy a scripted install to the M4500 it fails within a couple of minutes with the following error.
Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure the drivers are valid, and restart the installation.
I've since disabled the driver feed for the M4500, recached the drivers, restored my custom drivers back on to the KBOX 2000 driver share and recached the drivers once more. Scripted installs are working as they should now.
I'm going to read in to it a bit more before I take another stab at testing it again, but was wondering what other people's experiences with the Driver Feed were.
Thanks!
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
trentderby
13 years ago
Hi i am using it and after downloading the drivers for a specific model of dell laptop, boom, it started to blue screen, after removing the new model from the driver feed and recaching, it started to work. not very impressive considering its supposed to make scripted installations non-driver specific if you have them downloaded in the feed.
Posted by:
asanchez
13 years ago
Hi Corey,
Thanks for the info. I did try the Driver Feed once more for the M4500 and tried removing the mass storage drivers, then recached. Unfortunately, I received the same results and ended up having to remove drivers from the Driver Feed folder one at a time until I identified the problematic driver that was halting the scripted install. While it seems convenient to have the Driver Feed pull down the needed drivers for the scripted install, I don't see it being a "plug and play" type of solution where you can enable the feed for a specific Dell model and expect the scripted install to complete successfully Trentderby and others (including myself) were hoping for. It still requires a good amount of trial and error to identify what drivers need to be purged for the scripted install to complete or need to be added as post-install tasks instead.
We'll keep testing it as time goes on, but for now we'll stick with using our existing custom drivers and periodically updating/adding to them via the driver harvesting utility.
Glad to see new features are constantly being added, though!
Thanks for the info. I did try the Driver Feed once more for the M4500 and tried removing the mass storage drivers, then recached. Unfortunately, I received the same results and ended up having to remove drivers from the Driver Feed folder one at a time until I identified the problematic driver that was halting the scripted install. While it seems convenient to have the Driver Feed pull down the needed drivers for the scripted install, I don't see it being a "plug and play" type of solution where you can enable the feed for a specific Dell model and expect the scripted install to complete successfully Trentderby and others (including myself) were hoping for. It still requires a good amount of trial and error to identify what drivers need to be purged for the scripted install to complete or need to be added as post-install tasks instead.
We'll keep testing it as time goes on, but for now we'll stick with using our existing custom drivers and periodically updating/adding to them via the driver harvesting utility.
Glad to see new features are constantly being added, though!
Posted by:
dyehardfan
13 years ago
Not impressed at all with the driver feed. I have had multiple issues with it and have gone back to manually harvesting the needed drivers. Also, the fact that it only supports Dell machines is garbage imo. I understand that it takes a lot of work to go through different manufacturers and get the needed drivers, but you would think that this would be a necessary feature. Just a sales ploy to get everyone moved to completely Dell shops?
Posted by:
cblake
13 years ago
Posted by:
dyehardfan
13 years ago
As long as y'all can pick up Fujitsu I will be fine with it. You guys have already bought our souls, we're going with Dell desktops and laptops, but find the Fujitsu tablets far superior to anything else out there at the moment so we're sticking with them.
Posted by:
ncsutmf
13 years ago
I had some errors where one models drivers would cause other models to fail. Digging through the error logs before it reboots, and it appears to be some sort of cryptographic module. What was really interesting was even though it was there in the feed, the driver list for Win 7 32 bit didn't even show the item in the list, even after recaching the drivers. If I can find which driver it was again, I will post it here. It appeared to exist at least in the 760 and 780 feeds. Even between those two models, if I had one or both of them enabled/downloaded, the other model would give the error.
Posted by:
ncsutmf
13 years ago
Of course, with all the trouble I had finding it earlier, I am able to find it almost instantly after I posted above. Here is the 32-bit one for the 780:
\Drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf
I believe all of the optiplex models I downloaded had the same issue. I think windows 7 64-bit setup gives a different error, so not sure if it is the same driver or something else.
\Drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf
I believe all of the optiplex models I downloaded had the same issue. I think windows 7 64-bit setup gives a different error, so not sure if it is the same driver or something else.
Posted by:
ncsutmf
13 years ago
More info, this was on the Optiplex 745 in KBE before rebooting, from X:\Windows\Panther\setupact.log (last few lines)
2011-02-03 17:23:07, Info PnPIBS: The class GUID for INF Y:\drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf is 4d36e97d-e325-11ce-bfc1-08002be10318
2011-02-03 17:23:07, Info PnPIBS: The class GUID 4d36e97d-e325-11ce-bfc1-08002be10318 is boot-critical.
2011-02-03 17:23:07, Info PnPIBS: The driver Y:\drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf is boot-critical.
2011-02-03 17:23:07, Info PnPIBS: Importing driver Y:\drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf ...
2011-02-03 17:23:07, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.]
2011-02-03 17:23:07, Info PnPIBS: The class GUID for INF Y:\drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf is 4d36e97d-e325-11ce-bfc1-08002be10318
2011-02-03 17:23:07, Info PnPIBS: The class GUID 4d36e97d-e325-11ce-bfc1-08002be10318 is boot-critical.
2011-02-03 17:23:07, Info PnPIBS: The driver Y:\drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf is boot-critical.
2011-02-03 17:23:07, Info PnPIBS: Importing driver Y:\drivers\windows_7_x86\feed\dell\780\780\win7\x86\security\r230054\tcm.inf ...
2011-02-03 17:23:07, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.