- Jamf Nation Community
- Products
- Jamf Pro
- Re: Mac Mini keeps showing up as unmanaged after e...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-10-2014 08:35 AM
Mac Mini keeps showing up as unmanaged after enrolling it. I cant push any policies to it. I have removed it and enrolled it again, still running into the same issue..
Thanks
Solved! Go to Solution.
2 ACCEPTED SOLUTIONS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-10-2014 12:31 PM
Just to clarify: It is showing up as unmanaged when you log into it and run "jamf checkJSSConnection"? What, if anything, shows up in /var/log/jamf.log?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-10-2014 11:08 PM
It happens to me also, I solve it by run sudo jamf removeFramwork and re-enrol again.
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-10-2014 12:31 PM
Just to clarify: It is showing up as unmanaged when you log into it and run "jamf checkJSSConnection"? What, if anything, shows up in /var/log/jamf.log?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-10-2014 12:49 PM
I rebooted the casper server and re-enrolled the mini, it finally says its managed now by our system.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 09-10-2014 11:08 PM
It happens to me also, I solve it by run sudo jamf removeFramwork and re-enrol again.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-04-2015 08:33 AM
This can happen if you have a version mismatch between the jamf binary and the JSS. Ensure you're deploying using the same version of the tools as the JSS.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-04-2015 11:49 AM
In some cases (i.e. issues with Casper Imaging 9.63 and 9.64) it may be necessary to image/enroll with a newer version of the JAMF binary (i.e. 9.65 embedded in Casper Imaging 9.65), which will be downgraded at the next time the client checks in with the JSS (currently at 9.63 for many of my clients). Haven't run into an issue with devices being unmanaged.
Perhaps the issue occurs when enrolling with an older binary to a newer JSS...
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 03-17-2015 07:32 AM
I am having the same issue.
- Mac Mini (Late 2014)
- 9.3 JSS
- 9.65 Casper Imaging
- Yosemite (10.10.2)
I'm willing to bet its a combination of the difference in JSS version / Casper Suite products, or the fact that I'm running Yosemite on an older JAMF binary. I tried the remove framework and re-enroll and that didn't seem to do the trick for me.
CheckJSSConnection reported fine for me.
I am going to upgrade my JSS later this week and see if that does the trick.
