@EduardoTSeoane I am marking this as solved as I would think the quick fix should help in your environment and we haven’t heard anything negative back yet.

@sgoodman Bump…

@sgoodman @Daniel-Miller @Greg-Plamondon @george1421 Has anyone run into this issue (again)? I’d think this might have been caused by a major .NET framework update which we can’t do much about. In case people have PCs running for a long time without restart they might consider setting the service to auto-restart. I am marking this solved now. Feel free to post if you think it’s not. Cross reference to another topic: https://forums.fogproject.org/topic/13704/fog-service-quits-running

@rhromyko Well, although it “should” work I’d still change it to ipxe.efi without the slash. Please read George’s first message again. Hi linked a post on how to capture the network traffic so we see what’s actually going on. Anything else is just wild guess work and not much worth.

@tneuber The unattend.xml thing, is a windows thing and not a fog thing. For example I don’t use the FOG client in my environment but I use the unattend.xml file to configure the target computer and connect it to AD. Here is an example of a sanitized version of my unattend.xml file: https://forums.fogproject.org/topic/11920/windows-10-1803-sysprep-problem/7

@marted said in Remove press F12 for network boot (PXE): No need to press F12 if I stop all computers and send a signal with the image wake-up on lan Just be mindful that windows 10 doesn’t play nice all of the time with WOL. Many have reported that wol doesn’t work if the computer was in windows and is either put to sleep or shutdown from inside windows. WOL does work if the computer is unplugged and then pugged in, where windows wouldn’t leave its bits hanging around and breaking the wol process.

@Matthieu-Jacquart Sure right. If one client was pinned to the re-newed server CA cert then it can’t connect to the old original one. I missed that point! Good you figured it out!!! Great we got that worked out.

@Dv27842 said in Installing FOG on Ubuntu 18.04 Desktop: Synology NAS Setting this up is fairly advanced! You are better off just using a simple setup with just one FOG server (including it’s own storage) in a VirtualBox I’d say. Play with this and when you are ready take the next step.

@Sebastian-Roth OK. No problem.

@Daniel-Miller I looked into the speeds, auto-negotiating was set however the speed was messed up. It seems the port on the switch went bad. Plugged into another port and got the correct speed. Imaging seems to be back to normal now.

Hi folks! Thanks for taking time to look into this. And yes, you’re right about the FOG client. It’s inside the image and the service is activated from the beginnen. While researching I came across the mentioned link after I experienced those problems. It was just such a weird behavior I was unsure and did not try out the delayed strting of the service. I’m going to modify my image in the next weeks. If the issue continues I’m going to open a new thread. Thanks a lot! Great help from a great community! Chris P.S. How to mark this issue as “solved”?

@Sebastian-Roth Thanks again. I created an new image without that VPN software installed and everything is working as it should. Sorry about this and thanks again for all your help and time.

@george1421 Hey George, sorry for the late reply, work has been closed for Christmas, first day back now. That has worked, followed those instructions and reran the fog setup and now i can upload images without any issues. Many thanks, Pete

@Single Did the logs help you any further?

@Penguinsec said in Fog Client Not Communicating with Server: This time client logs are showing no errors, but the host is not showing up in the server. What do you mean by this??

I will go through the information you sent, but I cannot take photo of the screen. Thanks.

Hello it’s ok only with: ipxe.pxe, ipxe.kpxe, ipxe.kkpxe, realtek.pxe, realtek.kpxe and realtek.kkpxe. I will choose ipxe.kpxe because we also have computers on our network with Intel network cards. Thank you very much and happy new year 2020

@sascha735 If you installed FOG using the git method, switch to the dev branch and reinstall fog. That will put you on a prerelease version of 1.5.8 that does support Centos 8 and Debian 10.2 (I think). cd /root/fogproject git checkout dev-branch git pull cd bin ./installfog.sh That should put you on version 1.5.7.85 (or later) When FOG 1.5.8 is released (should be some time later this month) you will then need to do the following to switch back to the master branch. cd /root/fogproject git checkout master git pull cd bin ./installfog.sh

@Sebastian-Roth At some point you might need to think about updating your Ubuntu install but 16.04 LTS is still fine at the moment. No rush. Yeah thats definately on my to do list! I don’t think it is something you did. If I remember correctly there was an issue with this link in an older version. As you updated FOG from 1.4.x there is a chance that old version has messed it up. Sorry. no problem! just wanted to be sure to not repeat it if it were my mistake haha Learning Linux is a live long task. Even for me, working on Linux every day for many years. Just keep on playing with it and find yourself getting more and more comfortable. A great way is setting up a test environment in a VM where you can snapshot, test and re-install without much trouble… Yeah, I think I may try and work out of a VM every so often. Tried it before but the timing was unfortunate and I got literally buried at work so I never went back to it but it may be time to give it another go. thanks again for all you’re help! I’ll be back on Monday haha

@JonesDK Sorry for the delay. You can try it out now (as described below).