LENOVO DRIVERGRABBER DRIVER
So that means almost 60% of ConfigMgr OSD users are somehow working around the driver management challenges in the product (28% following Johan’s advice, and about half of the 63% that are using driver categories and driver packages and defeating duplicate detection, so 28+63*0.50=59.5). As a result, the percentages are probably flipped around, with the majority of customers preventing ConfigMgr from detecting duplicates. As I mentioned in the MMS session, these CAB files include a unique “release.dat” file so they defeat the duplicate detection process, so they are unknowingly in the other category. When you drill into the responses a little deeper, several of those that answered “manually handling duplicates” said that they were primarily Dell shops and were using the Dell driver CAB files.
LENOVO DRIVERGRABBER DRIVERS
So a lot of you are importing all of your drivers into the ConfigMgr driver store, but to make that work a significant percentage of you are purposely defeating the ConfigMgr duplicate driver detection by creating a unique file that results in a different has for every driver: The majority then use “Apply Driver Package”, with 39% importing the drivers into the driver store (the way driver packages were intended to be used) and the remaining following Johan’s approach (not importing drivers, creating driver packages pointing to the physical store). 24% use “Auto Apply Drivers” with categories to better control which drivers are used. So 9% import all their drivers and let the “Auto Apply Drivers” step inject the best one. While no one said they were using the “install drivers using applications” as their primary mechanism for handling drivers using Lite Touch, over 30% of those using Lite Touch said they were installing at least some drivers as applications once the OS was up and running – basically implementing hybrid scenarios.įor those of you using ConfigMgr 2007, the breakdown is a little different: And the majority of you are taking it even further and leveraging driver folders (DriverGroups), effectively becoming “control freaks”. 27% import all drivers and then use selection profiles to control which drivers to use (typically per OS). So 21% just import all the drivers and let the system figure it which ones to use on each computer (not too bad when the number of models is smaller). So here’s the interpreted results based on that sampling.įor those of you using MDT 2010 Deployment Workbench and Lite Touch deployments, the breakdown looks nice: Now that’s what I call “instant feedback”. Thanks to Rod, Chris, Reed, and others who helped encourage people to check out the driver management survey blog posting I made last night, I was quickly able to get over a hundred replies. First published on TechNet on Apr 29, 2010
0 kommentar(er)
