Newly DEP provisioned devices 10.13.3 not enabling FV (profile based)

[myronjoffe]

Anyone else seeing an issue with 10.13.3 devices even after receiving the FV profile. End users are not being prompted to enter password?

Within Jamf Pro 10.0 console. The device is not encrypted yet it still says the enduser is a FV user and FV has yet to be enabled.

10.13.2 and below not an issue.

[thefaded]

I have also run into this issue, but only for a couple of users at this point. My workaround has been to create a local account that the user can log into and back out of, then they can log in to their own account. I haven't been able to pinpoint a cause or fix at this point, however. I am looking into the AD accounts of the couple of users it is affecting, as I built a new machine for one user and ran into the same problem on the second machine as well.

[myronjoffe]

The users can manually enable FV by going in to system preferences>security>FV and turning on. It will then ask to escrow key to mdm.

Removing then repushing the profile also works. Are machines are not bound. We’re using local account with Enterprise Connect.

Annoying that the automation of enabling FV has stopped working in 10.13.3

[myronjoffe · Accepted solution]

It was an issue with profile collision from the 10.12 FV profile. Adjusted the scope and works as expected...