Cannot run policies on individual computer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on
09-13-2016
01:08 PM
- last edited on
03-04-2025
05:02 AM
by
kh-richa_mig
I have a user that I reconfigured a computer for that was previously in use by another employee. The employee taking over the computer did a time machine backup from her old machine, and restored it via the recovery partition, which, in turn, rolled the OS back from 10.11.6 to 10.10.5. I have not been able to get the computer to talk to the JSS since she did this. I have even gone as far as wiping the computer, removing the computer record from AD, and removing the profile from the JSS before re-imaging the computer. Still, when I try to run any policy, the progress stops at "Gathering Information."
Does anyone have any recommendations as to what can be blocking this process from running?
- Labels:
-
Jamf Pro

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-13-2016 01:13 PM
A user with enough knowledge to mess your entire day up. I always instruct the techs to just back up the user profile, I don't let the user do anything, then do a Nuke and Pave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-13-2016 01:25 PM
@CapU , we've gone that route to no avail.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-14-2016 11:21 AM
Look in Console at your logs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-18-2016 07:12 AM
@alexhberger Delete the computer from the JSS & re-enroll.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-19-2016 08:12 AM
@bentoms Already did that. An issue that did crop up the same day is the HDD failed, so that may have had some effect.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-19-2016 12:42 PM
@alexhberger right. New HDD = New UDID = Device Signature errors when contacting JSS.
Hence deleting from the JSS, removing the framework on the device, then re-enrolling.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-19-2016 12:46 PM
@bentoms Understood. I deleted from the JSS and removed the profiles and self service from the user machine prior to the HDD failure (More likely during the infant stages of the errors) and it was still having an issue. It will be reconfigured once it returns, and I will report back if I still have issues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-20-2016 01:10 AM
Hey @alexhberger
To remove the local JSS tools from a Mac, you'd need to do more than removing the profiles and self service.
When you next get your hands on the Mac:
1) Delete the computer record from your Casper Server
2) Either:
a) Complete erase and redeploy the Mac
or
b) run sudo jamf removeFramework
to completely remove the local tools
3) re-enrol using your preferred method.
Good Luck!
Darren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-20-2016 05:35 AM
@daz_wallace Awesome, thank you!
