Niall Brady confirmed this a few days ago as well (see attached e-mail). I
believe this to be correct, without having independently verified it.
Cheers,
Trevor Sullivan
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com]
On Behalf Of Chris Nackers
Sent: Friday, March 14, 2014 10:30 AM
To: mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] Post R2 Upgrade, PXE and default boot image selection
If memory serves, the boot image delivered by PXE will be the boot image
assigned to the most recent Task Sequence deployed.
Chris Nackers
Microsoft MVP - Enterprise Client Management
Email: <mailto:ch...@nackersconsulting.com> ch...@nackersconsulting.com
Nackers Consulting Services, LLC
From: listsad...@lists.myitforum.com <mailto:listsad...@lists.myitforum.com>
[mailto:listsad...@lists.myitforum.com] On Behalf Of Brian McDonald
Sent: Friday, March 14, 2014 10:05 AM
To: mdtosd@lists.myitforum.com <mailto:mdtosd@lists.myitforum.com>
Subject: [MDT-OSD] Post R2 Upgrade, PXE and default boot image selection
I have recently upgraded to R2 and have some questions around the boot
images and task sequences. I previously came from an SP1 CU3 environment. I
had full support setup for Windows 7 in my environment. In my environment I
was using the default boot image created during the initial SCCM 2012 SP1
installation process. This boot image is now my default boot image for PXE.
I recently created a new WinPE 5.0 boot image that I'd like to use for
testing Windows 8.1 deployments. However, I do not want to break my current
PXE process as I have technicians actively deploying Windows 7 in my
environment.
What options do I have to setup my new WinPE 5.0 boot image and still allow
my techs to continue to deploy Win7 with the current boot image?
How do I control which boot image PXE will use? Is it the most recently
deployed boot image? Can I enable support so we can pick and choose which
boot image to use? IF so, how?
Thanks,
Brian
--- Begin Message ---
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: ms...@lists.myitforum.com <mailto:ms...@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: ms...@lists.myitforum.com <mailto:ms...@lists.myitforum.com>
Im trying to boot a 32bit uefi boot image. The pc has a 64bit processor.
The problem is the pcs were imaged using a 32 bit boot image to deploy a 64
bit OS. The pcs 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 cant pxe boot into x86 via
uefi and then go into a 64 bit boot image.
Using SCCM 2012 R2.
I dont 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
_____________________________________________________________________
--- End Message ---
