Reports using the alias “at” could not be edited in the report builder The scanning queue would appear stuck when scanning certificates due to a stopped Remote Registry service on the scanning target LsAgent scans would incorrectly update tblAssets.ScanServer, leading to failed deployments Linux software was not scanned correctly when using LsAgent The Lansweeper service sometimes used excessive memory LsAgent scans returned an incorrect user domain if the user was logged in using a Remote Desktop session Background checks will automatically run every 30 minutes across multiple servers when cloud prerequisite checks fail More details are provided when cloud prerequisite checks fail The Microsoft 365 scan and mail tester can test non-default environments The default scanning schedules have been spread out to lower peak network traffic Selecting the OT assets menu in the web console will redirect to the cloud OT assets page for linked OT installations A message will display when the installer is ran on unsupported operating systems The volume of LsAgent scan file sizes can be reduced by disabling scan items A message will display when the installer is ran on systems with unsupported database servers Added a new section in the Scan Test Tool to fetch registry data using WMI Added a new cleanup option to delete unused data for Windows assets that are no longer in the inventory
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |