Right, i have reserved position of storage. I’ll set my FOG 0.32 storage as master on my Fog 1.x
When start the replication and will it consume all my bandwidth ?

Ok, so this image took 15 minutes and compressed down to 19gb so it is working.

I think it was just that image I was using. On to the next!

Thank you guys for all the help. I really appreciate it.

third link down from a search for “dban” right under the posts in this thread
[url]http://fogproject.org/forum/threads/remote-wipe.11009/#post-31889[/url]

the advanced menu options are set in the fog configuration page of the webgui
the “default file” that you’re accustomed to is now a dynamically generated page written in php now, btw

Quick is quick, it just assigns hostname and mac to FOG server. There’s two methods, auto pop where you can specify a common image id, group id, naming convention. If the image id exists and the image file exists it will also perform an image task after registration is done. This image task is unicast though.

Full requests the hostname, ip, user, image id, group, if you want ad to join, and if you want to image. This image task is unicast though.

I always used this way many time and once again last week and never had that certificate request or any error.
I find out that it was a proxy problem but I don’t know what they made different here on the proxy…
I uncommented and edited in “/root/.subvertion/servers” the following lines :

[QUOTE]http-proxy-host = 10.121.0.1
http-proxy-port = 3128
http-proxy-username = lyc-liegeard.fr\administrateur
http-proxy-password = **********[/QUOTE]

Sorry about the delay.

The command you’ve got is wrong.

It should be:
[code]wget -O /var/www/fog/lib/fog/BootMenu.class.php http://mastacontrola.com/BootMenu.class.txt[/code]

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

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

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.

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.

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.

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

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. 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. 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. 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. The regular DHCP server responds back with an ACK (acknowledgement), letting the client know it can use the IP configuration information it requested. 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

Assuming you are running Ubuntu 13 or below the kernel is located in /var/www/fog/service/ipxe folder.

If you run Ubuntu 14 or higher, or a CentOS/RHEL edition, your kernel will be located in /var/www/html/fog/service/ipxe.

To check to see which kernel you are using, please log into the FOG Web GUI and click on the Fog configuration button on the top right, then select Fog Settings from the left, and finally expand the selection TFTP Server in the center. There you can see the folder FOG is using for the kernel as well as the kernel in use, it should resemble bzImage32, if you are using the 64 bit kernel your file will be bzImage.

Fingers crossed it should be fine. like i say it pxe boots to the new server when i change option 66+67 and ive started to make a image and the vm registered in fog correctly as far as i can tell, just need to download the driver packs from home now as torrents are blocked on the work isp.

thanks for all the help ill be back if i get stuck

Well, I was doing it all wrong.
I just installed ubuntu on another server, and created a node.
The instalation gave me the user and the pass for that node, but now when I add another storage to fog it cant connect to the graphics

but I go the info from the server
[CODE]General Information
Storage Node teste
IP 172.17.2.6
Kernel 3.13.0-30-generic
Hostname fognod1
Uptime 16:30:15 up 11 min, 2 users, load average: 0.01, 0.12, 0.14
CPU Type GenuineIntel
CPU Count 8
CPU Model Intel® Xeon® CPU E5335 @ 2.00GHz
CPU Speed 1995.017
CPU Cache 4096 KB
Total Memory 12016
Used Memory 612
Free Memory 11404
File System Information
Total Disk Space 263.95 GiB
Used Disk Space 4.37 GiB
Network Information
eth0 Information
eth0 TX 554.07 KiB
eth0 RX 13.59 KiB
eth0 Errors 0
eth0 Dropped 1284
eth1 Information
eth1 TX 574.5 KiB
eth1 RX 39.71 KiB
eth1 Errors 0
eth1 Dropped 0
lo Information
lo TX 2.92 KiB
lo RX 2.92 KiB
lo Errors 0
lo Dropped 0[/CODE]

What do you mean by the storage password? The Storage Node username/password AND the FOG_TFTP_FTP_USERBNAME/PASSWORD?

I’m going to guess this is what you mean.

You’re probably running a “default” style install of FOG. The FOG_TFTP_FTP_USERNAME and FOG_TFTP_FTP_PASSWORD are what’s used to download new kernels to your FOG system. The Storage Management Username and Password are what’s used to upload images to your FOG Server. In a “Default” install, these are typically both the same because the Storage Node and the tftp and kernel/init files reside on the same exact host. This is why there’s “two” identical fields. That said, The Node does NOT need to be the same if you’ve separated the node from the FOG Server itself.

The Username and Password in these fields are the *NIX fog user account created during install. This username and password can actually be used to log in to the terminal or console of your FOG server albeit with limited use as it’s not an administrator account nor is it given sudo permissions.

The Config.class.php file holding area for this information is ONLY used during a fresh install. Why they’re blank in your setup I don’t know, but you can get this information from the /opt/fog/.fogsettings file as well. The Username is almost always going to be fog, but the password will be stored in a variable called password within this file.

Hopefully this helps.

I had the same problem.
You must set a correct value for the imageOSID field in the images mysql table.
1 for XP, 5 for Win7, etc…

[quote=“Tom Elliott, post: 31969, member: 7271”]
The path should be different and be set to whatever it is that you mounted the new hdd to: for example /mnt/newFOGImages/

From the command line you’ll need to add the new drive location to the /etc/exports file. Just copy the two lines and paste them below editing the /images /images/dev to match that of the new path for the new drive. Once done save and restart the nfs service.[/quote]

Ok, I formatted the second drive as newFOGImages, and created a folder in there called newImages. So the path should be /newFOGImages/newImages correct?

On the web dashboard I have two storage groups made, one is default, the other is group2. I also have two storage nodes, one is DefaultMember, the other one (I created) is newImages. I created it with the same settings as the default (IP address, etc.) except master node is unchecked, and the path is /newFOGImages/newImages/ instead of /images/

I opened the /etc/exports file and it has this:
/images *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/images/dev *(rw,sync,no_wdelay,no_root_squash,insecure)

Would I just copy-paste them within that file to look like this:

/newImages *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/newFOGImages/newImages/ *(rw,sync,no_wdelay,no_root_squash,insecure)

?

Thank you!!

we have seen somewhat similar issues regarding the reporting of mac addresses before. that is why the undionly.kpxe file now reports the first 3 macs it finds, in case the computer reports network adapters in the wrong order.

batch file should have:

shutdown /r

This will notify all users logged on that in 1 minute the computer will reboot … snapin executes with exit 0 🙂

You could always write a script to uninstall the client service once you’re finished with it and push it out via Group Policy.