Mar 9, 2015 - Driver packages in SCCM 2012 are used for install. How to upload drivers into SCCM, create driver packages and keep everything organised. Please check back for Part 3 which will cover the actual migration process including creating migration jobs, what those migrated items look like in the new console, and some items around migration cleanup. And as always I hope this information is beneficial to all those looking into Configuration Manager 2012.
Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up? It might have been caught by the spam filter. URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes. We don't check the modqueue very often. if your post is stuck!
Resources:. (largely outdated) Chat Groups. Current Version:.
Flair:. Flair is reserved for Microsoft employees and MVPs. Please send mod mail if you qualify and would like flair set for your account. Contributing MVPs.
Contributing Microsoft Employees. SCCM 2012 R2 SP1 Issue 1: Cannot create driver package Issue 2: Auto apply drivers step applies no drivers Creating a Driver Package Step 1: Import all x64 drivers for a specific model in SCCM Step 2: Highlight all drivers Edit Driver Packages This step fails 9/10 times with 'Not Found', and I just keep trying until it displays possible driver packages Step 3: Select driver package that I have created (but empty, non-distributed) Error: 'Driver Source Directory ' server source drivers Dell 9020 9020-win7-A05-R1RRw. Does not exist. Unable to add selected drivers to package' - this path does not exist, which is correct. This is NOT the path that my drivers are. Is not correct. I don't understand why it changes when I try and import into in a Driver Package To try and circumnavigate this issue, which is only happening for this specific device and set of drivers, I try to auto-apply the drivers Auto apply drivers Step 1: Import all x64 drivers for a specific model into SCCM Step 2: Highlight all drivers Categories Create or Add to existing category Step 3: Create 'Auto apply Drivers' step.
Select 'Install all compatible drivers', 'Limit driver matching.' And select my category.I've also tried 'Install only the best matched compatible drivers' and 'consider drivers from all categories'. Step 4: Attach a WMI query for this model Nothing happens. I have custom Status Message Query for Task Sequences and I can see that the WMI query worked and it ran the Auto Apply Drivers step, but it finishes in 1 second and nothing happens. Can anyone shed some light on this? 'I don't understand why it changes when I try and import into in a Driver Package' Because you don't import into a package directory. The driver source directory is not the directory you import the drivers from.
The driver source directory is the directory the driver package points to and is where ConfigMgr copies the files to during the add to package process from the import/original location. These must be two different locations. Also, it's hard to tell from the above, but are you trying to specify a.cab file? If you don't have any drivers in any packages, then nothing can be delivered to the client during OSD. I get the directory errors when I am trying to add my drivers that I extracted from a CAB file into an empty Package I created. I created a blank Package, not distributed. I then highlight 397 imported drivers and do Edit Driver Packages.
This usually fails with 'Not found' and displays no packages, but on the occsasion it does work, I select my created package, 'Dell 9020' where I then get the above error. Edit. I have smsprov.log opened and when I click those drivers, I get these errors the moment I open their folder: Error setting property (InUse) 0x80041002! SMS Provider 2/24/2017 4:21:20 PM 1008 (0x03F0) Error setting property (IsBroken) 0x80041002! SMS Provider 2/24/2017 4:21:20 PM 1008 (0x03F0) Error setting property (IsChild) 0x80041002! SMS Provider 2/24/2017 4:21:20 PM 1008 (0x03F0) I get the above errors 397 times, one for every driver that I had highlighted.
And smsprov.log grows and grows, thousands of rows, until it has made it through every single driver that I had highlighted. I'm sorry - I am a little confused.
To your first point - I understand you do not import directly into the package source directory. I have 10 other driver packages that have worked correctly, but this specific set is not. I have sub folders under 'Drivers'; '9020', 'E6430', etc. After importing the contents of the CAB, I then move those drivers into their appropriate folder. During that import, I select 'And create a new driver package'.
This step fails with the above errors about the paths not existing. Since creating the new package during import has failed, I then select all my imported drivers and do 'Edit' 'Package' and I add to my existing 'blank' package that I created and pointed to ' server source drivers dell 9020 sccm ' and get the errors again about the incorrect network paths. ' server source drivers dell 9020 e9020x64 security' My first point was that this is not a valid UNC but you didn't comment on that at all. 'I have sub folders under 'Drivers'; '9020', 'E6430', etc.
After importing the contents of the CAB, I then move those drivers into their appropriate folder. During that import, I select 'And create a new driver package'. This step fails with the above errors about the paths not existing.' By folder, I assume you mean folder in the ConfigMgr console, correct?
Sorry, but it's really hard to follow what you're saying - remember that I can't see what you are seeing. Just giving me a single path out of context means nothing to me. You need to provide all relevant details to paint the entire picture here and not assume I know what you are talking about. Here's what happens when everything works:. You acquire the drivers.
Doesn't matter how or from where - could be extracted from a CAB or exe. These are the import drivers files. You place the import driver files in a location accessible via a UNC like cm01 ConfigMgr Import Drivers Make Model. This UNC must point to a share and path that is accessible to the computer account of the system hosting the SMS Provider (which is usually the site server). If this path is on the site server, then share permissions need allow cm01$ read (at least) and NTFS permissions need to allow System read (at least) - I usually add System to the share permissions as well. You run the import wizard and specify cm01 ConfigMgr Import Drivers Make Model.
![Sccm Sccm](http://scug.be/sccm/files/2012/06/clip_image004_2.jpg)
This recurses through all sub-directories examining the.inf files and importing in drivers based on these.inf files. When adding drivers to a package, either during import or after, ConfigMgr copies the files from the import location, cm01 ConfigMgr Import Drivers Make Model in this case (although it's probably a sub-directory of this location depending upon how you or the vendor organized the driver files) to the location specified for the driver package. Based upon the incomplete information I see in this thread, it looks like the driver files either no longer exist in the import location or ConfigMgr does not have read access to this location. Note that the location you are calling out is a sub-directory of the import location. I deleted all my folders / packages / imported drivers related to my 9020. I re-imported all the drivers and selected 'import duplicate drivers and keep existing categories'.
I believe what is happening is that we have all Dell's here and duplicate drivers per model. The first package I created was for my 9020. Later, after I created 10 more packages, I removed the 9020 to import a new CAB. The driver wizard sees that these drivers exist it another package and that is why it was failing.
Principal Consultant and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Currently working for TrueSec as a Principal Consultant. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions.
Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences and user groups. Author Principal Consultant and Enterprise Mobility MVP since 2016. Nickolaj has been in the IT industry for the past 10 years specializing in Enterprise Mobility and Security, Windows devices and deployments including automation. Currently working for TrueSec as a Principal Consultant. Awarded as PowerShell Hero in 2015 by the community for his script and tools contributions.
![Create Create](/uploads/1/2/5/3/125390039/555413077.jpg)
Creator of ConfigMgr Prerequisites Tool, ConfigMgr OSD FrontEnd, ConfigMgr WebService to name a few. Frequent speaker at conferences and user groups.