Best posts made by Joe Schmitt

There is nothing we can do about it; the legacy client is depreciated (It hasn’t been worked on for quite a few years, minus my product key addition way back when). If you upgrade to SVN you can try out the new client and see if the problem is fixed.

@plegrand v0.9.6 is released, and this includes the Samba fix. (https://news.fogproject.org/client-v0-9-6/)

@Louis-CSUSA Can you post the contents of /opt/fog-service/fog.log ? Also, what version of OSX? We’ve only been able to test the client against Maverick, Yosemite, and El Capitan so far.

IPTables support added

Nope, you do not need to upgrade them. The client they are running will work with your FOG server.

@erkax I will provide a link to my policy within the day.

Requesting that a @Moderators split up this thread into two (the original topic about the FOG client, and the new topic about OS X net booting).

@Wayne-Workman said:

/usr/share/selinux/devel/Makefile

Updated main command to reflect this.

Confirmed and fixed in v0.9.7 (https://news.fogproject.org/fog-client-v0-9-7/). Upgrade your FOG server to get the patch. Sorry about the oversight.

Assuming this is the same issue I have been seeing, CentOS 7 screwed up big time. My CentOS server just recently stopped being able to start after updating, and I have other people experiencing the same issue. This is the closest bug report I have been able to find: https://bugs.centos.org/view.php?id=9860

The fix I used was to append initcall_blacklist=clocksource_done_booting right after quiet on the grub boot menu. Once it successfully boots edit /boot/grub2/grub.cfg and permanently append that line to all of the boot entries that have a quiet.

If this does not work, you should still be able to recover your data by booting to a live ISO and mounting your disk.

Its also worth noting that if blessing does work and you use the FOG Client on Mac then you can just deploy a snapin to bless all of them at once.

I was assuming if people had a dhcp server on that machine they’d already have it configured. I just added the options used by FOG alone. Not anything extra a person may add. I updated the main post with a DHCP section.

@george1421 @Wayne-Workman @pmonstad

Avoid disabling SELinux. If you ever want to re-enable it, you would need to relabel your entire filesystem. Instead set it to permissive. (This is essentially an ‘audit’ mode which records violations but doesn’t prevent them).

To do so:

setenforce 0
sed -i 's/SELINUX=enforcing/SELINUX=permissive/' /etc/selinux/config

This approach will NOT require a reboot either.

I have an SELinux policy that I’ve been working on that makes FOG work with SELinux enabled if anyone would be interested. I am also a huge proponent of NOT disabling your firewall for FOG, it is a terribly insecure idea and one of my biggest complaints about our recommended installation. I would take the time to configure the firewall by opening the appropriate ports. Or at the very least make a zone of your internal IPs and set it to open (not the best solution, but it will work). I also have firewalld configurations that will work with FOG, which I’ll publish soon.

@djbucci v0.9.X of the client is not linux / OSX compatibility. With that said, there is a good build of v0.10 of the client which operates on linux and osx. One group in particular has been using v0.10 linux client for the past several months. I’m resuming my work to polish up the installer and I should have a public alpha ready to go hopefully soon.

@Gary-Kulovics here ya go: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Installing_-_OSX

Basically just install the latest mono package, run smartinstaller, and restart.

@george1421 good catch on the iptables, updating the main post to reflect that and the REHL clarification.

Problem solved. I teamviewered in and saw that the AD options were disabled. So the host never got the needed ad user/password. (This should be resolved in a patch @Tom-Elliott is working on).

Either re run your fog server installer or upgrade. The smart installer can’t be downloaded from your server. This means it wasn’t obtained properly when you last upgraded your server.

@whereiswaldo7 could you try installing this build on a MacOS machine and let me know if it works correctly?
https://build.jbob.io/Client/release-candidate/0.11.16-RC-01/SmartInstaller.exe

@george1421 there is a DHCP section in the post. I will include DNS as well. Right now I wish to keep those options separate. Eventually the installer should automatically configure the firewall based on installation preference.