Skip to main content
Windows Agent 23.34 (2023-09-11)
A
Written by Arick Disilva
Updated over 11 months ago

Improvements

Proper Shutdown of the Agent

When a user shuts down the computer or logs out of Windows, the operating system provides a few seconds for all open applications to close. However, sometimes that might not be enough time for the Agent to close all its processes before closing properly. As a result, you might see a message like the one below and the Agent might lose data:

We have made improvements to the Agent so that the Agent will prevent the OS from shutting down/logging out until it completes a graceful shutdown.

Bug Fixes

"Do Nothing" Action Displayed as "Notify" Action on Alert Reports

Due to a bug, if you created a rule without specifying any Action (Do nothing), the rule violation reports such as the BI Reports > Behavior Alerts, Behavior > Alerts would display "Notify" under the Action column:

The bug is fixed so that the Action column will now display "No action" if no Action is selected on a rule.

Filenames Not Captured for WhatsApp Web Version

Due to some recent changes in WhatsApp's handling of the uploads/downloads mechanism, file names wouldn't get captured properly by the Agent. As a result, you might see names like, document.enc, image.enc, etc. when viewing web upload and web download activities on reports like the BI Reports > File Events, Monitoring > File Transfers, etc.:

Since file names weren't captured properly, any Files-based rule using the WhatsApp URL and the Download File Name or Upload File Name conditions might not work either.

The bug is fixed now so file names will be captured accurately.

File Transfers for MS Teams Not Detected

Due to a bug, file upload and download activities on Microsoft Teams wouldn't get detected. As a result, you wouldn't see those events on reports like the BI Reports > File Events, Monitoring > File Transfers, etc. For the same reason, any Files-based rule using the MS Team as the app/URL and the Download File Name or Upload File Name conditions might not work either.

The bug is fixed now.

Outgoing Messages Not Captured for Google Chat

Due to a bug, outgoing messages on Google Chat wouldn't get captured by the Agent. As a result, you would only see incoming messages on reports like the Monitoring > Instant Messaging report:

The bug is fixed now so that both incoming and outgoing messages will be captured as expected.

Messages Not Captured for Some Webex Web Domains

Due to some recent changes in WebEx, conversations on some domains wouldn't get captured on the Monitoring > Instant Messaging or Monitoring > Online Meetings reports.

The following domains seems to be affected but there might be other domains too:

  • meetXXX.webex.com (e.g., meet292.webex.com)

  • meetingsemeaXX.webex.com (e.g., meetingsemea31.webex.com)

  • web.webex.com

The bug seem to affect Agent version 20.0 but other versions might be affected too.

Rules to Detect File Uploads to WeTransfer Wouldn't Always Work

Due to how WeTransfer handles upload requests, sometimes a rule like the one below might not get triggered:

The bug is fixed now so that rules to detect uploads via the WeTransfer website will work as expected.

Search for Websites Not Working on the OCR Report

The Monitoring > OCR report has a search field that allows you to filter reports by apps or websites:

However, due to a bug, the search would work for apps only. If you tried to search for a website or URL (e.g., google.com, cnn, etc.) in the field, it wouldn't return any result:

The bug is fixed so that you will now be able to search the OCR results by both apps and websites:

Attachments Not Captured for Thunderbird Emails

Due to a bug in the mail parser, attachments in Thunderbird emails weren't captured. As a result, you would see no links for the attachments under the Attachments column on the Monitoring > Emails report or "No attachments to download" message on the context menu of the BI Reports > Emails report:

The bug is fixed now.

MS Access Wouldn't Close Completely While the Agent Was Running

Due to a bug, Microsoft Access might not close completely while the Agent was running. The process (msaccess.exe) would remain in the Task Manager as a background service even after closing the application window (including closing with Alt + F4 keys, closing from the Taskbar, using the Close button from the Alt + Tab App Switcher, etc.):

As a result of the bug, the user wouldn't be able to open any databases. The app wouldn't show any error message either.

The bug seems to affect Agent version 16.0 and above.

The bug is fixed now.

The Revealed Agent Would Crash After Sign Out and Sign In

Due to a bug, the Revealed Agent would unexpectedly crash/quit. This would happen in a very specific situation:

  1. The user signs into the Agent.

  2. The user opens an app like Firefox, Thunderbird or Skype.

  3. The user signs out.

  4. The user signs back in and starts using the same app(s).

It's usually at the fourth step that the Agent would crash without showing any error message.

The bug seems to affect Agent versions 11.0, 13.0, 16.0, 20.0 and 23.32 but other versions might be affected too.

The bug is fixed now.

The Agent Would Continuously Disconnect/Reconnect

Due to a bug, the Agent would continuously reconnect to the server every few seconds. As a result, the Online Employees widget on the Dashboard would become unstable (it would continue to show users online/offline) and the user would be shown as offline on the Employees report.

This could happen if you had an invalid regular expression specified in the DO NOT MONITOR THESE LOCATIONS (REGEX) field under the File Transfers monitoring settings:

In the above example, the correct version should have been c:\\programdata\\autodesk instead of c:\programdata\autodesk.

The bug is fixed now so that any invalid regular expression will no longer cause the Agent to disconnect/reconnect. Instead, the event will be recorded in the Agent Log as an Incorrect regex detected in tracking_profile_id=<agent ID> entry.

"Publisher Unknown" Warning When Installing the Cloud Agent

Due to a bug in the digital signature process, Windows might show a "Publisher: Unknown" warning when installing some versions of the Cloud Agent. The bug is fixed so that you will now see a "Verified publisher: Teramind Inc." message instead:

Did this answer your question?