After PXE boot, prompted to remove the CD
Hi, I am seeing an issue where after the PXE boot completes, I choose a task sequence from the Welcome to the Task Sequence Wizard, and then I am prompted to "Remove the CD and do not boot from CD". Well, I never used a CD to boot. The computer then restarts and downloads another boot image. I tried updating the boot image on all distribution points but that didn't help. This started happening recently. In the past, we were never prompted to remove media during a PXE boot. Does anyone know how to resolve this issue? I did some searching but haven't seen anything that matches what I am seeing so far. Thanks, Rob
October 29th, 2012 1:22pm

It happens because the task sequence you chose uses another boot image than was used for pxe boot.
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 1:28pm

I noticed when the PXE boot kicks off, it is downloading my 64-bit boot image instead of 32-bit. I am then choosing a 32-bit image deployment which is why it needs to change out the boot image. Normally, our PXE boot always uses the 32-bit boot image. The 32-bit boot image is what's assigned to all of my task sequences. I'm not sure why it has suddenly decided that it needs to start with the 64-bit boot image. A coworker told me to advertise any task sequence with a 32-bit boot image assigned. That seems to have fixed the problem but I wonder if there is any way to prevent this from happening or causes this problem to occur. Thanks, Rob
October 29th, 2012 1:42pm

probably someone has assigned a x64 boot image to some of the task sequeces advertised to same collection.
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 1:54pm

You can use a 32-bit boot image to deploy a 64-bit image, but not vice versa. Henrik is probably right on about the x64 boot image being assigned to the Task Sequence. Check the properties of the Task Sequence (properties - not edit) and see what boot image is assigned.
October 29th, 2012 3:00pm

The best way to prevent this from happening is to only use a single boot image for all of your task sequences. What is happening is that if there are multiple possible applicable task sequences when PXE booting, ConfigMgr must pick one. Thus, it picks the one associated with the task sequence with the highest advert ID (which generally translates into the last TS advertised).Jason | http://blog.configmgrftw.com
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 3:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics