Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT2010 U1 BitLocker issue with "more than 1 pre-existing partition is not supported in this version"

Answered MDT2010 U1 BitLocker issue with "more than 1 pre-existing partition is not supported in this version"

  • Wednesday, May 04, 2011 2:39 AM
     
     
    Sign In to Vote
    0

    Hello all,

    I have a bitlocker failure:

    • Microsoft Deployment Toolkit version: 5.1.1642.01 ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      The task sequencer log is located at C:\_ESD\CCM\Logs\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      Starting search for removable drive ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      The search for a USB drive failed ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      OSDBitLockerTargetDrive= , OSDBdeTargetDriveLetter= , sOSDBitLockerTargetDrive= C: ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      OS drive encryption requested. Drive:C: ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      Total Disk size in bytes80023749120 ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      Configuring BitLocker Drive Encryption on computers with more than 1 pre-existing partition is not supported in this version ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)
      ZTIBde processing completed successfully. ZTIBde 2011-05-04 3:07:43 PM 0 (0x0000)

    I originally thought that it is something to do with our APP-V client set to use S: (instead of Q:) while W7 or ZTIBDE.wsf is trying to temporarily map BDEDrive to S: with BDEDriveLetter variable.

    I resolved the potential issues by

    • setting BDEDriveLetter=T: on customsettings.ini
    • Move all Bitlocker related tasks higher than App-V Client installation (Install Applications task)

    No matter what I do, so far I cannot get out of the same issue.

    Any help is really appriciated...

    Thanks in advance...

    Young Pae

    YPae

     

All Replies

  • Thursday, May 05, 2011 4:02 AM
     
     
    Sign In to Vote
    0

    I did some more research and I think that the root cause is somewhere around ZTIBDE.wsf:

    Line 332 - 362

      '// Set our default BDE drive letter unless it is Windows 7 with a hidden system partition
      If Left(oEnvironment.Item("OSCurrentVersion"),3) = "6.1" and GetBootDrive = Failure Then
        '<== I confirmed W7 is 6.1, GetBootDrive should find one.
     
       'Reset the BDEDriveLetter
       oEnvironment.Item("BdeDriveLetter") = ""
       
      Else
      
       If oEnvironment.Item("BdeDriveLetter") = "" Then
       
        sBdeDriveLetter = "S:"
        
       Else
       
        sBdeDriveLetter = oEnvironment.Item("BdeDriveLetter")
        '<== I already set this to T:
        
       End If
       
      End If

      '// Perform BDE drive configuration only for both NewComputer and Upgrades with a single partition

      sSecondPass = oEnvironment.Item("BdeSecondPass")
      '<== This shouldn't be the second pass yet...

      If sSecondPass <> "YES" Then

       iPartitionCount = GetDiskPartitionCount(0)
       iFreeSpace = GetDiskFreeSpace(0)
       sExistingBdeDrive = GetExistingBdeDrive() 'this is empty then will have the error we are getting
       <== This has to return something but I think it is returning "" and causing my issue...

       If sExistingBdeDrive <> "" Then

    YPae
     
  • Thursday, May 05, 2011 4:49 AM
     
     
    Sign In to Vote
    0

    Well... with 2 days of trial and errors, without changing any thing, we found:

    • USB-Drive-Staged LiteTouch deployment always complains more than 1 pre-existing partition is not supported in this version 
    • Network-based LiteTouch with CD always successfully enable BitLocker (even without BDEDriveLetter...)

    Can someone explain why and how we can allow USB Drive to run BitLocker???

    Thanks,

    YPae
     
  • Tuesday, May 10, 2011 6:37 PM
     
     
    Sign In to Vote
    0

    Could it be something to do with USB Harddrives being recognized as Basic Disk X?

    When I plug in bootable (Active, Primary) USB Drives and USBStick, On Disk Management shows that

    • USB "Drives" are recognized as "Basic Disk" while
    • USB "Sticks" are recognized as "Removable Disk"

    So maybe both USB Drives and the targeted drive are both "Basic, Bootable Disk", it complains "More than 1 pre-exisitng partition is not supported in this version"...

    I need.... help!

    YPae
     
  • Wednesday, May 11, 2011 3:59 PM
     
     
    Sign In to Vote
    0

    Hi,

    I have exactly the same problem.

    when I launch the deployment with the DVD, no problem but with a storage disk, I have the same error message.

    Did you find a solution ? I am very interesting about that

     

    Best Regards

     
  • Friday, May 13, 2011 3:30 PM
     
     Answered
    Sign In to Vote
    0

    I still have some other issue related to BitLocker but I found this:

    "1" of the reason showing "More than 1 pre-existing partition" is because Windows 7 has "more than 1 pre-existing partition"!!!!

    Intially I thought that DoNotCreateExtraPartition need to be set to "NO" because we DO want to have the extra partition (BDEDrive) to be ready for "Enable BitLocker" task but because of this pre-exisitng BDEDrive created by DoNotCreateExtraPartition=NO, now ZTIBDE.wsf can handle the situation.

    All I did was to add DoNotCreateExtraPartition=YES on CustomSettings.ini and now ZTIBDE.wsf shows "Only single partition found" then create BDEDrive partition and run BitLocker Encryption as it has been working for XP to W7 Refresh scenario.

    So my working set of Bitlocker related variables on custom settings are:

    • SkipBitLocker=YES <== Not to show the option on Wizard
    • DoNotCreateExtraPartition=YES <== important for USB Hard drive based deployment
    • BDEInstallSuppress=NO <== double negative Suppress=NO means do bitlocker encryption
    • BDEDriveLetter=T: <== Default is S: and unfortunately APP-V Client is already using S:
    • BDEDriveSize=300
    • BDEInstall=TPMPin <== I had to have IsDesktop=TRUE, Set BDEInstall=TPM on Task Sequence so that I can disable PIN for desktop
    • DEPin=111111
    • BDERecoveryKey=AD
    • BDEKeyLocation=C:
    • BDEWaitForEncryption=TRUE

    Even with this great finding, we have so many other BitLocker failures depending on the models and situation, etc. and I think it could be something to do with TPM Chip's status (Disabled/Inactive, vanilla TPM setting requires reboot and ZTIBDE cannot handle it, etc.)

    I just disable the built-in "Enable BitLocker" Task and added my own to enable debugging mode:

    • Name: Enable BitLocker - debug:TRUE
    • Command line: cscript.exe "%SCRIPTROOT%\ZTIBde.wsf" /debug:TRUE
    • Options - Continue on error: Checked
    • Options - TS Variable BdeInstallSuppress not equal YES

    I wish someone can give us definitive guide how to make Bitlocker 100% successful...

    Thanks,

    YPae

    YPae
    • Marked As Answer by YPae Wednesday, July 11, 2012 9:08 PM
    •  
     
  • Friday, December 07, 2012 6:31 AM
     
     
    Sign In to Vote
    0

    Hi guys!

    I know this is a bit old thread.. anyway..

    Have you seen this thread?

    http://social.technet.microsoft.com/Forums/sr-Latn-CS/mdt/thread/736aabea-9c73-4f61-a393-1b4db27d2e1f

    Btw I have same issues with Bitlocker when I using USB-stick offline media deployment but NOT with online USB-stick deployment.

    I´ll try the "DoNotCreateExtraPartition=YES" and see if that resolves my offline issue deployment.

    Best regards

    • Edited by Code 46 Friday, December 07, 2012 6:37 AM
    •  
     
  • Sunday, February 17, 2013 9:54 AM
     
     
    Sign In to Vote
    0

    My issue was resolved by an new BIOS update for HP computers. HP found a problem and corrected it.

    I thought it was my stuff that was corrupted.. Thanx HP.


    • Edited by Code 46 Sunday, February 17, 2013 11:39 AM
    •