I have a policy that fires off an FV2 authenticated reboot using the built-in mechanism "Perform authenticated restart on computers with FileVault 2 enabled " under Restart Options. It worked yesterday, but my machine upgraded to 10.13.6 today, and now it does not work. The user interaction window comes up over and over again without ever rebooting. My jamf.log says (time-stamps removed for readability):
: Sending Restart command
: Attempting filevault authenticated restart.
: Error Domain=com.jamfsoftware.task.errors Code=15 "(null)"
: An Error Occurred. Unable to complete reboot command as requested.
: Exception: Restart Failed. Restart Command Unable to Run Successfully
: Regular Restart
...over and over again. Is this a new bug? Something broken by 10.13.6? This really sucks because I was just about to send this policy out to all of my users but without a FV2 Authenticated Reboot, the policy is worthless.