Windows Agent 9.0 (2023-03-16)

New Features

Monitoring Settings: New Options to Restrict the Agent Upload Bandwidth and Timeframe

We have introduced two options to limit the bandwidth and timeframe of the Agent uploads to the server. The options can be found on the Monitoring Settings > Advanced window:

  • The MAX UPLOAD BANDWIDTH (KB/S) field allows you to set the maximum upload bandwidth (in kilobytes per second). If no value or a 0 value is set in the field, the bandwidth will be unlimited.
  • The TIMEFRAME TO UPLOAD COLLECTED DATA lets you specify a time range for the upload activity. You can drag the two sliders to adjust the time. If no timeframe is configured, the Agent will be able to upload data anytime.

If you have many users or a slow network, these options will help you prevent overloading your network infrastructure by imposing a throttled bandwidth and the async upload of video/audio recordings. Furthermore, you can configure it in a way that the uploads take place during off peak hours only - making the operation smoother. These might also be useful if your end users have a slow connection.

Please note that restricting the Agent upload bandwidth/timeframe might delay the data availability on the Teramind Dashboard and impact some features. For example, playback of video recordings, OCR search, etc.

Bug Fixes

Behavior Rules: Block Action for Browser Plugins not Working Properly for Chrome Extensions

Due to a bug, the Block action for some behavior rules like the one below wouldn't work properly. The rule would trigger as expected, show the bock message and get logged on the BI Reports > Behavior Alert, but it wouldn't actually block the extension/plugin from running:

The bug is fixed now.

When the block action is working properly, it will remove the offending extension(s) from the browser's Extension menu and if you try to visit the extension's page, it will show that This item has been disabled in Chrome:

Monitoring: New Email on Outlook Web (OWA) not Showing Until Page Refresh

Due to a bug, new email notifications on the Outlook on the Web/Outlook Web Access (OWA) wouldn't work and arriving emails would only be shown when the webpage is refreshed. This might happen especially when you have the SUSPEND MONITORING WHEN WEBSITE CONTENT CONTAINS field set on the Monitoring Settings > Websites:

We have made changes to our email detection mechanism so that web apps like OWA which uses Server-Sent Events (SSE) will work properly now.

Monitoring/License: Windows Enterprise Multi-Session not Recognized as a Session Host

Windows Enterprise Multi-Session (previously known as Windows Enterprise for Virtual Desktops) available under Azure Virtual Desktop service would be incorrectly detected as an endpoint instead of a session host. As a result, the Agent wouldn't capture data for multiple users this version of Windows supports:

The bug is fixed now.

Monitoring Settings: Password Fields Still Captured Even when the Option is Disabled

When the MONITOR KEYSTROKES FOR PASSWORD FIELDS option on the Monitoring Settings > Websites is disabled, the Agent shouldn't track keystrokes when a password field is active. However, due to a bug, it would continue to capture keystrokes from the field:

The bug is fixed now.

Monitoring Settings: All Websites are Blacked Out when a Shared List is Used

You can use a text-based Shared List in the MONITOR ONLY THESE WEBSITES field on the Monitoring Settings > Websites window. The expected behavior is that, windows displaying websites not listed in the shared list will be blacked out on the Session Player/screen recordings. However, due to a bug, the Agent would black out all websites even if they were included in the shared list:

This would happen because the Agent would try to match the exact URL specified in a shared list. So, for example, if the shared list contained an item, it won't work. But would work as expected:

The bug is fixed now.

Teramind Diagnostics Tool (TMDIAG): Inconsistent Timestamps in Logs

A bug was fixed in the TMDIAG to address time inconsistency in the log records:


Was this article helpful?
0 out of 0 found this helpful