We have a mix of client computers that have either the older type BIOS or the new x64 architecture BIOS that requires a 64-bit boot image. If I remove the x86 boot image from the distribution points I can image these newer machines just fine, but when both the x86 and x64 boot images are distributed it defaults to using the x86 boot image during PXE. This kills the Task Sequence and reboots the machine. We have multiple imaging Task Sequences advertised to all our computers at the moment, with some using the 32bit and other the 64bit boot image.

Hi there Enten Do the 64 bit systems get installed OK? If so then you should be good to go. The selection of which boot image that will be used is made in the advertisement of the task sequence so if you only have one TS then you can only use one boot image. The way that is usual is to have BOTH the 64bit and 32bit boot images deployed so that a system can select the most appropriate boot image and then to use just the 32 bit boot image which can install both 32 and 64 bit Windows

Oh, I just re-read your post. The 32 bit boot image fails. At what stage of the task sequence?

It won't get an IP address and throws these errors in the smsts.log file: Failed to download pxe variable file. Code(0x00000001) PxeGetPxeData failed with 0x80004005 The 64bit computers are loading the 32bit boot image to get into WinPE, which doesn't make sense because I advertised the proper Task Sequences with 64-bit boot images.

The boot image that gets initially loaded is the boot image which was advertised the last to the collection. Maybe it's possible to create a different collection for x64 systems? Then you can seperate your task sequences. http://systemmanagement.ro/blog/2009/03/16/create-a-collection-with-all-x64-systems/ My blogs: Henk's blog and Virtuall | Follow Me on: Twitter | View My Profile on: LinkedIn I did split them into separate collections to help with this issue, but new devices are still hitting the All Unknown Computers collection with both boot images being advertised to it. I'm going to try making the x64 boot image as the last advertised boot image.