Hello,
I just installed lights out (version 1.5.3.1819) on my new windows server 2012 essentials after using it for ages on my windows home server v1.
I enabled hibernation. To test I set 2 calendar events
1 at 17:00, uptime end checked, hibernate selected. force end action enabled (tried before without forcing but that didn't work).
1 at 17:15, uptime start with wake from suspension or hibernation checked.
At 17:00 my server indeed shuts down (it's headless but I can see the HD starting to do a lot of stuff and the power light of the server go out). But 2 seconds later it comes back up and I have no idea why. I only have hibernation, sleep is not supported I think.
All updates are installed on my server, so I'm assuming the fix Microsoft released with the licensing service also ?
In my application event log I can see the following happening:
LoService: LightsOutService starts to hibernate
LoService: LightsOutService: stopping HealthAlertsSvc
HealthAlertsSvc: Service stopped successfully.
LoService: LightsOutService: stopping Spooler
LoService: Power event: ResumeSuspend
LoService: LightsOutService: starting HealthAlertsSvc
HealthAlertsSvc:Service started successfully.
LoService:LightsOutService: starting Spooler
LoService:Power event: ResumeAutomatic
In the system event log I see the following by Kernel-Power:
The system is entering sleep.
Sleep Reason: Application API
8 seconds later by NETLOGON:
Dynamic registration or deregistration of one or more DNS records failed with the following error:
No DNS servers configured for local system.
40 seconds after previous entry (all by Kernel-Boot):
The system time has changed to 2013-03-16T16:09:30.500000000Z from 2013-03-16T16:08:52.353083300Z.
Change Reason: System time synchronized with the hardware clock.
The firmware reported boot metrics.
There are 0x1262E0 boot options on this system.
The bootmgr spent 0 ms waiting for user input.
The boot menu policy was 0xC0000001.
The boot type was 0x2.
then some notifications from service control manager
The Windows Server Health Service service entered the running state.
The Print Spooler service entered the running state.
and then by Power-Troubleshooter:
The system has returned from a low power state.
Sleep Time: 2013-03-16T16:08:42.470697100Z
Wake Time: 2013-03-16T16:09:30.714489600Z
Wake Source: Unknown
Any idea what's going on and how I can fix ?
Thanks,
Jorn