Creating an Account that is Enabled for FileVault Fails (High Sierra)

HNTIT
Contributor II

When I use the Local Accounts section of a Policy to create an account that is FV2 Enabled, it fails to add to FV2.

The Account gets created but has no Secure Token, which I am guessing is why.

Is there a way to update this or is this going to be a JAMF backend issue that needs fixing ?

2 REPLIES 2

MacSysAdmin
Contributor

The bug is with Apple.

See this Jamf Nation Thread

HNTIT
Contributor II

People on that thread claim the issue is fixed in 10.13.4 beta 4, and I am running a later version than that and it does not work.