Hi Mike,

Take a look at this technet, it mentions this issue and although no definite 
solution, there are a few things you could try around the right path.

As you say you can build VM's and another laptop fine, that suggests the TS and 
all its packages are ok.

So maybe more so this particular machine itself / model.

https://social.technet.microsoft.com/Forums/en-US/30dd9b18-2be6-4a03-982c-230809820096/system-partition-not-set-bcdboot-failed-bcdbootexe?forum=configmanagerosd

Rich

From: [email protected] [mailto:[email protected]] On 
Behalf Of Marable, Mike
Sent: 22 October 2015 19:47
To: [email protected]; [email protected]
Subject: [mssms] Issues Deploying UEFI using SCCM+MDT?

I'm at a loss on this and getting nowhere fast.

I'm running SCCM 2012 R2 CU3 with ADK 8.1 and MDT 2013.  I'm starting to work 
on supporting UEFI systems and cannot get the image to apply successfully.

I started with a basic "native" OSD task sequence and I can deploy to UEFI VMs 
and a demo laptop successfully.

I create an MDT integrated task sequence and it fails, all the time, every time 
when it attempts to apply the image (either Win7-64 or Win10-64).

Here are the last few line in SMSTS immediately prior to the failure.  The 
image application completes but then it fails when setting up the boot 
partition.  I've tried using the same Format and Partition step copied from the 
successful non-MDT integrated sequence but that didn't help.  Niall Brady had a 
post on how to deploy Win 8.1 to UEFI so I tried his partition scheme but still 
no luck.

I don't understand why it would work using the non-MDT integrated sequence but 
fail when using the MDT integrated sequence.  These are stock sequences in both 
cases and I haven't customized them at all.

[cid:[email protected]]

Am I missing something?  I have a feeling that I'm so far out in the weeds on 
this that the answer is right in front of me but I'm not seeing it.

Thanks
Mike



**********************************************************
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues




Reply via email to