Hi again Tom,
I’ve updated to 1.1.1 and the behaviour is the same. Launching a mullticast deploy the associated snap-ins are not launched.
By the way, what is the deployment button that appears in host list for? It seems to launch a deploy of one host using multicast, but that doesn’t have much sense.
Regards.

Frank

Not to hijack the thread or anything 😉 but I think this is a related question:

Running Fog 0.32 - Do I need to upgrade to 1.0.0 first, or can I upgrade directly to 1.1.1 following the same upgrade steps in the wiki?

The NFS that works is on a Windows server, and the one I haven’t gotten working yet is on the FOG server. And I do have it in the exports file, but come to think of it I should take another look at the settings it has.

1827, technically now.

No… so I am not familiar with what a FAI server does. Does it behave like FOG where it will replace its standard menu with a chainload if you give a task for a workstation that is registered to it? Or does it only supply a menu during its PXE boot every time no matter what?

change the arch to amd64 and see if you get the same errors

Microsoft-Windows-Shell-Setup Microsoft-Windows-International-Core Microsoft-Windows-Shell-Setup

it changes how ipxe attempts to exit and allow the computer to the hard drive. different bios may require different methods to boot properly

Hi Again I did a complete reinstall both OS 13.10 ubuntu and Fog 1.1.0 still have the time issue . I went in to php5/apache2/php.ini and entered America/New_York ,restarted apache2 ,it’s not fixing the problem . please help.

I’d think, you could poll the database based on the Host to Group associations and make the entry in the inventory report yourself.

How to do so is not that hard either, though with 0.29 I don’t know how easy it would be to do.

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]