@Rusty

Here’s my two cents. When it comes to software, have general software pre-installed, and then use snapins to deploy specialized software.

When it comes to the universal image, I have made an image which was only 5GB or so larger that included a lot of drivers. It worked on all the models I had at my disposal (ranging from netbooks, to laptops, to desktops). If you are interested I could try helping out making this image (its been ~1-2 years since I have done so). And if the image works then I’ll write up the steps for the driver packs / configuration I use as an actual guide. However, there is no guarantee that this image would work on all your models. It would need to be tested and probably refined a little.

If you’re interested PM me.

I have someone else reporting this error too. Here is the apache error log. @Tom-Elliott

PHP Parse error:  syntax error, unexpected end of file, expecting function (T_FUNCTION) in /var/www/html/fog/lib/client/HostnameChanger.class.php on line 29

@Rusty how many different computer models are you going to use the image for? Are the models similar?

There are different guides because depending on the answer to the above question, different approaches can be taken.

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

@Hanz OU does not matter. All the client needs is the username and password to leave.

@Hanz

The problem seems to be with:

 11/22/2015 10:42 AM HostnameChanger Unregistering computer
 11/22/2015 10:42 AM HostnameChanger Removing host from active directory
 11/22/2015 10:42 AM HostnameChanger ERROR: Required Domain information is missing

I’ll look into it.

@Hanz That key is only updated on windows XP. There are multiple keys that are changed, and the one key failing shouldn’t affect any renaming (That registry key has always failed since the legacy client and up).

Is the error that the host is not renaming? What is the client failing to do?

@george1421 Centos 6 appears to be missing some of the modules I require. I’ve been trying to hunt down the exact dependencies I’d need, or if need be, a new policy with different rules / modules.

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

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

@RLane As long as you are only using the legacy client with your current server, you are good to go. No need to transfer over your certificates.

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.

@Wayne-Workman said:

/usr/share/selinux/devel/Makefile

Updated main command to reflect this.

IPTables support added

Below are instructions on how to make FOG work with your firewall left on. If you encounter any scenario where this configuration does not work, please let me know and I’ll make adjustments.

Firewalld vs IPTables

Firewalld is an IPTables wrapper. It comes installed on Centos 7 and newer fedora installs. If you do not have firewalld then you most likely will have IPTables. To check if you have firewalld run firewall-cmd. If the command runs fine (no command not found error) then you have firewalld.

Firewalld

for service in http https tftp ftp mysql nfs mountd rpc-bind proxy-dhcp samba; do firewall-cmd --permanent --zone=public --add-service=$service; done
systemctl restart firewalld.service

IPTables

echo "IPTABLES_MODULES=\"nf_conntract_tftp nf_conntrack_ftp nf_conntrack_netbios_ns\"" >> /etc/sysconfig/iptables-config
for port in 80 443 21 3306 2049 20048 111 138 139 445; do iptables -I INPUT 1 -p tcp --dport $port -j ACCEPT; done
for port in 69 111 4011 137; do iptables -I INPUT 1 -p udp --dport $port -j ACCEPT; done
service iptables save

DHCP & DNS

If you use your FOG Server for DHCP or DNS run these commands as well.

Firewalld

for service in dhcp dns; do firewall-cmd --permanent --zone=public --add-service=$service; done
firewall-cmd --reload

IPTables

iptables -I INPUT 1 -p tcp --dport 53 -j ACCEPT;
for port in 53 67; do iptables -I INPUT 1 -p udp --dport $port -j ACCEPT; done
service iptables save

@erkax https://forums.fogproject.org/topic/6154/selinux-policy

Below are instructions to test my SELinux policy for FOG. This should allow your server to operate while SELinux is still enabled. If you encounter any issues while using the policy, please state exactly what you were doing when you encountered the issue.

To get the files you need, update your fogproject trunk (git pull or svn up).

Installation

yum install -y selinux-policy-devel gcc make
cd ../fogproject/SELinux
make -f /usr/share/selinux/devel/Makefile fog.pp
semodule -i fog.pp

Removal

semodule -r fog

Troubleshooting

If you get an error like the one below

make: /usr/share/selinux/devel/Makefile: No such file or directory
make: *** No rule to make target `/usr/share/selinux/devel/Makefile'.  Stop.

You should:

1. Ensure you installed SELinux development tools
2. Locate your SELinux Makefile. The installation command will look for it under /usr/share/selinux.

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

@Kiweegie I have confirmed the pushbullet plugin is now broken. @Tom-Elliott.

@Wayne-Workman
http://php.net/manual/en/language.operators.string.php#language.operators.string