I've sorted it out now. The only downside is I have some old netbooks which 
will mean I'll need to make a boot cd/usb stick with the x86 boot image. Every 
other pc can support a 64 bit boot image.

From: Johns, Damon (DoJ) [mailto:damon.jo...@justice.tas.gov.au]
Sent: 11 March 2014 21:19
To: 'mssms@lists.myitforum.com'
Subject: RE: [mssms] UEFI boot 32 bit PXE

Or just remove an actual production TS deployment that uses an x64 boot image 
and then re-deploy it to unknown computers. You won't need to make a dummy one.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Niall Brady
Sent: Tuesday, 11 March 2014 8:23 PM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: Re: [mssms] UEFI boot 32 bit PXE

deploy a task sequence with a boot image that has the architecture you want to 
boot, if that's the last ts deployed to the target collection then that's what 
the client that PXE boot's will see.

On Tue, Mar 11, 2014 at 10:10 AM, Matt Wilkinson 
<mwilkin...@lcb.ac.uk<mailto:mwilkin...@lcb.ac.uk>> wrote:
So can I force SCCM to boot a 64 bit boot image? Even when there are task 
sequences with 32 bit boot images available?

From: 
christopher.catl...@us.sogeti.com<mailto:christopher.catl...@us.sogeti.com> 
[mailto:christopher.catl...@us.sogeti.com<mailto:christopher.catl...@us.sogeti.com>]
Sent: 10 March 2014 15:54
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>
Subject: Re: [mssms] UEFI boot 32 bit PXE

UEFI boot image must match the Processor Arch.

so x64 cpu = x64 boot image
x86 cpu = x86 boot image

Sent from Windows Mail

From: Matt Wilkinson<mailto:mwilkin...@lcb.ac.uk>
Sent: Monday, March 10, 2014 11:35 AM
To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com>

I'm trying to boot a 32bit uefi boot image. The pc has a 64bit processor. The 
problem is the pc's were imaged using a 32 bit boot image to deploy a 64 bit 
OS. The pc's in question were built with a standalone mdt 2012 u1 server.
Which is fine when they were using the legacy part of the bios. But now when I 
UEFI pxe boo it boots to 32 bit image which fails. It gives an error

Windows\System32\boot\winload.efi  0xc0000359 .


Everything I read points to UEFi needing the same architecture as the os you 
want to deploy. We have task sequences available to pxe some with 32bit boot 
images and some with 64 bit images. The reason for this is that PC get re 
purposed onto different domains and sometime architectures.

I can make all the boot images x64 or x86. I can't pxe boot into x86 via uefi 
and then go into a 64 bit boot image.

Using SCCM 2012 R2.

I don't want to use usb/cd boot images.

_____________________________________________________________________
This email has been scanned by the MessageLabs Email Security System on behalf
of Leeds College of Building.
For more information please visit http://www.symanteccloud.com
_____________________________________________________________________

_____________________________________________________________________
This email has been scanned by the MessageLabs Email Security System on behalf
of Leeds College of Building.
For more information please visit http://www.symanteccloud.com
_____________________________________________________________________


_____________________________________________________________________
This email has been scanned by the MessageLabs Email Security System on behalf
of Leeds College of Building.
For more information please visit http://www.symanteccloud.com
_____________________________________________________________________




________________________________

CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by 
legal professional privilege, and is intended only for the person or persons to 
whom it is addressed. If you are not such a person, you are warned that any 
disclosure, copying or dissemination of the information is unauthorised. If you 
have received the transmission in error, please immediately contact this office 
by telephone, fax or email, to inform us of the error and to enable 
arrangements to be made for the destruction of the transmission, or its return 
at our cost. No liability is accepted for any unauthorised use of the 
information contained in this transmission.

_____________________________________________________________________
This email has been scanned by the MessageLabs Email Security System on behalf
of Leeds College of Building.
For more information please visit http://www.symanteccloud.com
_____________________________________________________________________


_____________________________________________________________________
This email has been scanned by the MessageLabs Email Security System on behalf
of Leeds College of Building.
For more information please visit http://www.symanteccloud.com
_____________________________________________________________________


Reply via email to