Should you have additional question please use the official support forum here at WGS: http://forum.wegotserved.co.uk/index.php?showforum=89

I just bought my Tranquil SQA-5H-2000 and installed your great addin after reading this review. Thanks!

Originally Posted By Martin (Tinus)
Disabling SB Core
This is required for all home build machines. I assume that Microsoft has released a hotfix only for OEMs. The original version of sbscrexe.exe is 5.2.3790.3959, on a Fujiitsu-Siemens Scaleo we found version 5.2.3790.4173. The next minor update 0.8.0 of LightsOut knows about this version and does no longer display a warning message.

The SQA-5H-2000 has version 5.2.3790.4173, though there have already been a few auto MS updates, so I don’t know if that was originaly on the whs.

Originally Posted By Martin (Tinus)
You wrote (*)
* Shut down the client with WHS still on.
* Wait 10 minutes. WHS does not shut down.
This is probably a result of the missing third option on the NIC settings which keep the server active. To verify this I need your log file.
* Restart. WHS goes into hibernation! Hitting the power button required user input to start it up correctly.
This should never happen. I will look into this problem and try to reproduce and fix this. On restart the server should always run for 10 minutes. Have you restarted the client also?

I wasn’t sure what to do after reading the review (your reply was not there yet), so I figured I should just follow the instructions in the manual. With one exception, I did enable the first 2 options (“allow computer to turn off” + “allow to bring out of standby”), but kept “only allow management stations…” disabled. It all works like a sharm and I don’t experience the issue mentioned in test 5. I do see in the uptime Diagram that the whs wakes up for 10 minutes or so about every 2 hours (while it should not), so that might be the “Only allow management stations…” setting. I have it enabled now.

Leaves me with a question that probably also relates to another reply:

Originally Posted By AndreasfI stream music to a Squeezebox from my WHS, and unfortunately the WHS is not able to stay on when powered up by lightsout. This means that without any PC’s running the music will shut down after ten minutes.

If I am away from home, without any pc running, then the whs is sleeping.
1) What will happen when I access my whs website? Will it wake itself due to the WoL?
2) I supose this is a WoL sent from the router, does that mean the “Only allow management stations…” settings must be disabled?
3) Will lights out put the whs back to sleep after 10 minutes because there are no other pc’s running? Workaround?

Also
4) The WoL capabilities setting in the NIC’s advanced settings has a choice between “None”, “Magic packet”, “Pattern Match” and “Pattern Match & Magic packet”. Can you explain what the difference is? I chose the last option (I figured better too much then too less .
5) I don’t really like having to run the “LightsOutClientService.exe” on every workstation. Why is it needed? If it is to see which computers are still running, why can’t you use the “WHSconnector” service which is already running?

Thanks
JeePee

Regards
Martin

Regards

Disabling SB Core
This is required for all home build machines. I assume that Microsoft has released a hotfix only for OEMs. The original version of sbscrexe.exe is 5.2.3790.3959, on a Fujiitsu-Siemens Scaleo we found version 5.2.3790.4173. The next minor update 0.8.0 of LightsOut knows about this version and does no longer display a warning message.

Installing LightsOutClient
It’s not necessary to copy the installer nor use RDP, simply open \\Server\Software\LightsOut on your client to access the installer. Update 0.8.0 also knows that this share is called \\Server\Logiciel on a French WHS.

Chart readability
This is indeed a problem when you have a large number of clients. You can lower the number of days displayed. Version 0.8.0 will add tooltips to help identify the machine and the runtime.

Test 1 and 4
This is as expected. The NIC and the Bios are responsible for Wake-On-Lan when your WHS is shut down. Some NIC drivers offer additional options not controlled by Windows.

Test 2 and 3
This is as expected. In standby the NIC settings have to be changed for Wake-On-Lan to work. The NIC option “Allow this device to bring the computer out of standby” is required and simply enables wake up. But now your WHS will start up by any activity, for example, when your router is scanning the network. That’s the reason for the third option “Only allow management stations to bring the computer out of standby”. Enable this and only magic packets (wake on lan) can start the machine. These settings are documented in the manual and online help of LightsOut.

Test 5
You wrote (*)
* Shut down the client with WHS still on.
* Wait 10 minutes. WHS does not shut down.
This is probably a result of the missing third option on the NIC settings which keep the server active. To verify this I need your log file.
* Restart. WHS goes into hibernation! Hitting the power button required user input to start it up correctly.
This should never happen. I will look into this problem and try to reproduce and fix this. On restart the server should always run for 10 minutes. Have you restarted the client also?

Thanks for your advice to disable “Allow the computer to turn off this device to save power”. This seems to be one source for some strange issues.

Summary
I’m not happy with the SB Core situation. I still hope that Microsoft will release a public hotfix for this issue. Your proposal for a troubleshooting section or FAQ makes sense. I will definitely create one.

Regards
Martin