Importing Drivers

SCCM defines a driver as an INF file plus its associated content.  When a driver is first imported we do a check to see if the exact same driver (e.g. same INF file and content) has already been imported at the site and prevent it from being imported.  However, if there are any differences then…


When Auto Apply Drivers Fails to Resolve Content

We often get questions about the Auto Apply Driver action not being able to resolve content – which results in the following lines in the smsts.log file: Found 0 DPs in subnet, 0 DPs in local site, and 0 DPs in remote location. Failed to resolve content for driver “<Driver Name>”. Code 0x80040102. If you…


Why can’t I import a driver from a local drive path?

Boot Images, Operating System Images, Operating System Install Packages, and Drivers must be imported from a UNC path in ConfigMgr 07.  Many people have asked why they can’t reference a local drive path instead.  Here is the explanation for drivers, courtesy of Michael Kelley.   The explanation for the other types of packages is analogous. Because…

Intel ICH8USB drivers demystified

For the folks that are having difficulties with the Intel ICH8USB drivers there is a simple explanation and workaround. Explanation The driver references a system DLL (usbui.dll), which is not present in Windows PE.  This causes the driver installation to fail, and since it’s considered a boot critical device (chipset), the task sequence may fail….


Boot Critical and Mass Storage Drivers

The following contribution from Brett Flegg outlines the steps for working with boot critical and mass storage drivers in ConfigMgr 07 Operating System Deployment. First, you will need to determine if the default boot image contains a compatible driver for your RAID controller.  The easiest way to do this is enable the boot image’s debug…