Thanks for that. I'd recommend leaving quick add out of the image. You can deploy it later, or use the jamf binary to manage the machine (type "jamf help recon" in the terminal).<div><br></div><div>Following the modular methodology common to both Casper and InstaDMG, I would break up your post image script into a number of smaller scripts to increase modularity. If the DNS name of your timeserver changes, you change the script that contains that command. If you stop using a timeserver, you just remove that script from your configuration or InstaDMG imaging folders.</div>
<div><br></div><div>This is just my unsolicited advice, if what you have works for you, there's nothing wrong with that.</div><div><br><br><div class="gmail_quote">On Tue, Nov 4, 2008 at 11:02 AM, Steve Wood <span dir="ltr"><<a href="mailto:swood@integerdallas.com">swood@integerdallas.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
<font face="Arial"><span style="font-size:10pt">I love InstaDMG, even though I haven't been over following the development closely. I do not add a lot to the build train, just the major updates (10.5.5 for example), the Create User package to create the 501 user, Quick Add to get the machine into Casper, the Clear Reg to clear the registration screens, and a home grown package to drop a user picture file. The only problem I've noticed with the image and Casper is that I am having problems re-naming the machine when imaging it to either a name already in Casper, or to the MAC or S/N. I have not investigated this yet, and in writing this I'm questioning the wisdom of adding the Quick Add to the image and not doing it on restart or something. I'll have to test that.<br>
<br>
On restart after imaging I have a post image script that runs to set some small things:<br>
<br>
# now set the time zone<br>
<br>
systemsetup -settimezone America/Chicago<br>
<br>
# enable network time<br>
<br>
systemsetup -setusingnetworktime on<br>
<br>
# set the time server<br>
<br>
systemsetup -setnetworktimeserver <a href="http://time.apple.com" target="_blank">time.apple.com</a><br>
<br>
# set sleep times<br>
<br>
systemsetup -setcomputersleep never<br>
<br>
systemsetup -setdisplaysleep 15<br>
<br>
# now re-run recon<br>
<br>
jamf -recon<br>
<br>
# finally, reboot<br>
<br>
shutdown -r now<br>
<br>
The script does more than that, like add another hidden user, but those are the relevant parts.<br>
<br>
I also use the images built from InstaDMG as NetBoot images. Makes life very easy.<br>
<br>
<br>
<br>
No ideas on the server side. I've never played around with automating a server build, simply because I don't have a need to mass build servers.<br>
<br>
<br>
<br>
</span><font size="4"><span style="font-size:11pt"><b>Steve Wood<br>
</b>Director of IT<br>
<font color="#FE0000"><a href="http://swood@integerdallas.com" target="_blank">swood@integerdallas.com</a><br>
</font><br>
<b>The Integer Group</b> | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201<br>
T 214.758.6813 | F 214.758.6901 | C 940.312.2475<br>
</span></font><div><div></div><div class="Wj3C7c"><span style="font-size:10pt"><br>
<br>
<br>
On 10/31/08 2:16 PM, "Miles Leacy" <<a href="http://miles.leacy@themacadmin.com" target="_blank">miles.leacy@themacadmin.com</a>> wrote:<br>
<br>
</span></div></div></font><blockquote><font face="Arial"><span style="font-size:10pt"><div><div></div><div class="Wj3C7c">This message is in two parts...<br>
<br>
For anyone using InstaDMG with the Casper suite, I'd like to hear your experiences. I like the idea of never having booted my base system before dropping it. I'm curious as to how deeply we can mesh the InstaDMG concept & methodology with the Casper tool. It seems that they should be largely compatible.<br>
<br>
Secondly, I'm trying to automate my Mac OS X Server installs. Right now, I'm just thinking through workflow conceptually.<br>
<br>
If I create a Netinstall image from the OS X Server install disc, I'll still need to get a configuration file to the machine. There's the simple Apple answer of putting the configuration file on a USB key attached to the server, but I'm looking for a more automated way that won't require me to ever see the server, just to know its serial number . I've got Casper, and I want to rebuild Xserves via my iPhone at a café while on my way to more interesting things.<br>
<br>
One thought I had was to create a traditional image at a point before going through the server setup, and include the configuration file as a separate package on top of the image. Theoretically, at first boot, the system should see a config file present and use it.<br>
<br>
If anyone has any ideas, or better yet, proven workflows, I'd love to hear about them.<br>
<br>
Thanks,<br>
Miles<br>
<br>
<br>
</div></div><hr align="CENTER" size="3" width="95%"></span></font><div class="Ih2E3d"><span style="font-size:10pt"><font face="Lucida Grande">_______________________________________________<br>
Casper mailing list<br>
<a href="http://Casper@list.jamfsoftware.com" target="_blank">Casper@list.jamfsoftware.com</a><br>
<a href="http://list.jamfsoftware.com/mailman/listinfo/casper" target="_blank">http://list.jamfsoftware.com/mailman/listinfo/casper</a><br>
</font></span></div></blockquote><span style="font-size:10pt"><font face="Lucida Grande"><br>
</font></span><font size="4"><font face="Arial"><span style="font-size:11pt"><b><br>
<br>
Steve Wood<br>
</b>Director of IT<br>
<font color="#FF0000"><a href="http://swood@integerdallas.com" target="_blank">swood@integerdallas.com</a><br>
</font><br>
<b>The Integer Group</b> | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201<br>
T 214.758.6813 | F 214.758.6901 | C 940.312.2475</span></font></font><font face="Arial"><span style="font-size:10pt"><br>
</span></font>
<br>
<br>
<hr>
--<br>
The information contained in this email transmission is solely for the addressee(s) named above and is privileged and/or confidential. If the reader of this message is not the intended recipient or the person responsible to deliver it to the intended recipient; he or she is prohibited from reading or disclosing the information contained in this transmission. Any examination, use, dissemination, distribution, or copying of this communication is strictly prohibited. Please contact us immediately by telephone for instructions if you have received this communication in error: (214) 758-6800<br>
</div>
</blockquote></div><br></div>