Share via

Set up MDT for BitLocker

This article will show you how to configure your environment for BitLocker, the disk volume encryption built into Windows 10 Enterprise and Windows 10 Pro, using MDT. BitLocker in Windows 10 has two requirements in regard to an operating system deployment:

  • A protector, which can either be stored in the Trusted Platform Module (TPM) chip, or stored as a password. Technically, you can also use a USB stick to store the protector, but it's not a practical approach as the USB stick can be lost or stolen. We, therefore, recommend that you instead use a TPM chip and/or a password.

  • Multiple partitions on the hard drive.

To configure your environment for BitLocker, you'll need to do the following actions:

  1. Configure Active Directory for BitLocker.
  2. Download the various BitLocker scripts and tools.
  3. Configure the operating system deployment task sequence for BitLocker.
  4. Configure the rules (CustomSettings.ini) for BitLocker.


Even though it is not a BitLocker requirement, we recommend configuring BitLocker to store the recovery password in Active Directory. For more information about this feature, see Backing Up BitLocker and TPM Recovery Information to AD DS.

If you have access to Microsoft BitLocker Administration and Monitoring (MBAM), which is part of Microsoft Desktop Optimization Pack (MDOP), you have additional management features for BitLocker.

For the purposes of this article, we'll use DC01, a domain controller that is a member of the domain for the fictitious Contoso Corporation. For more information on the setup for this article, see Deploy Windows 10 with the Microsoft Deployment Toolkit.

Configure Active Directory for BitLocker

To enable BitLocker to store the recovery key and TPM information in Active Directory, you need to create a Group Policy for it in Active Directory. For this section, we're running Windows Server 2012 R2, so you don't need to extend the Schema. You do, however, need to set the appropriate permissions in Active Directory.


Depending on the Active Directory Schema version, you might need to update the Schema before you can store BitLocker information in Active Directory.

In Windows Server version from 2008 R2 and later, you have access to the BitLocker Drive Encryption Administration Utilities features, which will help you manage BitLocker. When you install the features, the BitLocker Active Directory Recovery Password Viewer is included, and it extends Active Directory Users and Computers with BitLocker Recovery information.

Screenshot of a dialog box showing BitLocker recovery information.

The BitLocker Recovery information on a computer object in the domain.

Add the BitLocker Drive Encryption Administration Utilities

The BitLocker Drive Encryption Administration Utilities are added as features via Server Manager (or Windows PowerShell):

  1. On DC01, log on as CONTOSO\Administrator, and, using Server Manager, select Add roles and features.

  2. On the Before you begin page, select Next.

  3. On the Select installation type page, select Role-based or feature-based installation, and select Next.

  4. On the Select destination server page, select and select Next.

  5. On the Select server roles page, select Next.

  6. On the Select features page, expand Remote Server Administration Tools, expand Feature Administration Tools, select the following features, and then select Next:

    1. BitLocker Drive Encryption Administration Utilities
    2. BitLocker Drive Encryption Tools
    3. BitLocker Recovery Password Viewer
  7. On the Confirm installation selections page, select Install, and then select Close.

Screenshot showing the selection of the BitLocker drive encryption administration utilities. Selecting the BitLocker Drive Encryption Administration Utilities.

Create the BitLocker Group Policy

Following these steps, you enable the backup of BitLocker and TPM recovery information to Active Directory. You also enable the policy for the TPM validation profile.

  1. On DC01, using Group Policy Management, right-click the Contoso organizational unit (OU), and select Create a GPO in this domain, and Link it here.

  2. Assign the name BitLocker Policy to the new Group Policy.

  3. Expand the Contoso OU, right-click the BitLocker Policy, and select Edit. Configure the following policy settings found under Computer Configuration > Policies > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drives

    1. Enable the Choose how BitLocker-protected operating system drives can be recovered policy, and configure the following settings:

      • Allow data recovery agent (default)
      • Save BitLocker recovery information to Active Directory Domain Services (default)
      • Don't enable BitLocker until recovery information is stored in AD DS for operating system drives
    2. Enable the Configure TPM platform validation profile for BIOS-based firmware configurations policy.

    3. Enable the Configure TPM platform validation profile for native UEFI firmware configurations policy.


If you consistently get the error:

Windows BitLocker Drive Encryption Information. The system boot information has changed since BitLocker was enabled. You must supply a BitLocker recovery password to start this system.

after encrypting a computer with BitLocker, you might have to change the various Configure TPM platform validation profile Group Policies, as well. Whether or not you need to do this will depend on the hardware you are using.

Set permissions in Active Directory for BitLocker

In addition to the Group Policy created previously, you need to configure permissions in Active Directory to be able to store the TPM recovery information. In these steps, we assume you've downloaded the Add-TPMSelfWriteACE.vbs script to C:\Setup\Scripts on DC01.

  1. On DC01, start an elevated PowerShell prompt (run as Administrator).

  2. Configure the permissions by running the following command:

    cscript.exe C:\Setup\Scripts\Add-TPMSelfWriteACE.vbs

    Screenshot of a PowerShell window that shows some script running.

    Running the Add-TPMSelfWriteACE.vbs script on DC01.

Add BIOS configuration tools from Dell, HP, and Lenovo

If you want to automate enabling the TPM chip as part of the deployment process, you need to download the vendor tools and add them to your task sequences, either directly or in a script wrapper.

Add tools from Dell

Dell Command | Configure provides a Command Line Interface and a Graphical User Interface.

Add tools from HP

The HP tools are part of HP System Software Manager. The executable file from HP is named BiosConfigUtility.exe. This utility uses a configuration file for the BIOS settings. Here's a sample command to enable TPM and set a BIOS password using the BiosConfigUtility.exe tool:

BIOSConfigUtility.EXE /SetConfig:TPMEnable.REPSET /NewAdminPassword:Password1234

And the sample content of the TPMEnable.REPSET file:

Activate Embedded Security On Next Boot
Embedded Security Activation Policy
*No prompts
F1 to Boot
Allow user to reject
Embedded Security Device Availability

Add tools from Lenovo

The Lenovo tools are a set of VBScripts available as part of the Lenovo BIOS Setup using Windows Management Instrumentation Deployment Guide. Lenovo also provides a separate download of the scripts. Here's a sample command to enable TPM using the Lenovo tools:

cscript.exe SetConfig.vbs SecurityChip Active

Configure the Windows 10 task sequence to enable BitLocker

When configuring a task sequence to run any BitLocker tool, either directly or using a custom script, it's helpful if you also add some logic to detect whether the BIOS is already configured on the machine. In the following task sequence, we're using a sample script (ZTICheckforTPM.wsf) from the Deployment Guys web page to check the status on the TPM chip. You can download this script from the Deployment Guys Blog post, Check to see if the TPM is enabled.

In the following task sequence, we added five actions:

  • Check TPM Status. Runs the ZTICheckforTPM.wsf script to determine if TPM is enabled. Depending on the status, the script will set the TPMEnabled and TPMActivated properties to either true or false.

  • Configure BIOS for TPM. Runs the vendor tools (in this case, HP, Dell, and Lenovo). To ensure this action is run only when necessary, add a condition so the action is run only when the TPM chip isn't already activated. Use the properties from the ZTICheckforTPM.wsf.


    It is common for organizations to wrap these tools in scripts to get additional logging and error handling.

  • Restart computer. Self-explanatory, reboots the computer.

  • Check TPM Status. Runs the ZTICheckforTPM.wsf script one more time.

  • Enable BitLocker. Runs the built-in action to activate BitLocker.