You might want to look into this.

[quote=“Bjorn Jentoft, post: 2149, member: 587”]It’s a known fact that tftp is not the fastest protocol out there. Bigger files transfer much better on http. If you exchange [B]pxelinux.0[/B] with [B]gpxelinux.0[/B], http is supported. This will decrease loading time of ISO files substantially.

Your pxelinux.cfg/default would then contain something like this

LABEL winstall32
MENU LABEL Install Windows (all 32-bit)
LINUX memdisk
INITRD [url]http://myfogserver/iso/LiteTouchPE_x86.iso[/url]
APPEND iso raw

or

LABEL winpe
MENU LABEL WinPE
LINUX memdisk
INITRD [url]http://myfogserver/iso/mywinpe.iso[/url]
APPEND iso raw

Good luck, Bjorn[/quote]

the gpxelinux.0 can be grabbed from SYSlinux, [url]https://www.kernel.org/pub/linux/utils/boot/syslinux/[/url]

I have installed FOG on my Fedore Core 7 box, and I am unable to get to the default management webpage ([URL=‘http://localhost/fog/management’][SIZE=12px][FONT=Arial][U][B][COLOR=#000000]http://localhost/fog/management[/COLOR][/B][/U][/FONT][/SIZE][/URL]). I created 'fog" in www, and copied everything from ‘packages/web/’ to ‘var/www/fog/’.

Now the problem is that I’m not sure if I’ve edited the ‘/var/www/fog/commons/config.php’ file correctly with the correct MySQL settings. I’m also not sure if the ‘/opt/fog_0.32/packages/service/etc/config.php’ file was also edited correctly.

And when I try to log into the MySQL server via the terminal using the username and password indicated in the config.php file, it doesn’t accept the password.
Any help would be greatly appricated!
Thanks.

What kernel are you using in fog? I found that I could not use the 3.6.9 core kernel with some of our machines including the Optiplex 755s. I have the 3.3.3 core as a secondary that I have to manually configure for and of the problem systems.

I am having the same problem, I am running the FOG server under Hyper-V on Windows 2008R2 datacenter. Could the virtualized network adapter (legacy network) on Hyper-V cause this?

It does not work either manually or thru the menu. I have used a WOL utility from the same subnet and it works. FOG does not seem to be sending any WOL packet.

Hi,

I had the same issue, it was simply the OS not being set properly… For a Windows 7 image marked as “single partition”, it creates a directory to skip the possible bitlocker partition anyway… So if you have a host marked as say WinXP, on a single partition image, it fails to restore it. Switching the Host OS type fixes it!

Cheers

Thanks! Ill check that out.

I’m trying to complete a similar task. I enabled the checkbox for the “Is Master Node” for my second storage node, which is in a second storage group. After doing so, both the default storage node and my new storage node are the Master Node in each storage group.

However, after doing this, I’m still receiving the same “Create task failed. Unable to located master node from storage group” error message you are receiving when trying to clone a computer to create an image on the new storage node.

Our new storage node is located on a NETGEAR ReadyNAS. I’m not 100% certain I have it configured correctly though, as I’m only my second day in with using FOG.

I believe that answers your question, but it’s not really a solution…unless your new storage is configured correctly and mine is not.

Let us know how it turns out for you.

More solutions to this problem here: [url]http://fogproject.org/forum/threads/error-creating-tasks-internal-service-error.3798/#post-10223[/url]

Ok so the issue seems to stem from two things, incorrect php/mysql version or a &$tmp flag in part of the includes scripts for FOG itself.

[B]Check your php version first with “php -v” in a terminal - if you’re running 5.1 or earlier you will need to update![/B]

I ran these instructions/commands to update from PHP 5.1 to 5.2 in Centos 5.5 and it got my FOG working again. Please try updating to php 5.2 first before you go to 5.3 - you never know what it’ll break.

Get the Atomic repo (for Centos)
[QUOTE]wget -q -O - [url]http://www.atomicorp.com/installers/atomic.sh[/url] | sh[/QUOTE]

Edit repo to exlude php 5.3 (we just want 5.2 for testing purposes, coz we’re updating from 5.1)
[QUOTE]nano /etc/yum.repos.d/atomic.repo[/QUOTE]

(and add in the line) [I]exclude = php5.3[/I]

Update php
[QUOTE]yum update php[/QUOTE]

Restart Apache
[QUOTE]/etc/init.d/httpd restart[/QUOTE]

After these steps, I went through the help provided here: [url]http://fogproject.org/forum/threads/solved-cant-upload-images.3652/#post-8628[/url]

[QUOTE]So you should be able to search the /var/www/fog/management/includes/tasks.confirm.include.php for all instances of “&$tmp” and replace them with just “$tmp” [/QUOTE]

Everything is now imaging again and working the way it should 😄

[quote=“Terry Bates, post: 5057, member: 594”]Hey Lethal

I added the following to /var/www/fog/management/includes/tasks.advanced.include.php around line 165, i’m using FOG 0.32, seems to work a treat, not sure why its not included in the standard build.

[PHP] <tr>
<td class=“c”><a href=“?node=tasks&type=group&direction=onesnap&noconfirm=<?php print $groupid; ?>”><img src=“./images/snap.png” /><p><?php print _(‘Deploy Single Snapin’); ?></p></a></td>
<td><p><?php print _(‘This option allows you to send a single snapin to a Group. (Requires FOG Service to be installed on client)’); ?></p></td>
</tr>[/PHP]

Would love to know how you have added extra info to the database I would like to add a location to the hosts section so I know where my computers are, have requested the feature maybe you can help [url]http://fogproject.org/forum/threads/location-information-for-each-host.913/[/url][/quote]

Thanks Lethal, this is a great help. I’m going to use FOG to apply updates for programs such as flash/java etc. This is great thankyou,

No, I take back what I said earlier. Did some research into how it actually works, and what I said made no sense.

Can you make a temporary file for PXE to attempt to download that isn’t labeled pxelinux.0, point the DHCP servers to it, and then see if PXE will recognize and pull it across?

Just like to add I’m having the same issue but with a Dell Optiplex 760, what confounds me is that I’m sure it’s worked before…
(Using Fog 0.32 on Ubuntu 11.10, I forget which kernel exactly but it was changed from the default to the ‘kitchen sink’ one as it wasn’t working with other clients)

I’d already gone through and done the &$ to $ trick, was battling with one error after the other setting it up but Google was my friend.

It’s imaging right as rain now.

I ended up testing on another (4th) machine and that worked too but this ASUS still refused to play ball.

However, finally solved it!! (I couldn’t work out how to change the title, if an admin wants to mark it solved, please go for it)

It ends up the problem seemed to be that my Fog server (within TFTP) was handing out the wrong DNS server IP (DHCP was handing out the right one, just it was wrong in the Fog settings). I’m still not sure why or how that was the problem (my FOG storage server was set using IP not hostname) and it was strange that all the other machines worked ok (just not this one). But that seemed to fix it, so happy days! 🙂

Do you have auto updates enabled or have you recently updated your mysql? I’ll look through the code to see what the exact statement is and why it might be broken now even though it worked before.

It looks like it’s at [url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/tags/0.31/packages/web/service/auto.register.php?revision=701&view=markup[/url] line 62, but I don’t see anything wrong with the statement.

Look at your /var/www/fog/service/auto.register.php and see if it’s been modified recently and check your apache logs to see if there are any errors about the PHP.

I don’t have much else for you at this point.

Hi again,

issue solved, my if is em1 not eth0 🙂

Someone has posted on these forums the code modifications necessary to implement this in FOG. Requires changing some code so it prompts you which partitions you want to restore.

[url]http://fogproject.org/forum/threads/more-control-with-partitions.68/#post-3330[/url]

It’s written to work with FOG 0.30, but might work with FOG 0.32 with some slight modifications.