Solution The Enable Bit. Locker task fails to run during a Config. Mgr 2. 00. 7 Task Sequence. Misc/8.12.jpg' alt='Sccm 2007 And Microsoft Deployment Toolkit Setup And Configuration' title='Sccm 2007 And Microsoft Deployment Toolkit Setup And Configuration' />When running a Configuration Manager 2. Task Sequence that has the Enable Bit. Locker task in it, the task fails to run and Bit. Locker is not enabled on the PC. Examining the SMSTS. Start executing the command line OSDBit. Locker. exe enable  wait False mode TPM pwd AD TSManager TSManager Expand a string Full. OS TSManager Executing command line OSDBit. Solution The Enable BitLocker task fails to run during a ConfigMgr 2007 Task Sequence. Download the latest from Windows, Windows Apps, Office, Xbox, Skype, Windows 10, Lumia phone, Edge Internet Explorer, Dev Tools more. Hello everyone, new to the forums here, been doing some extensive searching here and other sites, I see that others are experiencing similar issues but I. The best free PDF reader viewer used by over 475 million users. Foxit PDF reader for Windows, Mac, and more. A speedy PDF reader alternative to Adobe Reader. In this post we will see how to deploy Microsoft Office 2013 using SCCM 2012 R2, deploy Microsoft Office 2013 using SCCM 2012, SCCM 2012 R2. Acrobat, Reader, Adobe Reader, Enterprise Administration, Acrobat Products, registry, plist, deployment, configuration, wizard, GPO, AIP, Citrix, AppV. A collection of thoughts and resources for Microsoft System Center products and the Private Cloud. The latest version of System Center Custom Updates Publisher 2011 is released and ready for download. SCUP 2011 is a freeware tool from Microsoft that can assist you. Microsoft Windows Imaging Web Portal. MDTSCCM is my passion, so most content and articles are related to Deployment of Windows OS. Welcome to The Windows Server HA Blog My name is Robert Smit and this is my personal Blog. Im a Senior Technical Evangelist and Microsoft MVP as of 2009. Locker. exe enable  wait False mode TPM pwd AD TSManager OSDBit. Locker. exe OSDBit. Locker Command line OSDBit. Locker. exe enable wait False mode TPM pwd AD OSDBit. Locker Initialized COM OSDBit. Locker Command line for extension. OSDBit. Locker Set command line OSDBit. Locker. exe enable wait False mode TPM pwd AD OSDBit. Locker Target volume not specified, using current OS volume OSDBit. Locker Current OS volume is C OSDBit. Locker FALSE, HRESULT8. OSDBit. Locker Unable to find instance of Win. Encryptable. Volume where Drive. Letter C. Ensure that Bit. Locker Drive Protection is available for this device. OSDBit. Locker mp. Encryptable. Volume Initialize psz. Volume, HRESULT8. OSDBit. Locker p. Bit. Locker Initialize arg. Info. s. Target, HRESULT8. OSDBit. Locker Process completed with exit code 2. TSManager TSManager Failed to run the action Enable Bit. Locker. Unspecified error Error 8. Source Windows TSManager Examining the PC reveals that the Trusted Platform Module TPM chip on the PC has been activated and initialized in the BIOS. Cause. This error can happen if the drive where the Windows OS is being installed on has not been partitioned correctly for use with Bit. Locker. In order for a PC to be able to boot, the boot manager and boot files cannot be encrypted. For this reason, when Bit. Locker is being used, these files need to reside on a partition that is not encrypted by Bit. Locker, therefore two partitions need to be created. The first partition, which is usually 1. MB 3. 00. MB in size, is not encrypted, and is used as the boot partition that contains the boot manager and boot files. The second partition is encrypted, takes up the remaining disk space on the drive, and contains the Windows OS on it. The order of the partitions does not matter. When manually installing Windows 7 or Windows Server 2. R2 from the original installation source, such as DVD media, Windows Setup will automatically partition the drive into two partitions 1. The first partition will be 1. MB in size, is formatted NTFS, will be labeled System Reserved, and a drive letter will NOT be assigned to it. Not assigning a drive letter to this partition effectively makes the partition hidden, although assigning a drive letter to it, either via Disk Management or Disk. Part. exe, causes it to no longer be hidden. This partition will also be the boot partition and will contain the boot manager and boot files. The second partition will take up the remaining disk space on the drive, will be formatted NTFS, will not contain any label, and will be assigned the drive letter C. This partition is where the Windows OS is installed on to. One of the reasons the manual installations of Windows 7 and Windows Server 2. R2 from original installation source files automatically creates two partitions is in preparation for Bit. Locker use. Creating the two partitions during Windows installation makes enabling Bit. Locker much easier in the future. Manual installations of Windows Vista and Windows Server 2. Bit. Locker. This made enabling Bit. Locker in Windows Vista or Windows Server 2. Bit. Locker was desired. When deploying any version of Windows that supports Bit. Locker, including Windows 7 and Windows Server 2. R2, via a Config. Mgr 2. 00. 7 OSD Task Sequence, the Task Sequence will NOT automatically create the required partitions for Bit. Locker, whether deploying from an Operating System Install Package original installation source files or an Operating System Image. If the required partitions are not set up appropriately during the Task Sequence, when the Enable Bit. Locker task is attempted to be used, then the error will occur. Resolution. To resolve the problem, the drive needs to be partitioned correctly to support Bit. Locker. This can be done in one of two ways 1. Erase the existing single partition on the drive and repartition the drive with two partitions. After repartitioning, format the partitions NTFS. The drawback to this method is that all data on the drive is lost during the repartitioning and format of the drive. This is a problem if USMT with local capture or hardlinking is being used. This method can be accomplished in a Config. Mgr 2. 00. 7 Task Sequence by using the Format and Partition Disk task. Shrink the existing single partition on the drive, and then using the newly freed space, create a new second partition. The newly created partition will actually be the second partition on the drive and not the first. As mentioned, partition order is not relevant when using Bit. Locker. This method does not erase any of the data on the drive and is desirable when using USMT with local capture or hardlinking. The drawback to this method is that it may take longer to set up, and can be problematic if the drive is low on disk space or highly fragmented. This method can be accomplished in a Config. Mgr 2. 00. 7 Task Sequence by using the ZTIBde. MDT integration. Method 1 is recommended in the following scenarios Refresh with no USMT Refresh with USMT and a State Migration Point SMP New Computer Bare Metal Method 2 must be used in the following scenarios Refresh with USMT and local capture Refresh with USMT and local capture with hardlinking Method 2 can actually be used in ANY of the above scenarios and may be desirable in a Task Sequence that handles multiple scenarios. Method 1 CANNOT be used in any of the scenarios listed under Method 2 as doing so would erase the data captured locally by USMT. To implement the scenarios, follow the below instructions Method 1. To use the Format and Partition Disk task in a Config. Mgr 2. 00. 7 Task Sequence to automatically create the required Bit. Locker partition In the Config. Mgr 2. 00. 7 Admin Console, under the Computer Management Operating System Deployment Task Sequencesnode, right click on the affected Task Sequence and choose Edit. In the left pane of the Task Sequence select the Format and Partition Disk, Partition Disk, or Partition Disk 0 task. Double click on the first item under Volume to bring up the Partition Properties. In the Partition Properties window. Next to the Partition name text box, enter in System Reserved. This name can actually be anything desired as long as it abides by Windows naming rules but it should describe the partition as the boot or Bit. Locker partitiondrive. Under Partition options, make sure that Partition type is set to Primary. Under Partition options, change the option from Use a percentage of remaining free space to Use specific size. Change the value next to Use specific size from 1 MB to 3. Microsoft Word History And Physical Template For Pain. MB. Under Partition options, make sure that the option Make this the boot partition is selected. Under Formatting options, make sure the File system drop down menu is set to NTFS. Under Formatting options, make sure the Quick Format option is selected.