+1Hello,
we applied a FileVault policy, and it worked on every MacBook except one. We’re not receiving the FileVault key from that device, and the user keeps getting the policy pushed repeatedly.
I also made the policy available in Self Service, but even from there it doesn’t work.
What could be causing this issue?
+25
+26Dont use the policy to enable filevault, it uses the fdesetup command which is deprecated (still technically functions and is fine for local troubleshooting but dont build standards around using it). You should be using a configuration profile to enable filevault.
If using a configuration profile still fails to enable filevault, check the network configuration for the network the device is on as if it cant write the key back to Jamf it will fail to encrypt.
+1
It appears both policies/configuration profiles are currently active. I will proceed with deactivating the redundant policy. I can see the MacBook listed in the configuration profile, but we do not possess the recovery key.
However, we have verified within the user's settings that FileVault is enabled, but nobody has the key.
+1
+25
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.