Skip to content

Inconsistent behaviour when setting BitLocker PIN as required #37252

@GrayW

Description

@GrayW

Fleet version: 4.76.1 (customer-deebradel) | 4.77.0 (@GrayW Render)


💥  Actual behavior

When enabling Require BitLocker PIN under Disk Encryption advanced options, hosts do not behave as expected.

Behaviour 1: (deebradel and grayw)

  • Some hosts do not receive the configuration profile to enforce the PIN settings despite meeting the TPM requirements and the disk being 100% encrypted
  • The banner in self-service is present with instructions on how to set the PIN
  • There is no option to Change how the drive is unlocked at startup
Image

Behaviour 2: (deebradel only)

  • Some hosts receive the configuration profile
  • The banner in self-service is present
  • There is an option to Change how the drive is unlocked at startup
  • There is no option to set a PIN
  • deviceenroller.exe is repeatedly attempting to set the registry value to 2 (optional), rather than 1 (required)
Image Image

🛠️ To fix

TODO

🧑‍💻  Steps to reproduce

These steps:

  • Have been confirmed to consistently lead to reproduction in multiple Fleet instances.
  • Describe the workflow that led to the error, but have not yet been reproduced in multiple Fleet instances.
  1. Enable Require BitLocker PIN for a Team
  2. Sync host with Fleet

🕯️ More info (optional)

So far, this issue has only been reported by customer-deebradel. But, it is also showing inconsistencies on my test instance.

These issues were present and tested on Windows devices that had only ever enrolled to Fleet, and no other MDM services. All were clean installations. A mixture of physical and virtual machines.

Metadata

Metadata

Labels

#g-mdmMDM product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedcustomer-deebradelcustomer-susanoo~timeboxA task that is completed in a predetermined amount of time.

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions