@Sebastian-Roth
Alright, I have a bit of info to share here…
I have a machine with Windows 10 1709 OS Build 16299.15 and an identical machine (sitting next to it) that has Windows 10 1703 Build 15063.0. The 1709 machine FOG service is not running. The 1703 FOG service IS running.
I checked multiple machines and none seem to have logs that go back far enough to any events that happened on the day the service quit. That said the things these all have in common (on some machines) occurred two days prior to a system update. (8/20/19) The update occurred on 8/22/19… I had a few outliers that happened mid July.
Oddly enough, I was out of the office the week (8/19/19) this event occurred. I checked with the other tech and we had no physical issues that day and the folks that were here used this very lab that day.
So far all of my logs are not showing anything back when the problem occurred. I have noticed that a commonality in the FOG logs is that this issue happens after FOG sleeps or reboots.
Let me know what else I can provide you. I have several machines in the same lab that have this issue. I had a few that after I logged into AD, the service checked in and everything seems to be working.
Cheers,
Joe