@tom-elliott Tom, I just got around to installing a fresh CentOS 7.5 minimal server with FOG 1.5.4. I used the wiki instructions to install this system to the letter and it appears to be fixed. Sorry for the delay. I have another issue with 1.5.4 which I will detsil in a separate post. Thanks for your help and this post is indeed solved.

Reading through some of the forums, I saw the post about updating fog. I updated from 1.5.3 to 1.5.4 and that seems to have resolved the issue.

Thanks

Yep, my recommendation was to report it. That way we have a baseline to what was, when 1.6 is rolled out. Without it being reporting this issue is hidden from a support standpoint.

I know you said @Tom-Elliott that this post is old and that @thyago should start a new thread.
I just had the same problem and what worked for me was to have both network cards connected to the switch. (Computer was Dell R5500).

OK. I will create the files for Basque.

I will update the Spanish files too 😉

@tom-elliott Thanks Tom! I couldn’t find the path to the ‘binaries1.5.3.zip’ file, but I renamed the .fogsettings file under /opt/fog and reran the installer and that did the trick!

@austinjt01 Please create new threads for each issue.

I forgot to precise version: 1.5.2.31

Don’t worry!!

Hi

@Joe-Schmitt sorry for my delay too.
Thank you for your option to check it remote.
I was perparing some VMs so that you could access it vor remote and I have found out that with same Win10 Image, but Version 1803 that just came out, I can install Snapin Packs again.

And my Version of Fog is still the same.
I will still lookout for it, but I would say it is an issue with either 1709 or something specific with Windows internally.

From my perspective we can close this issue.

@tom-elliott This works after upgrading to version 1.5.2.28

OK, Tom. I wil wait for the 1.6 version to see it 🙂
Thanks for the information.

This is fixed in the working branch (pre 1.5.3). This issue is known and will be addressed in 1.5.3 when its released (very soon).

Thanks for testing.

The reboot was all that was needed, sorry for not trying that immediately.

@tom-elliott I think you can close this…apparently one node (of the 😎 missed an upgrade and was still running odler version…I’ll keep an eye on it this week to confirm.

That seems to have fixed the issue. I ran two images successfully.

Thanks.

@tom-elliott your the man! that was the issue. My Node was set to support 0 clients. thank you all for your awesome product!

@tom-elliott
I pulled the working branch: FIXED!
Thanks.

FOG 1.5.2 (working-branch)

Tested - works as expected. Thanks.

@robjwierenga Can you provide a screenshot of what you’re seeing?