We must be looking at different screens - Ah yes the task mgmt screen has the descriptions

[quote=“DoubleD, post: 35149, member: 24577”]I upgraded my FOG server from 1.1.x to 1.2.0 and my FOG server died too - luckily I found this thread

I did a sudo apt-get install libapache2-mod-php5
then I re-did the fog installation cd ~/fog_1.2.0/bin
./installfog.sh
Did the KEY thing [url]http://x.x.x.x/fog/management[/url] (pressed the button to install key)

and now my FOG server is back up & running

I’m running on Ubuntu

Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise

64 Bit

(wonder why the install broke it)[/quote]

I’m using dnsmasq to make PXE work for FOG and it seems that the Fog update undid a symbolic link to undionly.kpxe casuing the PXE boot to fail

To fix that I did the following

cd /tftpboot
sudo ln -s undionly.kpxe undionly.0

[quote=“fre2709, post: 34072, member: 24947”]Sorry All,

forgot to mention my version of Ubuntu is 12.04LTS.

Having dug a little deeper, the /etc/apache2/mods-enabled/php5.load file points to /usr/lib/apache2/modules/libphp5.so" which isn’t there. The only file beginning with “l” is “libphp5filter.so”

As suggested on an Ubuntu server forum I tried: sudo apt-get install libapache2-mod-php5

It installed a module (libphp5.so has appeared) uninstalled another (libphp5filter.so seems to have gone). Re-installed FOG 1.2.0 and hey presto “it works”. Updated the schema and I am back in and working.

Did I see on the download page that there is a SVN 2094 for FOG 1.2.0 already. What does that fix?[/quote]

I upgraded my FOG server from 1.1.x to 1.2.0 and my FOG server died too - luckily I found this thread

I did a sudo apt-get install libapache2-mod-php5
then I re-did the fog installation cd ~/fog_1.2.0/bin
./installfog.sh
Did the KEY thing [url]http://x.x.x.x/fog/management[/url] (pressed the button to install key)

and now my FOG server is back up & running

I’m running on Ubuntu

Distributor ID: Ubuntu
Description: Ubuntu 12.04.4 LTS
Release: 12.04
Codename: precise

64 Bit

(wonder why the install broke it)

I’m toying with a FOG server and I was wondering if I can import my Clonezilla Images to it

If yes how would I go about that

[quote=“Jaymes Driver, post: 33744, member: 3582”]I understand what it is you are asking, you want descriptive tooltips :)[/quote]

Its the age old question am I uploading the image to the server or an I uploading to the target ? Depending on what side of the fence you standing on both are correct but they have totally different meanings

[quote=“Jaymes Driver, post: 33743, member: 3582”]This is pretty typical. [/quote]
[quote=“chad-bisd, post: 33739, member: 18”]Depends on the speed of your client machine [/quote]

Thanks for the reply it helped!
Last time I did this it took over 16 hours. I must have down something wrong so I rebuilt the server with the new version of FOG and it seems OK. Now test downloading and maybe get a handle on what snap ins offer

I have the FOG Server and a AMD Dell on the same switch (100 mb) and I’m doing an upload

So far its taken 43 minutes with an estimate of 50 minutes to create the image on the server

is this typical ?

This may be petty but …

So depending on what side of the fence you are on it can be an upload or a download. It be helpful if when you hover the mouse over the upload or download icon fog would tel which way its sending data

Upload (Get Image from PC and store on Server)
Download (Load image from server to PC, replacing PC contents)
or something like that so newbies my have a clue

I had FOG running on Ubuntu it was very slooow 12-16 hours to take an image
I made a couple of changes and everything started to fail
Attempting to do a virus load failed
doing a memory test Failed
doin another image failed …

So I figured let me start over - I am using dnsmasq to do the PXE boot

Will attempt using the following steps (using the latest version of fog)

sudo -i

1. Get the tar file

wget did not for so I downloaded the current version to FTP server
logon to fog server
sudo -i
ftp to ftpServer
bin
get fog_1.1.0.tar.gz
exit

2. Extract the tar file

tar -xvzf fog_1.1.0.tar.gz
cd fog_1.1.0/bin

3.Start the Install

./installfog.sh
The following commands are for the installfog.sh installer information. Change the relevant values for your particular system.

Type 2 and press Enter for Ubuntu installation.
Type N and press Enter for Normal installation
Supply IP Address, it SHOULD be the static IP address you set up earlier, if it is not please revert to step 5 and try again.
Type N and press Enter setup a router address for the DHCP Server.
Type N and press Enter to set up DNS.
Type N and press Enter to leave the default Network Card the same.
Type N to use FOG for DHCP Service.
Type N to not install Additional Languages.
Type N to donate and press Enter.

4. Do the install

Type Y to continue
Next it will begin the install

Press ENTER to acknowledge the MySQl server message
NOTE: I set up MySQL with default passwords for MYSQL
Answer N when asked if I left the MySQL password Blank
Enter the password you used for MySQL and press enter
Enter the Password again and press enter.

5. Do the Database Schema Installer

Now we need to set up the web GUI for FOG. You will be preseted with a URL [url]http://(serveripaddress)/fog/management[/url].
Copy and past that into your browser and the click on the Install/Upgrade Now button
Press [Enter] key when database is updated/installed.
Type N to send your install information to the Project, and it will take some time to complete.

6. Script done, Install logged to file is /var/log/foginstall.log

apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade

=======================
How ProxyDHCP works

1. When a PXE client boots up, it sends a DHCP Discover broadcast on the network, which includes a list of information the client would like from the DHCP server, and some information identifying itself as a PXE capable device.
2. A regular DHCP server responds with a DHCP Offer, which contains possible values for network settings requested by the client.Usually a possible IP address, subnet mask, router (gateway) address, dns domain name, etc.
3. Because the client identified itself as a PXEClient, the proxyDHCP server also responds with a DHCP Offer with additional information, but not IP address info. It leaves the IP address assigning to the regular DHCP server. The proxyDHCP server provides the next-server-name and boot file name values, which is used by the client during the upcoming TFTP transaction.
4. The PXE Client responds to the DHCP Offer with a DHCP Request, where it officially requests the IP configuration information from the regular DHCP server.
5. The regular DHCP server responds back with an ACK (acknowledgement), letting the client know it can use the IP configuration information it requested.
6. The client now has its IP configuration information, TFTP Server name, and boot file name and it initiate a TFTP transaction to download the boot file.
   Environment
   Tested working with:
   OS Version FOG Version
   Ubuntu 10.04 LTS x64 Fog 0.29
   Ubuntu 10.04 LTS x32,x64 Fog 0.32, Fog 1.0.1, Fog 1.1.0
   Ubuntu 11.04 x32, x64 Fog 0.32, Fog 1.0.1, Fog 1.1.0
   Ubuntu 12.04, 12.10 LTS x32, x64 Fog 0.32, Fog 1.0.1, Fog 1.1.0
   Ubuntu 13.04, 13.10 x32, x64 Fog 0.32, Fog 1.0.1, Fog 1.1.0

dnsmasq
LTSP Server, further documentation at Ubuntu LTSP/ProxyDHCP.

Edit /etc/exports to look like this:
vi /etc/exports
/images *(ro,async,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,async,no_wdelay,no_root_squash,insecure)

apt-get install dnsmasq

vi /etc/dnsmasq.d/ltsp.conf

add the following

Sample configuration for dnsmasq to function as a proxyDHCP server,

enabling LTSP clients to boot when an external, unmodifiable DHCP

server is present.

The main dnsmasq configuration is in /etc/dnsmasq.conf;

the contents of this script are added to the main configuration.

You may modify the file to suit your needs.

Don’t function as a DNS server:

port=0

Log lots of extra information about DHCP transactions.

log-dhcp

Dnsmasq can also function as a TFTP server. You may uninstall

tftpd-hpa if you like, and uncomment the next line:

enable-tftp

Set the root directory for files available via FTP.

tftp-root=/tftpboot

The boot filename.

#dhcp-boot=pxelinux.0
dhcp-boot=undionly.kpxe,172.16.50.254

rootpath option, for NFS

dhcp-option=17,/images

kill multicast

dhcp-option=vendor:PXEClient,6,2b

Disable re-use of the DHCP servername and filename fields as extra

option space. That’s to avoid confusing some old or broken DHCP clients.

dhcp-no-override

PXE menu. The first part is the text displayed to the user. The second is the timeout, in seconds.

pxe-prompt=“Press F8 for boot menu”, 10

The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,

Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI

This option is first and will be the default if there is no input from the user.

#pxe-service=X86PC, “Boot from network”, pxelinux
pxe-service=X86PC, “Boot from network”, undionly

A boot service type of 0 is special, and will abort the

net boot procedure and continue booting from local media.

pxe-service=X86PC, “Boot from local hard disk”, 0

If an integer boot service type, rather than a basename is given, then the

PXE client will search for a suitable boot service for that type on the

network. This search may be done by multicast or broadcast, or direct to a

server if its IP address is provided.

pxe-service=x86PC, “Install windows from RIS server”, 1

This range(s) is for the public interface, where dnsmasq functions

as a proxy DHCP server providing boot information but no IP leases.

Any ip in the subnet will do, so you may just put your server NIC ip here.

Since dnsmasq is not providing true DHCP services, you do not want it

handing out IP addresses. Just put your servers IP address for the interface

that is connected to the network on which the FOG clients exist.

If this setting is incorrect, the dnsmasq may not start, rendering

your proxyDHCP ineffective.

#dhcp-range=172.16.50.254,proxy
dhcp-range=172.16.8.167,proxy,255.255.0.0

This range(s) is for the private network on 2-NIC servers,

where dnsmasq functions as a normal DHCP server, providing IP leases.

dhcp-range=192.168.0.20,192.168.0.250,8h

For static client IPs, and only for the private subnets,

you may put entries like this:

dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

restart your dnsmasq service
sudo service dnsmasq restart

Make a symlink for the undionly.kpxe file so dnsmasq can find it.
cd /tftpboot
sudo ln -s undionly.kpxe undionly.0

Thanks all for the replies 12.04.4 64bit LTS it is

Looking to install FOG on Ubuntu 12.

I typically use Ubuntu Server instead of the client

Is that OK ? – Since the server is lighter (less baggage) will there be missing components that FOG requires from the client install ???

[quote=“Jaymes Driver, post: 29880, member: 3582”]I use this in my environment, it is reliable. I have used it on all version of Ubuntu to date.[/quote]

Jaymes - Thank you ever so much this worked! ! !

:oops: I erroneously followed the directions for FOD 0.33 and it was all messed up. After rereading the [URL=‘http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE’]install instructions[/URL] I saw my error and undid all the stuff for FOG 033 and it worked like a charm - Now to try to figure out how to make images from an existing machine and then dump the image back

[INDENT=1]This information pertains to FOG 0.33 and the new iPXE boot method.[/INDENT]
[INDENT=1]In order to continue to use dnsmasq to dole out ip addresses and to help find the boot file, some changes need to be made to force the boot file to load the iPXE boot file.[/INDENT]
[INDENT=1][B]FIRST Update the schema by navigating to your fog management page and install the update.[/B][/INDENT]

[quote=“Jaymes Driver, post: 29873, member: 3582”]Don’t let fog be DHCP. If you already have a DHCP server it is bad to introduce another into the mix.

If you are having trouble resolving your bootfile in your network, try using DNSMasq to help alleviate the bootfile issues.

[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url][/quote]

I’m such a noob at this

I’m running FOG on ubuntu server 12.04 LTS - I see in the link you provided ubuntu 12 is tested and working so I will give that a whirl.

Thank you

Well I’m confused

I redid the fog server and told it to do DHCP

This is what it BUILT

DHCP Server Configuration file.

see /usr/share/doc/dhcp*/dhcpd.conf.sample

This file was created by FOG

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 172.16.50.254;

subnet 172.16.50.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 172.16.50.10 172.16.50.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 172.16.0.186;
option routers 172.16.0.1;
filename “undionly.kpxe”;

The wiki at [url]http://www.fogproject.org/wiki/index.php/Integrating_FOG_into_an_Existing_Network_in_non_intrusive_mode[/url]
talks to modifying this file. Since I don’t know what the file looked like before I’m not sure I know what the differences are. Equally confusing is the machine that is receiving an IP from FOG. - In my environment all machines begin to get DHCP from FOG instead of my existing DHCP server.

My network is 172.16.x.x 255.255.0.0 The fog server is bing placed on the same subnet

This does mess with my existing DHCP server.

P.S. DHCP seems to work - if I add new MAC addresses the server does reply with the address defined in the dhcp pool file

[quote=“Tom Elliott, post: 29835, member: 7271”]My guess is the dhcp server you have in place wasn’t working because it’s not passing the next-server or boot file parameters.

I’d make a copy of your FOG Server’s dhcpd.conf file and remove the packages for it from your FOG Server. Compare the dhcpd.conf file from your Solaris and dhcpd.conf from the fog server and find out how DIFFERENT they really are. My guess is it will actually be pretty simple.[/quote]

WOW that was a quick response

I attempted to go down that path but I can’t find a dhcp.conf file on my Solaris server - I did find a dhcptab file in /var/dhcp but I’m not sure how to add PXE or next server. The dhcptab file seems to define the DHCP environment. perhaps I can add the next server there if I knew the syntax

Locale m :UTCoffst=-14400:
sun1234 m :Include=Locale:LeaseTim=1728000:LeaseNeg:
172.16.0.0 m :Subnet=255.255.0.0:Router=172.16.0.1:
:DNSserv=172.16.0.2:Broadcst=172.16.255.255:
:MTU=1500:NetBNms=172.16.0.3 172.16.0.2:
:DNSdmain=mydomain.com:NISdmain=xxx.mydomain.com:
:NISservs=172.16.0.2:Timeserv=172.16.0.2:

I have an existing environment with an old Solaris DHCP server that I don’t know much about. The only thing that I have done with this server is to vi the IP segment file in /var/dhcp to add new devices that require DHCPing

I installed FOG 1.1.0 configured pointing to my DHCP server and told FOG not to run DHCP - PXE boot does not work

I then deleted the MySQL database, delete fog by rm -R /opt/fog I reinstalled FOG and this time I told it to run DHCP. I erroneously pointed the the DHCP ROUTER to my router instead of the DHCP server. - PXE worked but the new fog DHCP server was stepping on my old DHCP server and devices were getting the wrong IPs

Can anyone provide any guidance on how to make FOG & PXE work with my old DHCP server - keep in mind I don’t know much about the old DHCP server or how it was configured.