Categories

• Technical Help

  Get help with your FOG system.

  FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
  13k Topics

  115k Posts

  T

  @Paladin1 Thanks for the full logs. The autoexec.ipxe ... Not found lines are normal for your install. The installer removes that file from the TFTP root on purpose.

  The ASSERT ... udk2010 ... HiiLib.c lines do not come from FOG or iPXE. They come from the target machine’s own UEFI firmware. iPXE starts, then the firmware fails an internal check and stops.

  To narrow it down, please tell us:

  The make and model of the target machine, and its BIOS version. A photo of the whole screen, from the first line. We need the line that starts with “iPXE” and shows its version. Is any other DHCP server active on that network, such as your router? If yes, what boot file (option 67) does it give out? Does the target boot to the FOG menu in Legacy/CSM mode, with UEFI off?
• Announcements

  Get the latest news on what's happening.

  Security Advisories
  195 Topics

  836 Posts

  T

  The tenth release candidate for FOG 1.6.0 is available on the rc-1.6.0 branch. It reports version 1.6.0-RC-10.

  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-9

  iPXE: boot no longer freezes on some UEFI firmware (forum 18271, #1857). default.ipxe read the SecureBoot and SetupMode EFI variables. On some older firmware that read never returns, and the host froze before the menu. The installer no longer writes those two lines. Run the update to rewrite default.ipxe. Hosts no longer report their Secure Boot state on PXE boot. FOS still reports it when the enrollment task runs. CSV import reads a file that FOG exported (GH-1851, #1855). “CSV (All)” starts the file with a UTF-8 byte-order mark. The import did not skip it, so it did not find the header row. It imported the header as a host, and the row failed with “No viable macs to use”. The import now skips the mark.

  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.

• General Topics

  View tutorials or talk about FOG in general.

  General Tutorials
  2k Topics

  19k Posts

  8

  @Cpasjuste I just wanted to let you know that I’ve added in your method of using userland NFS support to my container. I have given you credit for the method in the README. I’d love for you to test it out if/when you get a chance. Thank you again for your work!

• Developers

  Report bugs, request features, or get the latest progress.

  General Feature Request Bug Reports
  2k Topics

  21k Posts

  T

  @Paladin1 Thanks for the report. You’re right, the docs were out of date.

  The installer now asks Install/update the FOG database schema now? (Y/n) and does the schema update itself when you answer yes, which is the default. The browser step only applies if you answer no.

  The “Denied” you saw is expected on a new install. With no FOG users yet, the schema page only accepts the link the installer prints, which ends in &fogtoken=.... On an existing install, you log in as an admin instead.

  The install pages are updated for both versions:

  1.5: https://docs.fogproject.org/en/latest/1.5/installation/server/install-fog-server/ 1.6: https://docs.fogproject.org/en/latest/1.6/installation/server/install-fog-server/