Regardless if you set up fog as your DHCP, or supply your DHCP server ip address, you still [B]NEED[/B] to supply the information of the next-server (your fog server) to your management console (DHCP server console) and reboot the network so that i can find the “next-server”. You also have to enter the file name that will be loaded on pxe boot.

[code]
3. Set up DHCP (For Windows DHCP)
[]Log onto your Windows DHCP server
[]Open DHCP console.
[]Right Click Scope Options -> Configure Options
[]Scroll Down to number 66 check and give the IP of FOGSERVER
[]Scroll down to number 67 check and give the value pxelinux.0
[]Apply and close.[/code]

Supplying options 66 and 67 are not OPTIONAL, they are REQUIRED.
This information came from a walkthrough on the forums, however there are MANY guides to follow to get FOG set up. There is even a different walkthrough on the wiki if you would like to take a look at that.
[url]http://fogproject.org/forum/threads/how-to-install-fog-on-ubuntu.5/[/url]

Hi guys, i’ve got a little problem with my firewall rules.
I start my iptable configuration and my computer stop in TFTP. It doesn’t show me the fog boot menu
The ports TFTP are open so what’s my problem ?

[CODE]#!/bin/sh

BEGIN INIT INFO Provides: PareFeu Required-Start: $remote_fs $syslog Required-Stop: Default-Start: 2 3 4 5 Default-Stop: 0 1 6 Short-Description: Start daemon at boot time Description: Enable service provided by daemon. END INIT INFO Vider les tables actuelles

iptables -t filter -F
iptables -t mangle -F
iptables -t nat -F

Vider les règles personnelles

iptables -t filter -X
iptables -t mangle -X
iptables -t nat -X

Interdire toute connexion entrante et sortante

iptables -t filter -P INPUT DROP
iptables -t filter -P FORWARD DROP
iptables -t filter -P OUTPUT DROP

Ne pas casser les connexions etablies

iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT

Autoriser loopback

iptables -t filter -A INPUT -i lo -j ACCEPT
iptables -t filter -A OUTPUT -o lo -j ACCEPT

ICMP (Ping)

iptables -t filter -A INPUT -p icmp -j ACCEPT
iptables -t filter -A OUTPUT -p icmp -j ACCEPT

SSH In

iptables -t filter -A INPUT -p tcp --dport 22 -j ACCEPT

SSH Out

iptables -t filter -A OUTPUT -p tcp --dport 22 -j ACCEPT

DNS In/Out

iptables -t filter -A OUTPUT -p tcp --dport 53 -j ACCEPT
iptables -t filter -A OUTPUT -p udp --dport 53 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 53 -j ACCEPT
iptables -t filter -A INPUT -p udp --dport 53 -j ACCEPT

NTP Out

iptables -t filter -A OUTPUT -p udp --dport 123 -j ACCEPT

HTTP + HTTPS Out

iptables -t filter -A OUTPUT -p tcp --dport 80 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 443 -j ACCEPT

HTTP + HTTPS In

iptables -t filter -A INPUT -p tcp --dport 80 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 8443 -j ACCEPT

FTP/TFTP Out

iptables -t filter -A OUTPUT -p tcp --dport 20:21 -j ACCEPT
iptables -t filter -A OUTPUT -p udp --dport 20:21 -j ACCEPT
iptables -t filter -A OUTPUT -p tcp --dport 67:68 -j ACCEPT
iptables -t filter -A OUTPUT -p udp --dport 67:68 -j ACCEPT

FTP/TFTP In

iptables -t filter -A INPUT -p tcp --dport 20:21 -j ACCEPT
iptables -t filter -A INPUT -p udp --dport 20:21 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 67:69 -j ACCEPT
iptables -t filter -A INPUT -p udp --dport 67:69 -j ACCEPT

MySQL IN/OUT

iptables -t filter -A OUTPUT -p udp --port 3306 -j ACCEPT
iptables -t filter -A INPUT -p udp --port 3306 -j ACCEPT

#NFS IN/OUT
iptables -t filter -A OUTPUT -p udp --dport 2049 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 2049 -j ACCEPT

iptables -t filter -A OUTPUT -p udp --dport 111 -j ACCEPT
iptables -t filter -A INPUT -p tcp --dport 111 -j ACCEPT
[/CODE]

thanks you for your ideas.

EDIT :
I find my problem

modprobe ip_conntrack_tftp
modprobe ip_conntrack_ftp

😉

In the FOG web management, you can update the value under Other Information -> Fog Settings -> FOG_CHANGE_HOSTNAME_EARLY to 0 and the imaging script will not try to update the username by editing a registry key before windows loads.

If you do not install the FOG service, you’re hosts will not rename after they load windows. You can also disable the hostnamechanger option in the FOG Service install, per host record, and for your FOG server completely.

Add the caveat now to Fedora 19, being that they changed the database (mysql) to mariadb. All works, but requires minor changes in the script. I’ve already created a thread pointing out the issue with Fedora 19 and a fixed tarball for it based on FOG 0.33b, though the same changes could just be made in 0.32.

From a quick search it appears most people do it the other way, using SCCM as the primary PXE server, although the following post does have a little info on doing it the other way.
[url]http://www.vcritical.com/2011/06/peaceful-coexistence-wds-and-linux-pxe-servers/#comment-14629[/url]

Yes it’s windows 7 SP1, Windows 32 bit.

I appreciate your feedback.

I have multiple computers all the same model, only this particular unit is giving me fits. I believe it is actually a failing controller.

Welcome to FOG. We hope you enjoy your stay.

Are you a previous FOG user? Are you new to FOG? What are your plans for using FOG?

There’s currently a work in progress which is a heavy re-write for the FOG code and hopefully it will bring some new integration for the UEFI Support and a few others!

This forum is a great resource and everyone is pretty nice here, just remember to search!!!

once again, Welcome!

You can set your options to auto subscribe to any thread to which you post. That is how I keep up with the threads I care about.

No, all my experience is with FOG 0.32 at this time. As far as FOG goes, the only thing different about Windows 8 is that I choose Windows Vista as the OS type and Multiple-Partition, Single Disk (non-resizable) for the image type.

wwyhy,

Here is what I posted in another thread:
[QUOTE]
That’s a known issue. What you need to do is go and download a kernel from here,[URL=‘http://sourceforge.net/projects/freeghost/files/Kernels/’]http://sourceforge.net/projects/freeghost/files/Kernels/ [/URL]then whichever kernel you download, you will need to rename to [B]bzImage[/B]. Once this is done, first rename the original kernel to something like bzImage.backup. This is located in /tftpboot/fog/kernel. Once you rename the kernel you downloaded, move it to this folder and you’ll be all set. Just note that it has to be spelled [B]bzImage[/B], all lowercase besides the I. If a capital letter is not right, it will not boot.
[/QUOTE]

Hi dusto,

I replied this option in another thread, see if it works for you: [url]http://fogproject.org/forum/threads/request-dnsmasq-fails-to-start.4457/#post-12837[/url]

I assume that when you say you can’t modify any of the network resources to use PXE you mean that you can’t modify DHCP options 66 & 67. In my enterprise there is a DHCP which has those options already busy, so I couldn’t modify them, my solution was to use ProxyDHCP as I mention in the thread above.

Tell me if this works for you.

Just an update, Falko and I ended up removing about 800 messages of spam earlier today. Everything should be back to normal on the forums.

Yes, that was another idea I have considered after posting my question - to use simple batch files for individual snap-ins, put the main executable on easily accessible samba share and manage different command line arguments from those batch files. Definitely a cleaner approach than my original symlinking idea 🙂 Thanks a lot for your response, it definitely helped me to solve my problem.

I would also say to upgrade to 12.04 LTS, this will guarantee you 5 years of patches and security updates.

Actually Jay_S_FogUser I want to clarify:

FOG is still active, however, there are really only 3 developers, 1 of which stepped back for a bit. But FOG is still alive and being actively modded and developed. Every program has issues, if you come across some, please post them in the Bug forums and we’ll try to get them sorted out. FOG works with up to Windows 8 and ext3 filesystems. It is being looked at to switch to partclone for the core imaging system. Yes, the best way to learn is to do it yourself. However, I’m currently putting something together to help new users get into FOG, I’m hoping to have it ready within the next few weeks. Chuck, the creator of FOG posted this today, please have a read: [url]http://fogproject.org/forum/threads/fog-status.4515/[/url]

FOG will not be able to image iPad’s. If 50 are going to be in one spot, Apple Configurator works well. However, if you need to manage them and they are spread out, you really need to look into an MDM solution, either paid such as AirWatch or a Mac server tools MDM solution.