[url]http://fogproject.org/wiki/index.php/WorkingDevices[/url]
[url]http://fogproject.org/wiki/index.php/ProblematicDevices[/url]

They are on the left column in the WiKi. [url]http://fogproject.org/wiki/index.php/Main_Page[/url]

If the image was set to “Resizable”, then it doesn’t matter.

I’m guessing it’s not re-sizable.

Make sure your FTP settings / permissions are correct for the Kernel Update. More info here: [url]http://fogproject.org/wiki/index.php/Troubleshoot_FTP[/url]

To update to the latest svn, go to where you downloaded the last one, and just run:
[code]svn up[/code]

then go to the bin directory, and run the installfog.sh

More info here: [url]http://fogproject.org/wiki/index.php/SVN[/url]

[quote=“KJ You, post: 46997, member: 22149”]mine doesn’t show “format” column[/quote]

I apologize… that might only be there for the newer developmental releases…

if you click on an image itself, on the left, it should show the image type. And there might even be an option somewhere in 1.2.0 settings to let you support older image formats… not sure… I’ve never used 1.2.0 in production. I use the developmental releases only, because Tom made a change in them to allow FOG to work in my environment.

oh … i didn’t read the whole post, my bad !

You do not need to install the new client, I just wanted to know which one you were having issues with so I could better help troubleshoot it for you.

It sounds like you fixed it though.

If you select any one of the tasks it will present a deployment confirmation. On the confirmation it asks you how/when you want it to happen. Instant means immediately. Delayed means one time in the future. Cron style means you want it to happen on a regular cycle.

solved
under fog configuration - fog boot setting

Duplicate thread. Follow here: [url]http://fogproject.org/forum/threads/failed-to-create-deployment-tasks-for-the-following-hosts-hosts-do-not-have-uniformed-image-assignm.12889/[/url]

Updated to SVN 3365 seems to have fixed the issue.

Also, I think changing this line will keep you from having to enter in the TFTP server IP manually into each workstation:

You have:
[CODE]pxe-service=X86PC, “Boot from network”, undionly.kpxe[/CODE]

Change to:
[CODE]pxe-service=X86PC, “Boot from network”, undionly.kpxe, <tftp-server-ip-goes-here>[/CODE]

Reference:
[url]http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html[/url]

I follow. So its the SysAdmin’s responsibility on their end, not the FOG Project’s responsibility. 😛

After updating to subversion 3356 the problem is solved.
Thanks a lot for you help!

Stefan

Compiling your own rom allows you to embed scripting for things like chainloading.
Additionally the ipxe.iso provided by ipxe.org does not support the [B]colour [/B]command which will cause the boot.php to fail

Update,

Appears to be the cable, yet we’ve been using this same cable to image all of our other machines. And the device is still capable of pulling DHCP using this ethernet cord. . .

Nothing like a bad cable

Brilliant Tom.

Your quite right. The internet link I use to connect to the Fog server, on a seperate link, has just been upgraded to fibre. I checked the NAT pool, and there were several IPs that were being used as the NAT address. so effectivly I could have one of 5 IP’s hitting the Fog server. So your right, the fog server was getting multipe requests from different IP’s with the same session. I changed the NAT to just one IP, and the problem has gone away. Well untill tomorrow when the Fog server’s 2 internet links also get upgraded, but that shouldn’t be a problem now.

Thanks you all so much for your help, it’s really apprechiated, and I am grateful. It also reminded me to do a backup, which takes a few days, but I need to do it.

Now this is resolved, how do I make it a “Solved” problem and easily found to the next poor chap who changes his network?

Thanks once again, and have a good day to all those that helped.

Yours

Julian

Thx for your answer…

All this talk about joining to specific OUs is kinda gross… (Just my opinion).

If you don’t want your computer objects to be joined and placed inside the default “computers” OU, you can just change the default…

I’ve got a nested OU inside my primary OU, it’s called “DEFAULT”. Everything new / renamed that gets joined shows up in there. This way, even if we forget to move the computer where it should go (like “Lab xxxx”, “Conference Room”, etc). The machine will at least get all the policy that we have applied to every machine in the building, and will also grab the right policy on reboot after domain joining.

It’s super spiffy and it lets me totally avoid all this Specific OU joining stuff.

Works SVN 3353.

[quote=“Joseph Hales, post: 46730, member: 18131”]Install FOG client for everyone you no longer need to run fog prep for fog 1.2 and up.[/quote]

Thanks for the reply! I let the virtual machine I make my image in run after sysprep and the test seems to indicate that installing for everyone is the way to go.

Thanks again.