@Tom-Elliott yes, I checked the services, they all running.
systemctl status nfs-server
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; preset: enabled)
Drop-In: /run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: active (exited) since Tue 2026-06-30 09:06:50 UTC; 17h ago
Process: 4995 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
Process: 4997 ExecStart=/usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS)
Main PID: 4997 (code=exited, status=0/SUCCESS)
CPU: 10ms

Jun 30 09:06:49 fog-svr.local systemd[1]: Starting nfs-server.service - NFS server and services…
Jun 30 09:06:50 fog-svr.local systemd[1]: Finished nfs-server.service - NFS server and services.

rpcinfo -p 192.168.13.99
192.168.13.99 mountd
rpcinfo -t 192.168.13.99 nfs
rpcin program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 50174 status
100024 1 tcp 34667 status
100005 1 tcp 20048 mountd
100005 2 tcp 20048 mountd
100005 3 tcp 20048 mountd
100003 3 tcp 2049 nfs
100227 3 tcp 2049 nfs_acl
100021 1 udp 38178 nlockmgr
100021 3 udp 38178 nlockmgr
100021 4 udp 38178 nlockmgr
100021 1 tcp 37227 nlockmgr
100021 3 tcp 37227 nlockmgr
100021 4 tcp 37227 nlockmgr

I deployed the image using a VM on Proxmox and it worked, but with a phisical PC it gives the error like above. All are on the same VLAN.

@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 …

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

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

@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!

@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.

@Tom-Elliott
Tom—I just can’t get this to work. I’ve been trying to set up a multicast with 6 PCs here: PC013CAD through PC018CAD. They’re all identical devices, and sometimes one set works, then the other. I think the problem is somehow with the client. In this log, I automatically installed the client after cloning (c:\Windows\setup\ … ), then uninstalled it and reinstalled it—but I still can’t get a connection.
01.07.2026 23:39:12 Main Overriding exception handling
01.07.2026 23:39:12 Main Bootstrapping Zazzles
01.07.2026 23:39:12 Controller Initialize
01.07.2026 23:39:12 Controller Start

01.07.2026 23:39:12 Service Starting service
01.07.2026 23:39:14 Bus Became bus server
01.07.2026 23:39:14 Bus Emmiting message on channel: Status
01.07.2026 23:39:14 Service Invoking early JIT compilation on needed binaries

Authentication--------------------------------

01.07.2026 23:39:15 Client-Info Version: 0.13.0
01.07.2026 23:39:15 Client-Info OS: Windows
01.07.2026 23:39:15 Middleware::Authentication Waiting for authentication timeout to pass
01.07.2026 23:39:15 Middleware::Communication Download: http://192.168.0.196/fog/management/other/ssl/srvpublic.crt
01.07.2026 23:39:15 Middleware::Authentication Cert OK
01.07.2026 23:39:15 Middleware::Authentication No token found at C:\Program Files (x86)\FOG\token.dat, this is expected if the client has not authenticated before
01.07.2026 23:39:15 Middleware::Authentication ERROR: Could not get security token
01.07.2026 23:39:15 Middleware::Authentication ERROR: Die Datei “C:\Program Files (x86)\FOG\token.dat” konnte nicht gefunden werden.
01.07.2026 23:39:15 Middleware::Communication POST URL: http://192.168.0.196/fog/management/index.php?sub=requestClientInfo&authorize&newService
01.07.2026 23:39:15 Middleware::Communication ERROR: Failed to POST data
01.07.2026 23:39:15 Middleware::Communication ERROR: Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.
01.07.2026 23:39:15 Middleware::Response Success

Authentication--------------------------------

01.07.2026 23:39:15 Client-Info Version: 0.13.0
01.07.2026 23:39:15 Client-Info OS: Windows
01.07.2026 23:39:15 Middleware::Authentication Waiting for authentication timeout to pass

@heix75 No.

Not because it’s not a QOL improvement (it is) but because what you see in 1.5.x.x is NOT what is the end goal.

If you want to see what the UX is moving toward install the version of FOG on working-1.6.

You’ll understand (I hope), then, why I’m saying this.

update the kernals on fog server / nodes

So I am alone ?