Ok. so easy ! sorry for bothering.

Another possibility is that if you are using HP ProCurve switches, the Spanning Tree protocol could be causing the delays which will cause pxe to timeout. I am not sure why reverting to an older bios will help this, but maybe they simply have a longer timeout period.

TRY turning spanning tree OFF for the switch that the system you are wanting PXE boot is connected to and see if that helps. If it does, then this could be an option for when you need to reimage a room. It is probably best to ensure Spanning Tree is re-enabled when finished to ensure there is some protection from network loops.

Just to touch base, setting the Clone flag in deepfreze while imaging did NOT fix the issue.

I also want to clarify that it is NOT a FOG issue.

Faronics is aware of the issues with the thaw spaces and the beta test team is working on resolving the issue.

I hate to tell you this, but I had to blowout my fog server and start over. Also, any images I created during the reign of 12.04 had to be removed as well. The recovery wasn’t that bad since I backup my SQL database, tftpboot folder, and images folder manually. Until a new version of FOG comes out, I’m staying at 10.04.

Was able to fix the udpcast glitch, using Timeloard83’s post. However now i cannot access the web interface, it redirects me to “[url]http://192.168.137.5/fog/commons/schemaupdater/index.php?redir=1[/url]”

[quote=“Kylejb007, post: 4521, member: 1442”]Chad and Raff,

That Did it!!! The intial results have been really impressive. Today we imaged our high School (Classrooms), which is approx. 80 machines… Normally we use to use Novell Zenworks to image them and it would take practically 1 whole day to image (at least 4-6 hours) and we would come in the next day and join them to the domain. Well im pleased to say that we started this morning at 9am, and completed the last computer (we dont have the fog service setup yet) we joined the last computer to the domain at 3:30PM. All of the machines loaded up fine with no Kernel downloading slow, and the Storage Node happily pumped images out to 10 machines at a time with everyone taking roughly 25-30 minutes to complete each. We even had to re-queue a couple computers due to Sysprep failing to process the unattend file, I assume this happens due to a network glitch pushing it to it or hardware glitch on the end station, usually a second image to it and it works rarely have I had to do it a thrid time, I end up switching patch cords and that fixes it.

Do I dare increase the amount of machines imaging at one time or I do have another decomissioned G5 I could use if I wanted… This is our largest building so the others shouldnt have any issues at all with time, I just figured for planning in the future to do 20 at a time would speed things up tremendously.

Definitly thanks for the advice, best product around![/quote]

Same experience here. We use ZENWorks for other functions, but dropped it for imaging purposes as soon as we found FOG!

Update - Yeah creating a brand new image from scratch from a new client seems to have fixed it.

See the following

[url]http://fogproject.org/forum/threads/tftp-problems.6442/[/url]

Hello Matt, I was wondering if you solved this. I’m stuck at the same point. We have over a 140 3330’s that are awaiting to be imaged.

[CODE]mysql -u root -h <hostname> fog[/CODE]
If you have a root password for mysql:
[CODE]mysql -u root -pPASSWORD -h <hostname> fog[/CODE]

[quote=“Musoni, post: 15873, member: 14999”]I too am having the same issues with the carbons. Have you had any luck moving forward? What corrected the locked driver issue?[/quote] Yes, we had some carbons with a bad motherboard (sorry I’m not sure exactly what was bad about the motherboard). We also had a some board USB network adapters - this was very frustrating - but we finally got the carbons out the door. If I were to do this again I would order a couple extra USB network adapters.

Glad I could be of assistance.

It turns out to be that [URL=‘http://www.rasteredge.com/how-to/csharp-imaging/load-from-file/’]Loading image[/URL] with fog is a wise choice !I use an image assistance to load image and process image before.But my computercrushed.So i changed as fog.I love it.

did you try sudo before editting the files?

[CODE]
sudo nano -w /var/www/fog/…whatever
[/CODE]

[url]http://www.fogproject.org/wiki/index.php?title=Change_NFS_location[/url]

Between your suggestions Tom, and the link above, I was able to solve all of the issues I’ve had so far as I can tell. This is basically a solved thread. Thanks a ton.

I don’t have a site, but the FOG Wiki’s pages do have a method of you creating them. It’s really simple though.

Download the kernel.

Untar/extract the kernel source

Copy the configuration file (either from your fog installation, or you can use mine.) [url]https://mastacontrola.com/fogboot/kernel/TomElliott.config[/url]

cd into the unextraced folder:
cd linux-<version>

Copy the configuration file as (note the period before the file name) -> .config within the linux-<version> directory.

Run the command:
make ARCH=i386 menuconfig
Make any changes you need, or just exit and save the configuration.
Then once complete run:

make ARCH=i386 bzImage

Once it’s done building copy the bzImage file to your /tftpboot/fog/kernel directory, also create a copy of the original for backup if you made a mistake:

cp /tftpboot/fog/kernel/bzImage /tftpboot/fog/kernel/bzImage.original

cp arch/x86/boot/bzimage /tftpboot/fog/kernel/

You should be set.

Also, here’s the link for the wiki:
[url]http://fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]

It sounds like you installed the DHCP server on your fog server, and it’s not communicating properly because your router doesn’t know how to pass the information, to the tftp server. What kind of router are you using? Do you have the ability to setup something like:
dhcp-boot=pxelinux.0,fogstorage,192.168.XXX.XXX
or
next-server options,
or
DHCP 66/67 information?

Could you try with a switch or hub connected directly to the fog server (bypassing the router) just to see if it can actually communicate with the FOG Server?

So you’re not running thru a mod_fcgi process if it’s all defaults. I’d find out what’s eating your memory on the server then. You mean that there’s 11+GB of RAM in use on your fog server? That’s crazy, and definitely would be the cause of slowness as that much used RAM would also mean your CPU is constantly in use.