none
Driver Best Practice in SCCM

    Question

  • I have had little luck in getting some driver questions answered. We're using SCCM to deploy ZTI images and PXE to workstations. Here's what I did...

    MDT Driver Installation - We use a WIM file for each brand of machine that has model specific drivers. we extract them to the C: drive and via a task sequence, install them. Works like a charm.

    SCCM Driver Install - I imported drivers to the SCCM console and created a driver package for my HP 2530p laptop. All the drivers imported w/o a hitch - even created categories and model specific folders. I wanted to add drivers for my HP 6930p laptop, so I did the same - seperate folders & categories. Only problem is that the 6930p uses a lot of the same drivers as the 2530p, so I got a boat load of dupilcates and less than half of the drivers in my new 6930p folder as my 2530p folder.

    My questions, specifically, are:

    1) How are duplicates in the driver package handled? If I have 20 drivers in one driver package and only 8 in the 2nd because of duplicates, how do the missing 12 drivers get loaded if they are not part of the 2nd ddriver package?

    2) I'm VERY scared the answer is going to be that i MANUALLY have to review the driver package foreach machine (this was already done and I now have ot do it a 2nd time??) and MANUALLY add the drivers to a specific group or category.... did I mention this is a MANUAL step. What are the best practices (and please don't link me to the page about good & bad drivers - been there) for driver management where you may have multiple machines using the same drivers?

    Any help is appreciated. My questions a quite specific and there is little more than the standard Microsoft vague reference available.


    Regards,
    -DaG

    Tuesday, March 23, 2010 3:50 PM

Answers

  • You've kind of stumbled into a bees nest of this one as there are actually very different opinions on driver management and depending on the hardware and drivers involved, there is no one correct answer to driver management. Driver Management was left open because of this and there are actually multiple paths that can be taken and these can even be mixed and matched.

    Kenny's post is excellent and describes one way doing things. Another great post is this one by the Deployment Guys: http://blogs.technet.com/deploymentguys/archive/2008/02/15/driver-management-part-1-configuration-manager.aspx.


    Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
    Tuesday, March 23, 2010 9:22 PM

All replies