we added a bunch of new drivers our central site for the latest HP desktop. we were able to create a WinPE boot disk (bootable media) and connect back to one of our primary sites and build a Windows 7 OS on our new HP desktop. but, every time we create a stand-alone DVD the new drivers never get placed on the DVD and when we try to build out a new machine it fails since there are no drivers. All drivers are Enabled and all drivers are on the DP's, we double and triple checked this. why do our stand-alone (FAT) DVD's not contain the required drivers that work perfect on a bootable media?

Hi, just make sure that all drivers needed are placed in a driver package. That driver package must be placed on a DP and used in the task sequence. That way your driver package will be also copied on the stand alone media. Another topic which discuss this: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/141bbe54-a375-48d2-945d-7874ddc7fe54/ Hope it helps!My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn

are you referring to the actual windows machine drivers or the drivers needed for winpe to communicate with your network?

yes, we did create a driver package and it was copied out to all DPs. but when we create a 'stand alone media' the DVD does not have the driver package on it. It has all the other packages but not the newest driver package.

we are talking about drivers for the hardware. NIC, mass storage etc....... WinPE works fine.

Hi, have you seen the topic mentioned before also? http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/141bbe54-a375-48d2-945d-7874ddc7fe54/ Jason mentions the following here: As long as the package is explicitly referenced in the TS, it will be copied to the media and thus accessible during the TS; it essentially uses the media like a DP. Just make sure that the newest driver package is also on your DP and use "Apply driver package" in the task sequence.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn

No, we do not call out the driver package in the Task Sequence. For the step called "Apply Device Drivers" we use "Install only the best matched compatible drivers" & "Consider drivers from all categories". Is that the reason? Here is a similar question. We have many different types of hardware we support. What do you do when you have too many drivers that won't fit on a DVD? Do you create a task sequence for each type of hardware? OR, can you have a Task Sequence use IF THEN logic and call sub-task sequences from within?

Yes, that's the reason. Just create a new driver package as mentioned before. That way all drivers needed will be placed on your stand alone media. Just use the drivers needed to have the hardware list complete. When using multiple driver packages for one single Windows image, put a WMI query on it. With the query SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%<MODEL>%" you can decide which driver package belongs to which system. With WMIC > "csproduct get name" you can see the Model for every system. Just use one task sequene for multiple hardware models.My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn

is that package being referenced in the task sequence you are creating DVD media from? the step should be of type: "Apply Driver Package"

Henk, thank you. I'd like to ask one more question if that's ok. For your SELECT statement where do I do this? Is that done on the APPLY DRIVER PACKAGE - OPTIONS TAB - Add Condition - Query WMI? - Also, I started WBEMTEST and ran this query. SELECT * FROM Win32_ComputerSystem WHERE Model LIKE "%780%" It returns my NetBIOS name, not the model. We need to get the Model type/name, how do you get that? - And one final question. If we have 30 driver packages for 8 different types of hardware and you want to build a FAT DVD, how does the stand alone media wizard know to grab the right drivers? Or does it grab ALL driver packages and if YES how do you deal with the huge ISO files? They won't fit on a standard DVD.

Hi, my pleasure :) 1) Yes, the condition is on the place you mentioned. Just do that for every driver package with a query. That way you can keep a single task sequence. 2) The model you can get with WMIC (started in cmd.exe) and command line "csproduct get name" (see other post above) 3) The right driver package will be choosen because of the query. To avoid swapping DVDs during imaging with larger stand-alone media based images, it is convenient to use a USB thumb drive. http://blogs.technet.com/b/configurationmgr/archive/2011/05/05/how-to-create-offline-or-standalone-usb-media-for-os-deployment-in-configmgr-2007.aspxMy blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn