I work in a two site school, comunicating with a VPN.
On the first site I have the master node, and a storage node.
The master one has not a lot of space so I disable his storage and I’m using only the sotrage node, with the flag “is master node” yes.
We have the same type of notebook also in the second site, but deploy an image over VPN is too long for our need.
So I want to setup a storage node on the second site that can take his time to replicate image from the master, and then deploy from this storage.
How to setup this solution?
I’ve made some work on this, but replication seems to hang many times and I’ve no idea how to choose the second storage node as source for deploing on the second site.
Maybe I’ve made some conceptual mistake.

@Quazz I know that I can capture and deploy UEFI images in Legacy mode, but I have to go in front of the PC turn it on, go in setup page, set network boot, then deploy, then go again in setup page, set windows boot manager … and do it 300 times.
So at the moment I’ve made a Legacy installation image, and I leave all pc in network boot, so when I want to deploy I just select the group and fire a multicast deploy.
I’m working on YASHI for booting in legacy mode I’ve ask to their support.

@george1421 Here we are, soon than I thought.
I’ve read the tutorial and I open pcap with wireshark … and the winner is …
Hey I’m a OLD Legacy type 0000
It’s an HP-8300 AIO.
As Quazz said, I need to find a way for UEFI LAN BOOT, maybe in this machine I can find the option because it’s not so old, but I’m afraid that in the others machines no uefi lan boot is possible.
Not so bad, I just install windows 10 in Legacy mode on MBR partition style.
It’s wrong? it’s unsafe?

@Quazz, you said something close to my situation.
There’s only a little difference … not “some” machine … ALL my machine haven’t uefi network boot on none of them, if I set UEFI only or something similar, simply I don’t have any LAN option in boot sequence.
I thougth that it may be the problem but I also assumed … in 2018 with UEFI everywhere how is possible that PXE is possible only in Legacy mode!!!
It’s a nonsense … but it seems to be the reality.
In that case … what can I do? is possible to do a legacy network boot and then a uefi boot?

@george1421 Thank’s for your answer, I think you catch the problem … is number 1, I have to see how my machine say “hey” to DHCP but I hadn’t no idea on how to do it, now I’ll take a look on the tutorial you linked.
I have no much time to spend now on this topic because I have to deploy 300 machines in few days so probably I’ll not answer soon, but for sure I’m not forgetting.
Thank’s again.
Marco Moraschi

Hello, I’m using Fog for managing some labs in my school.
I’ve a Linux DHCP and I make the setup for UEFI and BIOS.
The problems comes with win 10, capture and deploy are fine but if I leave pxe before windows boot manager in the boot sequence on the machines, windows just doesn’t boot.
I’ve read a lot of thread in this forum and I tried all kind of solution without solve my problem so I dig in my situation.
I’ve used 3 kind of machines Fujitsu P2540, Fujitsu P400, and Yashi AIO. ANY of these machines with ANY combination of boot option (Legacy first, Uefi First, CSM and so on) are always seen by DHCP as Legacy. How can I say?

class "UEFI-64-3" {
                match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
                filename "undionly.gino";
                }
class "Legacy" {
                match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
                filename "ipxe.kpxe";

Every entry but Legacy has a wrong filename, I’ve double checked and I can say that I was not able to do anything about it, all machines are seen as Legacy.
Then I’ve looked on FOG configuration tweaking EXIT mode.
As expected ANY type of machine with ANY type of setup settings are seen as BIOS …
How can I say? As before I tried all kind of combination but as I modify BIOS EXIT MODE, I see difference in boot behaviour, if I modify EFI Exit mode my behaviour doesn’t change.
Solution by now was installing windows 10 in legacy mode on MBR partition so with BIOS EXIT = SANBOOT all was working.
BUT
newer machines as YASHI AIO doesn’t have any option for legacy boot o CSM so is not possible to install windows that way.
So I need to solve my UEFI problems.
Has anyone some good ideas?

Thank’s Marco Moraschi
(as you can see I’m not english, so please be kind for my writing)