This sort of exists already, but in reverse. you can set the primary groups of images individually, and select many groups.

Very nice.

The tests I have going use Ubuntu 18.04 Server, not desktop.
There’s another issue open on github about this very thing I believe: https://github.com/FOGProject/fogproject/issues/261
That guy’s answer was to add the universe repository. I guess Ubuntu desktop 18.04 doesn’t come with that repo enabled by default.

Are you using dnsmasq? Have you checked that TFTP is running? Have you tested that TFTP is functional?

Look through this article: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

@LPetelik Great idea, I think this would be very useful.

@Joe-Gill Easy, here’s the guide: https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG

I’d recommend Debian 9 minimal installation. Historically with fog, Debian has had the least number of issues.

@ToxicFlyman

It’s a relational database model. their are IDs as PKs and FKs but are not enforced by the DB, but are guaranteed by the FOG front end I believe. Simple inner joins or outer joins will give you what you want. What version of FOG are you using?

Moved to feature requests, and you rock.

This is great, thanks Tom for your work here!

@Sebastian-Roth said in TFTP won't start at the installation:

@Onirix I probably need to test with Debian 9.9 myself to figure this out. Not sure when I will get to this.

I see you’ve already tested it, but the daily install tests - in the case of Debian 9 - always are testing the very latest version of Debian 9 automatically every day. Arch is always the latest version. Centos 7 is always the latest centos7. Fedora 30 is always the latest 30. Ubuntu 18.04 is always the latest 18.04.xx.

@ToxicFlyman

Do you have tables called “hosts” and “hostMac” ? what are the exact table names in FOG 1.2.0 ? (sorry don’t have 1.2.0 anywhere to test on).

What are the exact field names in those two tables? Are these the only tables you want info from or are there others?

@x23piracy I can fix that - give me a bit.

@george1421 said in FOG 1.5.6 Officially Released:

Why not setup both http and https in apache.

I’d say that’s a good idea.

It’s ChromiumOS, not ChromeOS just a friendly fyi. Try non-resizable if resizable is giving issues. I’ve uploaded ChromiumOS 48 before without issue after some changes by the devs, but have not tried with Cloudready but can’t see why it wouldn’t work. Read here: https://forums.fogproject.org/topic/6214/chromiumos-r48-elitebook-8730w

@mati-92 The first thing that jumps out at me is this line:

dhcp-boot=pxelinux.0

that should be changed to the boot file you want to use - generally this is undionly.kpxe

But, I asked for three things and you only provided one.

Look at the article link you posted, there’s a bit in there about symbolic links. if you wanted to use undionly.kpxe as your boot file, you need to create a symbolic link to undionly.kpxe.0

also - if you still get further errors after this - we really need to see a photo of the error and we need to know what changes you’ve made - and we need to see the output of the below command.

Details, details, details.

Firstly, suggestions are always welcome - this is some of the stuff that makes open source so awesome.

My first thoughts of this request is the complexity involved. So many additional pieces here - the fog client now is prompting users for input, the fog server is now having to record generic hostnames and pass that to the client before the client is even accepted by the server, and all the UI & client changes and communications that need implemented to make that happen. This is a large request.

How about instead - clients should report in with whatever hostname they have - and this not be a unique identifier for pending hosts. Then, in the pending hosts area, require the admin to specify a new hostname right there if there are conflicts with hostnames before the pending hosts can be accepted.

This is probably easily fixable, seems like the functions script for Debian 8 just doesn’t like how the FOG multicast management service is getting started.

let me find the code… and maybe post a work around… unless Tom beats me to it.

@thebaz The number of times someone has upgraded the OS of their FOG server and broken FOG is a lot. So many that it prompted me to write this article about five years ago. The article is still valid. My advice is to not upgrade the OS of your FOG server, unless it’s in a VM and you take a snapshot before hand. If it’s not in a VM, your safest choice is to migrate.

@EAHarvey We are suggesting that you change them to undionly.kkpxe

Note the extension.