Nope. I removed them from the task management tab and the hosts/groups tabs.

I have just found that if I manually add the devices and fill in the info and then create a new task, I am able to image a single device. I will try multicast next. This looks like it will be my workaround for this issue.

If multicast don’t work, then i’ll just do the last four individually.

Justin

I was going to try to do a multicast and it failed. I read in the forum that it failed because I did a quick registration instead of a full. That was exactly my problem. Now I am trying to register the hosts in FOG again but the four computers are not PXE booting to the FOG menu. Instead, they PXE boot to fog and they attempt to multicast and it says “invalid operating system ID.” I am unable to get the FOG menu to come up so that I can do a full inventory and register the hosts. I have removed the hosts from FOG and I am able to image other computers just fine. It is just an issue with the original four that I did a quick registration for.

There must be a table or setting somewhere where I can clear the hosts and allow them to PXE boot to the FOG menu instead of continuing to try and do a multicast which constantly fails.

It is installed on Ubunutu 13.10 and FOG 0.32.
Thanks,

Justin

Thank you for the reply.

I am following the directions to get fog 0.32 installed on Ubuntu 12 with this link.
[url]http://www.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]

In step five, I am unable to edit the exports file. How do I do this? It is in use or write protected?

Justin

Thanks for the replies.

The PXE boot worked when I downloaded [URL=‘http://sourceforge.net/projects/freeghost/files/FOG/fog_0.32/’][B][FONT=sans-serif][U][COLOR=#0099cc]fog_0.32[/COLOR][/U][/FONT][/B][/URL] using my home Linksys router. However, I had trouble accessing the RUI with that version. Now that I am installing the latest 1.0.1 and I can access the RUI but not get PXE to boot.

I am just doing this at home as a test. Once I am ready, I will be doing this on a network with a Cisco ASA 5505. I am guessing that will need its own setting to be modified to get it to work.

I was only going to image about 15 computers. At this point, it almost isn’t worth dealing with it.

The weird thing about this is that the FOG install will wake up the computer I am trying to copy the master image from but PXE still won’t boot.

I will look through your suggestions and see what I can get working.

Justin

I followed the directions to install and prepare FOG in the link below.

[url]http://www.fogproject.org/wiki/index.php/Ubuntu_12.04[/url]

The install went fine and I am able to access the Web GUI just fine. After following the directions, I am unable to get clients to PXE boot. It always fails with the error that not PXE file was received. I am running Ubuntu 13.10 and the latest 1.0.1 FOG.

I am testing this at home with my DHCP enabled Linksys router. I was hoping my router could assign the IP address and then FOG could load the PXE boot menu.

Anyone know what could be wrong?

Thanks,

Justin

Thank you.

I will try that now.

Justin

I am trying to install Ubunti 13 and the install goes fine. I start following directions to install FOG from this link.

[url]http://www.fogproject.org/wiki/index.php/Ubuntu_12.04[/url]

After I enable root and restart, the computer boots to a black screen. This has happened on two different computers of the exact same make/model.

Is this a known issue? How does this get resolved?

Thanks,

Justin

Thank you for the replies.

Since I already have the latest version installed. I will just try that quick. If it works, great. If not, then i’ll go back to version 13.

Justin

I installed Ubuntu 14.04 LTS 64-bit. I just ran the two commands you sent me. I will now try to install FOG and let you know if the same issues occurs.

Thanks,

Justin

Thanks for the reply but I am already reinstalling. It should not be this hard so something must of went wrong. I’ll let you know if I still have this issue after reinstalling.

Thanks,

Justin