Also, with notepad++, you can change the formatting from Windows to Linux, to prevent these kind of issues

@tom-elliott Thanks for your reply. I will give the snponly a try.
I wouldnt know where else to ask about iPXE to be honest, as this forum seems to be the most actively using it Hence why I hoped other users already had the same experience perhaps

I can add a static IP, but this info is also not working, I can’t ping the GW or do a DNS lookup.
the network works, otherwise the initial DHCP response would not service the WDS menu (that loads ipxe.efi)

this is my DHCP:

subnet 192.168.1.0 netmask 255.255.252.0 {
dynamic-bootp-lease-length 14400;
authoritative;
max-lease-time 14400;
default-lease-time 14400;
allow unknown-clients;
next-server 192.168.1.14;
range 192.168.1.30 192.168.3.200;
filename “ipxe.efi”;

Hello,
we have a new type of laptop that is unable to configure the network on iPXE: The Lenovo ThinkPad L14

It get’s to this:

Waiting for link-up on net0: OK
Configuring (Net0 <the mac here>) … No configuration methods succeeded

other devices do not have this issue.
I’ve created a new server and upgraded all of FOG, replaced the ipxe.efi with the included file (1.20.1+), but that did not solve this issue.

@Sebastian-Roth hi, yes: they have the same settings, they are all from the same batch (production wise)

I believe the system partition is the issue. I tried imaging on legacy and uefi, issue doesn’t change.

Tried to wipe the disks first, also no change.

Will try the full copy tomorrow, thanks for your suggestion.

Hi All,

So I have a Windows 10 golden image that is being cloned (SIngle Disk, Multi Part, no resize and resize) and restored to the same type of clients.
this is all fine and dandy, the issue is that the devices can’t boot. I receive a BSOD 0xc00000e while booting.

What I accidentally noticed, was that I CAN boot to Windows when plug in a bootable USB, then boot to Network and cancel that boot.

I am able to fix the device by running bcdedit C:\Windows /h E: /f BIOS

any idea how to fix this during the FOG phase? We need to do 300~ devices, so the workaround is not viable…

(i am using FOG 1.5.4)

@Quazz
I thinks that I fixed the issue somewhere along the way and kept on having a different issue on my debug VM, then when I went to check out that issue, I recognized the fact that I already solved it somewhere… The Physical devices also deploy without issue now;

I’ll still need to confirm that the exact issue is solved, so i’ll be creating a few images and see if they restore out of the box.

Thanks again for the quick support, I’ll mark this thread as solved

edit;
(…if I knew how… )

@Quazz
I’m confused.
Ok, so I tried to perform the command myself, it complains that the disk isn’t big enough;
so, I expanded the disk of the VM, and suddenly the image ís able to deploy, in both Debug and non-debug VM’s…

will have to check on the actual devices, since they gave the same issues as the VM

@Fimlore said in Migrated /images folder:

I’ll try the debug option to see what I can find.

the files are clearly there… what does Exit RC 4 mean?

@Quazz

(image is disabled because the team had to finish an order today, so am deploying using the ‘cheat’ I described earlier)

I’ll try the debug option to see what I can find.

@Quazz said in Migrated /images folder:

@Fimlore Yes, the FOS environment mounts your image location to /images on the client.

Does the FOSenv have some sort of shell so that I can troubleshoot while the folder is mounted?