@sebastian-roth I hadn’t thought through that iPXE development isn’t specifically related to FOG. I think it’d be worthwhile to inform.

Server

• FOG Version: 1.3.5
• OS: Ubuntu

Client

• Service Version: 0.11.11
• OS: Windows 10 1703

Description

I’m seeing an issue with the exit to hard drive after Windows 10 1703. We recently updatedto Windows 10 1703 in a lab, which were configured to boot to PXE by default. After the update, the computers sat at “Boot to SAN 0x80”. This wasn’t post-deploy. I could re-deploy a 1607 image and it would continue to boot just fine. I could also change the boot order or select booting directly from the HD without a problem.

I decided to take one of our test computers and create a fresh build with 1703 without going through the upgrade. I experienced the same trouble. After some troubleshooting I found that changing the exit type from SANBOOT to GRUB_FIRST_HDD seems to work ok.

It’s worth noting, though that the hardware on these didn’t change, only the Windows builds.##### Server

• FOG Version:
• OS:

Client

• Service Version:
• OS:

Description

Server

• FOG Version: 1.3.5
• OS: Ubuntu

Client

• Service Version: 0.11.11
• OS: Windows 10 1703

Hardware

Manufacturer: Dell
Model: OptiPlex 7040
BIOS: A01

Description

I’m seeing an issue with the exit to hard drive after Windows 10 1703. We recently updatedto Windows 10 1703 in a lab, which were configured to boot to PXE by default. After the update, the computers sat at “Boot to SAN 0x80”. This wasn’t post-deploy. I could re-deploy a 1604 image and it would continue to boot just fine. I could also change the boot order or select booting directly from the HD without a problem.

I decided to take one of our test computers and create a fresh build with 1703 without going through the upgrade. I experienced the same trouble. After some troubleshooting I found that changing the exit type from SANBOOT to GRUB_FIRST_HDD seems to work ok.

It’s worth noting, though that the hardware on these didn’t change, only the Windows builds. I also realize this issue seems similar to https://forums.fogproject.org/topic/10386/windows-10-1703-system-error-on-boot, but I wanted to make the point that this wasn’t isolated to being part of the sysprepping process.