The problem you are seeing is typical of an FTP credentials issue. Read through this, everything you need is in there:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@caw001 You don’t have to go back to legacy boot, you just need to turn off secure boot. Most system’s firmware allows you to do this.

@Sebastian-Roth said in Unable to register hosts:

Nevermind, I just saw that you added the 3350 latitude including the kernel parameter back when we figured this out.

LOL, I did?

@ray-f Have you tried? It should be as simple as creating an image and using “Multiple Partition Image - All Disks - Not Resizable”

I also recommend Zstd compression at about level 10, should really speed up deployments in general.

@jhuesser That is the manual method to reset it for all hosts, which is entirely not necessary.

You can do this on an individual host via the web interface, or through groups. On the “General/Basic” page, it’s a huge button that says “Reset encryption”, you cannot miss it.

@lof said in ..and one FOG-VM to rule them all.:

so would setting a static IP each time mess things up or you both are just saying it would be unnecessary with dnsmasq?

With the MakeFogMobile project, your FOG Server should consume DHCP so that everything is automatic (no static required as this is opposite of mobility). Also, with the MakeFogMobile project, you no longer need options 66 and 67 to be set on your DHCP servers - dnsmasq handles it all from your mobile FOG server.

@arainero I just ran some tests and learned a lot.

I tweaked the commands to specify a port, and after some failure and wireshark-ing, I’ve created new firewalld commands to allow specifically that port and ICMP. I’ve verified they are working here at home, and have updated the wiki.

On the server to configure firewalld:

echo "Open UDP port 9000, this is the default port of udp-sender." 
firewall-cmd --permanent --add-port=9000-9001/udp
echo "Allow IGMP traffic for multicast"
firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -p igmp -j ACCEPT
systemctl restart firewalld.service
echo "Done."

Then on the server to start the test using the default port of 9000:
udp-sender --file /opt/fog/.fogsettings --log /opt/fog/log/multicast.log --ttl 1 --nopointopoint --portbase 9000

On the client, it’s the same still:
udp-receiver

Ubuntu doesn’t have firewalld yet, you’ll need to figure out comparable iptables commands. It’s quite simply just allowing UDP port 9000 and 9001, and allowing IGMP traffic.

Alternatively, simplify it for yourself and allow everything and see if you succeed then.

@george1421 the scripts re-configure dnsmasq every time the IP of the box changes. See line 216 in the script.

All snapins run as SYSTEM, which is actually more powerful than “admin”. All snapins must be completely silent too.

You have to associate the snapin with a host (or group) and then deploy it. A single snapin task is in the advanced area of host tasks.

@george1421 said in ..and one FOG-VM to rule them all.:

I’m pretty sure that dnsmasq is not added by the script,

It does install the latest version of dnsmasq available from the OS’s package manager.

If 2.76 is required for UEFI, this can be manually installed before hand.

@Sandi-Trogdon search the wiki for “Troubleshoot FTP”. Everything you need to solve this is in there. There are also tests you can run in there to determine if FTP and credentials are correct.

What version of fog?

@dclark Awesome white paper! If I could upvote it 20 times, I would.

@HABCO we have tutorials for installing from scratch. It doesn’t take more than maybe 3 hours. Most of that time is waiting for updates to run.

@dclark said in Organizations Using FOG:

@adukes40 It will be a year next month that we started out with a test instance. Honestly it has been less headaches than our old solution ever was!

#famousquotes

@jhuesser try to Uninstall and then reinstall the fog client and see what happens.

@dpotesta50 My suggestion is keep trying. Personally, I find that running FOG from a VM is a far more flexible option - because you can migrate it to another VM Host easily, increase/decrease ram and cores easily, add disks easily, and take/restore snapshots easily.

@purpleturtle99 wherever you put the fog trunk directory, in the bin directory there will be a new directory called error_logs. In there you will find log files with version numbers appended to them. The last few lines will reveal what’s going on.

Please post that file.

@zer0cool said in Possible to Use Snapin Post Image to Join Domain?:

Note: Installing the FOG client on hosts isn’t going to be an option for me unfortunately.

Then using snapins isn’t an option for you either, since the fog client is what enables snapins.

Quick registration is just exactly that, quick.

What you’re wanting to do can be accomplished easily with a full registration.

Group settings are not persistent. At the moment that you set a setting using groups that setting is applied to all of the hosts in the group and not the group itself and additional hosts put into this group at a later time will not have the settings that you set prior.

For more information on this please search the wiki for the article titled password Central.

@zer0cool Read through these:

• https://wiki.fogproject.org/wiki/index.php?title=Snapin_Examples
• https://wiki.fogproject.org/wiki/index.php?title=SnapinPacks