Driver Package Export and Import. The Driver Package Export and Import feature was available in ConfigMgr 2012 RTM for most other content types, including software packages, applications, and content referenced within a task sequence. Import Drivers to Boot Image 1-From SCCM main console click Software Libray –> OverView –> Operating Systems –> Drivers, Select drivers, Right-click on Driver and click Import Driver. The import driver wizard will appear. 2- Specify the source folder where you saved the drivers, click browse and select the path. Anyone who manages drivers and driver packages for System Center Configuration Manager 2012 OS Deployment likely agrees that using the Admin GUI for importing drivers and creating driver packages can be a very time consuming process. Multiply that by number of OS’s, Architecture types and computer models you support and that can add up to a lot of lost productivity.
Configuration Manager 2012: Task Sequence Export and Import. Export and import functionality to the packages node. Some members of the System Center. How to Import Driver Packages In this blog I will take you through the steps of importing driver packages correctly into SCCM. Importing drivers into SCCM is in general a pretty simple task but their are a few pitfalls you have to be aware of.
Microsoft System Center Configuration Manager (SCCM) and Microsoft Deployment Toolkit (MDT) Package Index. SHOP SUPPORT. PC Data Center Mobile: Lenovo. Drivers & Software How-tos & Solutions Documentation. This is a quick post about making driver packages in SCCM 2012. When making driver packages, organization is key. Folder Layout. Your default folder layout for SCCM should look something like this, Sccm source$.
SCCM 2012 R2 Sp1 Console Version 5.0.8239.1403 Site Version 5.00.8239.1000
I imported the Surface Pro 4 win10x64 drivers into SCCM. Added them to a package. Distributed the package. THEN my network guy was showing me the awesome VEAM backup software and accidently restored my CM_SITE sql database on the sql server to the morning before. we lol'd.
Now, the drivers don't appear in the system and the package is gone and when I try to re-import the drivers it fails on every single one.
I created a new source folder, new package destination folder, new package (all with different names then before) and still it wont import any of those drivers but they still don't show up in the system. BTW, I did end up having to reboot the SCCM server to get it to sync up with the restored sql database.
Windows Driver Packages
Since then I have completed a different application roll out which worked fine but still can't get the SurfacePro4 drivers to re-import. Any idea where this ghost data is hiding out or what I can do to clean this up?
UPDATE: We did a full restore of both the SCCM server and the SQL DB to a date before I first successfully imported the surface pro 4 drivers. Thinking, this will obviously get me back to where I can reimport them without it failing like it did after the first db restore. I was wrong somehow. After the restore I created the source and package folders on the server just like I did the first time and tried to import and it fails, still thinking they've already been imported. The server is still on SCCM 2012 R2 SP1 CU3 which was totally capable of importing signed or unsigned windows 10 drivers before, as I already had the surface pro 3 and multiple win10 images on it. But the DriverCatalog.log is convinced the drivers are dups somehow. My mind is blown.
Lenovo Driver Packages
This driver has already been imported into the driver catalog. (CI_ID=SCOPEID_92B54D3E-85E8-4F67-BDE9-502F3B63DA1A/DRIVER_020C5852CA5072FA92E1E874E8C89FFA57872DB7_A6AF89A209601F97F89F7D491D8E0A3E03463A6BEE43786ED82A981391327CD6) DriverCatalog 9/26/2016 9:42:18 AM 4076 (0x0FEC)
CreateFromINF('SERVERNAMEe$XYZ-DataDriversSourceSurfacePro4DriversSystemI2C', 'iaLPSS2_UART2_SKL.inf') DriverCatalog 9/26/2016 9:42:18 AM 4076 (0x0FEC)
The driver import just fails on all drivers in the surfacepro4 catalog (which again, imported once before the restores successfully) and I see the above error many times in the log. I tried a tick where you use a bat file to add a .txt to each drivers folder to try to change the data size of the driver and maybe trick whatever hash it uses into thinking it hasn't been imported before and that failed also. I'm at a loss. Other ideas? Any reason to think an upgrade to 1606 or anything would improve my situation? About to burn a microsoft call as I feel there must be a quick fix to this.