This has now been solved.

I forgot to add /24 to the end of the IP in the nmtui configuration.

Server

• FOG Version: latest
• OS: Centos

Client

• Service Version:
• OS: Windows

Description

Hello,

Unfortunately one of my team set an image to capture instead of deploy and it now says 0.00 iB and fails on deployment

The files are all still there, is there a way to add it back into fog?

Kind Regards.

I have now solved the issue.

It was on multiple vlans which was confusing it, i needed to set it to the single vlan member.

Thank you very much Tom.

@Tom-Elliott Strange, if that was the case how come it can connect to fog and load that information?

Do you have any ideas what would cause this?

I have just deployed another image to a Hyper-V and worked perfect.

I am not sure what the issue is when deploying to this physical.

Forgot to add. i am using the latest version

Running Version: 1.3.3

bzImage Version: 4.9.1
bzImage32 Version: 4.9.1

Server

• FOG Version: Latest
• OS: CentOS 7

Client

• Service Version:
• OS:

Description

I am trying to deploy an image to a server but i am getting “Attempting to check in Failed”

I have no idea what is going on, i havent seen this issue before.

This has now been solved.

I forgot to add /24 to the end of the IP in the nmtui configuration.

Server

• FOG Version: latest
• OS: CentOS7

Client

• Service Version:
• OS:

Description

Hello,

I am getting this error when trying to go through PXE. i am not sure what has changed

NBP filename is ipxe.efi
NBP filesize is 0 Bytes

I have checked and ipxe.efi does exist. and the firewall is disabled, i am not sure why its not either picking it up or transferring it.

Any ideas?

I have managed to resolve this now, i needed to reinstall Windows on the server and choose New to create the partitions on the installation instead of just next for some reason.

I have now been able to image server 2012r2 and server 2016 without issues.

@Tom-Elliott Thank you, sorry for the stupid question how do i re-run the installer?