I have captured a win7 x64 machine and have created a task sequence for it. I had to inject the nic driver into the boot file also. The task sequence completed without any problems. The only problem that I see that there are a bunch of drivers missing (display, mass storage, card reader.....ect.) My question is, should I create a driver package and add these drivers to it and then add the driver package to my task sequence? Or should I roll out the driver package by itself after the OSD?Thanks, Mark-

Hi, I normally use one Driver Package per model and deploy them during the OS deployment task sequence. A driver package can contain all drivers needed by a computer model. You could also import the drivers in the SCCM console and apply only the best matching driver. As I said I still use driver packages and only import Nic and storage drivers needed for boot-images. There is a guide from SCUG.be that you could have a look at-. http://scug.be/blogs/sccm/archive/2009/02/27/sccm-2007-best-practice-importing-drivers-part-1-creating-a-driver-package.aspx regards, Jörgen-- visit my System center blog at http://ccmexec.com --

Hi, most of times I create a driver package per model also. With Windows 7 you will see that less drivers are needed, because most off them will be detected during installation. Just deploy the image per model, and see which driver are needed actually. When putting multiple drivers in a task sequence, use a WMI query do decide which driver package must be used. This will be explained on my blog: http://henkhoogendoorn.blogspot.com/2010/10/driver-management-in-configmgr-2007.html So the order you named is correct. Just create a driver package and add the drivers to it, and add this driver package in the task sequence.My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

You can use this PS script from Niehaus to create the packages for you http://blogs.technet.com/b/mniehaus/archive/2010/04/29/configmgr-2007-driver-management-the-novel-part-2.aspx Also be aware that even though it seams like you are not missing that many drivers in the device manager, the ones there, might be very old, as they were probably handed to Microsoft before the time of the 7 RTM. So even though your audio driver is not missing, it's probably not an HD audio driver and so on.. All in all, you should create the driverpackages pr. model, and supply all the drivers you want added to your OS, missing as well as updated ones! Michael Petersen http://blog.coretech.dk/mip/

I concur with the rest of the team on this one. You should import your drivers into SCCM, assigning them a category and a package. These can be based on each particular model, and if deploying multiple OS's, different OS Architecture (E.G. HPDC7900.XPx86, HPDC7900.W7x64 etc). If all or most of your hardware is from one manufacturer, start with the newest model of desktop/laptop first, import the drivers into SCCM, assigning them to a category and creating a driver package. Then apply your image + drivers via your deploy task sequence. If all the drivers install successfully on your newest hardware, deploy the same image + drivers to your older hardware. You should find that most if not all the drivers are compatible with the older hardware, with the exception of a few 'fussy' devices such as Intel AMT cards and alike. For these devices, you may need to use an 'Apply driver package' step in your task sequence, as they wont always be installed via the auto apply drivers step. Remember to add a task sequence variable based on 'model' so that the drivers are only applied to machines that require it! Good luck Mark. - Scott.