ok we are finally getting somewhere…[B]FYI if clients are trying to use FOG as the DHCP server you need to modify this directory as well if your modifying your pre-existing FOG servers ip information for a different site location.[/B]

/etc/dhcp/dhcp.conf - this was the culprit for me, it still had the old ip address information and I also discovered I can narrow down the dhcp address scope here as well.

You’re welcome,

For the future, when you’re building a base image, inventory into fog but tell fog not to join it to the domain. Then upload the image. This way you don’t have to disable the FOG Service.

Your method works, but if you have to restart for anything before the upload process, the Service will try to take over and could join the domain, lets just say you had to go to the bathroom while you waited for that restart.

Once the image is uploaded, then go ahead and enable join domain for that system should you need to.

So,

As you’re limited to the number of available DHCP addresses to hand out within your network, does your fog server have more than one interface?

You could install the DHCP Server tool onto the FOG Service and have it hand out requests through a specific interface. If you only have one interface, you can still do the same type of idea. Though it’d be better that your server is set to a static IP address if they at least provide the one. When you need PXE boot, have the FOG Server serve a range of IP’s outside the scope of your current setup.

For example,

Let’s say your 300 systems runs on the IP range of class B network: 172.16.xxx.xxx, (this ensures the 300 possible IP’s and then some) And you set your fog server to be dhcp for a class C network: 192.168.xxx.xxx. When the systems boot using ports 66/67, (PXE boot phase) they should pick up the IP address from the 192.168 series and be able to PXE boot to the fog server as it’s the only one handing out that IP range. When the systems boot up, they shouldn’t be requesting IP’s from the FOG Server, as they’ve already passed the TFTP phase of the process. I’ve never really had to test this too much, but if the FOG Server is handing out IP’s, you can set the scope inside the fog server to point the dhcp server to your main network so there’s less confusion.

If everything is working for you, i’d say just keep it the way it is. No need to fix it if it isn’t broke. The only reason you may want to upgrade the compatibility to level 10 is that you can up your hard drive space from 2TB to 62TB per drive. We needed to do this for a couple of our servers, but it’s rare that you would need a VM with that kind of space. But then again, you’d need VMWare Workstation or vSphere to edit it from there.

Now if they offered HA for 2 free ESXi servers, just for absolute basic redundancy, i’d be in thrilled. We are on a strong push to move our teams to VM’s instead of having actual boxes at their desk for testing.

While I don’t know if you’re trying to use a linux setup to host the deploystudio or trying to use a mac machine to host the fog server, I think the method that would, conceivably, work the best would be putting the FOG server on a mac machine. Deploystudio, to my knowledge works on different protocols than PXE so both can exist at the same time.

The best method I could think of would be to install FOG on the DeployStudio Server by porting the needed modules.

You’d probably need to install a tftp server, web server, mysql server, and depending on your needs, a dhcp server.

The install script from the site would probably not work for your setup, but you could install the components required individually. This is not something I could walk you through in one day or anything but I could try to think of all the components you’d need.

First,

apache, php 5.3 or higher, htmldoc, mysql, tftp, nfs, and ftp would be the first things to install and get working.

Once you know the setup is working with all those components, you’d probably have to do some heavy tweaking in the web gui side to get it to work properly with the system.

While it would be a lot of work, I don’t think its impossible.

the FUN just keeps on coming…

DAY 3
Decided to bond the NIC’s

again… googled the hell out of it, surprisingly, there is no result for Fedora 15 nic bonding, save the official docs from Fedora that clearly articulates how to achieve bonding…

HOWEVER, not once did they mention that you needed to chkconfig NetworkManager off, nor did they mention to service NetworkManager Stop…
They failed to mention that when bond0 comes up, for some reason eth1 still holds an ip address, and that ifdown eth1 then ifup eth1 gets it to behave… then ifdown bond0 followed by ifup bond0…

they failed to mention the horror when you can no longer ping anything… not even the router even though all settings in the ifcfg file are correct and you’ve quadruple checked ifconfig -a output…

endless googling finally reveals that “perhaps” you may need to add a route by tying route add default gw 192.168.x.x dev bond0 which doesn’t seem to persist on network restarts…

suffice it to say, blowing away the server and re-installing crossed my mind on several occasions…

the result???

I have internet access but I can only ping computers on the same subnet, all other computers on any subnet can ping me… thats fine for now because imaging is working… again…

note to self… charge more for this $h!t in future…

[COLOR=black][FONT=FangSong]This is an amazing deal, you get a Meraki MR12, the Power Supply, and 3 years of the cloud management license.Its Prise 700$.Youlern more clicl this site [/FONT][/COLOR][B]leadmesh.com Think you. click this linl [/B][B][URL=‘http://anonym.to/?http://www.leadmesh.com/’]:) [/URL][/B]

Solved, At first step in windows machine, I shared in haneWIN NSF server c:\FOG_IMG like /images.
And as you said, system cannot move /images/dev/${MAC} to /images/{IMAGENAME}.
I’ve created a subfolder c:\FOG_IMG\images and I mapped it to /images.
I don’t understand the reason but after this It works and moves the images.

Thank you

Awesome glad it worked out, have fun fogging 😄

I do the same thing.

I’m in East Coast

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]