Lights out 2 client install software#
In this blog post we present the changes to the user interface, the new automatic software updates and a better handling of away mode. Due to the many new features, we will split the presentation into 2 contributions. Many of our users’ suggestions have been implemented here. If you have not yet updated to 3.We are pleased to release Lights-Out 2.5 today. This concludes the presentation of the most important innovations of Lights-Out 3.5, which will make your server fit for the upcoming requirements.
Lights out 2 client install manual#
The previously required, manual and error-prone setup of certificates and reverse proxy is now done by Lights-Out itself. With version 3.5, Lights-Out can be installed on a Synology NAS without any further configuration steps. The necessary steps to activate these certificates have already been described in the blog. The Friendly Name also helps identify the new certificate. Here you can see a WSH 2011, left (in yellow) the old WHS 2011 certificate, right (in green) the new one for Lights-Out. The implementation was done in such a way that a new server certificate is created with the existing root certificate of the certification authority (Root CA) that meets Apples requirements. Synology certificates also have a much too long Of Server Essentials 2012/2016 still have a lifetime of 5 years and are It is to be expected that Apple will even shorten the lifetime to 1 year this year!Ĭertificates of Windows Home Server 2011 have a lifetime of 30 years (!), those
Especially the significantly shortened lifetime of just over 2 years is a problem for legacy systems. Implementation of Apple’s certificate requirementsĪpple has tightened its requirements for trusted certificates in recent years. If you are running a QNAP NAS, you can find detailed installation instructions here. Lights-Out 3.5 now officially supports QNAP NAS systems. This restarts the server immediately when it is no longer needed. Lights-Out 3.5 can detect a pending reboot and then perform a restart instead of the standard action (in our screenshot here hibernation). Pending reboot (Windows only)Īfter installing Windows updates, the server usually needs to be rebooted promptly. After 5 minutes the secondary server follows the primary server and goes off. On the secondary server, only the primary server is monitored as a network device. This task can in turn be solved with Lights-Out on-board equipment. Deactivate secondary server as soon as the primary server is offline As soon as the primary server becomes active, all registered machines are started via Wake-On-Lan. This completes the first part of the coupling. the secondary server is added to the new wake setting. The additional, secondary servers must be added as network device. This setting is implemented in two steps on the primary server:ġ. Wake other machines as soon as the primary server becomes active Note: This solution requires a Lights-Out license for both servers, the Professional Edition includes a license for 2 servers. The client computers can wake it up automatically or manually, if noįurther activity is detected, Lights-Out will disable it and save energy.Īnother server, we call it the secondary server here, should now be woken up parallel to the primary server and also deactivated again. However, client computers can only beĬonnected to one server at a time.
Who switch from a legacy system, such as the WHS 2011, to Essentials 2016 or a An upcoming article will then deal with the client side. In this article we will introduce the new server-side features of Lights-Out 3.5 in detail.
0 kommentar(er)
