Best posts made by Jaymes Driver

@Tony-Ayre

Thank you very much, This may help someone in the future with a similar issue

I appreciate you taking the time to explain your issue and your resolution!

@george1421 I second this notion.

I have a 32 bit Ubuntu 10.04 on FOG 0.32 that is moth balling at the moment.

I did clone the hard drive a few times with clonezilla and try to upgrade it… I spent FAR less time building a new server and importing new images. But I like to do things the hard way from time to time, just to see if it’s possible.

I did get the operating system upgraded fine. The move from x32 to x64 left a lot of things broken (packages wouldn’t install, etc.) and I couldn’t get to the images via pxe or web gui.

It seemed to work fine before I moved from x32 to x64 when I upgraded 10.04 to 14.04, but I digress: If you moth ball the server, you have something to fall back on in a pinch.

@plegrand Thank you for providing the solution that you have found, I am certain that someone else will benefit from this information!

Glad you got it all sorted!

@mimi1255
From command prompt
sudo apt-get update
sudo apt-get install update-manager-core
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo do-release-upgrade -d

If you don’t have much on the server, it might be faster to download 16.04 and install it to your machine.

I upgraded my 10.04 x32 all the way to 16.04 x64… I don’t recommend this, in the end due to all the errors, I just installed from scratch and imported my old images one at a time with a capture task from the new server.

@Tom-Elliott Excitedly downloads new RC

@matthewk2010

Is the tftp server that the VOIP system uses in the same subnet and vlan as the FOG server?

What switches do you use?

This leads me to believe that something in the network, or switches is not configured correctly.

@matthewk2010 This is unicast.

Multicast is when you send the same image to multiple computers at the same time as a “group” task.

They often wait in a Queue and download the same information at the same time. (they will all wait at 30% until all clients are are 30% and then proceed).

@george1421 Ahh yes, lovely QoS

@Almeida

@Tom-Elliott said in Multicast doesn't work:

As a mode of reference, this typically occurred because of the storage node network interface. If it couldn’t match the interface, the files couldn’t be found to enable the command.

As @Junkhacker stated you would be best to update to the newer series of FOG as many of these things have been corrected for and we have more direct capabilities to help troubleshoot.

I’d recommend the 1.3.5-RC’s particularly if your Server OS is Ubuntu flavored.

I can recommend Ubuntu 14.04 or 16.04. FOG installed with out a hitch!

@fredlwal that would be the boot file you choose to use.

In most cases it will be undionly.kpxe but you are welcome to use some of the other boot files located on the fog server at /tftpboot

@fredlwal As George stated, no the files stay on the fog server.

On the Windows DHCP server, you will change options 66 to point to the fog server ip address so that the network knows what server holds the boot file.

And option 67 is the NAME of the bootfile that you want the network to look for.

Did you run the installer as sudo?

sudo ./installfog.sh

We also recommend using 1.3.5 RC 11 instead of 1.3.4

In the future, please put all your “Pasting” into code brackets that way it won’t convert some of the code to smiley faces like

That and it helps to define what is the information pasted from the server, it differentiates what steps you have tried, and it outlines the error without having to thumb through the settings to get to where the issue actually lies.

I don’t know too much about the solaris system you are coming from BUT… Others in the past have had to deploy an image using their OLD imaging solution to a machine and immediately (WITHOUT BOOTING THE OS) upload the image to FOG, this will give you an exact replica, and it puts it in the format FOG knows how to interpret.

Did you register a machine as a host to the fog server (sorry silly questions but I want to make syre we are on the same page)? Have you set up an Image store on the FOG Server under Image Management? Did you assign an OS type to the image? Did you also assign the image to the machine registered as a host on the FOG server?

Did you add a .mntcheck to the server store?

[code]
sudo touch /Tools/ .mntcheck
sudo touch /Tools/BuildFarmImages/ .mntcheck
[/code]

Did you add FOG as the owner for the directory?
[code]
chown -R fog.root /Tools/BuildFarmImages
[/code]

Did you edit your etc/exports to reflect the changes in the image store?
[code]
/mnt/Tools/BuildFarmImages *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure)
/mnt/Tools/BuildFarmImages/dev *(rw,sync,no_wdelay,no_root_squash,insecure)
[/code]

It would be wise to create the /dev folder and give FOG full red and write access as it will upload the image to this temp folder then copy it to your image store.

Tom knows quite a bit more about the NFSMount options perhaps he will offer some expertise here.