So you open . You right-click the computer object. You look at the tabs: General, Operating System, Member Of, Delegation . Nothing says “Keys.”
Imagine you’re a system administrator. A user’s laptop is dead—motherboard fried, SSD ripped out of its original home. The data is critical. The drive is sealed with 128-bit or 256-bit AES encryption. Without the key, that SSD is a $50 paperweight.
Instead, Active Directory treats each BitLocker recovery key as a linked to the computer. The object class is called msFVE-RecoveryInformation (FVE = Full Volume Encryption, Microsoft’s internal code name for BitLocker). where is bitlocker key stored in active directory
If you query the computer’s distinguished name in (the low-level LDAP editor), you’ll see:
You dig deeper. You open . You scroll past cn , objectClass , operatingSystem . Still nothing obvious. So you open
Where is it? The key isn’t stored in a simple text field on the computer object. That would be too easy—and too dangerous.
That key package is stored in the same msFVE-RecoveryInformation object, right next to the password—silent, invisible, and potentially the last hope for forensic recovery. So, where is the BitLocker key stored in Active Directory? Nothing says “Keys
Get-ADObject -Filter objectClass -eq 'msFVE-RecoveryInformation' -SearchBase "OU=Workstations,DC=contoso,DC=com" -Properties msFVE-RecoveryPassword, msFVE-VolumeGuid | Where-Object $_.DistinguishedName -like "*CN=ProblemPC*" Or, for a specific computer: