@Tom-Elliott
fyi:
again no interaction with the web interface - today another PC lost the hostDevice.
root@fog:~/NVME_Problem/hostDevice# ./anzeigen
±---------+
| hostName |
±---------+
| PC102CAD |
±---------+
f48d8e63-b439-411c-8caa-e64d1764887a-grafik.png
Yesterday it was PC002CAD today PC102CAD.

@Tom-Elliott said in Windows 11 | 65x HP Z2 Tower G1i | UPDATE -:

dev-branch

ok
Your version of FOG is up to date.
You’re running the latest dev-branch version: 1.5.10.1858

@Tom-Elliott

I pulled latest dev-branch version 1.5.10.1856, re-run installer and snapins are working again.

Thank you very much for help.

@GregorS I have 3 Dell Models that are also doing this, but I will try the change to DHCP Boot file.

I will post back when I have an update.

Thanks!

@Chandlerbing Can you do a look for all files that contain:

grep -r 'display_errors' /etc | grep -v '#'

This should only display things where display_errors is defined directly.

I suspect there’s one that is doing this for you natively.

We can mark this closed. Turns out it was a old/bad snapin package on the old server. I set up Fog with a new DB and everything worked fine. Once I removed the snapins and exported and imported the DB again it all worked as expected.

Thanks for the help.

@Tom-Elliott just bumping this. Is there anything I can do to help? I have some experience building Linux kernels from a few years ago.

@Tom-Elliott
This is resolved in latest dev-branch version: 1.5.10.1853
Thanks.

@Mr_K
Thanks for the help Tom. You got me pointed in the right direction. Everything is working now.

I did a complete Ubnutu and fog fresh install to make sure I wasn’t missing anything and noticed during the installation it was grabbing my WAN IP as the fog server IP and then somehow changing the fog server IP to my LAN IP. So when I clicked on the link from the terminal after it had finished it was 192.168.1.148 however everything was setup “certs, storage Ipxe” ect as my WAN IP 20.21.X.X.

All I had to do was just change the fog settings so the IP’s matched re ran the installer to grab the new files and everything is running perfect now.

@Tom-Elliott Thanks for the clarification! I’ll try upgrading to the latest stable version, I was planning on doing this anyway.

I’ll look into the Persistent Groups plugin and see how it works!

@jmeyer Now worries, it gets a little confusing, and sorry for the late reply again, I was on Holiday last week so didn’t check the forums for a while. I believe that shim should already be signed and you should be able to use it. You should already have the signed shim package installed which would provide that file I would imagine, though I’m not familiar with Debian to say that with any certainty. However, that shim would need to be copied into the /tftpboot folder and it’s permissions changed accordingly. Remember to renamed your ipxe binary to grubx64.efi or whatever the Debian shim is programmed to automatically chainload.

@vanfifty1
I have some simelar Problems maby read the post
https://forums.fogproject.org/topic/18157/windows-11-65x-hp-z2-tower-g1i-update/2
My problem is/was that Fog uses sometimes the wrong nvme …

Fresh install using ver1.5.10.1826

Works perfectly. Can register hosts as normal

Maybe a bug with 1.6.0… hopefully if anyone else experiences this issue this might help

@bruno67

Are you sysprepping the image with all OOBE options set to be skipped before capturing it with FOG?

@gabriel-pissoto

I often record this with a phone then you can pick out the error in that micro flash of text.
I think most of the time picking a different X.pxe file resolves this for me.

@Nono Without going through the web interface you can check the file in /var/www/fog/lib/fog/system.class.php.
Toward the bottom of the file there is a line that start with define('FOG_VERSION'

So I am alone ?