Got a Error while opening JAMF imaging on Big Sur

jun_zhang
New Contributor II

I'm trying to run JAMF imaging on Big Sur to image a new Mac but JAMF imaging can not start up and give me an error message.
"An exception of class NilObjectException was not handled. The application must shut down"

The version of my JAMF imaging is newest, the Big Sur version is 11.2. Does anyone have solution to solve this?

3 ACCEPTED SOLUTIONS

m_entholzner
Contributor III
Contributor III

Well, yes. Don't use imaging, because imaging is REALLY dead...

http://isimagingdead.com

View solution in original post

talkingmoose
Moderator
Moderator

Also, Jamf doesn't recommend using Jamf Imaging beyond macOS High Sierra 10.13. See the disclsimer at the top of this page.

https://www.jamf.com/jamf-nation/articles/313/creating-a-minimal-base-os-image

View solution in original post

Chris_Hafner
Valued Contributor II

@jun.zhang Is there any reason you are still imaging? I can replicate your issue but you should run away screaming if there isn't a super solid crazy reason to (perhaps there is?). But it's going to be a fight against all odds. Trust me, I was an imaging diehard until a few years ago. DEP and other enrollments can accomplish the same tasks, though slower, but MUCH more reliably than any of the existing imaging "hacks" I hear of.

View solution in original post

8 REPLIES 8

m_entholzner
Contributor III
Contributor III

Well, yes. Don't use imaging, because imaging is REALLY dead...

http://isimagingdead.com

Jamf imaging isn't just for monolithic imaging!!!! We use this all the time to install software on top of Fresh OS installs on which recon has not been run. We use multiple partitions. What is the alternative?

talkingmoose
Moderator
Moderator

Also, Jamf doesn't recommend using Jamf Imaging beyond macOS High Sierra 10.13. See the disclsimer at the top of this page.

https://www.jamf.com/jamf-nation/articles/313/creating-a-minimal-base-os-image

Chris_Hafner
Valued Contributor II

@jun.zhang Is there any reason you are still imaging? I can replicate your issue but you should run away screaming if there isn't a super solid crazy reason to (perhaps there is?). But it's going to be a fight against all odds. Trust me, I was an imaging diehard until a few years ago. DEP and other enrollments can accomplish the same tasks, though slower, but MUCH more reliably than any of the existing imaging "hacks" I hear of.

What if you don't have the option for DEP? What if you don't have time for slow? What if you have a slooow network and you use Jamf imaging to install configurations (not complied obviously) on top of a base os with scripts that pull part of the installs from locally attached storage? What if you've found this works MUCH MORE reliably?

TSOAFTVPPC
Contributor

I am having the same issue and quite irritated by the snarky responses!!! Not at all professional! Jamf imaging isn't just for Monolithic imaging. Please recommend a solution for those of us for whom DEP is NOT an option. Recon isn't working either.

TSOAFTVPPC
Contributor

Even after manually enrolling we fin=d the alternatives don't work. What is the alternative? You can't even roll out a configuration as a policy! Tell me snarky genius what are people with huge payloads 70-80 GB min supposed to do? Jamf imaging used work PERFECTLY to get a lab up and running within 20 minutes or so.

 

cpenna
New Contributor

@TSOAFTVPPC I can relate. imaging does have a purpose. In our case thin provisioning is very handy when DEP is not viable. We use it for thin provisioning over pre-existing macOS. In the scenario I wanted it for today, I have a pre-existing mac that I wanted to make a Catalina partition so I can test Catalina to Monterey update without grabbing yet another mac onto the workbench. DEP will fight at AD Binding as serial number will already be in use then trust relationship can break.