I think you see this: pxe uses the RAM disk only at this point, hence bitlocker isnt an issue until the same TS would want to write data, which it would later on anyway.
The 2nd PE already runs the TS and wants to write to the volume which cant be the ram disk but the OS volume, which has to fail. You have to disable protection (manage-bde -protectors -disable c: (you need to get the proper letter) ) or format the disk to use it. In other words, that volume must be writeable, thats why there is a format step at the beginning if there isnt a writeable volume -R Von: [email protected] [mailto:[email protected]] Im Auftrag von Mawdsley R. Gesendet: Samstag, 19. März 2016 13:21 An: [email protected] Betreff: [mssms] Bitlocker not allowing change in boot wim Afternoon All, So I have this scenario; I PXE boot a machine to an SCCM winpe image which presents me with a HTA screen. This then allows me to select a task sequence. The task sequence being selected uses a different boot wim, so the machine downloads the boot wim, and restarts to boot to it. Then Bitlocker, which is enabled, either stops the machine from booting to it and just goes back into windows, or prompts for the encryption key. Ive tried a handful of things but I cant seem to get around this (which, yes I know is kind of the point). I find it odd tho that I can boot to pxe and run a task sequence (same boot wim) and use the built in Disable Bitlocker step in a task sequence and all works fine. But I cant find anyway of running this Disable Bitlocker step as part of the HTA, pre task sequence. All I want to do is allow it to change the boot order. Ive tried the MDT script ZTIDisableBDEProtectors.wsf, but that doesnt seem to do anything. Anyone else do this? Or have any ideas?? Thankyou Rich ------------------------------------- Rich Mawdsley Software & Desktop Services iSolutions University of Southampton -------------------------------------
