@explosivo98 Strange that kernel should boot because the only thing added was some apple hardware IDs and an apple disk patch. Nothing for non-apples should be impacted.

Solved. OMG it’s so good to have another set of eyes on. Talk about not seeing the tree for the forest! I am watching first clone progress. This is far further than I was ever able to get with Symantec ghost - never could build their PXE client. Thank you so much Sebastian.

@Sebastian-Roth
I have no idea what I was doing wrong here… My calls now work.

@nonamejason How did you change it? Probably a config file, post that config file here. Or if it was through the GUI, post a picture of that.

I think i may have found the solution

https://forums.fogproject.org/topic/13891/cant-create-user-setting-up-fogproject-user-failed

@Sebastian-Roth Yes. I marked @Quazz as the correct answer.

@Sebastian-Roth

I’ll have to brush up on the commands for replacing the certs on the clients. Been a long time.

Thanks for your response @Daniel-Miller! It looks like I overlooked this plugin; it seems to be generally what I am looking for. There definitely seems to be issues related to provisioning with plugins (as has already been mentioned in the link you shared). Currently I can either have the printers auto-add using the persistent group and have snapins not run (which essentially breaks the provisioning process) or I can have Snapins run but not use the persistent group.

I have run at least a test or two where I think I got both to work but it may have been a fluke as I can’t really replicate that. I will keep plugging along.

Thanks for pointing me in the right direction!

@Dv27842 said in Unable to change IP for FOG Server installation on Ubuntu Server 18.04:

I have tried to change the IP address to a static IP address that is currently on my sandbox, but it will not keep the changes

Please give us more details. Where exactly did you try to change the IP? Within Ubuntu? Which file did you edit? What did it look like before?

I can imagine you were editing the wrong file. Ubuntu 16.04 network config is different than Ubuntu 18.04, see here: https://www.ostechnix.com/how-to-configure-ip-address-in-ubuntu-18-04-lts/

@tiengdung90 Can’t help you without further information.

@Greg-Plamondon Is this still an issue or did you find what was causing this?

@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

@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.

@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.

@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

@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.