Lights-Out 2.5.1 maintenance release
We published Lights-Out 2.5.1 maintenance release today.
This is a minor bug fix release and addresses issues reported by our customers.
#354962 Fixed failing login after server rename or domain join
#200111 Fixed scaling issues in Remote Desktop from High DPI system to server
#491426 Fixed client installer warning “RemoteRegistry Service not running”
#252270 Fixed inner forced calendar task with same action (was previously ignored)
Fixed Direct Deploy error “can’t create config file”
Fixed some dialogs with truncated translations
Fixed Console crash if settings file is damaged
Changed behavior for client action after backup: If there was user activity within the last 10 minutes, the action is ignored unless forced by a calendar entry.
Upgrading the Server
Simply use the automatic update feature or download and run the installer. You don’t need to uninstall any previous version 2.x. The installer takes care of it.
Upgrading Windows Client Computers
Windows Client Computers should upgrade within 15 minutes. You can also restart the computer to trigger the upgrade.
Upgrading Apple Mac Computers
Open Safari and download the Mac installer. Run it. It automatically takes care of any previous installation.
July 9, 2018 @ 1:14 pm
Any reason why the lights out service is constantly using CPU i.e. more than 20%? Every time I look in task manager it’s hogging the processor.
July 9, 2018 @ 1:35 pm
Hi Lee,
do you see a constant 20% load? The actual load depends on the cpu speed, number of cores and the number of monitored items. A peak every 10s is expected, but not all the time.
To analyze that further, please open a ticket to share log files and additional information.
Regards
Martin
July 9, 2018 @ 2:11 pm
Constantly above 20% despite a re-install. CPU is a XEON E3-1225 so pretty capable.
July 9, 2018 @ 2:14 pm
Then please open a ticket here https://green-it-software.com/osticket/ and attach your server logs. Simply zip the whole folder c:\programdata\LightsOut2\Logs (via right click, send to compressed folder) and attach the archive to the ticket. If you do not see a folder c:\programdata, then open explorer options and enable “show hidden files and folders”. Please attach a screen shot of taskmanager also.
July 9, 2018 @ 2:26 pm
Doing it now, quick look shows this constantly:
2018-07-09 13:04:49:048 [1136] ERROR EssentialsBackupMonitor: Timer and monitoring stopped, too many errors
2018-07-09 13:04:53:560 [ 3] WARN Evaluation of Backup/Client computer backup needed more than 2.7954341 seconds!
2018-07-09 13:06:28:756 [1253] ERROR EssentialsBackupMonitor: Exception in TimerCallback GetIoLoad System.ComponentModel.Win32Exception (0x80004005): The requested resource is in use
at System.Diagnostics.PerformanceMonitor.GetData(String item)
at System.Diagnostics.PerformanceCounterLib.GetPerformanceData(String item)
at System.Diagnostics.PerformanceCounterLib.GetCategorySample(String category)
at System.Diagnostics.PerformanceCounterLib.GetCategorySample(String machine, String category)
at System.Diagnostics.PerformanceCounter.NextSample()
at System.Diagnostics.PerformanceCounter.NextValue()
at AxoNet.LightsOut2.Activity.Essentials.EssentialsBackupMonitor.GetIoLoad()
July 9, 2018 @ 2:39 pm
That sounds like damaged performance counters. Try to do a repair: https://support.microsoft.com/en-us/help/2554336/how-to-manually-rebuild-performance-counters-for-windows-server-2008-6
July 9, 2018 @ 3:45 pm
That solved that error, cpu usage still high. I’ve submitted a ticket.
Thanks
July 19, 2018 @ 3:28 pm
Problem has been fixed. Lee told me “Found an error in the events logs to do with usbperf performance counter. I repaired this from the Winsxs folder and lights out CPU usage dropped dramatically (less than 1%).”