I have always liked Microsoft BitLocker Administration and Monitoring(MABM) as it provides us with additional functionality compared to saving the BitLocker recovery key in Active Directory. MBAM brings us for example: – Protection against accidental deletion of AD computer object (Separate DB) – Key rotation – Self-Service – Role based access to Recovery Keys – Compliance reporting – Escrowing TPM Password Hash ..and more.
MBAM was integrated in Configuration Manager and first released in 1910 and has been improved in every release after that. Where the latest addition is support for Enhanced HTTP and CMG to escrow the recovery key which is awesome! To enable BitLocker during OSD when using MBAM Standalone we used the script “Invoke-MbamClientDeployment.ps1” after first installing the MBAM client during OSD. The script then escrowed the recovery key and if present the TPM Password Hash to the MBAM Webservice and all was well.
When MBAM was integrated into MEMCM many of us still used the same script / solution to enable BitLocker during OS deployment as the WebService/DB tables used by MBAM was basically just added to Configuration Manager.
However in MEMCM 2103 this all changed after supportcase it turned out that using the script (and I would assume GPO) creates extra policies and drastically impact performance. From the KB article: “Using the Invoke-MbamClientDeployment.ps1 PowerShell script or alternative methods that utilize the MBAM Agent API to escrow recovery keys to a Management Point in Configuration Manager current branch, version 2103 generates a large amount of policy targeted to all devices which can cause policy storms. This leads to severe degradation of performance in Configuration Manager, primarily with SQL and Management Points.”
More information can be found here: https://docs.microsoft.com/en-us/mem/configmgr/hotfix/2103/10372804 If you have used the script or MBAM GPO pointing the MBAM client to MEMCM I would run the script in the KB article above to check if you are impacted, if so you need to create a support ticket to get help to fix it. In one of my lab environments I have one entry as shown in the sample output below:
The CM Update KB10372804 and later versions of MEMCM contains a fix to make sure that these policies are not created. It does not clear up already existing that is why a support call is needed to clean up the already created policies.
Docs now also has a clear statement the using the “Invoke-MbamClientDeployment.ps1” together with MEMCM 2103 and later is not supported. Even if the issue is fixed I would not use the script anyway as it clearly states “Not Supported”
What options do we have then to enable BitLocker during OSD to save them in MEMCM? – Do not enable BitLocker during OSD but let the Configuration Manager client handle it after OSD ( many security departments would not approve) – Enable BitLocker and don’t save the Recovery Key during OSD and then let the MEMCM client manage it(I would not go down that road either) – Enable BitLocker and save the registry key in Active Directory using the builtin-steps in the Task Sequence to then later let the MEMCM client escrow it to the Configuration Manager DB.
Here are some sample steps, really simple in the Task Sequence, Important is to use the same Encryption Algorithm in both steps in the Task Sequence as in the BitLocker Policy in Configuration Manager.
Pre-Provision BitLocker :
What about the TPM Password Hash? Well it has been tricky to get it to escrow as it since Windows 10 1607 it is no longer available from within Windows. We can no longer store TPM Password hash anymore even if it exists in a Task Sequence variable if TPM Ownership is taken during OSD. More information can be found here: https://ccmexec.com/2016/11/mbam-tpm-password-hash-and-windows-10-1607/
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.