Skip to main content
Question

MacBooks randomly becoming unmanaged

  • November 14, 2013
  • 27 replies
  • 122 views

Show first post

27 replies

Forum|alt.badge.img+26
  • Honored Contributor
  • April 28, 2016

The process isn't terribly relevant anymore, but that being said, I'll explain my logic at the time. You can still exclude MAC addresses but the problem isn't quite as acute.

It used to be that JAMF used the MAC address of the device as it's index record. So imagine if you were imaging 400 MacBook Airs and used 40 thunderbolt to Ethernet dongles to do it. Used to be that the database would report the MAC address of your imaging dongle as the MAC address of the device and each device you add would overwrite another one. Less than helpful. You would exclude the MAC address of your imaging dongle so it wouldn't report it's info to Casper. Page 440 of the Casper Admin Guide covers this particular issue.

That being said, newer versions of hardware/Casper implementations no longer rely on MAC address as an identifier...instead the UDID is used. I think this change came in Casper 9.0, BUT any existing records from before may include it.

So, these days I'm not to worried about it, but I usually take a second to exclude MAC addresses from my imaging dongles at the very least.


Forum|alt.badge.img+10
  • Contributor
  • April 28, 2016

Oh, okay thanks. Came across this article because MacBooks are suddenly becoming Unmanaged and I was trying to figure out why. I am now looking into RTrouton's auto repair process:

https://derflounder.wordpress.com/2014/04/23/caspercheck-an-auto-repair-process-for-casper-agents/

Thanks

Mark