I’m so confused.

I see 2 posts now with:

1923168.1.10...... One @Sebastian-Roth brought up, and the post directly after that also has the same typo.

Is this a typo, or is this literally what’s being displayed on the Host machine?

@fogusnew We are working towards a next stable FOG version by pushing out release candidates (RCs). FOG 1.5.9-RC1 is out since a few days and you might want to update to that to see if the issue mentioned is really fixed. If it’s not we can still look into it before the final release comes out!

@Jeff-Findley said in kernel interface not working:

Just an FYI - according to Netgear none of their unmanaged switches do any sort of STP. But who knows.

Yeah you never know. But beside STP we have seen a few cases where ethernet energy efficiency (EEE) stuff kicked in and caused such things. While it is possible to be EEE I still suspect George is right with STP…

@Greg-Plamondon another suggestion. We had enough issues with pxe boot compatibility acorss different devices that we embed a custom bootloader that has an option for booting directly to a local copy of the ipxe.efi file. We use grub2win and just have its installation as part of our provisioning scripts that are started by sysprep firstlogon. Found this to work better than trying to get custom nvram type settings, this way you get it individuallized per hardware but also using a universal config file.

@lewisreid01 Thanks for the update and good to hear that you were able to fix it this way. I was hoping we could figure out what happened to your install and try to fix it “a less invasive way”. But possibly this is the quickest way to solve this issue anyway. Well done.

For anyone reading this: The installer option -C should be used with great caution! It will reset all the pinning you have made when installing the fog-client on your hosts. So as described by @lewisreid01 the second step is to re-install fog-client on all hosts!

@Dreded said in Think I deleted my SSL keys/Failed SSL:

just wanted to add to anyone else that stumbles across this… the -K was definately needed(guess it resets the encryption keys client side?)

No it regenerates the certificate used by the fog-client (not to confuse with the CA cert the fog-client is pinned to).

Hi @Sebastian-Roth yes, you’re right. pfSense was the problem and solution. Found the solution on this post ((https://forums.fogproject.org/topic/9513/pfsense-is-great/2)

Thanks for the assistance. I love this community.

@JYost
Thank you George…this pointed me to the etc/network/interfaces file where I found that the dns-search field only had “domain.local” and was missing “domain.com”. Once I added that into the dns-search field all was good and FOG was able to see devices which were online (denoted by green Windows icon).
Thanks again guys…great support as always!!!
Go ahead and mark this as solved.

@Cire3 Lets start with what version of FOG are you running

What does the image definition look like for the one that doesn’t deploy? Is everything stored on the root partition or did you add a new disk (originally) to contain your images? What does the output of df -h and lsblk look like?

@mactuan12 The content you posted a good half an hour ago has nothing to do with FOG. I removed the external links as it’s considered spam…

I know this is a very old topic but it seems like people find this and follow it blindly. Please be aware that using the installer parameter -C (or --recreate-CA in long form) will overwrite your FOG internal certificate authority and break all fog-client installs because of this. The fog-client is pinned to this CA when installing the software on the machine and you need to re-install fog-client (or magically exchange the CA cert) on all your machines!

@george1421 Great, thank you! I appreciate the help.

@RipAU Can you give us more detailed infos on the ZIP file contents?

Could you upload the picture to some image share and post a link here?

@Tom-Elliott Hi Tom, sorry, I didn’t reply with that info, but yes, I did run the command you suggested to explicitly turn off bitlocker, but it was still giving me the same error. The error only went away once TPM was disabled in the BIOS. Thanks for your help trying to figure this out!

@Sebastian-Roth
I took your advice with certificate issue, and solved it easiest way, by preparing a new image, and voila, workstation joined the Domain with no problem. Need to prepare two more images, but its easier than searching for another solution. thank you!

@Salman-KB123 You’re on the wrong forums for this. FOG in this forum is a computer imaging software. iFogSim is something else entirely.

@zyzhang When a deploy fails it will set this value to zero. I know this is not great behaviour but that’s how it was in FOG 1.5.4. Nothing we can do about it. You’d need to update to the latest developer version (called dev-branch on github) for it to be fixed.

@CpServiceSPb said in ERROR: Not able to find a network interface that is up on your system:

And is got the same error.

What exactly do you mean by that?

Please run ip a s as root and post full output here.

@davide1611 said in No configuration methods succeeded: DHCP failed:

Thanks Sebastian and sorry for asking something already resolved

You are welcome. No trouble at all. It might not be too easy to find the answer to this in the forums if you don’t know what is causing this.

@Mightmar said in New computers- no configuration methods succedeed:

I got a new problem now

May I ask you to open a new topic for this? We try to keep things sorted here so others can find solutions to same or similar issues better.