Here's a high level overview of the steps required:
- Check TPM status
- Enable & activate TPM if needed
- Take ownership of TPM
- Create Bitlocker recovery password
- Backup recovery password to Active Directory
- Enable Bitlocker using the TPM as the key protector
In order to do this, the server must have a TPM module installed. Believe it or not, this is still not standard hardware for many servers. For HP servers, a TPM add-on is available for about $50 as p/n 488069-B21. If you do have to install a TPM, go into the BIOS and enable the TPM under the security settings, to save yourself some steps later.
Now comes the tricky part. Powershell version 4 added some handy new cmdlets for managing the TPM. Unfortunately, for some reason those cmdlets are not included in Server Core installs, so we have to resort to using WMI. The Scripting Guy has a great blog post that gets into all of the details on this, written by guest blogger Stephane van Gulick, which my process was based on.
First, use WMI to get the Win32_TPM class, which contains all of the methods required for managing the TPM. By assigning it to a variable $TPM, we can use the variable to call the methods we need.
EDIT 05/26/2017 : It may be necessary to use "Get-WMIObject" instead of Get-CIMClass in the above command.
Next, run the following commands to check the current status of the TPM.
Each of those commands will return a boolean true or false. If the TPM isn't enabled, enable it using:
Once the TPM is enabled and activated, it's time to take ownership. If the TPM is already owned, it will need to be cleared first. Then, prepare a TPM owner password to be used, and take ownership.
Now the Trusted Platform Module is enabled, active, owned, and ready to store the Bitlocker key protector. But before we can start encrypting the drive, the Bitlocker feature must be installed using 'install-windowsfeature'
At this point, I tried to enable bitlocker using a TPM protector, but because our group policy settings require that a bitlocker recovery password be backed up to Active Directory, the command failed.
According to the documentation for Enable-Bitlocker, the there are several parameters which can be used to specify what type of key protector should be used. While some of these parameters include multiple protectors, The TPMProtector and RecoveryPasswordProtector options are mutually exclusive, and cannot be combined. Lucky for me, the documentation also includes this handy tip to point me in the right direction:
It is common practice to add a recovery password to an operating system volume by using the Add-BitLockerKeyProtector cmdlet, and then save the recovery password by using the Backup-BitLockerKeyProtector cmdlet, and then enable BitLocker for the drive. This procedure ensures that you have a recovery option.Use the Add-BitlockerKeyProtector cmdlet to create the recovery password. Then find the protector ID and use it to back up the recovery password to Active Directory using Backup-BitlockerKeyProtector. (It may not be necessary to run Backup-BitlockerKeyProtector if group policy requires the password be backed up when created, but it won't hurt anything to back it up again just to be safe.)
I ran Enable-Bitlocker again, but once again hit a snag:
Because my group policy also requires that OS drives encrypted with Bitlocker use a TPM protector, it appears that a TPM protector was assigned automatically when I added the Recovery Password protector. Since the drive was already set up with a TPM protector, the enable command failed when it tried to add another. The Enable-Bitlocker command requires the use of one of the protector parameters though, so even though the required protectors were already present, I couldn't simply enable bitlocker using the existing protectors. To work around that, I ran it again using the RecoveryPasswordProtector option.
Finally, bitlocker was successfully enabled. Powershell helpfully provided the recovery password again and instructed me to save it in a safe place, and instructed me to restart the computer for a hardware test before encryption begins. The restart can be avoided if necessary by using the -skiphardwaretest parameter, but I wouldn't recommend it.
One unfortunate result of my mis-steps along the way is that I ended up with 3 separate Recovery Password Protectors assigned to the drive, and all 3 backed up to AD. I will need to do further testing to determine why the additional passwords were created, but I suspect it may have happened as a result of my failed attempts with the "enable-bitlocker" command. If you know why this happened, or if you have any questions, please leave a comment below.
Thanks for reading!