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

A VM or physical server (or AWS instance) is the correct answer.

FOG wraps itself so tightly into the OS, it really should be an appliance. But since we are all volunteers and FOG is totally open source and nobody who works on fog actually has any money or time to do anything else besides what we’ve been doing - we just have a really elaborate installation script that we work hard to support.

I was able to confirm the issue of the sub directories not being created and after making the proposed suggestions the installer did indeed create the pxelinux.cfg and i386-efi folders. This issue was present on both Ubuntu and Fedora.

I’m marking this as solved.