Thank you for the replies.

One more quick question not related to the thread title.

Is there an easy way to export my old fog groups/hosts/images/etc to the new fog server?

I see the new fog has it built in!

Thank you, I did not see it in documentation at first glance. I love easy fixes!

[IMG]http://i.imgur.com/u2CzAQS.jpg[/IMG]

Good morning!

I have a working fog .32 server that I have been using for a few years. I have a windows domain with dhcp that I have configured to use the fog server as the boot server.

I recently added a fog 1.1.2 server to check out the new features. I gave the new server a new IP and changed my dhcp scope option to reflect the new IP (to test the new server).

However when I boot clients with the NIC first they do not find the server. I’m sure I’m missing something simple, here is how the dhcp scope looks (10.10.1.251 is the new fog 1.1.2 server):

Any ideas?

When I boot the clients say: something along the lines of TFTP: File not found

It worked. Yay!

Took a little playing with to get the files copied correctly, linux file permissions aren’t my strong suit.

P.S. I used pxelinux.0, chain.c32, and vesamenu.c32 all from syslinux 4.05 in case anyone else runs into this.

I have no idea what syslinux even is but it fixed my problem, so it can have my first born.

A modification to /tftpboot/pxelinux/default looks like what I may need. However like previously stated I’m not sure fog is even seeing the hard drive.

LABEL fog.local
localboot 0
MENU DEFAULT
MENU LABEL Boot from hard disk
TEXT HELP
Boot from the local hard drive
If you are unsure, select this option.
ENDTEXT

I wonder if localboot 0 is not working with this systems drives configuration? Hmmmm…

That’s what this thread is about though. I would like them to boot to the nic as the first option for remote administration purposes.

I found this from another post, not sure if it’s what I need yet though,
[url]http://www.fogproject.org/wiki/index.php?title=Boot_looping_and_Chainloading[/url]

After reading another recent thread this sounds like an issue fixed by chainloading…

Agree?

Sorry if this is a duplicate post but I’m not sure they’re the same.

It’s a dell optiplex 390 small form factor. I’ve never had this issue before, in fact my SFF optiplex 380s are working just fine.

I’m thinking it might have something to do with outside processes not having access to the drive. When I boot up a ubuntu usb drive on this system I can’t even see the disk file system.

I can still image these PCs but I just can’t have the network card set as the first boot option (which will be a little problem since the remote branch where they will be located is an hour away and I’d like to have automated imaging out there :)).

If I do set the network card to boot first, the fog menu displays, but then it won’t boot the hard drive and just reboots the computer instead. Hope I’m explaining that well enough…lol.

Any ideas?