@bmckevitt said in Problems with FOG client servive windows 10:
It seems to register the host and sees it for a little while at which point the connection goes dead. I can’t access the units nor assign tasks to it.
Well, this thread slipped by and I sincerely apologize. Sometimes things get crazy here, and about 2 months ago we were getting about 30 to 60 new threads a day, and that’s a lot for the active members to help with (maybe you can help?). In the future, don’t feel bad about bumping your thread if it’s been a while. Again I apologize.
For the issue, I can’t see anything wrong with the log towards the bottom. It’s communicating with the server properly. I see you installed a snapin early-on, with a return code of 1603. I looked up some info on this, that probably means what you were installing was already installed. Read here for more information on that.
When you say the ‘connection goes dead’, what do you mean? What is indicating this to you? For troubleshooting the FOG Client, you’re very first stop should always be the c:\fog.log, see what it says. Every time anyone has an issue with the FOG Client, we always ask for this file, because it’s the first place to look, always.