Tick boxes to be selected automatically upon Casper Imaging launch

I second that, it's annoying when a tech forgets to erase the drive and then complains to me about things not working properly.

Created a Feature Request.
https://jamfnation.jamfsoftware.com/featureRequest.html?id=1438

in one scenario of our imaging process the check mark for "erase" being selected wasn't needed as it was handled in the asr script that was in place, so to check it, had the same adverse affect.

@mahughe
In the FR, I'm asking to create an option to get it done not a locked down solution. Preferably in the imaging config.
So an admin can preconfigure them to be unchecked or checked from JSS.

Thanks

If they are existing in your inventory you can edit the autorun data to do this, if not, then yes...I can the FR needed and agreed with.

I made some comments in your feature request, but why doesn't the existing options for Autorun data and Prestage imaging not suffice for this?

Pre-Stage would take care of it, but only if you're actually using that feature. Given there is no real easy way to import a batch of serial #s or MAC Addresses into Casper for the purpose of Pre-Stage, I'd imagine its just extra work and key entries for something that should in fact be selectable in the Configuration itself. Probably not worth the effort in many cases.

Auto-run would also fit the bill, but only if they are existing systems. If they are new Macs, you're back to option 1, Pre-Stage, but then the same issue above applies.

We use DeployStudio here, partly for historical reasons, but also because quite frankly, Casper Imaging is lacking some advanced features that we really need. In DS, you can specify that the disk be wiped as the first order of business, so we don't have this issue. Its as simple as a tech booting up from an imaging drive, selecting only one of two DS configurations (the only possible margin for error) and hitting the Play button. The rest is fully automated. Its too difficult to recreate this workflow in Casper Imaging.

Prestage imaging supports MAC Address/Serial Number restriction though. I don't see what's going to be easier/quicker than copying the serial numbers/addresses into the scope for the prestage, having it restrict which machine gets a particular prestage configuration.

I use pre-stage for all new machine deployments and lock it down to the subnets for the teams that handle deployments. It does not automatically image but it does preconfigure Casper Imaging for them. If this scenario works for you it can be very handy. Prestage will only ever take affect on machines that are not known to Casper. Using the subnets means I never have to input MAC addresses for serial numbers. It's a bit of a hack for how Prestage was intended but it does the job.

Thanks for all your input guys. It seems like lot of work and time needs to be dedicated to maintain this simple feature.

With regards to the FR I've submitted;
PreStage or Autorun wouldn't do it for us as we need a unified solution across all machines including the existing computers and new computers. Users need to have the same experience for the imaging workflow. We are trying to simplify things here. Also if you cancel the very first imaging attempt and then you open the Casper Imaging for the second time, Prestage data wouldn't kick in.

From the users prospective, they don't need to know if the machine is already recorded in JSS or not and imaging workflow has to be a simple one for them. This will make management tasks easier.

As @mm2270 said Casper Imaging functionality needs to be revisited by JAMF for it's usability. I'm glad that most of the FR are in "Under Review" stage and hope that they will be implemented soon.

Some of the main enhancements we like to have in Casper Imaging;

1)Update Casper Imaging - Give it some LOVE
https://jamfnation.jamfsoftware.com/featureRequest.html?id=1155

2) Hide or scope configurations to specific groups
https://jamfnation.jamfsoftware.com/featureRequest.html?id=170

3) Ability to look for the first available disk instead of the target drive name(we had to run some scripts to achieve this)
https://jamfnation.jamfsoftware.com/featureRequest.html?id=61

4) Imaging logs to contain who imaged the machine.
https://jamfnation.jamfsoftware.com/featureRequest.html?id=145

5) Imaging logs to contain the configuration used for imaging and record in the inventory or able to read from an EA.
https://jamfnation.jamfsoftware.com/featureRequest.html?id=841

...........

Thank you all.