uEFI is a hard requirement for GPT and boot disks larger than 2.2TB. 

 

You can verify that the machine properly booted to uEFI by checking the 
ZTIGather.log and looking for isUEFI=True.

 

MDT should support uEFI just fine in LTI and ZTI environments. I’m not 100% 
sure what the scenario Niall references below is from the MDT 2013 Release 
notes, but from what I can tell it’s more of an edge case, than a common 
scenario.

 

-k

 

From: [email protected] [mailto:[email protected]] On 
Behalf Of Feret, Greg
Sent: Wednesday, December 17, 2014 8:51 AM
To: '[email protected]'
Subject: RE: [MDT-OSD] Issue imagining systems with large disks

 

Thanks Niall,

 

It is a Gen 8. I think the Gen 9s will support UEFI.

 

I just found this 
http://h20565.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c02591108

 

HP ProLiant servers and UEFI

At HP, we are always evaluating new server technologies, including UEFI. 
Currently, we believe that the best customer value 

for ProLiant servers is provided by continuing to use BIOS-based firmware. 
Going forward we will continue to evaluate and 

remain involved in the UEFI efforts so that we can determine when and where it 
may add customer value and provide 

development flexibility.

 

So I guess I will have to change my disk configuration.

 

Thanks again.

 

From: [email protected] <mailto:[email protected]>  
[mailto:[email protected]] On Behalf Of Niall Brady
Sent: Wednesday, December 17, 2014 11:30 AM
To: [email protected] <mailto:[email protected]> 
Subject: Re: [MDT-OSD] Issue imagining systems with large disks

 

first of all is the server in UEFI mode, that is required for GPT disks,

secondly have you seen point 6 below

Known Issues for LTI Deployments Only

1.      Check for Updates downloads an older list of components
2.      Windows 8.1 AppX cleanup maintenance task can affect Sysprep
3.      Existing databases will retain 50 character application names when 
upgrading to MDT 2013
4.      The deployment will fail on a legacy BIOS system if BitLocker is 
enabled and a data partition is created
5.      Provisioning of Windows Store applications does not include dependencies
6.      GPT drives are partitioned as MBR
7.      Domain join fails due to default variable values
8.      User data may not be restored from USB
9.      User mapped network drive Z: is not restored
10.     Bare-metal deployment fails with “fixed disk” USB flash drive on UEFI 
system
11.     LTI progress on the Windows 8.1 Desktop is not visible from the Start 
screen

 

 

On Wed, Dec 17, 2014 at 5:24 PM, Feret, Greg <[email protected] 
<mailto:[email protected]> > wrote:

Hi all,

 

Looking for a little help on this. I have HP servers which have arrays larger 
than 2.2 TB so they have to be partitioned as GPT.

 

Using Cm 2012 R2 CU3 MDT 2013 integrated. 

 

I created a server TS and am trying to apply my captured reference image to one 
of the systems with large disks. 

 

I changed my TS to format the drives as GPT and that works fine but when the 
Apply Operating System step happens it tries to find an active MBR partition. 
(see the report capture at the bottom)

 

Any help would be greatly appreciated.

 

Thanks in advance.

 



The information contained in this email message may be privileged,
confidential, and protected from disclosure. Any unauthorized use,
printing, copying,disclosure, dissemination of or reliance upon
this communication by persons other than the intended recipient
may be subject to legal restriction or sanction. If you think that
you have received this E-mail message in error, please reply to
the sender and delete this email promptly.

The information contained in this email message may be privileged,
confidential, and protected from disclosure. Any unauthorized use,
printing, copying,disclosure, dissemination of or reliance upon
this communication by persons other than the intended recipient
may be subject to legal restriction or sanction. If you think that
you have received this E-mail message in error, please reply to
the sender and delete this email promptly.


Reply via email to