Thursday, August 02, 2012 7:12 PM
Is it possible to choose created selection profiles from the deployment wizard the same way you do with applications? I know you can change the selection profile in the "inject drivers" section of the task sequence, but I use the same deploy task of an image for more than 1 machine type and do not want to change this in the task sequence every time I want to deploy an image.
Thursday, August 02, 2012 7:19 PM
This is my response to a similar question on this forum:
From this thread
- Proposed As Answer by Kevin Orrison Thursday, August 02, 2012 7:21 PM
Thursday, August 02, 2012 7:42 PM
Thank you for the quick response. I think I understand to use driver groups instead of selection profiles. Forgive me if I missed something in that article... Is this pretty much telling me I need to create a seperate task sequence for each type of hardware base I have even though I can still use the same imported / created image??
A little background... I am using MDT 2012 Litetouch only, as I do not have ConfigMgr. I used a VM to create a base image for all Win7 workstations in my environment. I only currently have 1 task sequence for this wim file (sysprep image) that I load to all of my workstations. We currently have Dell small form PC's, GigaByte barebones, and Asus barebone setups.
The task sequence puts the image fine on all hardware setups but I install various driver apps and tweaks per setup.
Thursday, August 02, 2012 9:14 PM
Your environment sounds similar to mine. I use MDT 2012 as follows:
I have one task sequence for Win 7 x64 and one for Win XP x86. I am using driver groups as described in that article. This way, you will be able to deploy your image to any make/model if you have the drivers in MDT. The driver path has to follow the same folder structure as you have it laid out in Out of Box Drivers. For example: My driver path in my TS is set to the following for Win 7 x64:%make%\%model%\Windows 7\x64
Here is my folder structure:
Thursday, August 02, 2012 10:24 PM
Thank you for the info. Hopefully I can get it working by following the article and your replies. It would be a nice addition/option in the deployment wizard for future updates/versions. As in a step similar to adding application packages during deployment. But I guess would also defeat the purpose of automation as it would be another step of user intervention. I originally only had just NIC's in the out of box driver folder (all in the root) for WinPE reasons and let Windows update install any PnP hardware drivers. Now I am trying to clean up this "tree" and organize folders and driver packs for different models so I do not have to rely on Windows Update to "hopefully" find everything.
Friday, August 03, 2012 1:28 AM
I also found a someone appropriate / recent video from someone that describes the inject drivers actions in MDT 2012 for those that might be interested. Similar to the article mentioned above.
Friday, August 03, 2012 2:05 AM
Question... It is obvious on some big vendor names to do a "WMIC computersystem get model" command to match your driver folders by model number, but when I use this command on barebones/clone computers I get no info or blanks. Do you have any idea how I am to get the model number to match it exactly as follows from that article from Johan?? I am stumped.. :(
Friday, August 03, 2012 2:57 PM
The way to tell if the MDT detect function would work is by checking the BIOS for the make and model as this is where it gets its info for the TS. I'm not sure what would be listed for a bare bone but it's worth a shot. Otherwise, I'm not sure as all the machines I deploy with MDT are Dell. But the process is the same for other manufacturers. It may be worth creating a new thread for that question.