Since the last release notes, we have brought to you the following new features, changes and enhancements to existing functionality:
- Software usage level categorization has been enhanced.
Software usage categorization has been improved both in the Applixure Agent as a better detection, as well as in our backend analyzing the usage data.
This improved detection should especially affect complex software suites such as Microsoft Office or Visual Studio, which may have multiple different installed components (some visible and some not in the Installed Programs applet in Windows). Previously, such "umbrella" products might not show usage associated with one or more of installed sub-components/products, but now Applixure gathers up and accounts the usage from sub-produts against the main product as well as for the actual product.
For technical reasons, this software product parent/child relationship detection and usage accounting can only be done for software products installed with certain standard installer technologies, mainly Windows Installer (MSI).
- Support for manual/explicit network proxy settings for Applixure Agent.
Due to some organisations' internal networks requiring all end-user devices to use proxy for outgoing HTTP/HTTPS connections [to Internet], we have added support for configuring explicit proxy settings for Applixure Agent using Group Policy and/or manual method.
Under most circumstances, no action should be required for Agent to communicate successfully with our backend, but if it is known that software running on end-user devices (such as Applixure Agent) require proxy settings it's now possible to do so. Please refer to Helpcenter article on the subject for further instructions.
Please note that since Applixure Agent runs as a service and not under user's logon session context, usual PAC file -based solutions for distributing proxy settings automatically to the users may not be visible to the Applixure Agent.
- More detailed display/monitor and battery asset information.
While before Applixure did show current maximum batter capacity (our of max design capacity) and number of displays attached to the computer, if any, we have now improved this information in the following way.
For displays attached to the computer, Applixure now tries to detect and show display's information as reported by the monitor (primarily) or by Windows' driver (secondarily). Depending on the display, Applixure now also shows display's serial number and manufacturer/model information.
For batteries found in the laptops/tablets, we now accurately show all regular batteries present and not just one (out of possible multiple). Depending on information reported by the battery - like with display - we report the manufacturer and the serial number.
Serial numbers for both displays and batteries are also searchable in the devices list view, making it easy to locate particular asset by its serial number.
- Azure AD joined Windows 10 devices are now detected.
In the device's operating system security readiness information, Applixure has previously only detected if the device is joined to a [local] Active Directory domain and show those devices as having "good" OS security readiness for centrally managed policies.
We have now added support for detecting Windows 10 devices that have been joined to Azure AD, instead of local AD, and show this information for OS security readiness:
In addition to detecting the join status, we now also show detected Azure tenant name. For local Active Directory -joined devices, we also now show AD's domain name.
- Display of multiple active security products in operating system security readiness.
Previously Applixure would only show one active anti-virus/anti-spyware/firewall product per device in the security readiness information. However, if user for some reason has multiple active security products in the computer protecting the same category of issues, those are now all listed.
- Fixes for miscellaneous technical issues and minor functionality improvements.