I take that you are familiar with drivers and manually creating driver categories and driver packages in Configuration Manager. Here I will show you how you can optimize the process by running a very need little PowerShell script called ImportDrivers.ps1 (main developer is Claus Codam).

  1. There are a few prerequisites that needs to be in place before the script will work.

    Driver source has to be 3 levels deep like this example (Make\Model\OS). The driver source is where you store the original driver packages from the vendor.


    You need to create a Driver packages folder (where ConfigMgr will import the drivers to). The script will automatically create a folder using folder names in Driver Sources.


  2. Open the ImportDrivers.ps1 script and modify the last two lines in the script as in this example.

    New-SCCMconnection: add the FQDN of your site server e.g. cm01.viamonstra.com

    SMSSiteCode: Type your site code e.g. PS1

    Driver source: Type the unc to the toplevel of the driver source (the location where you have the original drivers) e.g. \\FileSrv01.viamonstra.com\sccm_sources$\OSD\DriverSources and in
    Driver package type the destination e.g. \\FileSrv01.viamonstra.com\sccm_sources$\OSD\DriverPackages


  3. Launch the script from PowerShell to start the import. The script will automatically import the drivers, create unique driver categories and driver packages.


  4. You can re-run the script multiple times, it will only import new drivers.