Added as option 4 to the previous post.Maybe if you start watchdog first option,
Added as option 4 to the previous post.Maybe if you start watchdog first option,
I'll do this now and report back when I return home again.
P.S.: I verified the network adapter. Strangely the tick at "Only Magic Packages can wake up this PC" was missing. I had this surely activated. Well, I ticked it again now.
LightsOut is the Service that ensures that the Server is automatically waking up (and going to sleep if not needed). Actually it's part of the Server 2012 connection and automatically pushed to the Client. It is needed to keep the Server alive while the HTPC is on.HTPCSourcer, my gut is telling me that the problems in the latest logs are not from plugins. Of course I could easily be wrong (as I often am! ), so you're welcome to try the Watchdog with option 1.
the Windows application event log refers to a "LightsOutClient". A quick Internet search tells me that may be used for managing power. I'm very suspicious.
That's a Windows 10 thing. The "Troubleshooter" veriefies a couple of things and even repairs them - it is launched manually and that's what I did yesterday I think. Nothing to be concerned about.The system event log also references a "Microsoft-Windows-Power-Troubleshooter" which I also wonder about.
Isn't this what I just reported above? Server was online, then resume of the client.So next test will be to wakeup the server first before the client to see if it's better too