-
Notifications
You must be signed in to change notification settings - Fork 836
Inconsistent behaviour when setting BitLocker PIN as required #37252
Copy link
Copy link
Closed
Labels
#g-mdmMDM product groupMDM product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documentedcustomer-deebradelcustomer-susanoo~timeboxA task that is completed in a predetermined amount of time.A task that is completed in a predetermined amount of time.
Metadata
Metadata
Assignees
Labels
#g-mdmMDM product groupMDM product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documentedcustomer-deebradelcustomer-susanoo~timeboxA task that is completed in a predetermined amount of time.A task that is completed in a predetermined amount of time.
Type
Projects
Status
Done
Fleet version:
4.76.1(customer-deebradel) |4.77.0(@GrayW Render)💥 Actual behavior
When enabling
Require BitLocker PINunder Disk Encryption advanced options, hosts do not behave as expected.Behaviour 1: (
deebradelandgrayw)Change how the drive is unlocked at startupBehaviour 2: (
deebradelonly)Change how the drive is unlocked at startup🛠️ To fix
TODO
🧑💻 Steps to reproduce
These steps:
🕯️ 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.