Driver Package on OSD - How contents are injected
Hello, I need to understand how the Driver Package contents are used by the OSD process (excluding those injected into WinPE, dont care about those). Are the driver files only pulled from the driver package IF the hardware is present? Or will it blindly dump all relevant inf files to system32 etc? The reason I ask is I have a 3g card that whose drivers I have injected into a driver package yet the files are not there. The device is DISABLED in the BIOS at build time. Best, W
May 3rd, 2012 3:15am
Hi, in this links the process is described About the Driver Catalog Auto Apply Drivers Apply Driver Packages So it seems that if you use the auto apply drivers, it search only for the present hardware. Maybe you can use a seperate software package which copy the drivers to the driver store if it is necessary. To check, if your device have to use the package, you can use WMI Filter regards, Stefan
May 3rd, 2012 6:00am
Thanks for that, very useful. I am using the "Apply Driver Packages" step. The drivers are applied to the package and referenced by the task sequence correctly. The Hardware IDs match correctly. Yet, If I do a search in system32 for the inf file, it is not present. I have tried even with the device ENABLED in the BIOS. It seems to me that the files simply are not being copied, as the device is detected but windows says Driver files not found. What log files should/can I check to track the behaviour and check for sure if the files are copying? Thank you
May 3rd, 2012 6:13am
Hi, have you checked the installation of unsigned drivers? have you distributed the driver package? regards, Stefan
May 3rd, 2012 7:12am
I havent checked the installation of unsigned drivers - How do I know if they are unsigned? If I install via the vendor setup exe, i do not get a prompt for unsigned drivers. Yes, the package is distributed. Otherwise, the task sequence would not run,. Thanks.
May 3rd, 2012 7:13am
I should also mention the hardware in question is GOBI x000 3G internal cards. which look very difficult to get working.
May 3rd, 2012 9:29am
I suspect that the vendor's driver inf is a culprit here. It's not unheard of at all for bad infs to cause issues. You could just run the vendor's setup during the task sequence.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 3rd, 2012 1:29pm
This is exactly what I have to do. Sucky GOBI 3G Card drivers! Aiming for Make and Model in MDT. Testing ongoing.
May 8th, 2012 9:07am