Secure Endpoint 9.2 release notes

The pre-defined Event History report has been retired, and the link to this report has been removed from the Events report category in the Reports area. All user-defined reports based on the Event History report are also retired.

You can now track actions as follows:

• Go to Action History to track your Freeze and Run Script requests.

• Go to Event History to track your Manage Supervisor Password requests and triggered Offline Freeze rules.

The Event History page in a device's Device Details has been retired.

You can now track a device's actions as follows:

• Go to the device's Actions page to track its Freeze and Run Script requests.

• Go to the device's History page to track its Manage Supervisor Password requests and triggered Offline Freeze rules.

• The Policy Groups resource has been added to the API. Learn more

• The following endpoints have been updated:

  • POST / actions/requests/freeze (Freeze devices): You can now specify an existing Freeze message by messageUid.
  • POST / actions/requests/eum (Send a message): You can now specify an existing message by messageUid.
  • POST /tracking/device-missing/missing (Report devices missing): The request is now processed successfully when the emailContacts field is empty.
  • GET /reporting/devices (Get device details): The Statuses.status parameter in the deviceFreezeActionStatus object now includes a separate Score for each Freeze type.
  • POST /actions/requests/reach (Run a script): The Script name field is no longer empty when you view the request in the console.

• An API token's expiration date now defaults to 90 days instead of 3 months.
• When an API token is used by a SCIM integration, the token's Last used date is now updated as expected.

• When Microsoft Intune is reported as Unhealthy, the following unhealthy reason may now show: Certificate expired.

• Application Health now supports the following persisted applications:

  • Avast Antivirus

  • Halcyon Anti Ransomware

  • HP Insights

  • Octopus Desk

  • OneBe TRUST DELETE

  • Secureworks Taegis Agent

  • Syxsense Responder

  • VMWare Carbon Black EDR Sensor

• Lanscope An Client

  Application Resilience now supports Lanscope An Client Learn more

• You can now persist the following application versions:
  • Absolute Secure Access 13.x or higher
  • Blackberry CylancePROTECT 3.1.x or higher
  • BeyondTrust Jump Client 23.3.x or higher
  • Crowdstrike Falcon 7.x or higher
  • Deep Instinct 5.x or higher
  • Dell Trusted Device Agent 6.x or higher
  • F5 Big-IP Edge Client 72.22.x or higher
  • HP Insights (formerly HP TechPulse) 5.x or higher
  • Symantec DLP 16.x or higher
  • Syxsense Responder 24.8.x or higher
  • VMware Carbon Black Cloud 4.x or higher
  • FortiClient Fabric Agent 7.x or higher
• The Do not reinstall or upgrade if the app is already installed option is now available when you’re configuring the Report, repair, and reinstall option for the following applications:

  • BeyondTrust Jump Client

  • SentinelOne

• The following Application Resilience policies have been updated:
  • Absolute Secure Access

    When configuring the Report, repair, and reinstall option, you can now upload a file containing the Secure Access client settings to apply during reinstallation. Learn more

  • Dell Trusted Device

    In the console, all instances of Dell Trusted Device Agent have been changed to Dell Trusted Device.

  • F5 Big-IP Edge Client

    The version format xx.xx.* (such as 72.22.*) is now supported in the Application Resilience policy.

  • FortiClient Fabric Agent

    The Application Resilience policy now checks that the following file is present and signed: Forticlient.exe.

  • HP TechPulse

    In the console, all instances of HP TechPulse have been changed to HP Insights.

  • Microsoft BitLocker

    For BitLocker with standalone MBAM, you can now add installation parameters that correspond to the installer you use.

  • Syxsense Responder

    You can now successfully set the application version to a version that is lower than 22.11.*, such as 22.5.*.

  • Trellix Drive Encryption

    When the Report only option is selected, installer settings are no longer displayed.

• If a device is manually set to a date and time that is more than 24 hours ahead of the current time, its Application Resilience payloads are now ignored.

• Chromebook extension version 2659, which includes some stability improvements, has been released.

• The following hardware data points are now synced from the Google Admin console:

  • Volume > Free Space

  • Volume > ID

  • Volume > Size

• The display name of a time zone (for example, Pacific Standard Time) is now shown consistently across the console. Previously, some pages showed GMT+/-<#>, such as GMT+/-8.

• If a device is manually set to a date and time that is more than 24 hours ahead of the current time, its Device Usage payloads are now ignored.

• When Google Maps Geolocation is unable to resolve a device's Wi-Fi location, and its IP location is reported instead, the BSSID and SSID of each detected Wi-Fi access point are now included in the event on the device's History page.

• Previously, a Windows device's CPU > Architecture field may have shown a numeric code, such as 9, instead of a valid value, such as x64. This issue is now fixed.

• Clicking Action Requests on the navigation bar when the Action Requests page is already open no longer displays a blank page.

• When you export the Events page, the exported report now includes a Device/Object's details column, which shows additional information about the device or object, such as the device's serial number, or the name of the object that was updated.
• For events triggered by an Offline Freeze rule, the Summary area now shows one of the following instead of the username of the rule creator:
  • Name of the rule

  • Absolute System

  Also, fields that do not apply to Offline Freeze rules are no longer displayed.

• Previously, when you exported the Report on Devices page, the report included columns for product licenses that were not in use. To simplify the report, these columns are now excluded.
• The following default filter has been removed from the Unlicensed devices report: Final license expiration date is empty. The filter is no longer required to ensure that the report shows all unlicensed devices in your account.

• When all devices in an account are unlicensed, the Missing devices page is no longer accessible using its URL.
• If a refurbishment center attempts to refurbish a missing device, refurbishment is now blocked and an event is logged.

• After a Reach Script runs on a device, the script parameters are no longer visible in process monitoring tools, such as Task Manager.
• You can now successfully add a script to the Script Library when a script with the same name already exists in the library.
• Previously, when the Collect .exe files script ran successfully with a return code of "0", the output file was empty. This issue is now fixed.
• To inform Administrators that a restart is required after the Change Windows wallpaper script runs on a device, the following note has been added to the script: "A device restart is required for the change to take effect."
• Previously, the Start Processes with Optional Arguments script failed to run if the specified process path contained a space character. This issue is now fixed.

• In addition to showing a checkmark, selected options in a quick filter are now highlighted and bolded.
• In a device report, repeatedly searching for devices and then switching between map view and the report caused the Search field to stop working. This issue is now fixed.
• Previously, when deleting a Device Analytics report, the Delete Report confirmation dialog did not close after you clicked Delete. This issue is now fixed.
• In the Anti-Malware report, if you remove and then add back the Anti-Malware columns, you can now successfully remove the Product name and Version columns.
• For Offline Freeze rules, the Requester report column in the Device Freeze Status report now shows the rule name instead of the username of the user that created the rule.

• For Alert rules and Action rules, the subject line of each email notification now includes the device name of the device that triggered the rule. If the device name is not available, one of the following is shown (presented in priority order):
• Serial number
• Absolute Identifier
• Unknown device
• When you add the Freeze action to an Action rule, the Generate a random code for all devices option is no longer available for selection in the Unfreeze Code section.

• In a Send Message request, you can now edit the name of the End User Message template used in the message. The edited name shows when you view the request in Action History.