[27515] in resnet
Re: Managing Hardware Drivers in MDT
daemon@ATHENA.MIT.EDU (Umansky, Shawn)
Fri Mar 30 12:30:33 2012
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_E9F8CA088AE7B645B6A412B2F7133AAA2BC7086ASMCEXMBX02miken_"
MIME-Version: 1.0
Message-ID: <E9F8CA088AE7B645B6A412B2F7133AAA2BC7086A@SMCEXMBX02.mikenet.smcvt.edu>
Date: Fri, 30 Mar 2012 16:29:14 +0000
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: "Umansky, Shawn" <SUmansky@smcvt.edu>
To: RESNET-L@listserv.nd.edu
In-Reply-To: <CAEPWjzt6k_YNK5zJrwpuXNe5iaEVB0Fh85M35keR22Nd0_MijA@mail.gmail.com>
--_000_E9F8CA088AE7B645B6A412B2F7133AAA2BC7086ASMCEXMBX02miken_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Thanks, Marc. That is helpful. I notice you chose not to organize by comp=
uter hardware model. Did you find that to be unnecessary?
From: Resnet Forum [mailto:RESNET-L@LISTSERV.ND.EDU] On Behalf Of Doughty, =
Marc
Sent: Friday, March 30, 2012 10:13 AM
To: RESNET-L@LISTSERV.ND.EDU
Subject: Re: Managing Hardware Drivers in MDT
We're using WDS, and only parts of the MDT. What I do is this:
/DRIVERS
/<class>-<vendor>[-item]-<version>
e.g. /video-nvidia-verde-295.73
/audio-sigmatel-stac93xx-5.0.1403
/DRIVERS.PE<http://DRIVERS.PE>
/chipset-intel-10.3.1019
/lan-intel-16.8
/storage-intel-matrix-9.6
Using this method, I can add the entire 'DRIVERS.PE<http://DRIVERS.PE>' fol=
der recursively to the boot images/utility disks, while the all-inclusive D=
RIVERS folder gets slipstreamed into the images themselves. We pushed hard =
to only build x64 images going forward, so I don't have to worry about that=
. If you're doing x86 AND x64, you probably want to have two separate DRIVE=
RS hierarchies:
/DRIVERS
/x86
/PEx86
/x64
/PEx64
- Marc Doughty
"If you aren't sure who is the give-way vessel, you are the give-way vessel=
."
On Fri, Mar 30, 2012 at 9:08 AM, Umansky, Shawn <SUmansky@smcvt.edu<mailto:=
SUmansky@smcvt.edu>> wrote:
Has anyone found a preferable way to manage/organize their hardware drivers=
in MDT (i.e., folders based on hardware model, etc.)? I know it's somewha=
t personal preference, but am curious to learn how others handle this (and =
why it works for them). Any advice is welcome.
Thanks,
Shawn
Shawn L. Umansky
Network Engineer
Saint Michael's College
Phone: (802) 654-2763<tel:%28802%29%20654-2763>
SUmansky@smcvt.edu<mailto:SUmansky@smcvt.edu>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
___________________________________________________ You are subscribed to t=
he ResNet-L mailing list.
To subscribe, unsubscribe or search the archives, go to http://LISTSERV.ND.=
EDU/archives/resnet-l.html ________________________________________________=
___
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--_000_E9F8CA088AE7B645B6A412B2F7133AAA2BC7086ASMCEXMBX02miken_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D">Thanks, Marc. That =
is helpful. I notice you chose not to organize by computer hardware m=
odel. Did you find that to be unnecessary?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1F497D"><o:p> </o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:"=
;Tahoma","sans-serif"">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:"Tahoma","sans-serif""> Resnet F=
orum [mailto:RESNET-L@LISTSERV.ND.EDU]
<b>On Behalf Of </b>Doughty, Marc<br>
<b>Sent:</b> Friday, March 30, 2012 10:13 AM<br>
<b>To:</b> RESNET-L@LISTSERV.ND.EDU<br>
<b>Subject:</b> Re: Managing Hardware Drivers in MDT<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
<p class=3D"MsoNormal">We're using WDS, and only parts of the MDT. What I d=
o is this:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/DRIVERS</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/<class>-<vendor>[-item]-<version></s=
pan><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
e.g. /video-nvidia-verde-295.73</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/audio-sigmatel-stac93xx-5.0.1403</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/<a href=3D"http://DRIVERS.PE">DRIVERS.PE</a></span><o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/chipset-intel-10.3.1019</span><o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/lan-intel-16.8</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/storage-intel-matrix-9.6</span><o:p></o=
:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Using this method, I can add the entire '<a href=3D"=
http://DRIVERS.PE">DRIVERS.PE</a>' folder recursively to the boot images/ut=
ility disks, while the all-inclusive DRIVERS folder gets slipstreamed into =
the images themselves. We pushed hard
to only build x64 images going forward, so I don't have to worry about tha=
t. If you're doing x86 AND x64, you probably want to have two separate=
DRIVERS hierarchies:<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class=3D"MsoNormal">/DRIVERS<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"> /x86<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"> /PEx86<o:p></o:p>=
</p>
</div>
<div>
<p class=3D"MsoNormal"> /x64<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"> =
/PEx64<br clear=3D"all">
<br>
- Marc Doughty<br>
"If you aren't sure who is the give-way vessel, you are the give-way v=
essel."<br>
<br>
<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On Fri, Mar 30, 2012 at 9:08 AM, Umansky, Shawn <=
<a href=3D"mailto:SUmansky@smcvt.edu">SUmansky@smcvt.edu</a>> wrote:<o:p=
></o:p></p>
<p class=3D"MsoNormal">Has anyone found a preferable way to manage/organize=
their hardware drivers in MDT (i.e., folders based on hardware model, etc.=
)? I know it's somewhat personal preference, but am curious to learn =
how others handle this (and why it works
for them). Any advice is welcome.<br>
<br>
Thanks,<br>
Shawn<br>
<br>
Shawn L. Umansky<br>
Network Engineer<br>
Saint Michael's College<br>
Phone: <a href=3D"tel:%28802%29%20654-2763">(802) 654-2763</a><br>
<a href=3D"mailto:SUmansky@smcvt.edu">SUmansky@smcvt.edu</a><br>
<br>
___________________________________________________<br>
You are subscribed to the ResNet-L mailing list.<br>
<br>
To subscribe, unsubscribe or search the archives,<br>
go to <a href=3D"http://LISTSERV.ND.EDU/archives/resnet-l.html" target=3D"_=
blank">http://LISTSERV.ND.EDU/archives/resnet-l.html</a><br>
___________________________________________________<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
<p class=3D"MsoNormal">___________________________________________________ =
You are subscribed to the ResNet-L mailing list.
<o:p></o:p></p>
<p>To subscribe, unsubscribe or search the archives, go to <a href=3D"http:=
//LISTSERV.ND.EDU/archives/resnet-l.html">
http://LISTSERV.ND.EDU/archives/resnet-l.html</a> _________________________=
__________________________
<o:p></o:p></p>
</div>
</body>
</html>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--_000_E9F8CA088AE7B645B6A412B2F7133AAA2BC7086ASMCEXMBX02miken_--
