Hi,I have a question concerning boot images. This is what i know:a. The boot image that gets loaded initially when starting a machine which is member of a collection with multiple task sequences advertised to it, is the boot image defined on the last advertised task sequenceb. When the loaded boot image is different compared to the boot image defined in the task sequence which you want to execute, that boot image is first downloaded locally and that boot image is booted after you press finish or restart.Context:I'm using SCCM 2007 R2 which as far as i know uses the WAIK 1.1. boot images. I always believed that a new feature of these boot images would be that you can start an x64 installation from an x86 boot image. But for some sort of reason this doesn't work in SCCM. I currently haveone TS whichcan install an x86 and x64 OSes with a x86 boot image defined, and made sure that that TS is the last advertised TS on the collection.My smsts.log file displays the following: The detected setup program architecture does not match the current boot image. You must correct your task sequence so that the installation package matches the boot image.The WAIK 1.1. User Guide states though: Only x64 (AMD64) Windows editions are supported from 32-bit preinstallation environments for cross-architecture deployments. Cross-platform deployments of Itanium-based Windows images are not supported. Additionally, deploying a 32-bit image from a 64-bit preinstallation environment is not currently supported.My ideas about this issue for now:Either the WAIK 1.1 boot images can install an x64 OS from an x86 boot image, but SCCM doesn't support this yet, or maybe i'm overseeing something.Questions:Anyone have the same issue? And how do you handle TS in combination with collections? Hope someone can point me in the right direction, Regards, Kennethhttp://www.techlog.org | http://www.activewin.com

Kenneth, The only thing I can think of is creating 2 task sequences.Create one using ax64 boot imageand one using x86 boot image. Configure both advertisments to only run on their respective system (x86 or x64)and advertise them both to the collection. Thats the only thing that comes to mind. Paul

Hi Paul,Thanks for your answer.At this moment i've devided my collections in x86 and x64 and advertised task sequences with different boot images to it. Eventually i want one task sequence though, perhaps someone else can tell more about this issue.Regards,Kennethhttp://www.techlog.org | http://www.activewin.com

The ApplyOS action has a check that compares the architecture of the boot image and the architecture of the OS that it needs to apply. It insists that both architectures have to be the same.So, to deploy a 64-bit OS, you need a TS that has a 64-bit boot image associated with it. And to deploy a 32-bit OS, you need another TS that has a 32-bit boot image associated with it.

I disagree with Kerwin. We have been deploying hundreds of Windows 2008 R2 (x64 only) images in OSD using a 32-bit winPE iso. Works fine.