Honeycam

What's new in this version:

Added:
- When sending DHCP packets for CDR (Credential-free Device Recognition), we now include the MudUrl for better analysis and correct detection
- Added a new tool that can be found in the filesystem under Tools/Gatherlogs.exe. This tool allows for the automatic gathering of all of the relevant logs and system information into a zip file which can be provided to Lansweeper support for troubleshooting purposes
- vMotion-related properties are now extracted during the scan of a VMware cluster. These new properties are visible on the asset page of the VMware cluster and include info on high availability enablement, DRS enablement, default virtual machine behavior and the number of virtual machine movements
- The system will now extract vMotion-related properties during the scan of a VMware host. These new properties are visible on the asset page of the VMware host and include info on CPUs, cores, the power state of guests and hyper-threading enablement
- Added a new report ‘Vmware: vMotion overview’ that shows the new scanned properties of Vmware environments
- Mentions to new functionality in Lansweeper Cloud like vulnerability insights and normalized software were added to certain reports and in Software > Authorization
- CDR (Credential-free Device Recognition) is now also applied to asset data with the Windows asset type
- In the User Cleanup options, the option to cleanup groups detected in on-premise Active Directory and Azure Active Directory was added. The option allows the automatic cleanup of groups that haven’t been found in the most recent scan of the Active Directory environment
- Add frequent check to see if LsAgent relay access has been overridden by another installation
- Extended SQL server scanning with SQL Server 202
- Change text of label “Security” into “Maintenance information” label on the Asset details page

Changed:
- Improved the status and description of errors when linking with Lansweeper Cloud
- Moved the general search bar to the left side of the screen
- The sub-menus for reports are improved visually and functionally by reworking the hover functionality and the search bar
- Extended SQL server scanning with SQL Server 202
-An asset that was imported or added through the Lansweeper web console will have its MAC address corrected when it is retrieved during regular scanning. This behaviour was introduced to avoid faulty merge behaviour where two unrelated assets would be merged
- Rephrased the warning message for a scan server without an internet connection when changing the dedicated scanning server to track warranty information
- Visualisation of Asset Radar network interfaces with multiple IP addresses has been altered as network interfaces can only be enabled or disabled in their entirety and not per linked IP address
- Sorting on mailbox size in the Exchange mailbox data on Exchange server asset pages will no longer sort alphabetically on numbers but will sort numerically
- Some icons in popovers in the Lansweeper web console have been reworked: the icon of the installation status to the cloud, the icon for unassigned tickets, the icon for the notifications and the icon for events
- Updated the built-in list of OIDs used for SNMP lookup
- When editing the website access on the website settings page, the groups can now be sorted and filtered in their various fields
- When performing CDR (Credential-free Device Recognition), the properties of assets with an unknown asset type are now also filled and corrected with data from CDR
- Some reports on historical data have been extended so they now show all 3 possible values for history entries (add, delete AND update)
- Under the menu ‘Community’, the menu item ‘API’ is renamed to ‘Cloud API’

Fixed:
- Scanned Linux assets are merged with existing assets based on IP address first and foremost which can lead to incorrect merged assets
- During Windows computer scanning, the main IP of an asset is not always being updated if the newly acquired IP is a public IP
- Unable to insert an image in a note or a description in a helpdesk ticket through an image browser
- It is no longer possible to use the Show header, Show footer or Show message buttons under ConfigurationWebsite Settings as the results are not saved
- When using deployments, a superfluous error could be logged when there was no exception to the flow
- The netBIOS name of Active Directory scanning targets is used to generate assets rather than the scanned NetBIOS name. This can potentially lead to duplicate assets
- Disabling the Linux scan items, configured under ScanningScanned Item Interval, has no impact during LsAgent scan file imports
- When disabling scan items for Linux under ScanningScanned Item Interval, the actual items are not marked as disabled from scanning in the corresponding asset information pages
- After every update, the manually changed authorization rules in IIS for the Lansweeper web console are reverted
- Scanning of Hard Disk Partition information on Linux systems doesn’t parse correctly when the Linux distribution is in another languag
- After editing and saving a scanned Azure Resource Group in the Lansweeper web console the unique identifier gets shortened
- The cleanup option ‘Scan users that are disabled in on-premises Active Directory.’ behaves incorrectly as another option overrides the value
- The uptime field is no longer present on asset summary pages
- Sorting on LsAgent version in Assets > LsAgent Assets is unable to retrieve the correct data
- Unable to process a scanned certificate when the issuer of the certificate is empty
- The 'Import from AD' button under Configuration > Asset Groups is not functional. The selected IP ranges are not imported
- Incorrect user domain for the last logged-on user for Windows assets scanned via LsAgent that have their Azure environment scanned separately
- Incorrect main MAC address displayed for Windows assets with multiple IP addresses. The MAC address linked to the IP address of the scanned network interface should be displayed
- The asset page of a scanned SCCM Server is broken when the SCCM scan of the asset fails
- Incorrect domain information retrieved for an ESXi host during vCenter scan
- Unable to retrieve OWA information for Exchange mailboxes. When certain information is not found, it is erroneously displayed as ‘No’ instead of being omitted
- A deployment does not start from a dynamic group when the group is created by applying a filter on the last successful scan
- Disabled LsAgent groups are not shown in the dropdown that allows moving assets to an LsAgent group
- The Information icon in the Configuration tab of LsAgent groups under ScanningLsAgent Scanning has an excessive size
- When creating multiple AWS scanning targets, a separate credential needs to be created and mapped for each scanning target. Reusing a created credential is not possible
- The built-in admin for the helpdesk and knowledgebase is shown a dialogue to enter the email address on the second login
- SCCM managed device shows the wrong SCCM server when the asset moves to a new SCCM server
- During SSDP discovery of an IP range scan, superfluous errors are logged
- When linking to Lansweeper Cloud, the prerequisite checks don’t react correctly when the Lansweeper database is hosted in an Azure SQL-managed instance
- Mass edit of assets for custom fields of type Date are not persisted in the database
- Error when performing a certificate scan for the first time. Subsequent scans do not show this issue
- After scanning Linux Solaris, an error is shown on the asset detail page of those assets
- Built-in report: “Windows: Last scanned Windows update by computer” does not return the last update
- The field LastseenCredentials of an asset is filled with the first tried SNMP credential when it isn’t scanned successfully via a protocol requiring a credential
- In the new menu layout, custom names with international characters are displayed in the wrong encoding resulting in unreadable names
- The asset location on a location map is sometimes shown in front of the left-side menu
- The menu overlays a couple of rows from the table of interfaces on the switch asset pages when in print mode making it seem that some data is missing
- Some random assets are often not synced towards Lansweeper Cloud
- During custom file scanning of Linux system, an error is often shown in place of the type of the scanned item
- Warranty for Dynabook devices isn’t being fetched
- Resource entry missing for upgradescript570 in master builds
- Asset Radar is overloading the SQL server with queries
- Displaying ChromeOS device result in webserver error
- OU relations not shown on user pages
- VMware scanning – VMware vMotion report shows ESXi cluster while the asset isn’t shown in the related ESXi Cluster repor
- Custom OID scanning returns null values while devicetester.exe returns values for the same OIDs
- Deployments don’t execute after being delayed because of another deployment on the same machine