Server behavior changed after hardware upgrade
Verfasst: 20. Jun 2019, 09:13
Hello!
Been using all versions of Lights-Out for a number of years. Currently using version 3 on Windows 10 set up as a media server. Settings are to wake the server at a specific time of day, and monitor clients to remain on. Wake server with client activity is disabled, so it stayed off/hibernated when clients are turned on. I was also able to put the server to sleep manually, and it would stay off once done so regardless of client status. I recently upgraded the boot drive from a SATA SSD to NVMe and added a couple more storage drives. Since the upgrade, the server no longer remains asleep when connected clients are turned on. Furthermore, on my computer I no longer am able to trigger "Save energy now", which now says "Save energy now (Forbidden for this device)".
Something similar happened when Lights Out v3 was released and the server automatically updated from v2. I was able to fix things by uninstalling/reinstalling on the server, but that didn't work this time. I also uninstalled/reinstalled on the clients, to no avail.
I am using, and always have used, Lights Out in Community Edition mode. Let me know if there's anything else you need in order to diagnose and solve the issue. Thank you!
Been using all versions of Lights-Out for a number of years. Currently using version 3 on Windows 10 set up as a media server. Settings are to wake the server at a specific time of day, and monitor clients to remain on. Wake server with client activity is disabled, so it stayed off/hibernated when clients are turned on. I was also able to put the server to sleep manually, and it would stay off once done so regardless of client status. I recently upgraded the boot drive from a SATA SSD to NVMe and added a couple more storage drives. Since the upgrade, the server no longer remains asleep when connected clients are turned on. Furthermore, on my computer I no longer am able to trigger "Save energy now", which now says "Save energy now (Forbidden for this device)".
Something similar happened when Lights Out v3 was released and the server automatically updated from v2. I was able to fix things by uninstalling/reinstalling on the server, but that didn't work this time. I also uninstalled/reinstalled on the clients, to no avail.
I am using, and always have used, Lights Out in Community Edition mode. Let me know if there's anything else you need in order to diagnose and solve the issue. Thank you!