No new features were introduced in the 1.07.03 release.

• Windows Server 2019
  The Identity Awareness Agent now officially supports running under Microsoft Windows Server 2019.

• The setting "Allow source IPs/networks" has been updated
  "Allow source IPs/networks" in the Identity Awareness Agent Settings previously required at least one value in the list. The save option was disabled without any obvious reason if all values were removed. All networks are now used as default fallback if the list is empty. The description for this setting has been changed to "Restrict source IPs/networks to" to better reflect what the setting does.
• User caching has been updated
  Caching of users is no longer done using a local database. Instead the cache is kept in memory.
• Windows Server 2003 no longer supported
  Support for Microsoft Windows 2003 has been removed.
• Updated .NET Framework requirements
  The Identity Awareness Agent now requires .NET Framework 4.7.2 to be installed.
• Support for new event ID has been added
  The Identity Awareness Agent now also listens for event ID 4624, "An account was successfully logged on", which is used by Windows 10 and Windows Server 2016.
• Improved program logging
  The output of logged events during run time has been improved. More events are logged and the use of log levels has been improved. Logs are now logged in NLog format.
• Support for use of wildcards in excluded users list
  It is now possible to use the wildcard characters in the excluded users list. Two kind of wildcards characters are supported:
  ? (any character, one and only one)
  * (any characters, zero or more)

• Global Catalog query
  IDA now supports querying of Active Directory Global Catalog which enables the cross-domain searching of the universal user groups in the multi-domain Active Directory installations.

• Support for filtering of client IP addresses
  IDA now supports filtering of client IP addresses when logging in to the Active Directory.

• IDA-281: Under heavy load, the agent could sometimes fail to perform AD lookup for group memberships properly.

• IDA-274: A log message was sent too often and caused some annoyance in some installations.
• IDA-275: The Identity Awareness Agent parsed one type of response from cOS Core incorrectly, which caused a warning message to trigger.

• IDA-273: The Identity Awareness Agent threw an error when the ANONYMOUS LOGON event was triggered. The Agent now ignores this event.

• IDA-225: The Identity Awareness Agent crashed if it had no permission to the AD Server. Instead of crashing, the Agent now logs if permissions are missing.
• IDA-262: cOS Core could sometimes lose contact with the Identity Awareness Agent, and for long periods being unable to reconnect.

• IDA-195: Remote Desktop IP Virtualization feature was reporting the host IP address to the Firewall instead of a Remote Desktop session IP address if Remote Desktop services was running on a server which was not an Active Domain server.
• IDA-214: IDA service was unexpectedly terminated in a case when an IPv6 address could not be converted to IPv4

• IDA-146: An unexpected exception was thrown and logged in the Windows Event Log every time the IDA service was stopped.