Friday, December 9, 2011

Manage DRIVERS in SCCM 2007 / 2012

Managing drivers can be quite a struggle.

Here a few ways of dealing with it.


The HP way




Import your Storage and Network drivers, Add the respective X86/X64 drivers to eatch boot image.

Then Add these to a Driver Package.

Add the Driver Package to your Task Sequence.


Then you have the most inportant drivers working.
You need to deal with all the rest.
Heres a easy way of doing it! And less administration. But with some cons though.
Offline media does not work, and download - install is not approriate because of the size.
Other than that it's a nice way of handling the drivers.
What it really does is running all drivers a silent install packages.

Alternativly you can skip the metod with SSM below and create all the Silent install packages and add them to Task Sequence with WMI query it you want a more robust, with download and with the Offline media option.

Allright here we Go!:
You need to get the

HP.com homeHP SoftPaq Download Manager

http://h20331.www2.hp.com/Hpsub/cache/509658-0-0-225-121.html
And the

HP.com homeHP Client Management Solutions - HP System Software Manager

http://h20331.www2.hp.com/hpsub/cache/284133-0-0-225-121.html?jumpid=ex_R2845_vanityim/gossm/ka011106

Uncheck all the software you don't want.  (get it right the first time, removing packages later can be a bit time consuming.
Look in the category Software - Security.  You might not want all the HP Protect Tools stuff etc..

Then hit the Download... and wait a few hours.

Then Update the database running in the download folder:



SSM /AM_BLD_DB



Create the Package in Configmgr Console



No Source, because this package would be like 10-20GB large depending on your amount of models.
This is most likely caused by the enourmous Video drivers.




Command line:        \\sccm\ssm\SSM.EXE . /INSTALL /ACCEPT



Add the Package to the Task Sequence.

 Get it ON. Now run the Task Sequence and test!

Now, all you have to do when a new models arrives is to download and run the update database command.

To handle TPM for Bitlocker use the HP tool. Check out this:
http://systemcenterforefront.blogspot.no/2012/06/sccm-and-bitlocker-tpm-real-life.html
 -----
The Dell way - the easy way :)
 
Look at my earlyer post:
http://systemcenterforefront.blogspot.com/2011/10/dell-client-integration-pack-20-for.html




The Lenovo way - how can we make this easy..
 



This metod is not a bulletproof metod, and must be tested every time after changing the Update repository. But is a easy way of handling drivers for Lenovo.

Install Lenovo Update retriever on server.




Follow this blog from my fellow Configmgr MVP Kenny. It works.
http://scug.be/sccm/2011/01/17/configmgr-2007-osd-using-lenovo-update-retriever-to-install-all-your-drivers-without-importing-them-in-the-configmgr-driver-catalog/

But choose the updates carefully, or the Updater may fail.



Another metod is to Use the Lenovo Update retriever to download the drivers you need, and use the new function Export Package. Then import that package to SCCM creating a Driver Package. This is more failsafe metod.

But as Lenovo now are creating SCCM ready driver packages, this will be no issue any more.
Except it seems for older models, they might not bother creating packages for them.
http://download.lenovo.com/express/sccm.html


No comments:

Post a Comment