Any attemp to multicast on network switches that do not have IGMP Snooping will cause network flooding of broadcast packages. IGMP (Internet Group Management Protocol) settings should be found on your switches.

Hi,

Make sure that /tftpboot/fog/kernel/bzImage exists. If it doesn’t, open management console, go to Other Information --> Kernel Updates and download a kernel file.

I have noticed that you modified options 067 and 068 in the DHCP server, but the options that have to be modified are 066 (server’s IP) and 067 (pxelinux.0).

[FONT=Calibri][SIZE=2][url]http://www.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG[/url][/SIZE][/FONT]

I am trying a benchmark with virtual machines (Win 2003, Ubuntu 10.04 Desktop + FOG 0.32, Win 7) and it works perfectly.

Add the machine into fog manually, then send any task to it. through the web console. eg, an inventory task. this should clear the old task out of the data base.

I’m sure the T3500’s I have don’t have dual video cards but I’ll double check again tomorrow, its not been too much of a hassle anyway as I only have a few to image.

Alright thanks we will check it out.

Does FOG sends data to EEPROM?

Hmmm. No answer. So I will just use Windows backup… not the best solution, but it will have to suffice.

hey just an update for you guys, I got it working by using a dumb switch the managed cisco I was using as a image station was having issues. Unlike other cisco switches that flood the network when fog multicast my switch (cisco 2960) just stopped broadcasting causing fog to think the imahe ahd finished deploying causing me all sorts of MBR issues etc on the laptops. I’ll have a look in the switches config and see if I can find a fix but for now i’m just happy I can finish this roll out of laptops easily, albeit much slower than the cisco switch but atleast it works!

Thanks to all!

-James

Ok, it was supersimple 🙂

I just had to add “shutdown=on” to the pxelinux.cfg default file.

Fixed this - just reinstalled fog.

Sure. Just look in the wiki under [URL=‘http://www.fogproject.org/wiki/index.php?title=FOGUserGuide#Troubleshooting’]Troubleshooting.[/URL]

then i removed all php5 stuff and re-installed them it all worked again :). Thanx for your reply!

A follow-up for those interested.

Re-uploading a fresh SOE image to Fog solved the issue: once I had done that it was fine. Still not 100% sure why I had the issue with restoring the image files I restored from backup, but maybe it could be related to the following…

I use the standard Fog backup script, which does a good job of getting all the important stuff. One thing it doesn’t backup by default though is the /tftpboot/ partition. Now, you don’t really need to back this up unless, like me, you have made changes to anything pxe-related.

In my case, I had applied the chainloading fix described here:

[url]http://fogproject.org/wiki/index.php?title=FIX:_Chainloading_alternate_SYSLINUX_to_force_boot_from_first_hard_drive[/url]

Of course, that was ages ago and I had forgotten about it…until all of our newer Dell machines (optiplex 790) started rebooting when they tried to load the pxe boot menu 😞 Once I reapplyed the fix it was fine though.

The end result is that I manually added the /tftpboot/ partition to my fog backup scrupt, just to make things easier next time I have to do a restore (hopefully not for a while!).

If you are new to FOG, I would recommend that you set it up that that it sends out the DHCP request (The default value) This is a good way to get your feet wet with FOG. Once comfortable you can always setup a new server once you are comfortable with the test server and actually point it to your real DHCP server. If you install FOG on VMware player/workstation make sure that in your NIC settings that you have it set as Bridged and not NAT. Bridged will allow your server to pull a real IP from your network where NAT will hand out a “fake” IP based on your network.

If you are new to FOG, I strongly recommend using all default values when installing FOG on a test server, especially when MySQL is installing. If you put in a password at this point you’ll need to configure other files to match your password. Leaving everything blank will create an encrypted password that will automatically add itself to the correct files.

kwisher: Glad I’m not mad, I thought I remembered v0.32 didn’t need Fogprep… Hmmm, it’s certainly a strange one. I may have to try the wipe and reinstall method the way things are going… Or use Clonezilla 😞

Would the kernel I’m running have any bearing on the upload process (i.e. determining the wrong format?), I’m still using the original one that comes with Fog I think!!

That’s what I did, a new installation for 0.32 with the kernel that comes with it.
I don’t want to update to avoid those problems, I have to stick to the production plan.