Client status shows that FileVault isn't managed (Recovery partition is missing)

Technical Articles ID: KB83473
Last Modified: 2022-10-07 04:54:18 Etc/GMT

Environment

Management of Native Encryption (MNE) - all supported Mac Operating Systems

For supported environments, see KB79375 - Supported platforms for Management of Native Encryption.

Problem 1

FileVault isn't enabled after you successfully install MNE. The status of FileVault reported at the ePolicy Orchestrator (ePO) console remains disabled.

The deployment is configured to prompt for reboot, but no system restart prompt is displayed. No logon prompt is displayed when you restart the system manually.

On the Mac client, the Encryption Status window reports the following.

FileVault Status	Status not available
Management Mode	FileVault is not managed
Encryption Status	Unable to determine status
Recovery Status	Client has not escrowed the key in ePO

At the ePO console, the status for the client shows the following error.

Information
Mode	Managed
Agent GUID
Status	Platform does not meet requirements
Model Name
Model Identifier
Serial Number
Operating system version
System Encryption Status	No encryption

Problem 2

The Native Encryption.log on the Mac OS X client records one of the following errors (depending on the version of MNE installed):

ERROR 1
MFE_MNE: PID: 1408 : ePO policy enforcement started.
MFE_MNE: PID: 1408 : ePO enforce policy - FileVault is managed (Turn On) mode is enforcing from policy.
MFE_MNE: PID: 1408 : FileVault activation will not proceed as recovery partition is not available.
MFE_MNE: PID: 1408 : Skipping policy enforcement on unsupported platform.
MFE_MNE: PID: 1408 : None of the policies will be enforced. FileVault will not be managed.
MFE_MNE: PID: 1408 : ePO policy enforcement completed.
MFE_MNE: PID: 244 : Subscribed for data channel messages.

ERROR 2

Activation failed as OS X recovery partition is not found – Event 35203

Cause

FileVault requires a valid Recovery Partition to activate.

On some newer systems, Apple uses an NVMExpress drive interface, which isn't being detected correctly for the recovery partition.

Solution 1

Confirm that you do not have a valid Recovery Partition. Then, rerun the OS X installer application on the system.

Confirm that the Recovery Partition is missing or invalid:
1. Open a Terminal Session on the client.
2. Type the following command and press Enter to view the drive configuration:
  
  diskutil list
  
  As an example, this output shows the presence of Apple_Boot Recovery HD under Type Name:
Run the Mac OS X installer app on the disk and re-create the recovery partition.

IMPORTANT: When you reinstall OS X using the OS X installer app, you do not lose your data unless you choose to delete the existing partitions or volumes on the disk.

Solution 2

If you see the same symptoms, but find that the Recovery Partition is present, take the following action:

Determine if your Mac model has the SSD drive connected via the new NVM Express bus.
Contact Technical Support and request a hotfix.

Knowledge Center

Client status shows that FileVault isn't managed (Recovery partition is missing)

Environment

Problem 1

Problem 2

Cause

Solution 1

Solution 2

Related Information

Affected Products

Languages:

Title

Title

Knowledge Center

Client status shows that FileVault isn't managed (Recovery partition is missing)

Environment

Problem 1

Problem 2

Cause

Solution 1

Solution 2

Related Information

Affected Products

Languages:

Choose your region

Title

Title