Partager via

Importing Drivers

  • Article

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 the metadata is read from the INF file (including name, manufacturer, supported operating systems, etc.) and a new driver object is created.

It is not uncommon for hardware vendors to package different INF files for each operating system they support in the same directory.  When this happens, SCCM will create a driver object for each INF file but it is smart enough to only keep a single copy of the content.  Since the default name of a driver comes from the supported hardware list in the INF file, each of these driver objects will likely get the same default name even though they support different operating systems (to see if this is the case, check out “Applicability” tab on the Driver’s preview pane).

There are a few things you can do about this:

  1. SCCM generates a default name for a driver based on the hardware that it supports – but you can change this in the driver’s properties screen.
  2. Add additional columns to the Drivers view so that you can tell the difference between the drivers:
  • Select the Drivers node in the Admin UI
  • Run the ViewAdd/Remove columns… action
  • Select additional columns to display (for example “INF File”)
  • Ignore it – Since SCCM automatically determines driver applicability at deployment time you don’t really need to worry about the specific drivers in the driver catalog.

After importing a driver you can review the driver catalog matching reports (“Driver catalog matching report for a specific computer” and “Driver catalog matching report for a specific collection”) which use hardware inventory information to predict what drivers match devices in your environment to give you a better idea of how the drivers will be used.

Contributed by Brett Flegg

Comments

  • Anonymous
    January 01, 2003
    PingBack from http://aceddl.cn/x/configmgr2007-importing-drivers.jsp

  • Anonymous
    January 01, 2003
    How do you import an INF when it states that there are no supported OS's?? From the Wizard for Importing: Verify the following drivers for importing. The following driver(s) will be imported: \xxxxxxxxsourceFilesDriversUATHPPROVISTA32e1y6032.INF Add drivers to the following packages: HP NIC Packages will not be updated on distribution points. Add drivers to the following boot images: Development Boot Boot images will be updated on distribution points. When I click the finish button I get the following: Error: Some driver(s) can not be imported successfully. Please see following details.   Error: Failed to import the following drivers: \ukdc209001sourceFilesDriversUATHPPROVISTA32e1y6032.INF - The selected driver is not applicable to any supported platforms. The driver is correct for Vista SP1 and the hardware model in registered in SCCM. Can you provide any pointers/help??

  • Anonymous
    January 01, 2003
    he there BlUNt, you shuld try this one itdiplomat.wordpress.com/.../you-cannot-import-a-driver-into-an-osd-image-if-the-driver-is-signed-for-only-the-windows-7-operating-system-in-sccm-2007-sp2

  • Anonymous
    October 22, 2008
    Is it possible for ConfigMgr to add the drivers to a new driver package even if they have already been imported??? When tell ConfigMgr to add some drivers in a directory and create a driver package it only adds drivers to the package that haven't already been imported. This seems, well silly....