@zclift15 Any news on this?

@zclift15 As well read through this: https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

@Sebastian-Roth I had the same errot as @zclift15 but it seems to have fixed itself perhaps it just took a minute for the change of primary disk to trickle down

@Tom-Elliott looks like the password was different than in the setting gonna change it to that and i will let you know

There is a wiki page to reset the default fog admin’s password. Its here: https://wiki.fogproject.org/wiki/index.php/Reset_WebUI_FOG_password

I would also look at both the apache and php-fpm’s log files in /var/logs directory to see if there is any error messages listed in there.

@zclift15 Just for clarity one downed node caused all replication to fail?

Works fine thank you for your help!

Are you sysprepping? Was the reference machine previously joined to the domain?

For your images, you should keep them pure - never capture a dirty image because it only causes problems. Pure means NEVER having been on the domain before, and as lean & clean as possible meaning not using old images to make new ones - keep your old images as backups, but build from scratch (installation media) every time - always delete old partitions and remake them, and capture new images.

At my old job, I would include month and year (not day) in my image names.

@george1421 said in Remote node on different DHCP and subnet:

Not being able to alter the remote dhcp server is a problem but you can fix if you install dnsmasq on your storage node. Dnsmasq will then supply the pxe boot options you need.

It wouldn’t be a problem if the DHCP server didn’t have any 066/067 options. In this case it does. I think it’ll be hit or miss for proxy-dhcp working in this case. And if it works, it might intermittently work.

@george1421 Thanks for all your help!