Thanks for the reply, I’m using my home environment for testing since i’m pretty new with Ubuntu, but I’ll look into Clonezilla afterwards. As for the router I just bought a new one from D-link…I’ve never had a bad one in the past and didn’t realize the one I got can not use DD-WRT without risk.
The instructions state “[FONT=sans-serif][COLOR=#000000]This allows clients to get IP addresses on the network and connect to the FOG server”[/COLOR][/FONT]. Then to turn off and configure FOG’s DHCP and turn back on. Won’t there be a conflict later on between Windows DHCP server and FOG’s after I turn it on? Is there a step missing on this page to still update the Windows Server with the PXE forwarding?
Damn I’m such a newbie
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.
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.
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.
As long as the kernel image supports the RAID you will have no issues. You may (probably will) need to download the latest kernel.
[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. This feature supports remote booting a PC that has a corrupted or missing OS.[/quote]