last night i wanted to disable Lights-out from hibernating so StableBit Scanner could run through the night. Surprisingly I found the server this morning had hibernated during the night. After awaking the server I confirmed that the Lights-out status page still shows Lights-out disabled and 11:43 sill left on the countdown clock. I checked the windows log and found where LoService initiated hibernation at 1:57 AM.... but why? Unfortunately I did not have LO logging enabled. I have now enabled logging. LO version is 1.5.5.2136 on WHS2011. I have a calendar event scheduled daily at 2:00 AM to hibernate the server. Do calendar events take priority? I would expect the Disable LO feature to completely disable the service including all monitoring until the timer expires. Any thoughts? Many thanks, Joe
↧