Search the Community
Showing results for tags 'driver packages'.
Hi Everybody, this thread is for those who want the old SCCM 2007 driver management back. Normally you have to import every driver to the database first, put them into a driver package, and then deploy them during OSD. In SCCM 2007 you could easily create a Driver Package from your Driver Source Folder and apply this Driver Package during OSD. This way of Driver Management was much easier and more reliable than the new way in SCCM 2012. But luckily there is still a method to prevent importing drivers into database and directly distribute driver packages to your clients. Step 1 Download drivers for your brands and models. Put them into seperate folders - one folder for one model - like you did in SCCM 2007 Step 2 Create a Package for each model and operating system. Then distribute this packages to your DP. Step 3 Create a Step "Set Task Sequence Variable" under your Auto Apply Drivers Group (after the Apply Operating System Step) in your Task Sequence. Task Sequence Variable: winrootdir Task Sequence Value: D:\ Condition: If Folder "D:\Windows" exists I created a second step after this with Drive Letter E:\. Because on some Notebooks the Systemroot is E:\ during OSD. Step 4 Create TS Steps for each model to apply the driver package. Type: Run Command Line Command line: DISM.exe /Image:%winrootdir% /Add-Driver /Driver:.\ /Recurse Package: Choose the corresponding package you created in step 2 Success codes: Add 2 and 50 Condition: WMI Query (here an example for Dell Latitude E7240) select * from win32_computersystem where Model like "Latitude E7240%" Repeat the steps above for each computer model you want to image. With this way of applying drivers we have 0 problems in our environment. Very easy and reliable. BR Achim If you have questions - feel free to contact me http://ithilger.de/kontakt
Hi, Our current Task sequence for the Surface pro devices has been working great for sometime. Now with our entity moving towards Windows 10, I'd like to just add on the driver package step in my task sequence to get the needed driver package at it's desired OS. Currently, I have one driver package for Surface devices with all drivers and firmware as shown in the tutorials provided from here. My current WMI query for identifying the device is the basic " Select * From Win32_ComputerSystem WHERE Model LIKE "%Surface Pro 3% " Which works fine for when you have two different generations of Surface Pro devices. With our WIn10 migration coming up, I've gone ahead and imported the Win 10 driver package into SCCM, but I need to find a find a better way to query the two different driver packs. Otherwise the TS will install both packages to the system, defeating the whole point... So, my question is- What is the best way to query the driver packages for the same device but each being guided at a different OS? (we need to keep both packages present for the time being) By OS? - with the builds of windows 10 changing every 8 months, how will this(if at all) affect my query? Any suggestions or wake up calls is always appreciated!
Hello. This is my first post here. I have been using SCCM 2012 for a little while now. I have imported about 30-40 different PC models. About 20% of the models "failed". The wizard does not give any indication of any foul play, it all seems like everything went ok. But when I check the Monitoring - Content Status and compare the size (MB) of the package to the folder of the imported drivers, they "often" dont match. If I delete the Driver Package and delete the imported drivers, and do the same import again, I have managed to force some more models that previously had wrong size. I did the import exactly the same way, some times the size is wrong and sometimes the sizes is correct. I have no clue as to why it some times failes and some times work... I tried to look at the DriverCatalog.log, but didnt find anything interesting.. Has any other then me experienced this problem? Can someone please check this Compare this "Monitoring" - "Content Status" - "Size (MB)" to the folder you use for imported driverpackages They should be the same size... PS. The driver with wrong size seem to work fine, so im wondering if this is just a bug to the "Monitoring" - "Content Status" - "Size (MB)" view... sometimes not updating correctly? Thanks
Hi. Have a question regarding driver packages in SCCM 2012. We have added driver packages for different computer modells, we can se that it access the packages but no drivers get installed. Then we read that you have to import the drivers as driver packages dont work as before. Is that correct? I think it seems strange that you have to import all drivers to get it to work, as in CM07 driver packages are enough. Do anyone have experience regarding driver packages in CM12? Thanks in advance