<div>
If I understand you correctly, the next step is to duplicate the step to install drivers in your task sequence and sign each one to a particular model selection profile. You will then need to restrict each driver install step to only activate if the response to a wmi query defining the model is correct.<br />
<br />
I'm on mobile now, but will try to add more detail when at a computer.
</div>


If I understand you correctly, the next step is to duplicate the step to install drivers in your task sequence and sign each one to a particular model selection profile. You will then need to restrict each driver install step to only activate if the response to a wmi query defining the model is correct.

I'm on mobile now, but will try to add more detail when at a computer.

<div>
The attached screenshot is from an SCCM integrated MDT Task Sequence, but you have similar options in MDT.<br />
<br />
You can determine the model from the command line using 'WMIC ComputerSystem GET Model', then use a WMI Query as in the screenshots.<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/02_w09/899988/ApplyDriver1.png" target="_blank" class="file-inline" title="Apply / Inject Drivers phase properties tab (29 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>ApplyDriver1.png</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2015/02_w09/899989/ApplyDriver2.png" target="_blank" class="file-inline" title="Apply / Inject Drivers phase options tab (27 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>ApplyDriver2.png</a>
</div>


The attached screenshot is from an SCCM integrated MDT Task Sequence, but you have similar options in MDT.

You can determine the model from the command line using 'WMIC ComputerSystem GET Model', then use a WMI Query as in the screenshots.
ApplyDriver1.png [https://filedb.experts-exchange.com/incoming/2015/02_w09/899988/ApplyDriver1.png]
ApplyDriver2.png [https://filedb.experts-exchange.com/incoming/2015/02_w09/899989/ApplyDriver2.png]

ApplyDriver2.png

Apply / Inject Drivers phase properties tab

ApplyDriver1.png

<div>
<div class="content wysiwyg-content">
Hello<br />
i already had built windows server 2008 and install MDT 2012 service.<br />
it's work fine and i successfully installed windows 7 over network<br />
but my problem is.. <br />
i need to make MDT recognise the computer model and loaded the appropriate driver from Out of box drivers<br />
&nbsp;where is configured with all computers drivers in my network.<br />
attached snap pic. showen my MDT structure.<br />
<br />
So, Whats the next step to achive my point?<br />
<a href="https://filedb.experts-exchange.com/incoming/2015/02_w09/899970/mdt.JPG" target="_blank" class="file-inline" title="mdt.JPG (62 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>mdt.JPG</a>
</div>
</div>


mdt.JPG

Hello
i already had built windows server 2008 and install MDT 2012 service.
it's work fine and i successfully installed windows 7 over network
but my problem is.. 
i need to make MDT recognise the computer model and loaded the appropriate driver from Out of box drivers
 where is configured with all computers drivers in my network.
attached snap pic. showen my MDT structure.

So, Whats the next step to achive my point?

how to let computer order driver automatically from MDT 2012

Windows 7 is an operating system from Microsoft. Features include multi-touch support, a redesigned Windows Shell with a new taskbar, referred to as the Superbar, a home networking system called HomeGroup, and performance improvements.

Windows 7

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.