<HTML>
<HEAD>
<TITLE>Re: [Casper] Dumb client question</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>The JAMF binary when it reports in should use the hardware’s NIC MAC addresses to identify itself in the JSS, so it should remain unique to each machine no matter what. Unless you run into the issue of identical MAC addresses which I think someone posted about a little bit ago. =) A very unlikely thing to happen...<BR>
<BR>
We make images that do not have any of the Casper Suite components in it, those get installed to the image when the system is imaged.<BR>
<BR>
Hopefully that makes sense to your question, assuming I understood it correctly.<BR>
<BR>
Craig E<BR>
<BR>
On 7/8/09 9:23 AM, "Nichols, Jared" <<a href="jared.nichols@ll.mit.edu">jared.nichols@ll.mit.edu</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi-<BR>
<BR>
We have a monolithic image that we’re slowly moving away from. If I put the Casper client onto a machine that I then prep for snapping an image of to distribute as my main image, are there any caveats to doing so? Will a new machine that gets the image then check into the JSS as a new machine and not the machine I created the image on?<BR>
<BR>
Thanks<BR>
<BR>
j<BR>
---<BR>
Jared F. Nichols<BR>
Desktop Engineer, Infrastructure and Operations<BR>
Information Services Department<BR>
MIT Lincoln Laboratory<BR>
244 Wood Street<BR>
Lexington, Massachusetts 02420<BR>
781.981.5436 <BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>