Computer enrollment is not occuring and ends with an error

Hi @khurram

What happens if you try to enrol this computer from the https://jamfservername:8443/enroll url? Do you get an error?

@stevevalle
Hi,
Even this process let you download QuickAdd package. I tried it anyway but same error occurred.

@khurram - try a sudo jamf removeFramework. If the computer entry is in Casper, remove it also. Then recon.

on terminal, its not recognizing "jamf" commands because this computer was never managed. JSS have No traces of this computer I tried using S. No., mac Address and name.

Are you able to re-image the machine?

I'd like to echo that we're having the exact same problem here. Something stalls out during the imaging process, because the printers also never get installed, in addition to no computer entry in the JSS being created. I saw in another post that someone suggested unchecking the box to collect printer inventory to get around that "CRUD" error in v.9.X, but that didn't do the trick for us. QuickAdd package runs into the same problem, as does Recon.

@khurram, what's the OS of the machine you're having problems with? These are 10.6.8 laptops we're trying to image here (with a slightly older version of Casper Imaging to get around the new restriction), and the JAMF binary actually looks like it gets installed. But, when I try to jamf manage/recon/policy, I get the familiar "Device Signature Error" that indicates a machine can't talk to the JSS and needs to be re-enrolled. So, I tried to jamf enroll, but was given the same CRUD error there. I did a jamf removeFramework (and also a find script ((find / -name *jamf* -exec rm -r {} ;)) to remove anything with the name jamf attached... nothing personal), and tried starting from scratch, but it still errored out.

We just updated to 9.5.2 a couple of days ago, so I have to imagine it's related to this, and possibly the dropped support of 10.6.8, which doesn't bode well for us since we have 2,500+ still running district-wide.

@stevevalle
oh, I think we re-imaged machine 3 - 4 times with different combinations.

@NoahRJ
Target Machine - 10.9.4 (we bought in lot, this machine's other peers have embraced JSS)
Hardware - Mid 2011
JSS - 9.31

Just came across another computer that is presenting with the same CRUDdy error. Tried unchecking all computer inventory collection boxes in case that was hanging it up, but still can't get it enrolled.

Any new developments on your end, @khurram?

This problem is not solved yet. I considered this machine as faulty and sent it to our supplier. We have also purchased the Casper from the same supplier so it makes sense sending it to them rather sending it to Apple. I had a phone call from the supplier andI talked to a technician and gave him the QuickAdd.pkg file and explained him the problem and never heard from them since then. I thin this is a macbook problem and they are going to replace it. @NoahRJJ this is the case where jss is not installing on the macbook at all. We had another mac where jss will install but MDM profiles will nit install, in this case the macbook's serial number was missing from the macbook.

Thought I would update that we got this solved (for @khurram or anyone else who runs across a similar issue). I spent some time in the MySQL database with a support specialist from JAMF and we determined there were orphaned records of the affected computers in the computers table, but not in the computers_denormalized table, which stopped those machines from successfully enrolling since records containing their UDID already existed somewhere in the database. Below are the commands used to 1. reveal the orphaned computer records and 2. delete them:

1. ``` select computer_id from computers_denormalized where computer_id not in (select computer_id from computers);

   2. ```
   delete from computers where computer_id not in (select computer_id from computers_denormalized);

If any orphaned records do show up after you run the first command, you'll want to take a screenshot or copy that text, since after you delete the orphaned records and exit the session, there will be no way to see which computers have been affected.

Command 1 didn't produce any results for me but I was able to tweak command 2 to reveal those Macs that we knew were causing this issue. See other command that may reveal issue.

select computer_id from computers where computer_id not in (select computer_id from computers_denormalized);

See my response here for partial solution.

https://jamfnation.jamfsoftware.com/discussion.html?id=8225#responseChild88085