[27516] in resnet
Re: Managing Hardware Drivers in MDT
daemon@ATHENA.MIT.EDU (Doughty, Marc)
Fri Mar 30 13:25:31 2012
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=f46d04462f16df9b0404bc791f06
Message-ID: <CAEPWjztL0WJzOwHevo+HMOg0CvhOXV4vj7kF18oLqbmNjo5xog@mail.gmail.com>
Date: Fri, 30 Mar 2012 13:25:18 -0400
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: "Doughty, Marc" <marc_doughty@brown.edu>
To: RESNET-L@listserv.nd.edu
In-Reply-To: <E9F8CA088AE7B645B6A412B2F7133AAA2BC7086A@SMCEXMBX02.mikenet.smcvt.edu>
--f46d04462f16df9b0404bc791f06
Content-Type: text/plain; charset=ISO-8859-1
We only create two images now: A 'Standard image' for desktops and laptops
and a 'Lab image'. I avoid Dell's drivers where possible and use stuff from
as far upstream as possible (Intel, NVidia, AMD, etc.) so I can cover more
hardware. We recently had a group that's not managed by central IT buy a
lab full of machines that aren't even the same brand as ours and our image
installed without a hitch.
- 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 12:29 PM, Umansky, Shawn <SUmansky@smcvt.edu> wrote:
> Thanks, Marc. That is helpful. I notice you chose not to organize by
> computer 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****
>
> /chipset-intel-10.3.1019****
>
> /lan-intel-16.8****
>
> /storage-intel-matrix-9.6****
>
> ** **
>
> Using this method, I can add the entire 'DRIVERS.PE' folder recursively
> to the boot images/utility 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 that. If you're
> doing x86 AND x64, you probably want to have two separate DRIVERS
> 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>
> 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
> somewhat 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
> 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
> 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 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 the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--f46d04462f16df9b0404bc791f06
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
We only create two images now: A 'Standard image' for desktops and =
laptops and a 'Lab image'. I avoid Dell's drivers where possibl=
e and use stuff from as far upstream as possible (Intel, NVidia, AMD, etc.)=
so I can cover more hardware. We recently had a group that's not manag=
ed by central IT buy a lab full of machines that aren't even the same b=
rand as ours and our image installed without a hitch.<br clear=3D"all">
<br>- Marc Doughty<br>"If you aren't sure who is the give-way vess=
el, you are the give-way vessel."<br>
<br><br><div class=3D"gmail_quote">On Fri, Mar 30, 2012 at 12:29 PM, Umansk=
y, Shawn <span dir=3D"ltr"><<a href=3D"mailto:SUmansky@smcvt.edu">SUmans=
ky@smcvt.edu</a>></span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1f497d">Thanks, Marc.=A0 That is =
helpful.=A0 I notice you chose not to organize by computer hardware model.=
=A0 Did you find that to be unnecessary?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:"Ca=
libri","sans-serif";color:#1f497d"><u></u>=A0<u></u></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:<a href=3D"mailto:RESNET-L@LISTSERV.ND.EDU" target=3D"_blank">=
RESNET-L@LISTSERV.ND.EDU</a>]
<b>On Behalf Of </b>Doughty, Marc<br>
<b>Sent:</b> Friday, March 30, 2012 10:13 AM<br>
<b>To:</b> <a href=3D"mailto:RESNET-L@LISTSERV.ND.EDU" target=3D"_blank">RE=
SNET-L@LISTSERV.ND.EDU</a><br>
<b>Subject:</b> Re: Managing Hardware Drivers in MDT<u></u><u></u></span></=
p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<p class=3D"MsoNormal">We're using WDS, and only parts of the MDT. What=
I do is this:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
/DRIVERS</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
=A0 =A0 =A0/<class>-<vendor>[-item]-<version></span><u></=
u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
e.g. /video-nvidia-verde-295.73</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
=A0 =A0 =A0/audio-sigmatel-stac93xx-5.0.1403</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
=A0 =A0 =A0/<a href=3D"http://DRIVERS.PE" target=3D"_blank">DRIVERS.PE</a><=
/span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
=A0 =A0 =A0 =A0 =A0 /chipset-intel-10.3.1019</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
=A0 =A0 =A0 =A0 =A0 /lan-intel-16.8</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:"Courier New"">=
=A0 =A0 =A0 =A0 =A0 /storage-intel-matrix-9.6</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Using this method, I can add the entire '<a href=
=3D"http://DRIVERS.PE" target=3D"_blank">DRIVERS.PE</a>' folder recursi=
vely to the boot images/utility disks, while the all-inclusive DRIVERS fold=
er 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=A0sep=
arate=A0DRIVERS hierarchies:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">/DRIVERS<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0/x86<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0 =A0 =A0 /PEx86<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=A0 =A0 =A0/x64<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">=A0 =A0 =A0 =A0 =A0 /=
PEx64<br clear=3D"all">
<br>
- Marc Doughty<br>
"If you aren't sure who is the give-way vessel, you are the give-w=
ay vessel."<br>
<br>
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Fri, Mar 30, 2012 at 9:08 AM, Umansky, Shawn <=
<a href=3D"mailto:SUmansky@smcvt.edu" target=3D"_blank">SUmansky@smcvt.edu<=
/a>> wrote:<u></u><u></u></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.=
)? =A0I know it's somewhat personal preference, but am curious to learn=
how others handle this (and why it works
for them). =A0Any 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" target=3D"_blank">(802) 654-276=
3</a><br>
<a href=3D"mailto:SUmansky@smcvt.edu" target=3D"_blank">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>
___________________________________________________<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
</div>
<p class=3D"MsoNormal">___________________________________________________ =
You are subscribed to the ResNet-L mailing list.
<u></u><u></u></p>
<p>To subscribe, unsubscribe or search the archives, 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> _________________________=
__________________________
<u></u><u></u></p>
</div></div></div>
</div><div class=3D"HOEnZb"><div class=3D"h5">
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
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>
___________________________________________________
</p></div></div></blockquote></div><br>
___________________________________________________
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
___________________________________________________
--f46d04462f16df9b0404bc791f06--
