UNSOLVED FOG Client causes unwanted Shutdown of any Windows Host straight after booting
- FOG Version: 1.3.0 RC10 (SVN Revision: 5955)
- OS: deb8u1
- Service Version: 0.11.5
- OS: Windows 10 Enterprise LTSB 2015
Our school started using FOG this term (since September). Imaging works perfectly. Systems boot our generalized image, set up Windows, join domain (Server 2012 R2). All testing positive.
The next morning all colleagues experience their client windows to shut down shortly after booting. Some straight away before logging in, others about a minute later. This happened to all clients and all of the time. Shutdowns are issued by FOGclient.
We figured out that deleting all affected machines from FOG Server’s Host List fixed the Problem - only to re-appear again several days later in exactly the same manner (this time without prior deployment to affected systems). Again Host-deletion worked as a quick fix.
Of course we don’t wanna go on like this and dig a bit deeper. Has anybody experience our problem before or knows the cause?
Our ideas so far:
- End of lease-time / renewal of IP-address might cause the issue (since today we use IP-reservations, before DHCP worked however it wanted)
- Our FOG serving hosts on different subnets might play a role. FOG is on the same net as Windows Server. WoL works via Subnet Directed Broadcasts, same for DHCP. Maybe the problem is rooted somewhere there…
Thanks for any help!
@Tom-Elliott from the logs:
10/7/2016 10:32 AM PowerManagement On demand shutdown requested. An on-demand shutdown is always queued and not being cleared. We need a clear on-demand tasks button.
@Tom-Elliott I am also having this issue, but with a Linux machine. Just after installation, it wouldn’t shutdown. Then I turned off all the machines and on the next day when I came back to the lab and turned the machines on, I reinstalled the FOG Client and tried to shutdown again. It worked, but now it keeps constantly trying to shutdown. Here is the log: http://pastebin.com/3cqXAcTw
Tom Elliott last edited by
@Wayne-Workman It’s in bytes, because who knows what size a person want’s the log file to refresh at? Maybe you want the log file to refresh have 10 bytes, maybe you want to have it refresh at 10 Gigabytes.
Wayne Workman last edited by Wayne Workman
@kouzinger Cool. We’re here to help, but we really need the log to help.
The client will only clear the log automatically after it reaches the size limit for the log, you can adjust this in the web interface here:
FOG Configuration -> FOG Settings -> FOG Client -> FOG_CLIENT_MAXSIZE
I think the value is in bits, but I’m not sure. IMHO it should be MegaBytes @Senior-Developers.
Hi and thanks so far,
unfortunately the clients apparently reset their log-files after having been deleted from FOG-Server’s database and so far we could not reproduce the error.
Guess we’ll have to wait until it reappers - then I’ll paste the appropriate log-portion.
Wayne Workman last edited by
We cannot help you without a full client log from an affected computer, shortly after the problem happens.
The log is generally here: