Ghost Solution Suite

 View Only
  • 1.  PXE Boot File

    Posted Mar 03, 2016 12:03 PM

    We are testing migrating from GSS 2.5 to 3.0 and previously we had a DHCP option pointed to a bootfile which in turn display the PXE boot menu where we would push or capture images. DHCP is not on the same server as GSS/PXE etc. so we are using the 3rd option in the PXE configuration of  GSS 3.0. We are having two issue, one we get PXE-E53: No boot filename received. We are unclear what bootfile name to put in our DHCP options (previously it was something like mbr.PXE). The second issue is that when imaging from a "job" the target machine reboots but doesn't (network boot). When done manually you have to interrupt the target machines boot by pressing F12 then choose onboard network device. How do we pass the F12 automatically when trying to image from a job so that no user intervention is needed when we image 40-50 stations at once?

     

    Our previous setup included a third party TFTP application and GSS 2.5



  • 2.  RE: PXE Boot File

    Posted Mar 03, 2016 02:06 PM

    Update:

     

    We have resolved the TFTP boot issue but still are unclear on how to pass the F12 during a image "job" from the console.



  • 3.  RE: PXE Boot File

    Posted Mar 05, 2016 05:44 AM
    You have to change the boot order in the BIOS so that Network Boot is higher than Hard Disk. You can often do this remotely with BIOS management tools from the hardware vendor.