Two issues I'm having

[BrendoJohnso]

This post is deleted!

[Tom Elliott]

@BrendoJohnso
Imported Hosts need at least two fields:

First field would be the mac address(es) of the host.
Second field would be the hostname.

The CSV would look something like:

00:ab:cd:ef:12:34|01:02:03:04:05:06,SomeHostName

Importing this would create a host with:
Name: SomeHostName
Primary MAC: 00acd:ef:12:34
Additional MACs: 01:02:03:04:05:06

[george1421]

If given the option I would install FOG 1.3.4 or 1.3.5RC (dev branch) over 1.2.0. If this is only for testing 1.2.0 (stable) will work. The issue you have is that 1.2.0 is about 4 years old and it doesn’t support Win10, GPT format, uefi, and Nvme disks. If you are testing with old hardware then 1.2.0 will work just fine. Its the newer stuff that you will have issues with.

Now to your point.

Getting FOG rolling, includes several technologies outside of FOG itself.

You need to update your dhcp server to point to the FOG server so the PXE booting clients know how to find your FOG server. This is done by updating dhcp options 66 {next-server} and 67 {boot-file}. DHCP option 66 should be set to the IP address of your FOG server. DHCP option 67 should be set to undionly.kpxe. Once you have that setup you should be able to PXE boot your target computers and see the FOG iPXE menu.

Once you get to this point you can take the next steps.

[BrendoJohnso]

@Tom-Elliott I used Excel and put in the primary Macs and host names does it all need to be in one cell or will adjoining cells work

[BrendoJohnso]

@george1421 Thank you if there are anymore outer Fog steps that are needed please go ahead and list them for me as itll be awhile before i can setup the actual server

[george1421]

@BrendoJohnso You have FOG 1.2.0 running on Ubuntu 14.04 right?

If so that part is setup, all you need to do is setup / change your dhcp settings. If you are doing this test setup in a home lab then there are a few other things we could setup. Home dhcp servers (typically your ISP router) doesn’t have the options needed to pxe boot computers. This isn’t a problem either, we just need to know a bit more of your setup.

[BrendoJohnso]

@george1421 Thank you very much makes it a lot better I’m going to see like you said about updating the Fog version quickly to 1.3.4

[BrendoJohnso]

@Tom-Elliott It is working perfectly with the imports now thank you so much just saved me from manually entering 600 hosts

[george1421]

@BrendoJohnso That is find if you want to upgrade. Its not a bad idea.

I can tell you the normal work flow for fog is this.

(new computer)->PXE boot into FOG->Select Registration Menu->Register->Image deployment.

You don’t need to pre-register computers as you are doing with your spreadsheet. You can do it that way, its just extra work for little value.

[BrendoJohnso]

@george1421 My higher-ups would like to have them all on file beforehand or i would do it that way but thank you

[BrendoJohnso]

@george1421 I managed to get the settings and everything changed for the DHCP server but when i Pxe boot now it says that TFTP has “open timeout” and still does not get to Fog

[Tom Elliott]

@BrendoJohnso Have you checked firewalls on the FOG Server?

[george1421]

@BrendoJohnso There are 2 things you need to do to the FOG host server when FOG is installed.

1. Disable the firewall (iptables)
2. Change selinux config to permissive.

beyond that.
On the fog server linux console, if you key in the following command sudo netstat -an|grep 69 that should give you an output that looks like this:

# sudo netstat -an|grep 69
udp        0      0 0.0.0.0:69              0.0.0.0:*

That tells us the tftp server is running (what the client needs to pick up the undionly.kpxe file)

If you are unsure if the firewall is disabled, post the output of this command sudo iptables -L

If your output looks like this then your firewall is off

# sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

[BrendoJohnso]

@george1421 The firewall one looks the same so its off
However the tftp one says this

[Tom Elliott]

@BrendoJohnso What’s output with:

sudo systemctl status tftpd-hpa

[BrendoJohnso]

@Tom-Elliott its saying that’s an unknown command

[Tom Elliott]

@BrendoJohnso Maybe:

service tftpd-hpa status

[BrendoJohnso]

@Tom-Elliott tftpd-hpa start/running

[Tom Elliott]

@BrendoJohnso So looking at the picture of the netstat -an | grep 69 command, I don’t see anything showing “network” outgoing stuff.

Maybe:

ifconfig

Might help us out?

[BrendoJohnso]

@Tom-Elliott