I don’t think a session will not start until all hosts have checked in. Have you made sure this is not the issue?

The image definition is what you actually create with the FOG interface. Basically follow all the steps for creating an image with FOG, just don’t actually create an upload task, and then copy the image files created with PING to the directory specified for the image file.

You will probably need use something like wireshark and look for the packets to see how far they are getting.
it uses UDP port 9 i believe so you may have to allow that to go in your router also.

Also you may want to remember that allowing ip-directed broadcast has the ability to flood your network with broadcast across sub nets unless you put something in place to mitigate that.

Shows here as well under windows 7 Chrome 20.0.1132

You aren’t running any extensions like no script or are you?

I had a similar problem. I merged two Windows 7 partitions (boot and system) because I wanted to use single resizable partition. The image size was over 200Gb. I restarted the computer, ran chkdisk /f twice, defragged, and used FogPrep and… the new image size was 16GB. I’m using version 0.32

unmanaged switches don’t allow switch admins to misconfigure them…

Check the processor statistics on the switches to see if they are overloaded. There may be too many rules, or rules that are invalid or detrimental.

If you are allowed and technically able, backup the running config and then reset the switch to factory settings. If it works without issue, compare the configs until you find the issue.

Hi Robin

I take it you’ve created your new Win7 image and have uploaded it to the server correct? And you’ve associated that new image to the host you’re trying to image and also updated the host os entry to win7 too. If you open the host from the GUI and deploy the image from there what happens?

Tom

The stGroupHostID is the hostID, I believe. Look for hostID=12 in the hosts table:
select * from hosts where hostID=12;
See if that host is listed twice in the active tasks on the webpage. You should be able to look up the hostIDs in the hosts table and figure out which ones have “scheduledTasks”.

astruga

Solved:
OK, as I said in the last post this is a secondary node with a master storage node for images. I had updated the image and uploaded it directly to the secondary storage node, but the main storage node at the central office still had the previous version of the image. Jus to test I uploaded the image file from the secondary node back up to the main node and tried to multicast again. It worked at it should! Note to self: Always upload to main storage node fresh images and let them replicate down to the secondary nodes at the schools.

Thank you, I sent my email address.

I did get that error and, on a whim, checked permissions on the /images folder. As it turns out, only root had write permissions there. Once I corrected the permissions, all is well. Thanks for the post. Everyone here is great.

I tried that and it still didn’t fix it, very wierd I though

you may be able to chroot/fakeroot with the fog kernel and init.gz, but I am not experienced with that enough to tell you how.

looking at the ubuntu install, it only has language packs for IT, EN, ES, and ZH-HANS. There is a wiki article on [url]http://fogproject.org/wiki/index.php/How_to_translate_FOG[/url]

[quote=“chad-bisd, post: 5103, member: 18”]Download the kernel from the sourceforge page you linked above. Backup your current kernel and then copy this one to the /tftpboot/fog/kernel directory. Rename it bzImage and chown to fog:root.

Try to boot up one of the new laptops and see how it works for you.[/quote]

Thanks for your help. Updated kernel and it’s working, using a custom kernel from fellow user.

Have you tried getting a later kernel from the “Other Information” > “Kernel Updates” page?

Update on this,

If you modify your pxe boot menu passwords after doing this, it will overwrite /tftpboot/pxelinux.cfg/default which breaks the chainloading.

To fix it just replace

LABEL fog.local
[COLOR=#339966]localboot 0[/COLOR]
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive
If you are unsure, select this option.
ENDTEXT

with

LABEL fog.local
[COLOR=#339966]kernel chain.c32[/COLOR]
[COLOR=#339966]append hd0[/COLOR]
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive
If you are unsure, select this option.
ENDTEXT

In /tftpboot/pxelinux.cfg/default
To re-fix it.

🙂

You set the IP or FQDN of the FOG server when you install the FOG client. That is stored in a config file inside the FOG client install directory. I can’t remember the path off the top of my head but it’s something like C:\Program Files (x86)\FOG\etc\config.ini …or something like that.

Chad, sorry for the delayed response, and to answer your question yes I had. I ended up doing a DBAN wipe and fresh installing which resolved my issues.

Thanks for all your help,

Jeff

quote=“Gorosoki, post: 4981, member: 1248”]I deployed an image with the bzimage34 kernel and it finished after about 4 hours. The Windows 7 image didn’t deploy right. Window repair tried to fix it, but it couldn’t. Any suggestions?[/quote]

How do you have the rest of your image definition set up? Try setting the image type to “Multiple partiton - single disk(not resizable)”, even if it is only 1 partition.

Is this a clean install of Win 7 or an OEM install? I’d take one of the spares and install windows 7 from scratch (removing the 100 MB partition). No apps or patches. Just try to upload and deploy. If it works, you can be sure that FOG is working with your hardware and you can focus on your partition/filesystem.

Sounds like this is unlikely to help, but here is a 3.4.5 kernel. I used it the other day and it works fine on my systems:
[SIZE=2][COLOR=#0060e0][url]http://www.filedropper.com/bzimage34_1[/url][/COLOR][/SIZE]

astrouga