The add-In which is used to put a Windows Home Server into suspended mode or hibernation and resume on user defined events has been updated. LightsOut is now at version 0.7.5 and includes:
New:
- Calendar entries are sorted by start time
- Check for duplicate client entries
- Check for process sbscrexe
Changed:
- Calendar control replaced by self-developed control
- Restart of services now happens on PowerStatusChange event
- Client service uses less entries in eventlog
- Client service is increasing the time between WoL pakets/pings when server is unavailable.
- Client service depends on TcpIp
- Service restart is done on PowerStatusChange instead of ResumeAutomatic
- Information for client monitoring is no longer based on WHSInfoClass()
- History range can now be set to any number of days between 2-14
Fixed:
- CodeSigning problems
- Crash after creating two identical tasks in calendar
- Day change in calendar (today tag not moved)
- Calendar creates 100% CPU load
- Action erroneously started on midnight
- Wrong backup time displayed after change
- Wrong index in English online help
More information, the download and a PDF are available from here.
April 24, 2008 at 6:43 pm
I don’t like WHS, all it’s third party add-ins are beta built quality. Take for example, this third party add-in, as quote above from the article, “Calendar creates 100% CPU load”.
Why would any WHS user want to experience this type of eperience when purchasing their home server? Is everything going to be “beta” quality produced when it comes to using WHS?
April 24, 2008 at 10:13 pm
More Beta 4 U.
You really need to go back and read the article. Do you use WHS?
April 25, 2008 at 8:09 am
@More Beta 4 U
“Calendar creates 100% CPU load” – this happend on a few installations and was a problem of the calendar control under special conditions. It has not happend during testing on my 3 WHS installations and with the beta testers.
From a developer point of view it’s impossible to test all hardware/software combinations out there in the real world. So you will always have to fix some problems after the first release.
Nobody is forced to use a third party add-in.
Nobody has to pay for it – your free to use it or not.
April 25, 2008 at 2:30 pm
[...] WHS Add-in: Add-In: LightsOut 0.7.5 [...]
April 26, 2008 at 5:50 pm
I use this add-in, and it’s great! Thank you for your work.
April 29, 2008 at 6:21 pm
Since when has WHS given away for FREE to the public? How can anyone use a WHS third party add-in without WHS? WHS isn’t FREE!
In addition, it’s true in that all them third party add-ins are needed because of missing features and functions from a broken WHS product that customers paid the highest cost…
Nobody can be proud of that, from a multi-billion dollar corporation… Which didn’t even get it right with a proven data corruption design flaw that still hasn’t been resolved since last year!
And as Martin points out, there is a bug that makes using this third party add-in total unusable when the customers PC client experiences 100% CPU load.
How good is that? Or it is just that 15% of WHS customers don’t count who suffer with it? Why is BETA code being used in RTM and OEM Windows Home Server anyhow?
Enough of WHS! Customers are completely tired of being hassled with how everything about WHS requires work arounds, just to overcome the many deficiencies and inadequacies!
April 29, 2008 at 6:57 pm
“Customers are completely tired of being hassled with how everything about WHS requires work arounds, just to overcome the many deficiencies and inadequacies!”
Please, don’t speak for “customers” unless you are one (and I doubt you are). You don’t speak for me and I resent that you pretend to.
May 2, 2008 at 1:17 am
@Aaron
Um, who claimed that WHS is free? Where did you come up with 15%? Everything requires workarounds? What?
Let me guess, you take the short bus to school.
May 25, 2008 at 11:27 am
I installed this add-in, tried it out, but didn’t find much of a help. So – uninstall – making me wish I never have installed this add-in in the first place.
First the WHS took a very hard landing – and now I cannot open my settings panel in the Console; Whenever I click the ‘Settings’ in the console (remote or local) – I get HomeServerConsole.exe found an error and ext, Sorry for the inconvinience. You have lost all your data.
So I have to reset the homeserver (pain in the neck) – my advice DO NOT EVEN CONSIDER INSTALLING THIS