Skip to content

Changes in Release 1.103 (2026/04/05)

Management Console

  • New: OS compliance policy now supports Maximum Updates Behind condition to enforce that clients stay within a defined number of OS updates.
  • New: OS compliance policy now supports Reject End-of-Life OS option to block clients running unsupported OS versions.
  • New: Event Log now tracks authorization events (access denied), client compliance changes (OS version, security products, disk encryption, domain membership, geolocation, agent version), and configuration changes for API keys, enrollment tokens, tenants, partners, and user groups — with old/new value tracking for role and posture changes.
  • New: Event Log filters for Authorization and Client Compliance event categories.
  • New: Event Log records authentication initiation events, enabling detection of silent login failures where the identity provider callback is never reached.
  • Fixed: Signing up with an Azure AD domain that already had a tenant would create a duplicate tenant instead of linking to the existing one.
  • Fixed: Saving DNS Server settings did not show a success confirmation.

Agents

  • Fixed: Authentication flow not recovering properly after screen lock or failed login retry on Windows.
  • Fixed: Agent updates on Windows could fail if the agent was started by autostart or the user during the update.