Subcategories

• General

  General Developer questions relating to FOG.
  389 Topics

  5k 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/
• Feature Request

  Request a new feature to be implemented.
  632 Topics

  4k Posts

  T

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

• Bug Reports

  Report a bug with FOG.
  1k Topics

  12k Posts

  T

  @fierke A correction to my last post. The fix is now merged into working-1.6 and rc-1.6.0. Update your checkout and re-run the installer. The installer now writes default.ipxe without those two lines, so you do not need to comment them out again.

  You are right that this can happen on other machines too. Any UEFI firmware that never ends its variable list hangs the same way. The update fixes it for all of them.

  I would still like the show efi/SecureBoot result and your BIOS version when you have time. That confirms the cause before the iPXE side ships.