<html><head><style media="all" type="text/css">         #sig {                 font:12px Arial, Helvetica, sans-serif;                 line-height: 13px;                 color: #4c4c4c ;                 margin: 6px 0;                 padding: 6px;         }         #sig .row a:link, #sig .row a:visited {                 color: #d02d33;                 text-decoration: none;         }         #sig .row a:hover {                 color: #4c4c4c;         } </style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I'll have to dig around for the information, but you could manage your network interfaces using shell scripts that run after imaging the system. &nbsp;Again, I use InstaDMG for my base image, that way the image is never booted until it is laid onto the system. &nbsp;Once you have the image on the machine, then push your preference changes to the system. &nbsp;You may even be able to capture the settings using Composer and push those plist files to the system.<div><br></div><div>Just makes it cleaner, in my opinion.</div><div><br></div><div>Just my 2 pennies.<br><div>  <div><div id="sig">         <div class="row"><br>        <strong>Steve Wood</strong>        <br>        Director, Information Technology        <br>        <a href="mailto:swood@integerdallas.com">swood@integerdallas.com</a>        <br><br>        The Integer Group  |  1999 Bryan St.  |  Ste. 1700  |  Dallas, TX 75201        <br>        T 214.758.6813  |  F 214.758.6907  |  C 940.312.2475        <br>    <br>        <img src="http://extranet.integerdallas.com/Integer/signature/green.jpg">             <br><br>         </div> </div></div> </div><br><div><div>On May 13, 2008, at 12:25 PM, Nicometo, Tim S. wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div> <font size="4"><font face="Lucida Grande"><span style="font-size:11pt">Thanks Craig (again). &nbsp;I like this part of your post...<br> <br> I think I will try this, test and see how it goes.<br> <br> tim<br> <br> <br> On 5/13/08 11:32 AM, "Ernst, Craig S." &lt;<a href="mailto:ERNSTCS@uwec.edu">ERNSTCS@uwec.edu</a>> wrote:<br> <br> </span></font></font><blockquote type="cite"><font size="4"><span style="font-size:11pt"><font face="Verdana, Helvetica, Arial">I include all the required settings for our private network in the AirPort, but I turn Off the AirPort interface when I’m done configuring it before creating the image.<br> </font></span></font></blockquote><font size="4"><span style="font-size:11pt"><font face="Verdana, Helvetica, Arial"><br> </font><font face="Lucida Grande">-- <br> Tim Nicometo<br> Mayo Clinic<br> <a href="mailto:timn@mayo.edu">timn@mayo.edu</a><br> (507) 255-3034<br> </font></span></font> </div>  _______________________________________________<br>Casper mailing list<br><a href="mailto:Casper@list.jamfsoftware.com">Casper@list.jamfsoftware.com</a><br><a href="http://list.jamfsoftware.com/mailman/listinfo/casper">http://list.jamfsoftware.com/mailman/listinfo/casper</a><br></blockquote></div><br></div><BR />
<BR />
<HR />
--<BR />
The&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;email&nbsp;transmission&nbsp;is&nbsp;solely&nbsp;for&nbsp;the&nbsp;addressee(s)&nbsp;named&nbsp;above&nbsp;and&nbsp;is&nbsp;privileged&nbsp;and/or&nbsp;confidential.&nbsp;&nbsp;If&nbsp;the&nbsp;reader&nbsp;of&nbsp;this&nbsp;message&nbsp;is&nbsp;not&nbsp;the&nbsp;intended&nbsp;recipient&nbsp;or&nbsp;the&nbsp;person&nbsp;responsible&nbsp;to&nbsp;deliver&nbsp;it&nbsp;to&nbsp;the&nbsp;intended&nbsp;recipient;&nbsp;he&nbsp;or&nbsp;she&nbsp;is&nbsp;prohibited&nbsp;from&nbsp;reading&nbsp;or&nbsp;disclosing&nbsp;the&nbsp;information&nbsp;contained&nbsp;in&nbsp;this&nbsp;transmission.&nbsp;&nbsp;Any&nbsp;examination,&nbsp;use,&nbsp;dissemination,&nbsp;distribution,&nbsp;or&nbsp;copying&nbsp;of&nbsp;this&nbsp;communication&nbsp;is&nbsp;strictly&nbsp;prohibited.&nbsp;&nbsp;Please&nbsp;contact&nbsp;us&nbsp;immediately&nbsp;by&nbsp;telephone&nbsp;for&nbsp;instructions&nbsp;if&nbsp;you&nbsp;have&nbsp;received&nbsp;this&nbsp;communication&nbsp;in&nbsp;error:&nbsp;(214)&nbsp;758-6800<BR />
</body></html>