![]() ![]() nothing personal), and tried starting from scratch, but it still errored out. I did a jamf removeFramework (and also a find script ((find / -name *jamf* -exec rm -r )) to remove anything with the name jamf attached. So, I tried to jamf enroll, but was given the same CRUD error there. 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. QuickAdd package runs into the same problem, as does 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. 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. 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'd like to echo that we're having the exact same problem here. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |