13 replies to this topic

[Tinus]

Release Notes for Public Beta of Service Pack 2 for Lights-Out
A public beta refresh is available for all user of Lights-Out on WHs 2011 and WHS v1. Please read these instructions carefully because SP2 introduces some functional changes.

Changes added for the beta refresh are marked with a red font.

Download
WHS 2011 http://www.homeserve...1.5.1.1656.wssx

Installation
Important: Always uninstall any existing version first!
Close WHS Console/Dashboard and download the beta version
Install beta and open WHS Console/Dashboard again


New option for client action after backup
Service Pack 2 Beta refresh introduces a new client option called “Force end action”. This option is enabled by default to ensure the previous behavior. If you disable this option, the action after backup is only executed if a start-up or wake-up for a scheduled backup has been detected AND if there has been no user activity in the last 10 minutes or during backup.
This new features prevents a standby or shutdown (after backup) if a user is already working on the machine. It also prevents a standby or shutdown (after backup) if the machine is already running before the backup has been started.

[WHS 2011 only] Changed IP and MAC address detection for WHS Client Computers
Problem: Lights-Out on WHS 2011 tried to resolve the client name into an IP address and then tried to get the MAC address via an ARP request. This was sometimes not working reliable. In SP2, this information is now transmitted from the Lights-Out client.
Advantage: Correct information
Disadvantage: Missing IP and MAC address if no client is installed/available. This affects currently Apple MAC OSX machines until a native Lights-Out OSX client is available (under development).

Changed handling of Gateways or Repeaters
Problem: Devices connected via a router (or a repeater or VPN gateway) are not visible to the Lights-Out network scanner because for each IP address we always get the same gateway MAC address. Manually added devices with fixed IP addresses sometimes lost the IP address because Lights-Out wrongly detected an IP address conflict and changed that fixed IP address to 0.0.0.0.
Service pack 2 addresses this problem with two changes: Manually added devices are marked with a “fixed IP flag” and are no longer changed to 0.0.0.0 on a conflict.
The second change is a new flag for routers (and repeaters or gateways). Setting this flag in the device properties (Lights-Out computers tab) allows Lights-Out to handle manually added devices with a fixed IP.
If you have a setup, where devices are connect via a repeater or router, assign a fixed IP address and add these devices manually in Lights-Out. Then run the network scanner and Lights-Out should automatically find and mark the router (or repeater/gateway).

User Action instead of Standby or Shutdown
Service pack 2 introduces a new user action. When you select “User Action” in Lights-Out settings, a new text box is displayed where you can enter a command file. The command or batch file can run several actions but must end with a standby or a shut down! You can use the internal shutdown.exe command or you can use psshutdown from the Sysinternals Suite. If you use psshutdown.exe then the first parameter has to be /accepteula, otherwise the command file blocks. Always use a zero time span to run the command immediately!
A standby looks like this:
psshutdown /accepteula /d /t 0

Other changes since 1.5.1 Build 1555

• Fixed MAC detection on server for bridged server NICs
  
• Fixed WHS v1 console crash after clicking on error link in monitored sources
  
• Fixed unwanted client standby when client was started from shut down for a backup
  
• Fixed problem with wake-up on client when no IPv4 route is available
  
• Fixed remote access detection after IIS reset
  
• Fixed handling of IP clients without a MAC
  
• Fixed problem with incomplete or damaged xml data files
  
• Fixed end of DST problem with WHS v1 connector
  
• Fixed wrong date formatting in calendar for some regions like Japanese
  
• Fixed wrong backup date when client backup is disabled
  
• Fixed problem with deleted tasklist (delete was not handled, tasks were not removed)
  
• Fixed bug in edit properties dialog
  
• Changed action after backup: runs only if started for backup with no user activity
  
• Changed internal structure of services (both server and client) to fix start-up problems
  
• Changed handling of IP and MAC detection for WHS clients
  
• Added new option for devices which act as router or repeater
  
• Added a user action to run a user defined command instead of standby
  
• Added handling of additional routers or gateways
  
• Added client command line application
  
• Added handling (starting) of dependent services on server resume

[Wozza999]

Martin,

Firstly I wish to thank you for an excellent piece of software.

However I have found a small bug in this release.

When changing expert settings and adjusting the network load field (typing in a figure, not using the up and down arrows which works) the ok button remains greyed out. This had me fooled for a moment, but is easy to work around by unchecking and re-checking the selection box.

No big deal really but nice to iron out all those little bugs. If I find anything else I will let you know.

Regards

Wozza

[Tinus]

Thanks for reporting, will have a look at it.

Edit: Now fixed.

[picaresqu3]

Martin,

I think your add-in is fantastic.

Would you be able to stop the Lights-Out window from being displayed on the Remote Access page if a user does not have access to it? Otherwise, it just shows up as empty telling them they have no access.

Best regards,
Carl

[Tinus]

Unfortunately this is a Microsoft limitation. It's not possible to suppress elements on a per user basis.
My solution is a workaround.

[Robertc]

Glad to see you still working on this!!!! Tinus, something unrelated back about 2 years ago we discuseed a stand alone box that can wake server since port 9 cannot be forwarded, you had something you were looking at that was in development, do you know if it has come to market. I still would ike to wake server on the fly, but my router wont allow the magic packet and the port 9 thing. Can't wait for the new update!! Thanks for staying on board with this great product and continuing to suport your users. Means a lot to us.

[Tinus]

The hardware I mentioned is the Raspberry Pi http://www.raspberrypi.org/ which should arrive in the next weeks/months...
As soon as I get mine I will create that wol proxy software.

I don't know where you live and if you can buy and use a Fritz!Box. Their latest firmware includes support for wake-up as soon as you access the external router address http://www.avm.de/en/index.php3.

[Wozza999]

Martin,

Just a quick question. Under the computers Tab and selecting device properties on a device is it possible to enable monitoring without showing in the uptime diagram, as currently you are unable to deselect the Show in uptime diagram. I wish to monitor my TV but am not interested in seeing this in the uptime diagram.

Regards

Wozza

[Tinus]

That's not possible - because people then complain that their server will never sleep and can't see it in the uptime chart.

[Wozza999]

Thanks for your clarification Martin, I did wonder why. It's just that my chart is getting a little crowded guess I'll have to live with it.

[tdh76]

Martin,
I have a Fritzbox with the newest firmware but when I activate the function to wake the WHS as soon as it accessed from the internet, the server keeps on resuming every minute or so. When I suspend the server from my client one minute later it is resumed. It is as if a magic packet over the internet is sent to the WHS internetaddress from my client. Do you have an idea? I would really like to have a wake on wan function.
By the way, lightsout work perfectly for all other functions!
Best regards,
Tom

[Tinus]

I also have this Fritz!Box model. The problem with the AVM solution is that every port scan does now wake your server. I noticed the same behavior. You can either disable the functionality (that's what I did) or you can move the SSL port from 443 to a higher port like 5443 which is less likely scanned (but this solution creates other issues).

I hope that AVM implements a true WOL port forwarding to the LAN broadcast address some day in the future...

[tdh76]

Okay thx, I have also disabled the function, in this way it is of no use. What issues will occur if I change the SSL port to another port?

[Tinus]

Leave the port on the WHS at 443. On the Fritz!Box you can map to any port you like, for example 4443. In that case you have to add this external port to the url: https://xxx.homeserver.com:4443

If you use the new Mac Agent configure that port also into the url as above.