[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.

Check out this article:

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

Please give an attempt to troubleshoot this on your own first. If you still have problems, let us know and we’ll help out.

More than likely you need to make a custom 32-bit bootfile for these to work. At the very least it will save you from having mess with bzImage/init.xz.

[SIZE=13px]Go here:[/SIZE]

[URL=‘https://rom-o-matic.eu/’][SIZE=13px]https://rom-o-matic.eu[/SIZE][/URL]

[SIZE=13px]Advanced - EFI PXE Bootstrap 32-bit[/SIZE]

[SIZE=13px]Check these boxes:[/SIZE]

[URL=‘http://www.ipxe.org/buildcfg/PARAM_CMD’][SIZE=13px][FONT=Arial][COLOR=#000000]PARAM_CMD[/COLOR][/FONT][/SIZE][/URL][FONT=Arial][SIZE=13px][COLOR=#000000], Form parameter commands [/COLOR][/SIZE][/FONT]
[URL=‘http://www.ipxe.org/buildcfg/CONSOLE_CMD’][SIZE=13px][FONT=Arial][COLOR=#000000]CONSOLE_CMD[/COLOR][/FONT][/SIZE][/URL][FONT=Arial][SIZE=13px][COLOR=#000000], Console command [/COLOR][/SIZE][/FONT]
[URL=‘http://www.ipxe.org/buildcfg/CPUID_SETTINGS’][SIZE=13px][FONT=Arial][COLOR=#000000]CPUID_SETTINGS[/COLOR][/FONT][/SIZE][/URL][FONT=Arial][SIZE=13px][COLOR=#000000], CPUID settings[/COLOR][/SIZE][/FONT]

[SIZE=13px]And paste this script in the script box (Replace x.x.x.x with your FOG server’s IP or hostname):[/SIZE]

[SIZE=13px]#!ipxe[/SIZE]

[SIZE=13px]dhcp[/SIZE]
[SIZE=13px]cpuid --ext 29 && set arch i386 ||[/SIZE]
[SIZE=13px]params[/SIZE]
[SIZE=13px]param mac0 ${net0/mac}[/SIZE]
[SIZE=13px]param arch ${arch}[/SIZE]
[SIZE=13px]param product ${product}[/SIZE]
[SIZE=13px]param manufacturer ${product}[/SIZE]
[SIZE=13px]param ipxever ${version}[/SIZE]
[SIZE=13px]param filename ${filename}[/SIZE]
[SIZE=13px]isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme[/SIZE]
[SIZE=13px]isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme[/SIZE]
[SIZE=13px]:bootme[/SIZE]
[SIZE=13px]chain [/SIZE][URL=‘http://x.x.x.x/fog/service/ipxe/boot.php##params’][SIZE=13px]http://x.x.x.x/fog/service/ipxe/boot.php##params[/SIZE][/URL]

[SIZE=13px]Click Proceed, and voila! Copy the new EFI bootfile to your /tftpboot folder and give it a whirl![/SIZE]

[quote=“Tom Elliott, post: 39607, member: 7271”]This is good.

This is good.

What do you mean a text file? Is it asking you to download a file or is it displaying text in the browser? Can you give us some of the output?

colour --rgb 0xff0000 0 is the correct syntax

The english spelling never worked. iPXE was never coded using US English syntax. All the error you’re seeing means is that the ipxe.iso you have does not have the command tools built into it.[/quote]

I’m running into the same error. I’m using a website, [url]https://rom-o-matic.eu[/url] , to build my ipxe.iso.
I’m guessing that I’m missing some build options that deal with the command tools.
Have any of you used this site before to build your ISO? If so can you tell me what option(s) I must select in order to rectify this issue?