1. Windows 7 Tool Usb

Windows 7 Tool Usb

I'm deploying Windows 7 RC with MDT 2010 Beta 2, and I'm trying to figure out how to automatically inject hardware-specific drivers while still in PE and before the image boots up to Windows 7. I realize that I can import all of the drivers for all of the different hardware models into the Out-of-Box Drivers node; however, this will always dump all of the drivers for all models onto every machine that I install to. Pokemon mystery dungeon explorers of darkness free romantic poems. I do not want this. I'd like to be able to filter (perhaps through WMI) which drivers get injected based on the hardware model.

I can't find any instructions on how to easily do this in MDT 2010 Beta 2. Are there any walkthroughs or guides on how to deploy only the drivers that apply to the particular computer hardware model in MDT 2010? Thanks!Brian Hall www.bhall.com. Since MDT 2010 is still in beta, I anticipate that there are many changes to come in regards to driver injection based on make and model. As I was scouring the sparse and often esoteric MDT 2010 Beta 2 documentation, I found reference to a Make and Model node in the Deployment Workbench: From the Microsoft Deployment Toolkit Documentation Library distributed with MDT 2010 Beta 2: 'To automate deployment using make and model, begin by identifying the make and model combinations in the organization and how they will be used to apply configuration settings to the target computers.

The make and model combinations are based on the Make and Model properties of the target computers' 'After creating the make and model combinations, specify configuration settings for properties for the computers that match them. These configuration settings are stored in the database and are retrieved by ZTIGather.wsf.' 'In addition to querying the locations directly by the make and model combination, associate a combination with a group of computers that performs a specific role using the Role properties associated with the role within each location. Do this by configuring the Roles tab in the Properties dialog box of a make and model combination item on the Make and Model node in Deployment Workbench.' So, I take this to mean that there will be a Make and Model node in the Deployment Workbench that will allow for further customization of driver (as well as application, etc.) deployment based on hardware make and model.

Or else, I'm completely misunderstanding the documentation. Anyone out there with some insights?Brian Hall www.bhall.com.