I have a OSD task sequence with pre-provision of bitlocker and have created partitions following the images in this thread:

http://social.technet.microsoft.com/Forums/en-US/configmanagerosd/thread/7a9b6953-7dad-4935-b480-ce4b6f75e5a7

Pre-provision seems to be working, but the BDEDrive is assigned letter C: and the OSDisk gets D: although the BDEDrive should not be assigned a letter.

When the workstation is done installing the BDEDrive is visible. What am I doing wrong? I would like to end up with the os on C: and the BDEDrive not visible.

Firstly, ignore the drive assignments within Windows PE - they have no relation to drive letters when in the OS.  So, it is perfectly normal for the BDEDrive to be C: and the OSDisk to be D: when you are applying the Operating System Image.

When applying an Operating System Image, you must consider using the "OSDPreserveDriveLetter" variable if your image was captured from a machine that was configured with multiple partitions - this variable controls the preservation of the drive letter the partition had when it was being captured.  If your image was from a machine with multiple partitions then set the variable value to "FALSE" if you want Windows to finish showing as installed on C:  - otherwise set the value to "TRUE" and whatever drive letter was assigned in the image will be

The image was captured on a system with only one partition.

A small update. It seems that although during install it states that windows is being deployed to D:, in the end the OS is installed on C and the BDEDrive is D:. The issue of the BDEDrive being visible still remains. BitLocker is getting enabled by I can't understand why the BDEDrive is visible.

If I look at my TS, it looks like this.

Have you tried putting a tick in the box for the BDEDrive "do not assign a drive letter to this partition" ?

I personally don't have that option ticked in my task sequence that has the same partitions as yours and whether I enable bitlocker or not I do not see any BDEDrive.  This could still be an image thing.

I do have that option ticked. I will try to remove the tick and see if it makes any difference.

As you can see in my screenshoot for the BDEDrive there's no ticket in "Do not assign a drive letter to this partition".

My TS is a standard MDT TS and the Operating System Image is build on a virtuel machine using MDT.

What kind of laptops do you have? I noticed that if I deploy the task sequence to a HP laptop the partition is NOT visible, but if I deploy to a Lenovo laptop then the partition IS visible after installation.

I have both HP and Lenovo laptops and I don't have any issues.

I think I found a work around for this.
My use came up after injecting updates, the Bitlocker partition (BDEDrive) will gave a letter (Win8.1)
After I captured Win7x64 SP1 with SCCM it showed up as well

I noticed the step on the TS that formats the drive is assigning a letter drive to the partition.

Work around: added a "Run Command line" step after the format and partition with the following command line:
diskpart /s Diskpart.txt

you must create a package containing the txt (don't create a program)

Also I had to check "Do Not Assign a drive letter to this partition" on the BDEDRive

this is what I put in the TXT:
select volume 1
remove

Can anyone tell me if there is something wrong with this approach?

• Edited by Leo T Thursday, December 11, 2014 6:38 PM

I think I found a work around for this.
My use came up after injecting updates, the Bitlocker partition (BDEDrive) will gave a letter (Win8.1)
After I captured Win7x64 SP1 with SCCM it showed up as well

I noticed the step on the TS that formats the drive is assigning a letter drive to the partition.

Work around: added a "Run Command line" step after the format and partition with the following command line:
diskpart /s Diskpart.txt

you must create a package containing the txt (don't create a program)

Also I had to check "Do Not Assign a drive letter to this partition" on the BDEDRive

this is what I put in the TXT:
select volume 1
remove

Can anyone tell me if there is something wrong with this approach?

• Edited by Leo T Thursday, December 11, 2014 6:38 PM

I think I found a work around for this.
My use came up after injecting updates, the Bitlocker partition (BDEDrive) will gave a letter (Win8.1)
After I captured Win7x64 SP1 with SCCM it showed up as well

I noticed the step on the TS that formats the drive is assigning a letter drive to the partition.

Work around: added a "Run Command line" step after the format and partition with the following command line:
diskpart /s Diskpart.txt

you must create a package containing the txt (don't create a program)

Also I had to check "Do Not Assign a drive letter to this partition" on the BDEDRive

this is what I put in the TXT:
select volume 1
remove

Can anyone tell me if there is something wrong with this approach?

• Edited by Leo T Thursday, December 11, 2014 6:38 PM

Any update on this one ? I also have "sometimes" I visible bitlocker partition and I do not know why ??

I still have the issue....when deploying and checking with F8 prompt i see that my partions are created:

500MB BDE (NTFS) visible as drive S

300GB OSDISK (NTFS) visible as drive C

After deploying the OS and enabling bitlocker i do have the following visible disks:

C: 300GB OSDISK

D: 500MB BDE disk

:-(

sounds like you have a script elsewhere in the task sequence assigning that drive letter (s:) to the bde drive, check your task sequence again and verify if one exists, also, verify that the task sequence is ending correctly.

I still have the issue. Today I did some tests. Just after the TS created the partitions I checked with F8 and I saw a S drive an a C drive. The task sequence completed normally at my Lenovo and dell laptops without a visible bitlocker partition. But all my HP laptop ended with a visible bitlocker partition. All got the same TS !!! Strange :-( I found out then when I put a 60 second sleep at the end of the TS, also the HP laptops ended without a visible bitlocker partition. But why ??? This is really strange. The sleep is not a solution, but a workaround. But what are the HP machines waiting for and why they need some extra time ? For what ? Any ideas ????

This was related to a timing issue.

I created 2 vbs script which i put in the task sequence after the PreProvisioning task and the EnableBitlocker task.

When i put that it worked fine for all models, including HP.

• Proposed as answer by pollewops 17 hours 48 minutes ago