TIMEOUT of 30 or 3 seconds is probably what you want. If you hit the down arrow while the fog menu is displayed, it will not move on to the secondary boot device. A short display time for the PXE menu, insures that the startup process is not delayed too long.

Make sure the Primary MAC address listed in the FOG console is the wired MAC address on the laptop, should be correct since you did full registration from boot menu but double check anyway.

Also when you add the job check the /tftpboot/pxelinux.cfg/ directory to make sure FOG placed a file in there named with the wired mac address of the laptop. If that file is not there the laptop will instead show the default fog boot menu.
If that file is not there verify the TFTP password for the storage node configuration and the rights on the tftpboot folders.

Trying to find a page in the wiki that details the rights/passwords part, I thought one existed already.

I advise you to mount the nfs share directly on you server by adding a line in your /etc/fstab :
192.168.2.50:/nfs /images nfs defaults 0 0

2.6.39.1

Yes… make sure the image type is ‘Single Disc (Resizable)’ and it will be done automatically.

Okay, I’m going to assume it’s my image. I will add chkdsk /x 😄 to my imaging steps.

Thanks!

James, it sounds like you are having permission issues.

First, it was unable to remove the PXE file, now it cannot move image files?

The error that said it was unable to move the file told you WHY it couldn’t move the file. What was the full error message?

To fix this one
[LIST=1]
[]I would power off the uploading machine
[]Cancel the task in FOG
[]Manually move the image
[]Find and fix your system issues
[*]Life goes on 🙂
[/LIST]

Thanks, that is great news!

[B]Drive[/B]
Unless you are using E-SATA, using an external hard drive for your images is going to create a massive disk bottleneck.

I dont see the reason for the separation of images. There is no added security or performance gain, so the separation is pointless.

Apart from the reasons above (which should trump this), you cannot have 2 separate image directories.

Easy answer: Spend less money, buy internal drives, set them up in RAID, get better performance.

[B]Network[/B]
I would setup DNS in each network that points the hostname ‘fog’ (or what ever your server is called) to the correct IP Address on each network. i.e. Network 1: fog resolves to 192.168.1.1, Network 2: fog resolves to 192.168.2.1

Then configure your Clients and anything else fog related to use the hostname ‘fog’ instead of an IP Address.

[B]RAID[/B]
As long as the kernel image supports the RAID you will have no issues. You may (probably will) need to download the latest kernel.

It depends on your hardware and how your BIOS is configured.

Intel have ‘vPro’ which allows you to do what you want. (remotely change boot order)

[url]http://en.wikipedia.org/wiki/Intel_Active_Management_Technology#Using_Intel_AMT[/url]

[quote]Remote boot the PC by remotely redirecting the PC’s boot process, causing it to boot from a different image, such as a network share, bootable CD-ROM or DVD, remediation drive, or other boot device.[1][7] This feature supports remote booting a PC that has a corrupted or missing OS.[/quote]

I think this is what you want:
[LIST]
[]PXE boot to capone
[]capone displays a list of images
[]You pick an image
[]FOG images your machine
[/LIST]
Short answer: Out of the box, No
Long answer: Anything is possible if you have enough time

The FOG service can set IP Address and join your machines to your domain.

I would be using this over bat files.

I would recommend a Cisco or HP. They are both standards compliant.
I know that there are Classes / scripts out there to interface with these routers easily.

FOG is a network based solution, where clonezilla is more a media based (CD, USB, etc) solution.
That being said, Clonezilla does have network support.

Thanks for the information.