Configuration scripting..

[sggr57a]

Does anyone know of a way to reference the current parent/smart configuration images being used through bash?

[wlcasey]

I dont know how everyone else is doing this, but I leave a "breadcrumb." I have heard that people sometimes stick a directory in /Library and call it something like /Library/<my organization>/image. Then I put in anything related to the imaging process (date, version, etc) into text files in there. Then you can read those files via script. You can hide the directory if you care to as well, but then you have to have a good memory. ;-)

Wayne

[mm2270]

Yeah, unless you plan ahead and drop some kind of file/folder/plist. etc on your Macs during imaging, you're not going to have any luck really tracking that later. Even the Casper Imaging log doesn't record the config that was used, although it will list all the pkgs installed, so that may help with differentiation. I see this as a flaw personally. I think it should be stored somewhere within the Casper Suite db so it can be picked up in a search later.

[sggr57a]

Thanks to both of you for your ideas! I think we'll use a text file dropped into /private/var/tmp/ for later reference as our breadcrumb if/when we revisit the issue.

[jeffs]

I've found the concept of dummy receipts to be very helpful as well. Here are two good blog posts about using them with imaging configurations and reporting on them with extension attributes:

http://www.kitzy.org/blog/2013/9/26/the-art-of-the-dummy-receipt
http://www.kitzy.org/blog/2013/10/5/making-smarter-dummy-receipts-with-plists

[sggr57a]

That's a great idea too. Thanks for sending info!

[garryfresh]

Hello,

We include an image tag in /private/etc/company_name/info. then we use post image 1st boot scripts to timestamp the image and JSS extended attributes to read things like the image version, imaging date etc...

Please contact me directly if you'd like additional detail or examples.

Garry