@george1421 I should note, that we don’t use FOG client and storage nodes or anything, so it literally only does network boot menu and imaging, which might explain it a bit.

@WourN That’s correct.

@sbenson Maybe the FOG setting, FOG Linux Service Sleep times can be helpful. You could set it to 24hours. Then you only need to run the cron once to restart at for eg 11PM

@Warrender6 This looks like a very old generated file.

At any rate, try adding authoritative; before the subnet declaration.

Hi, you need to insert the entire menu data at FOG Settings -> iPXE Boot Menu -> Advanced Configuration options

Here’s an example that I’m using:

:urls
set msdart-url http://192.168.1.155/2-MSDART
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item msdart6x86 Microsoft DaRT for Windows Vista 32bit
item msdart6x64 Microsoft DaRT for Windows Vista 64bit
item msdart7x86 Microsoft DaRT for Windows 7 32bit
item msdart7x64 Microsoft DaRT for Windows 7 64bit
item msdart81x86 Microsoft DaRT for Windows 8.1 32bit
item msdart81x64 Microsoft DaRT for Windows 8.1 64bit
item fog.return Return to previous menu
choose --default fog.local --timeout 5000000 target && goto ${target}
:fog.local
sanboot --no-describe --drive 0x80 || goto MENU
:msdart6x86
initrd ${msdart-url}/MSDaRT60x86.iso
chain memdisk iso raw
:msdart6x64
initrd ${msdart-url}/MSDaRT60x64.iso
chain memdisk iso raw
:msdart7x86
initrd ${msdart-url}/MSDaRT70x86.iso
chain memdisk iso raw
:msdart7x64
initrd ${msdart-url}/MSDaRT70x64.iso
chain memdisk iso raw
:msdart81x86
initrd ${msdart-url}/MSDaRT8.1x86.iso
chain memdisk iso raw
:msdart81x64
initrd ${msdart-url}/MSDaRT8.1x64.iso
chain memdisk iso raw
:fog.return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU

Check Advanced Menu Login at iPXE Boot Menu as well.

Advanced menu login should stay on show on : Advanced Login required

With the configuration of:

login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param advLog 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme

@abos_systemax Imo, this indicates that the drive itself has issues, bad sectors most likely.

If you want certain things to run on only certain hosts, you need to either create a very intelligent script or use snapins which are already designed for that.

@sjensen Try

sudo rm -rf /var/www/html/fog && sudo rm -rf /var/www/fog

Then rerun the installer with ./installfog.sh -y

What’s the output of cat /etc/exports ?

If boot from hard drive says chainloading failed, I think you need to change the exit type.

As for the script, I ran it through shellcheck and it notes several problems.

https://www.shellcheck.net/

Not all of those are necessarily faults (since it can’t be aware of variables assigned outside of the script), but some do stand out.

One small thing I noticed is on line 24 where there’s umount ntf instead of umount ntfs

Also, on line 77 you only check for one variation of ntfs/Windows/Setup/Scripts, but I’ve seen at the very least a ntfs/Windows/Setup/scripts as well.

DEFAULT vesamenu.c32
MENU TITLE Fog Reimage Menu
MENU COLOR TITLE        1;36;44    #ffffffff #00000000 std
LABEL iPXE Boot
MENU DEFAULT
KERNEL ipxe.krn
APPEND dhcp && chain http://x.x.x.x/fog/service/ipxe/boot.php?mac=${net0/mac}
PROMPT 0
TIMEOUT 1

Pulled this from wiki, feel free to try

https://wiki.fogproject.org/wiki/index.php?title=Chainloading_PXE_to_iPXE_using_pxelinux.0

Afaik, aside from updating the Storage node, you also need to update the /opt/fog/.fogsettings file with the correct path and then rerun the installer. (not necessarily addressed at anyone in particular, more for people who might run into similar problems)

Linux distribution and version?

Can you run the output of the following command (start in the folder that you would use git pull in) and paste the results here:

tail bin/error_logs/fog_error_1.3.4(press tab here)

@palloquin So I’m guessing you’re on Centos 7.

You will have to disable Selinux for now, there is no working policy made available for it yet.

sed -i 's/SELINUX=enforcing/SELINUX=disabled/' /etc/sysconfig/selinux
sed -i 's/SELINUX=enforcing/SELINUX=disabled/' /etc/selinux/config
service iptables stop
chkconfig iptables off
yum -y update && reboot

From https://wiki.fogproject.org/wiki/index.php/Installation_on_CentOS_7

Although, since it seems you have it set to permissive currently, the following code is probably better

sed -i 's/SELINUX=permissive/SELINUX=disabled/' /etc/sysconfig/selinux
sed -i 's/SELINUX=permissive/SELINUX=disabled/' /etc/selinux/config
service iptables stop
chkconfig iptables off
yum -y update && reboot

But I’m not 100% sure.

@palloquin https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

That might help

@Sebastian-Roth According to this discussion (http://serverfault.com/questions/806875/how-to-tell-isc-dhcp-correct-zone-for-reverse-zone-ddns-update) it has to do with reverse dns lookups

@Raymond-Bell If he does not have access to DHCP server, he could actually use dnsmasq DHCP proxy for handing out boot files.

https://wiki.fogproject.org/wiki/index.php?title=Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server

@Albertus

.bat script, barebones just pure functionality:

fsutil dirty set c:
shutdown /r

This sets the dirty bit flag, so that windows will run a chkdsk /f on next reboot, which is triggered immediately after.

This assumes windows is installed on

You can make it more advanced if necessary of course, but this is the core of what you want.

@irishfoguser

not sysprepped

This is possibly the problem. Not everyone syspreps here, but I recommend trying it and see if that alleviates the issue.

Not 100% sure on how what you’re expecting, but there are some options.

If you want to deploy remotely, you’ll need to register the PC somehow. Otherwise FOG will have no information to work with.

Knowing that, computers running the FOG client will automatically send their info to the server as pending registration. So if the computers are currently in use, deploying the FOG client to all of them, will take care off the heavy lifting.

If that’s not an option, you could make Quick registration the default option, boot the PCs and they’ll loop through it by themselves. (assuming default settings, meaning no special key presses or anything needed to get to FOG menu)

An alternative, if you have a list of MAC addresses, you can use those to create a host csv file that you can import to FOG.

If you’re asking about simply deploying without having to register at the PC itself, Deploy Image option works as expected.