With Windows 7 deployments, BitLocker installation for Operating System and data volumes has typically been configured as a post Operating System deployment activity – usually using the Enable BitLocker task sequence actions or by using the manage-bde.exe command line.
The impact on the Windows 7 deployment process is that the full volume encryption process may take several hours as BitLocker requires that all data and free space on the drive is encrypted. This is especially true with the large volumes.
With Windows 8, BitLocker can also be provisioned before the Operating System is installed, from within Windows PE. This is achieved by using a randomly generated protector that is stored clearly on the volume. The volume is then encrypted, all before the Windows setup process has started.
That’s a great feature, however you’ll be thinking it will still take time to encrypt your entire disk – however Windows 8 also includes the option to encrypt only used disk space.
When the Used Disk Space Only encryption option is configured during BitLocker setup, only the area of the drive that has data will be encrypted with free disk space remaining unencrypted. The result is that the encryption completes much faster – which will speed up the Windows provisioning process.
The great news is that MDT 2012 Update 1 will handle this for us. The ZTIBDE.wsf script is executed during the PreInstall phase and will automatically enable BitLocker Offline from with Windows PE, using the UsedSpaceOnly parameter (if the partition is not already encrypted). This will literally take seconds to run. The data written to the volume during OS and application installation is then encrypted as it is written to the disk, with a very small impact on performance (less than 1%)
Once the OS image, applications and configurations have been installed, we include the standard Enable BitLocker task to configure the encryption protectors as required.
One challenge is configuring BitLocker on additional data partitions. Using the Enable BitLocker task sequence action will not allow us to set the parameters for Used Space Only. This is where we can use the new BitLocker PowerShell cmdlets.
There are a host of new BitLocker cmdlets available in Windows 8, all described in the TechNet article at the end of this post. For this example, I am going to use the Enable-BitLocker cmdlet to encrypt my extra data partition and specify the –UsedSpaceOnly parameter.
Then literally by the time I had typed Enable-BitLockerAutoUnlock D: to configure Autounlock for the D partition, the encryption process had completed and the Protection Status had changed to On.
The PowerShell cmdlets can be called during the deployment process using the Run Command Line or even better, put together in a PowerShell script and called using the new Run PowerShell Script action in MDT 2012 Update 1 (thus making use of the integrated logging features with BDD.Log). A very simple example is illustrated below.
The output from the script will be logged into the BDD log file automatically, as highlighted below:
Take a look at the new BitLocker cmdlets documented in the following article:
This post was contributed by Matt Bailey, a Consultant with Microsoft Services - UK.
interesting to see this. I would suggest that lines to encrypt additional partitions (do people still do this?) are reworked to support the drive letter being passed in as a parameter from the TS. Thus you only need one script regardless of how many drive letters you want to encrypt. Much more in keeping with the whole MDT ethos.
How would you check that the encryption had 'taken'? Using something like manage-bde -status %driveltr%: -protectionaserrorlevel ?
Absolutely, use task sequence variables whenever possible, either setting them using the task sequence action or through the MDT database. I still see quite a number of organisations using additional partitions, although this isn't an approach we would typically recommend. I'll be posting some scripts for an alternative approach using virtual hard disks soon.
To check the encryption status of drives, there are some WMI objects we can access. I have previously posted an article on how to query these using vbscript:
Alternatively, with Windows 8 you could use the BitLocker cmdlet Get-BitLockerVolume, which returns the volume status attribute. For example:
$BitLockerStatus = (Get-BitLockerVolume D:).VolumeStatus
If the volume is encrypted, the returned status will be "FullyEncrypted"
i cant use the Bitlocker cmdlets in WinPE 4.0 in ConfigMgr 2012 although the optional components "WinPE-SecureStartUp" is included to the WinPE 4.0
Which commands are you trying to run and what errors are you seeing returned?