I've seen this before in the past and if I recall (but please don't hold me to this because it was while ago) deleting the configuration for the image and then recreating it and checking the box that reads "ensure AppleSetupDone exists" should fix the issue. If not let us know.
Thanks,
Tom
Are you talking about deleting the configuration in Casper Admin and recreating it? I can't see anywhere that refers to AppleSetupDone?
I believe it is in the auto run data, and if the box labeled "show setup assistant after reboot" is checked it will not delete the /var/db/.AppleSetupDone file and thus you will get that after imaging.
Check a machine's auto run data that has the issue. Is that box checked? If you delete the auto run data and recreate it, does it fix the issue? I have seen this issue in the past with upgrading the JSS some of the auto run data did not migrate properly when the database gets updated.
If this isn't the case and you still cannot fix the issue then let's get a support ticket on it. If it does fix the issue please post back so others that have the same issue can search JAMF Nation and find a solution.
Thanks,
tom
That worked thank you. So in JSS i went to the computer AutoRun Data and Advanced Tab and then ticked the "Show Setup Assistant After Reboot"
Problem solved.
I now have a Factory Restore Image of Macintosh HD and Recovery HD.
Thank you very much.
I'd like to bring this topic back from the dead for a bit more discussion.
What I would like to accomplish is to snag an image of a factory fresh device and then be able to restore it a few years later when we sell it off. Is there a nice way of accomplishing this using Casper? Will there always be "JAMF bits" left behind on the disk?
Off the top of my head i'm thinking the process would look like this:
1. Unbox the new device and right off the bat use composer to grab an Image of the Recovery HD and Macintosh HD.
2. Create a configuration containing both Recovery and Macintosh HD DMGs that will be used at a later time (Factory Restore of Macbook Pro 2011)
3. Use Casper Imaging to run that Configuration and make sure the Show Setup Assistant After Reboot is selected so that the next owner can setup their own acct etc....
I believe that method will still result in JAMF binaries getting injected....
Any suggestions?
Wouldn't it just be easier to use the existing Recovery HD to do a fresh reinstall of the OS (nuke and pave), skipping any imaging process? It won't be the OS the Mac shipped with, which may present a problem; I don't know. But I do know it would be as close to an untouched OS as you can get. No jamf binary or other stuff will get on the Mac that way.
You could use Disk Utility for the whole process and leave Casper out of the mix. Since you're not likely wanting to install anything special for a computer you are getting rid of. Disk utility will get both the recovery and boot partitions and wrap them up in one disk image file. A process such as:
1. Boot from an external hard drive or put the new computer in target disk mode and plug into another computer.
2. Launch disk utility and use it to create a new disk image of the factory-fresh never-booted hard drive.
3. Once the disk image is created, scan it for restore in disk utility.
4. Save the disk image somewhere safe for future use.
5. When the time comes to get rid of the equipment either boot from an external hard drive or put the computer in target disk mode and use disk utility to erase the hard drive (possibly doing a zero-data erase or better) and restore the image back to the computer.
Then you will have a computer that is right back to the way it was when you took it out of the box.
Ok.... Since i'm not sure if we need to sell them off with the exact version it came with I'm heading down the Disk Utility route for now.
I think i'm running into some problems due to my lack of Mac admin experience. I'm trying to work through the steps listed above and have sprinkled in a few additional steps from this resource (http://twocanoes.com/support/winclone/using-jamf-casper-suite-and-winclone-pro-to-image-a-lab-of-dual-boot-macs) so that I can see the Recovery HD partition in Disk Utility.
I have captured a DMG file via Target Disk Mode but when I go to restore it I get an error!
Restore Failure
An error (22) occurred while copying. (Invalid argument)
You don't need to make the Recovery partition visible in Disk Utility. I'm going to assume you are putting the computer you want to capture the DMG file of in target disk mode and connect it to another computer. Try the steps below, they should work for you.
1. In Disk Utility, click on the disk that is mounted in target disk mode. Not the volume but the actual disk.
2. Click the New Image button.
3. Name the file appropriately so you know what model computer it is for and when you created it and save it to the desktop.
4. Once the image has been made, you need to scan it for restore under the Images menu. To do this either click on the image listed in the sidebar to highlight it and go to the Images menu and choose Scan Image for Restore and it should start the scan process. If you didn't have the image selected just select the image from the desktop. Once it's finished scanning it should say it was successful. If it's not then something went wrong.
To restore, you choose the disk image you created as the source in Disk Utility and a the volume of the destination computer and make sure the erase destination box is checked and let it restore. Thats it. Let me know if it works for you or not.
@Hobbs155, I forgot to mention if you search Disk Utility's help for restore it will give you a nice guide on creating a disk image from a disk or folder as well as restoring a disk image to a disk. They do a pretty good job of explaining the process. Probably better than I did.
Yeah! I think i'm in business now!
Here is how others can learn from my stupidity....
When attempting to restore the captured DMG I was trying to use the actual disk as the destination. That seemed to make the most sense to me because that is what I used to make the DMG... When I used an actual Volume as the destination everything seems to work.
Thanks for walking me through this!