SCCM OSD: push X86 image on X64 Machine

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SCCM OSD: push X86 image on X64 Machine

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Operating System Deployment >> SCCM OSD: push X86 image on X64 Machine

Page: [1]

Message

<< Older Topic Newer Topic >>

SCCM OSD: push X86 image on X64 Machine - 4/11/2008 5:54:04 PM

betemtl

Posts: 23
Score: 0
Joined: 4/10/2008
Status: offline

I have Dell T3400 with x64 architected. I am trying to push a x86 image on it but it give me this error from the ConfigMgr PXE service point log files:

Message id 6321: The SMS PXE Service Point does not have a boot image matching the processor architetcure of the PXE booting device.

My image is working properly on x86 architected dell machine. I am wondering if there is anyway to force that x64 machine to get the x86 image.

< Message edited by betemtl -- 4/11/2008 5:56:11 PM >

Post #: 1

RE: SCCM OSD: push X86 image on X64 Machine - 4/14/2008 9:28:13 AM

jsandys

Posts: 207
Score: 13
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

Just make the x64 boot image available. I'm doing this as I write this. Make sure that your Task Sequence uses the x86 boot image though. The initial PXE boot will be to the x64 image and then it will reboot into the x86 image.

_____________________________

Jason
________________________________________
http://ihaveablog.wordpress.com

(in reply to betemtl)

Post #: 2

RE: SCCM OSD: push X86 image on X64 Machine - 4/17/2008 4:45:31 PM

betemtl

Posts: 23
Score: 0
Joined: 4/10/2008
Status: offline

Hello jsandys,

Could you please clarify that more? is it working properly with you?

What I have now is an image for x86 XP wiondows , captured using x64 boot image. Then in my Task Sequence I used x64 boot image to deploy it. I keep getting the following errors: 80070057 & 80070032 exactly after the format ends.

Any idea about that? is there something wrong with my proccess?

< Message edited by betemtl -- 4/17/2008 4:46:27 PM >

(in reply to jsandys)

Post #: 3

RE: SCCM OSD: push X86 image on X64 Machine - 4/17/2008 4:50:16 PM

jsandys

Posts: 207
Score: 13
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

Your task sequence(s) for deploying and capturing the x86 XP image should use the x86 boot image. You can right click on the task sequence, select properties, go to the advanced tab to change this. The x64 boot is needed only to initially boot the system via PXE and should not be used for your task sequences.

_____________________________

Jason
________________________________________
http://ihaveablog.wordpress.com

(in reply to betemtl)

Post #: 4

RE: SCCM OSD: push X86 image on X64 Machine - 4/18/2008 10:37:27 AM

betemtl

Posts: 23
Score: 0
Joined: 4/10/2008
Status: offline

and how to force the system to boot via PXE using the x64 boot if it is not included in the capture or the task sequence?

what I am getting now is: "" Selected boot device not available"

thanks

(in reply to jsandys)

Post #: 5

RE: SCCM OSD: push X86 image on X64 Machine - 4/18/2008 10:57:16 AM 1 votes

jsandys

Posts: 207
Score: 13
Joined: 3/24/2005
From: San Antonio, TX
Status: offline

Make sure that both boot images (x64 and x86) are available on the PXE distribution point and the normal distribution point. Initially, a 64 bit system will boot into the x64 boot image but will transfer control to the x86 boot image when necessary to deploy the x86 OS image.

_____________________________

Jason
________________________________________
http://ihaveablog.wordpress.com

(in reply to betemtl)

Post #: 6

RE: SCCM OSD: push X86 image on X64 Machine - 4/28/2008 2:11:16 PM

betemtl

Posts: 23
Score: 0
Joined: 4/10/2008
Status: offline

Thanks for the tip. It is working properly now

(in reply to jsandys)

Post #: 7