@george1421 pls ignore, internal network issue. thank you.

@george1421 pls ignore, internal network issue. thank you.

@razercortex pls disregard. internal network issue.

@razercortex I’m looking to set this up with winpe but the [link](wget http://git.ipxe.org/releases/wimboot/wimboot-latest.zip) is no longer valid. Do you know if there is an updated link?

@george1421 hello. I’m trying your article in the following blog. I’m at step 3 where you try and get the wimboot file by running the following command but it looks like it is no longer a valid path:

wget http://git.ipxe.org/releases/wimboot/wimboot-latest.zip

what kind of files am I looking for? Can I use the existing ipxe files used by the fog server?

Hello,

We have many systems with a similar configuration (1TB nvme system drive and 2TB nvme data drive). When capturing and deploying images, we are having the issue where sometimes the image is deployed onto the 1TB (as intended) other times the image is deployed onto the 2TB data drive. I’ve tried Single Disk - Resizable images and Multiple Partition Image - All Disks (Not Resizable) images. I’ve also tried specifying /dev/nvme0n1 in the Host Primary Disk but this does not resolve the issue. I read that the reason why this happens is because linux enumerates nvme drives differently from sda/sdb drives (my understanding was that linux would randomly select which drive will be nvme0n1 on boot); I confirmed this by booting into the fog menu checking the drive, rebooting and verifying that the first time /dev/nvme0n1 was the 1TB drive and the second time /dev/nvme0n1 was the 2TB drive. Is there any way we could reliably target the drive such that upon capture, /dev/nvme0n1 is the 1TB and upon deployment /dev/nvme0n1 is also recognized as the 1TB drive? Thank you very much in advance.