none
Legacy PXE Boot x64 RRS feed

  • Question

  • HI,

    I'm having some problems getting Laptops to PXE boot into an x64 task sequence.  We have some laptops that are being upgraded to a new Window 10 SOE, part of this upgrade is to switch them from Legacy BIOS to UEFI via a BIOS script, however we're having a problem that the Legacy BIOS is not finding the X64 boot image and so is not completing the Windows 10 Task Sequence, it's only seeing the X86 version (We need it to be x64 in order for the BIOS upgrade script to work) 

    Is there a trick to get Legacy BIOS to boot into a x64 task sequence?

    Any help appreciated. 



    • Edited by Swamps Wednesday, December 11, 2019 5:58 AM
    Wednesday, December 11, 2019 5:58 AM

All replies

  • Which boot image is assigned to the task sequence? Whichever one it is is the one that the system must be running for the TS to kick off into. If this isn't the initial image delivered to the client, the first thing the task sequence does is download the assigned boot image, stage it, and then reboot the system into that boot image. Thus, unless you've incorrectly assigned the boot image, the task sequence engine will automatically sort this out.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, December 11, 2019 12:59 PM
  • Hi,

    It seems there is no update for a couple of days. May we know the current status of the problem? Did you check the boot image as Jason said?

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 16, 2019 8:55 AM
  • I identified the issues. It seems that unless the boot image is assigned to the unknown computers collection it' snot available to PXE boot. Even though we don't build machines using that collection.  There must be something inbuilt which requires the image to be deployed to that collection.
    Monday, December 16, 2019 8:24 PM
  • Sorry, but this doesn't really make sense. You do not ever assign or deploy boot images or any images to anything. You deploy task sequences and you only need to deploy them to the unknown computers collection if you are intended to use unknown computer support.

    So, no, there's nothing in-built around this whatsoever.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, December 17, 2019 12:02 AM
  • Sorry, yes, I meant We had to deploy the task sequence to the unknown computers before any computer would see the boot image. 
    Tuesday, December 17, 2019 12:38 AM
  • Regardless, unless you are PXE booting unknown systems, this is irrelevant. My guess here is that the systems were in fact unknown. This is easily confirmed by reviewing the smspxe.log or smsts.log.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, December 17, 2019 2:24 AM
  • Hi,

    Since you have identified the issues. It can be considered the question is solved. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    Have some problems get Laptops to PXE boot into an x64 task sequence.

    Possible Cause:
    ===================
    It is possiable that the systems were in fact unknown.

    Solution:
    ===================
    Deploy the task sequence to unknown computer collection.

    Regards,
    Allen

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, December 18, 2019 9:40 AM