Can someone tell me what I'm doing wrong with Imaging?

Is the Base Image set to install on first boot?

Are you using the same distribution point? The one thing I forget sometimes when my testing goes wrong is that I have multiple distribution points and I need to replicate them.

I don't see an option for installing base image on first boot. I have boot to target drive after imaging checked though.

Only have one distribution point set to the JSS.

I did another run with PreStage imaging and it seemed to take it. I will probably delete the configuration and start over since the PreStage used the DMG directly.

This computer is now bound to our Active Directory, but the login screen still shows users instead of being set to name and password no matter how many times I change it, and allow network users wasn't checked either.. Is there a good resource of commands to change settings like this that I might be able to make a script to do these after the first reboot?

<double post>

On the actual Information for the package it is NOT necessary to check the box "Item is a DMG with an OS X Installer, or Adobe Update/Installer for CS3 or CS4"
Here's pics of how my base image is configured.

This is in my standard config

My Recovery Config just has the Recovery Partition:

Setup like this:

You mention that you are trying to update from 10.7 to 10.9. Are you wanting to do an install in place, an upgrade, or are you wanting to wipe the systems and install a fresh copy of 10.9?

If you simply want to update to 10.9, look on the forum for info on upgrading to Mavericks, and possibly check out the video on the session on it:

https://jamfnation.jamfsoftware.com/jnucEvent.html?eventId=44

And the video:

http://goo.gl/ibPGGP

You can setup a Self Service item to allow your users to upgrade themselves. This method should maintain any AD binding you currently have in place, and any other settings.

It sounds like the problem you're having might have to do with the system you built the image on. You may not have the proper boot loaders for the hardware you're deploying to, and this would happen if you were building on an older machine and deploying to a new.

Look at using AutoDMG from Per Olofsson: https://github.com/MagerValp/AutoDMG Using AutoDMG will give you an image you can deploy that has never been booted. That means that you shouldn't have to worry about new or old hardware, as long as the hardware can run Mavericks.

HTH

Thanks for the screenshots rderewianko, my settings are the same.

Stevewood, I'd like to build an image to do a clean install of Mavericks on our machines. I am building on one Macbook Pro and deploying to another one that is the same model. I was considering just doing an upgrade after setting up a policy to cache the install, but I'd like to have a fresh image so I can refresh everything over the summer.

Do you get the folder with question mark when you try to netboot or after imaging? If it is at net boot, you will need to update your netboot image to a version of OS X that is compatible with your mac device. I just had to update my netboot image to allow the new 2013 MBA's to boot over the network. Just a thought.....

It was after imaging. Netboot still works ok so I am able to recover it after the bad image. We're using Mid 2012 13" MBP.

Some new hardware was released that forked Mavericks, I'm assuming there's still the machine specific vs agnostic version issue?

@stevewood][/url wrote:

Look at using AutoDMG from Per Olofsson: https://github.com/MagerValp/AutoDMG Using AutoDMG will give you an image you can deploy that has never been booted. That means that you shouldn't have to worry about new or old hardware, as long as the hardware can run Mavericks.

What version of Casper Suite are you using? I think you need 9.1.2 or 9.2 to support Mavericks.

I think 8.73 supports Mavericks to some extent, but 9.2 is required for full compatibility.