I have a WHS 2011 which I custom built, and after a year online I have had no problems with it.
However recently, although it is only set to wake up with one computer on the network is switched on (using Lights Out) it has developed a nasty habit. The server wakes, runs for the assigned period (10 mins), and then shuts down, immediately waking again after a second or two.
It appears to do this whenever any of the computers are live on the network.
None of the clients are configured to "enable monitoring", so the server should stay in hiberantion.
The server is configured to come on at back up time, (early evenings), or by WOL from a computer on the network.
Lights Out is configured so that only one computer should automatically wake the server, and that it should remain on for this PC. Everything else on the network shoiuld be a manual request to wake the server.
I am aware that with the old WHS there was an issue with SB Core services, and a work around for that, is this a similar issue ?
I would appreciate any thoughts on this.
Gary
However recently, although it is only set to wake up with one computer on the network is switched on (using Lights Out) it has developed a nasty habit. The server wakes, runs for the assigned period (10 mins), and then shuts down, immediately waking again after a second or two.
It appears to do this whenever any of the computers are live on the network.
None of the clients are configured to "enable monitoring", so the server should stay in hiberantion.
The server is configured to come on at back up time, (early evenings), or by WOL from a computer on the network.
Lights Out is configured so that only one computer should automatically wake the server, and that it should remain on for this PC. Everything else on the network shoiuld be a manual request to wake the server.
I am aware that with the old WHS there was an issue with SB Core services, and a work around for that, is this a similar issue ?
I would appreciate any thoughts on this.
Gary