@george1421 thank you for this. I have hit a bit of a snag as I made some network changes on the VM without a snapshot and am experiencing connectivity issues. once I have resolved I will test and advise.
1.I have registered a host manually
2. I have scheculed a debug deploy
3. I will feedback once I have resolved my network issues with step 3-6

@george1421 subnet mask is 255.255.0.0 that is correct
Fog server IP is 10.245.220.30
there is no routers or firewalls
Fog server is running on VMware and there is 2 dedicated switch port that connects the vm to the clients we want to fog (I have tried to keep all settings the same as the old server to minimize any other configs on the switch)

@george1421
noted with regards to the IP addresses, I have reattached the pictures.
will stick with 1.5.5 for now
Yes - the 2nd picture is the result of pressing enter on the 1st picture

Yes Fog server and booting computer are on same subnet

Kind regards

the

@george1421
thank you for the prompt response.
I understand that the old server is outdated with the both OS and FOG application, I am happy to leave it as is for now.

I had already spun a VM running Ubuntu 18.04 and loaded Fog 1.5.5 a while back before 1.5.7 was a stable release.
quite a few issues experienced and other projects that took priority put this on the backseat however it has become critical to get the new server up and running.

On the new server OS was installed updates ran and downloaded fog and installed successfully after a couple of failures.
had an issue with the DHCP server as well but this was resolved but I seem to still be having issues:
booting to UEFi on the new server fails
Legagy boots up but I get the following error when I try to register a device(please see attached error received)

Press enter to continue and I get host registration failed

Good day

We recently bought new dell desktops and laptops which are giving the issue. We have 4 fog servers at different sites which are all running on Ubuntu 12.04 and fog 1.2.0 and can fog all old equipment fine no issues.

Old devices uses legagy mode and work fine
Old devices using UEFI boot does not seem to detect any server or boot file ?

Only issue is with the new devices, able to boot to network get an IP using legacy mode and select quick registration, then it does not complete the host registration but seems to go into a loop with blinking underscore.

Again with the UEFI option on the new devices unable to see any bootloader image just keeps going to back to the screen unable to find boot device.

any assistance with checking logs or advise on which drivers can be installed if this is driver related.

A new server has been commissioned to try and see if these issues will be resolved but seem to be broken more than the current working server.