Error instslling MDM Profile on One Mac

musat
Contributor III

Hello,
I have one Mac sitting on my desk that is getting an error installing the MDM profile. I have reimaged the Mac several times and the MDM profile never gets installed. When I run `jamf mdm` or `jamf manage` I get this message:

Error installing the computer level mdm profile: profiles install for file: '/Library/Application Support/JAMF/tmp/mdm.mobileconfig' and user:'(null)' returned -915 (Unable to contact the SCEP server at "https://jss-01.ccsd93.com:8443//CA/SCEP".)
Problem installing MDM profile

We don't have anything in the SCEP URL in the Global Settings. And this is only on this single Mac. All other Macs enroll and re-enroll without any issues. And, of course, since the MDM profile isn't getting installed, none of the other profiles are getting installed.

Any ideas?

Tim

3 REPLIES 3

davidacland
Honored Contributor II

Hi,

Is it a clean (never booted) image or does it have some customisations?

Another possibility is that there is a problem with the record in Casper. I would try deleting it completely, re-imaging the Mac and then re-enrolling.

Last thought is firewall related. I assume the mac is on the same network / VLAN as the working Macs?

musat
Contributor III

Yep, clean image that we've been building off of for a year or so (still Mavericks.)

I've tried deleting the record, but I'll try that again.

Yeah, all on the same internal network, verified that the Mac firewall is off. I'm imaging this one at my desk using the drop I have there for testing, that I use frequently for imaging. I took another Mac and reimaged it there just to make sure that worked, and it imaged and enrolled without issues.

I'll try deleting the Mac in our JSS and wiping the drive again before imaging.

Tim

musat
Contributor III

Ok, so I deleted the Mac from our JSS, and then erased the drive using Disk Utility, and then imaged the Mac. After doing that, everything installed and enrolled properly. I know I had deleted the Mac from the JSS before, but I had never erased the drive separately from the imaging process, which erases the drive.

Anyway, at least it's working again, so the child will be happy.