Test it on a lab or non-production server first. The upgrade from 1.5 to 1.6 is one-way: it changes the database schema, and there is no down-migration.

Changed since RC-14

• Installer: choose the UEFI loader that DHCP hands out (#1915, #1916). Some firmware does not release the NIC when snponly.efi hands off to FOS. Those machines boot with ipxe.efi. Install with --uefi-bootfile ipxe to hand out the iPXE loader. The installer saves the choice in .fogsettings, so an upgrade keeps it. The default is still snponly.
• Dashboard: a peer FOG server no longer shows “Access Denied” (#1917, #1918). A storage node entry can point at a full FOG server with its own database. Its disk usage and server information now accept the node signing key, not only a known IP address. Set the same key on both servers: https://docs.fogproject.org/en/latest/1.6/management/web/storage-node/
• FOS: fixparts is back. A capture showed “Could not fix partition layout (runFixparts)”. The fix is in FOS EXP_20261021-160109, which the update installs.

Before you upgrade

• Back up your database and /opt/fog/.fogsettings.
• Read the release notes: https://github.com/FOGProject/fogproject/blob/rc-1.6.0/docs/release/1.6.0-release-notes.md
• 1.6 removes Display Manager, Directory Cleaner, User Cleanup, Client Updater, Green FOG and the persistentgroups plugin. Their data is dropped. The site and accesscontrol plugins move into core.
• PHP 7.4 or later is required. Plugins built for 1.5 do not load.

Install or update (as root)

• A 1.6 beta or RC server: run bin/updatefog.sh --channel rc from your FOG checkout.
• A 1.5 server installed from git: update to the current 1.5 stable, then run bin/updatefog.sh --channel rc from the checkout.
• A new server, or a 1.5 server installed from a tarball:
  curl -fsSL https://raw.githubusercontent.com/FOGProject/fogproject/working-1.6/bin/bootstrap.sh | bash -s -- --channel rc

Report problems

Open an issue at https://github.com/FOGProject/fogproject/issues. Include your FOG version, your OS, and the installer log from bin/error_logs/. Report a security problem through “Report a vulnerability” on the same repository, not in a public issue.