If you want to make it so you don’t have to comment out port=0 then you can fix this by fixing the resolvconf missing dns server issue.

See this old post for a ton of detail…
https://forums.fogproject.org/topic/2799/dnsmasq-kills-dns-lookup-on-fog-server/6
I know I’ve posted it in a more readable form more recently, but found that one first.

TL:DR
just edit the interface-order at /etc/resolvconf/interface-order to have your main ethernet adapter at the top and be sure to have nameserver lines defined in your static ip definitions if not using dhcp.

Thanks Wayne for taking time to reply.

I will review your suggestions. I’m not really committed to Ubuntu so perhaps changing to OS is worth a look.

@irishfoguser Not sure what we can help you. The solution you mentioned (setup a new RAID and move the images) is perfectly fine!

@Tom-Elliott I know… and was wondering why Wayne posted the “old” URL. Didn’t pay attention and didn’t see that his post is months old…

@Tom-Elliott I updated earlier at work today (like I do most days) and I did notice that “adding needed repositories” took significantly longer than usual.

But - if that’s what it takes to ensure the remi repo gets installed, then that’s what it takes.

Should be fixed in the very latest version!

@mxc Logical partitions were an issue with FOG 1.2.0 when OS type was set to Windows as far as I can remember.

Best to debug things is to start the job/task in debug mode. When creating a capture/deploy task there is a checkbox “Schedule task as a debug task”. Starting the client you’ll get to a linux shell and you can start the task running the command fog from there (description will be displayed as well). Then you can step through the whole process by hitting ENTER. As well taking a picture or video (slow motion!) is always a great way to find out what’s going wrong. When reporting an error we need the exact error message (plus FOG version, server OS, image type and OS type) to be able to understand and reproduce the error.

GPT/MBR is a big chapter. GPT often leaves traces on the disk that might cause an issue. There is a tool called fixparts that you can use from the debug shell as well.

@RipAU Marking this solved as I feel there is nothing much more we can do. Feel free to post again if you have more questions on this.

@xmotion Sounds about right. 🙂

@Sebastian-Roth said:

@Wayne-Workman I like the “Related_to_xyz” naming. Would suite other things as well I guess. Might wanna add this to the Knowledge Base which is linked on the main wiki page!?

Done.

@Sebastian-Roth actually when I said both versions are 1.2 I meant that my old setup that is not on this network(and not connected at all, I connect to it to physically with an unmanaged switch to image right now) and the new server that is on 1.2 the other requests are coming from the dhcp and lead to an Altiris imaging server. I don’t think that matters but Ill try your solution and post real response tomorrow.

**Update ** this has been resolved using the new Undinoly.kpke from as instructed by Sebastian, Thanks you were 100% correct!

You can mark this as resolved if thats an option.
Thanks a bunch guys I just updated to trunk and am imaging my room right now.

If your running Ubuntu you should have some type of file editor installed already. I would assume that it has that loaded.

When you open your terminal you will be a local prompt, if your paths arent set you will not be able to access the file directly.

you will need to

cd /
cd etc
cd network
sudo vi interfaces

It will bring up the file in the VI text editor. Hit the insert key and then arrow down to the last line and enter

FOG Server IP (This is just a remark to remember what your doing)

auto (the name of the NIC you are using. You can use IFCONFIG to view the NICS in the machine) in my case its
auto p4p1
iface p4p1 inet static
address (your server address)
netmask(Your server netmask)
gateway(Your server gateway)

It should be some form of this. Hope this helps.

Tks Sebastian, I’ll try it on Monday in my work because I do not have access to the server today;)

@ManofValor I think Tom’s guess is right, It makes sense.

To be honest, there appears to be absolutely nothing wrong with any of the network configuration on your FOG server.

We can test to see if Tom’s guess is right or not. If this CentOS 7 was installed with a GUI, it came with Firefox. Use firefox to try to visit our forums. If you can, Tom is right - and it also means that only ports 53, 80, and 443 are allowed into your network. IF this is the case, you’ll need your boss to loosen the straps so you can get your FOG server going - after that, he can tighten em down again. Or he can create rules that allow the FOG server full access to the internet. If it were up to me, I wouldn’t have a firewall that prevents work from being done. Do you guys have a demilitarized zone the fog server can be placed in temporarily so it can be installed and configured?

@Amélie What version of FOG?

I’d say try to partition it using Linux. I have some instructions here but they are for Fedora.
https://wiki.fogproject.org/wiki/index.php?title=Fedora_21_Server#Formatting_.26_mounting_a_2nd_SATA_drive

@Jbob Hello
In first sorry for this long delay
I just made the test today with the latest client. Everything seems to work fine !!

@krishnakulkarni said:

how to upload existing captured image of CentOS on FOG?

I’m not sure if that’s a typo or poor English… no offense.

You can not upload an already captured image of anything to fog, unless the capture was done with another fog server.

If you’re simply asking how to capture an image of a CentOS machine, this is pretty basic. Network boot the machine, register it with FOG. Create a image definition in the web interface. Assign that image to the just-registered host via the web interface. in the host’s basic tasks area, choose upload. Then network boot the host again.

Version: 6122 6128
bzImage Version: 4.4.0
bzImage32 Version: 4.4.0

Edit: Just updated to check. Still no go. Rebuilding that machine from scratch and i’ll take a new reference image i guess.

@Tom-Elliott Thank you again Tom. The installer script successfully completes. All appears to be running, now to test.