@george1421 " That is fine, but we need to be clear you are not using FOG as it was intended"

Yes we are intended to use the FOG as our prior imaging/capturing server instead our WDS. We had to much issues lately with our WDS so i want to get it out off our network. I have worked with FOG earlier in schools where i had it deployed and works fine many years for there needs, but know with my other job we need something different.

Let me explain :
Current situation : We use WDS for imaging and capture beside that we run a special menu on the ipxe server.

New situation : Fog server for imaging and capture and an add advanced menu to push the same menu of the old ipxe server.

Question is there a way to hold the old ipxe server and remove the WDS and combine it with the new fog server?

These are the ip :
WDS server 10.50.10.20
IPXE Server 10.50.10.21
FOG Server 10.50.10.30

I want to keep the IPXE Server as the default one and when my tech guys want to deploy or capture a image to can boot to the FOG server and do there thing.

I have tried to setup the situation i was intended to implement but it doesn’t work it give me issues when i want to deploy or capture a image.

I can give you my menu settings so you can take a look from the IPXE Server.

Thx,

Br,

Stijn

Hi,

Installed the Fog Server as our new deployment server instead off WDS.

Now i have added in the advanced menu iscsi boot :
sanboot --no-describe iscsi:10.50.10.25::::iqn.2022-03:dss.target1
This one boots to a lun with some test scripts on it but when you leave the shell untouched it reboots after +/- 5 minutes…

When you boot to a live OS like mint and you leave it untouched we have no reboots.

I have tried to change the watchdog to 0 like here : https://forums.passmark.com/memtest86/42356-system-reset-occuring-5-min-after-booting-memtest86-site-edition-pxe-network-boot

Any idea?

Stijn