Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, August 19, 2016 7:39 AM
I have problems deploying Windows 10 on some computers.
This error occurs on only some computers.
The error occurs when BitLocker is activated.
Turns out that on all the computer that fail the EFI-partition and a 300MB restore partition are missing.
For some reason they are not created when installing Windows and activating BitLocker.
All computers that succeed have these partitions.
Installing Windows from a regular media does create the EFI-partition on the failing computers.
Tried to change partitioning in the task sequence to leave about 2GB unallocated, but to no avail.
Do anyone know why these partitions are not created during Windows deployment and BitLocker activation?
I took some screenshots of the error and partitions on a computer that fail and the partitions on a computer that succeeded.
Also exported the logs from a failed deployment.
Link to screenshots and logs:
https://drive.google.com/open?id=0B9sVUhLLQKNYNWdlUG4xdkpZTlk
All replies (4)
Monday, August 22, 2016 9:38 AM âś…Answered
Hi Bjodan,
Just wanted to check that the machines that this is failing on are actually doing a UEFI PXE boot and not a BIOS PXE boot? This potentially might explain why you see missing partitions when they fail.
Regards,
adrian
Sunday, August 21, 2016 10:38 AM
If the systems are UEFI systems, you must create the partitions properly in the TS. You should also create the partitions necessary for BitLocker. Thus, if these are existing systems and you are running a refresh task sequence, you will need to tread carefully as refresh TSes normally don't repartition systems and doing so may cause you USMT issues if you haven't planned on moving the data off.
Jason | http://blog.configmgrftw.com | @jasonsandys
Monday, August 22, 2016 6:08 AM
All the systems being deployed are UEFI-type systems.
The systems that succeeded the firs time and are re-deployed also succeed next time.
I guess it is because partitioning was done right the first time.
Also tried to switch harddrives and reset tpm on a failing system, but the result is the same.
just wanted to see if it would trigger a fresh deployment on that system.
Could you explain a little more the last part of your answer?
I am far from a pro on MDT as you probably figured out.
Tuesday, August 23, 2016 7:24 AM
Seems like you were right Adrian.
All computers succeeding and failing are set to hybrid boot, but the failing computers must perform a bios boot.
Had to make these settings in bios to make them succeed:
HP Elitebook 820/840/850 G1 and HP Elitebook 725/745/755 G1/G2:
Advanced -> Boot Options -> Set to Native UEFI.
HP Elitebook 725/745/755 G3: Advanced -> Boot Options -> Remove Legacy Boot Order.
Advanced -> Option Rom Launch Policy -> Set to All UEFI
Thanks a lot for all answers.