Apparently, the issue has been resolved with v10.9 according to Jamf
Support: *"With the release of Jamf Pro 10.9.0, we were able to resolve
a number of Product Issues. I'm happy to report that a Product Issue you
reported or was attached to one of y...
Great news that 10.8 has seemingly resolved it for you @blochcw ! We are
still on 10.6.1. As @FritzsCorner has pointed out, now I am wondering it
best to wait and update to 10.9 once the dust settles (I try to avoid
being an early adopter). Thank you...
ditto @blochcw I have previously had to restart tomcat services, which
is not a desired course of action, for computers to show as eligible.
Crickets from Jamf Support at the moment.
Whoa there, pull in the reigns a bit. The challenge is with the sequence
of when these commands are hitting the device upon enrollment. I am not
convinced this is exclusively a Jamf issue. There is actually a simple
solution to this challenge that I ...
Ultimately, this issue for us appeared to correlate with Undercover
unintentionally being blocked from communicating with its server by our
web filter. As a result, I think it would trigger this behavior in an
attempt to erase the device as a securit...
