The FOG Configuration->FOG Settings->FOG_PIGZ_COMP is defaulted to 9 which means maximum compression/slowest upload.
It only functions on the upload process.

If this is where you’re trying to “speedup” the images, I’d recommend adjusting this value.

If you’re trying to “speedup” the download of images, then check your networking. Is there 10/100MB limiting that lab down from a gigabit network?

[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]

Thanks Junkhacker that will help to plan hdd size for deployment!!

Great job Tom and Team. My hearty Thanks.
I am going to update my FOG today.

[quote=“tamatech, post: 29736, member: 24111”]Looks to me like whatever computer you are using doesn’t like the included bzImage kernel. Try a different one or try adding kernel arguments. There are several threads on these topics.

Andy[/quote]
You were correct… Found the following solution in another thread:
[CODE]sudo mv /var/www/fog/service/ipxe/bzImage /var/www/fog/service/ipxe/bzImage_05JUN2014
sudo mv /var/www/fog/service/ipxe/bzImage32 /var/www/fog/service/ipxe/bzImage32_05JUN2014
sudo wget -O /var/www/fog/service/ipxe/bzImage --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage
sudo wget -O /var/www/fog/service/ipxe/bzImage32 --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage32[/CODE]

This Code was Courtesy Tom Elliot

Ahh okay, that makes sense. So the download button is basically just a shortcut. I’m usually using the download.

Tom,
Of course. However I didn’t think it through all the way. Right now the only service I use is joining the AD. In the future I would like to get snapins working, but so far multiple images has worked for me.

I was having enough issues getting Fog to run, I didn’t want to try using 14.04. Now that Fog is working as it should maybe I will try the newer version. As for hardware I am using VMware 5.1 on a HP DL380G6. Each Fog VM gets 2vCPU and 8GB of RAM. I will post the results when I get the chance to try 14.04.

[quote=“GBison, post: 28720, member: 18212”]Hello all!

In my last FOG setup in .32, I had the menu background changed, removed the descriptions of the functions, and changed the wording for some of the functions themselves through an easily edited text file. If I recall, the file was called default.something and was located somewhere inside the pxelinux folder.

Now, with the new FOG 1.0.1 moving things around, I’m a bit lost. I found where the background goes after a bit of digging, but I’m wondering where I go to change the font color, highlight color, edit the text, etc. I know about the webUI PXE menu edit field, but this just adds extra text to the bottom… not what I’m looking to do right now.

Any help is appreciated![/quote]

If you really want to edit the menu, there’s no major issue, and it is (more or less) still editing one simple text file.

The file is now located in:
/var/www/{FOGWEBDIR}/lib/fog/BootMenu.class.php

Just be cognizant of what you’re editing. iPXE is a bit finicky about syntax. If you’re dealing with gap’s and have dashes in them, you need to have two prepending dashes: (example below)
[code]item --gap – ---------------------------[/code]

You’ll break ipxe if you have:
[code]item --gap ---------------------------[/code]

Here’s ipxe’s scripting documentation:
[url]http://ipxe.org/scripting[/url]

Here’s ipxe’s command information:
[url]http://ipxe.org/cmd[/url]

[COLOR=#000000]It’s pretty simple once you look at it, but it may take a little bit to understand how it’s being build. The old /tftpboot/pxelinux.cfg/default file was useful, but it wasn’t dynamic. That’s where moving to ipxe made things so much easier. While confusing at first, it’s much simpler and, from a programmatic standpoint, nice to work with as you can add anything you need dynamically.[/COLOR]

[quote=“Scott B, post: 29522, member: 15315”]If I want to use a different kernel how do I go about that? I downloaded “Kernel.TomElliott.3.14.2.64” from the Fog Project page, but I don’t know what to do with it from there.[/quote]

How did you download the kernel?

If you did it from the gui, and saved the name as bzImage, FOG automatically will be using that kernel. If you saved the kernel as a different name, you would need to change the kernel you’re using from FOG Settings to that of the name of the name you saved it as.

If you downloaded the kernel directly from sourceforge, you would need to copy it to your fog server in /var/www/{FOGWEBDIR}/service/ipxe/

The easiest method would be to save it as bzImage after making a backup of the current bzImage.

What makes you think you need to use sysprep? There was a period of time that the BETA svn required sysprep of all images, but that was fixed before release. You can use sysprep, or not, either way the imaging process seems to work anyway.

the client software has not changed. if the ip address of the server does not change, the existing clients will talk to the new server

True but as a warning you DNS records and DHCP records will have probable issues. Since its the same MAC and JOINED to the domain DNS will have to fix the A record pointers and DHCP will have to updated the A records from the DNS. UNC paths may take much longer than expected and so on…

This dual boot is nice for testing software but I would not recommend it.

[quote=“Frank, post: 29117, member: 691”]Hi Tom,
Can it be that the search use snapinAssoc table and the SELECT lacks DISTINCT clause? That would explain the repetititon.
Frank[/quote]

I don’t think that’s it. If we added DISTINCT to the SELECT params, it would not allow certain search functions to work properly. I’ll take a look at the query string, if that’s even being used, for the snapin page.

I think it’s possibly because the link: [url]http://voxel.dl.sourceforge.net/sourceforge/freeghost/fog_1.0.1.tar.gz[/url] is not a valid link anymore.

The proper link should be:
[url]https://sourceforge.net/projects/freeghost/files/latest/download?source=files[/url]

The direct link to download the file is:
[url]https://downloads.sourceforge.net/project/freeghost/FOG/fog_1.0.1/fog_1.0.1.tar.gz[/url]

If you read during the install of fog it tells you do do this. That is direct documentation.

Would you just keep clicking next in an install of Java and install all the extra crap that comes along for the ride? No you untick the extras and just install java. Same goes for any other install. [SIZE=4][I][U][B]Read the output.[/B][/U][/I][/SIZE]

I can confirm Dell E6410’s work with v1.0.1. They work with the new updated kpxe files in [url]https://mastacontrola.com/ipxe/latest-DEFAULT-TEST/undionly.kpxe[/url].

I have no issues with this right now.

[quote=“number_one, post: 28807, member: 24434”]As a new FOG user, are there any quick tips to make sure there aren’t any catastrophes related to users booting PXE with a FOG server in an existing production network ?

I’ll be using an existing DHCP server that redirects PXE requests to the FOG server and I want to be dead certain that a random user isn’t going to be able to accidentally image their computer when booting up. There is is much info out there and so many complex configurations related to PXE so I thought I’d just ask for any quick pointers.

And if I missed a post or WIKI page that covers this I apologize.[/quote]

In 0.32 and earlier the PXE boot system was a little more “dangerous” in that it had all options by default. What I mean by this is it had:

Boot to Hard disk
Run Memtest86+
Quick host registration and Inventory
Perform Full host registration and inventory
Quick Image
Client System information
Debug Mode

The user could, if the host wasn’t registered, perform full host registration and inventory, join their system to FOG and have it perform an image of their system without knowing any information. They could also boot the system into debug mode, and completely wipe their systems or erase passwords if they knew what they were doing. So, yes, there were ways to have regular users hurt their systems. This was not typical though as it does require some knowledge of computers and linux. But there was always the possibility. Unless of course you added pass codes to each of the menu’s.

With 1.0.0, we started actually limiting options. If a host is registered, it only presents:

Boot to Hard Disk
Run Memtest86+
Quick Image
Quick Deletion
Client System information.

The Quick Image and Quick deletion options require the FOG username and Password natively to be successfully entered to run. So the user could run a memtest operation or boot into the Client system information, but the only real harm with these would be loss in production, no damage to the system.

If the host is not registered, it only presents:

Boot to Hard Disk
Run Memtest86+
Quick registration and inventory
Full registration and Inventory Client System information
Client System information.

With quick registration the user “could” register their system to fog, and if you’ve enabled the QUICKREG_AUTOPOP stuff their systems could be imaged for them, based on the circumstances, but that’s about the only threat. Full Registration could occur, but if you set it up to image there, it will prompt for username and password of the FOG System to allow imaging.

You’ll notice options are removed and display for the variants of the host. You’ll also notice the debug option is not available in the default menu system. So while Quick registration, if setup on the FOG Server with an IMG id, the system COULD be imaged, this is really the only time this could happen.

That all being said, where I work we have around 2500 systems that are imaged with fog. We have never had a person “play” with the menu options in 0.32 with or without the passwording of the menu options. They typically just boot the system and wait until it’s booted into Windows. 0.32 you can simple password encode the menus. You could also Hide the menu structure if you’re that worried.

1.x.x you can Keysequence the menus, meaning they’re not available to the user in the first place, until a preset key sequence is pressed AND a valid fog username and password are entered. You can also have a No Menu option which simply checks if there’s tasks for the host, if not, just boot to the hard disk. So there are many ways you can prevent and/or stop this “issue” altogether if needed.

Hope this explains it.

[quote=“Junkhacker, post: 28517, member: 21583”]there was a line in the install script telling you that you would need to edit the config.php file if you had a password
you had to hit enter to proceed past that message[/quote]

here is the line:

[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]We are about to install MySQL Server on[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]this server, if MySQL isn’t installed already[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]you will be prompted for a root password. If[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]you don’t leave it blank you will need to change[/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]it in the config.php file located at:[/SIZE][/FONT][/COLOR]

[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]/var/www/fog/commons/config.php[/SIZE][/FONT][/COLOR]

[COLOR=#000000][FONT=Arial][SIZE=15px] [/SIZE][/FONT][/COLOR][COLOR=#000000][FONT=Arial][SIZE=15px]Press enter to acknowledge this message.[/SIZE][/FONT][/COLOR]

It talks about if MySQL isn’t install. It was already installed. Therefore It did NOT apply to me. Maybe you should read the line before criticizing me. Or you should write the line in the script so that it says change the config.php file even is you already have MySQL installed.

Also a line in the script says:
[COLOR=#000000][FONT=Arial][SIZE=15px] Please see our wiki for more information at [url]http://www.fogproject.org/wiki[/url][/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=Arial][SIZE=15px][/SIZE][/FONT][/COLOR]
That is why I suggested it should be in the wiki, not the script.

[COLOR=#000000][FONT=Arial][SIZE=15px][/SIZE][/FONT][/COLOR]