[SCCM 2007] x86 PC only wants to boot x64 WinPE

[Ric_]

I've got a single PC that I'm trying to build but it only seems to want to boot the x64 boot image.

The PC is correctly identified as being x86 prior to loading the image and then, of course, it bombs out.

I have the PC in a collection that only has an x86 task sequence applied to it and I've even updated the BIOS in a hope to fix the problem.

Any ideas guys?

[sparkeh]

Just wondering if at any point you advertised a task sequence with an x64 boot image to that collection?
Reason I ask is that when you advertise more than one task sequence to a collection, the last boot image architecture is used.

Edit: Also is the machine already in SCCM or are you using the unknown computer feature?

[SYNACK]

Are you able to track whether it is being identified correctly by SCCM, if it is being mistaken for another machine perhaps this is confusing it, same UUIDs or something. If it is IDed by MAC address this rules it out though it may be an idea to recreate the computer object incase it has been corrupted.

You could also packet sniff the PC while it is attempting to boot using wireshark on a different computer and a hub (or switch with mirror port turned on) to see exactly what it is requesting.

[sparkeh]

Are you able to track whether it is being identified correctly by SCCM, if it is being mistaken for another machine perhaps this is confusing it, same UUIDs or something. If it is IDed by MAC address this rules it out though it may be an idea to recreate the computer object incase it has been corrupted.

You could also packet sniff the PC while it is attempting to boot using wireshark on a different computer and a hub (or switch with mirror port turned on) to see exactly what it is requesting.

As I understand the PC doesn't request the boot image, rather the boot image selected in the task sequence advertised to the collection is sent to the machine. If you are using the unknown computer feature of R2 then this complicates matters slightly, with this you should create two collections, one for x86 and one for x64 so the that 'last advertised TS' issue doesn't apply.
I would rather think that the problem is related to the task sequences than the machine itself.

Edit: actually you should always have two locations to avoid the last advertised TS issue.

[Ric_]

Forget it... I was being stoopid and had assigned the wrong boot image to my task sequence