A new report, Audit is added to the BI Reports:

This report contains similar functionalities available on the System > System Log report but comes with enhanced filtering and other features available to the BI reports. For example, advanced filters, customization/cloning, detailed views, etc. At the moment, the report comes with a Grid widget only. You can select from the following columns (by clicking the Columns tab on the right-side of the grid):

We have added a new dataset option, LDAP Groups on the BI Reports > Filter panel:

This option will allow you to filter employees by their Active Directory group(s).

Content Sharing >Emails rules like the one below will now be able to detect draft emails. Previously, you could only detect contents when the email was being sent:

The rule will trigger when the draft is saved. This way, you can be more proactive and prevent threats such as potential data leaks.

We have added support for Zoom (Web) version:

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:

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.

Currently, a user/admin is required to confirm changes with their password when making changes to some settings on the Teramind Dashboard. However, some users might not have a password (e.g., if they are external LDAP users).

We have introduced a new option, CONFIRMATION METHOD FOR DASHBOARD CHANGES under the Dashboard authentication section on the Settings > Security tab. This option will let you choose the preferred authentication option for confirming any changes made on the Teramind Dashboard:

A few notes:

We have introduced some new API calls to get entities from menus that have dynamic sub-menus such as BI Reports, Dashboards, Monitoring, etc.:

You can now lock/unlock employees from the Employees > Action menu:

The Status column will show if the employee is Locked or Active. When you apply the Lock action, the employee they will be taken to the lock screen immediately if they are online. Otherwise, the lockout will take effect when they next come online:

If the employee tries to log back in, they will be automatically logged out within a minute. Note that, once the lock feature is enabled, it will continue to work even when the employee is offline. You can use the Unlock option to unlock the employee.

We have introduced a new option, Stay Logged In to the Mac Revealed Agent:

When this option is enabled, Teramind Agent will automatically log in when it's started. Please note that the Stay Logged In option is only shown when you enable the Save password option.

We have updated the Mac Revealed Agent so that it's now similar to the Windows Agent and supports hierarchal project and task lists. You can also now search by task names:

We have introduced a new Hidden/Stealth Agent configuration option that will let you override the default domain name. There are two ways you can set this:

We have introduced a new Hidden/Stealth Agent configuration option that will let you override the default domain name. There are two ways you can set this:

1. Use the domain-override parameter in the agent.conf file. For example:

2. Rename the installer/package file to include the -do() parameter. For example:

Once set, the username on the Teramind Dashboard will show the new domain name:

By default, Teramind doesn't track connections to a website with a bad SSL certificate. So, for example, if your On-Premise server had a self-signed certificate, downloads from the Teramind Dashboard wouldn't be recognized as web downloads.

With the MONITOR CONNECTIONS TO HOSTS WITH INVALID CERTIFICATES option on the Monitoring Settings > Websites, you can now monitor websites that have an invalid certificate:

Adding an IP address in the field will activate SSL traffic decrypting so that Teramind will be able to properly parse and present the information on the Dashboard.

At the moment, Teramind on AWS doesn't support the removal of screen recordings from AWS S3 buckets. As a result, the DELETE HISTORY AFTER (DAYS) setting on the Monitoring Settings > Screen doesn't have any effect. Customers could still use the Amazon S3 Lifecycle to manage their storage.

However, users who weren't aware of this would try to use this setting and get no results.

We have updated the Monitoring Settings > Monitoring Profile page so that it now displays a message about on the Screen's SETTINGS column. We have also updated the Screen: Edit settings window to display the message, "Retention settings for cloud storage are not supported yet. Please setup retention policy manually in the cloud.". Also, the DELETE HISTORY AFTER (DAYS) field is no longer editable for AWS deployments:

Teramind lets you create HTML alerts for some rule actions using an alert template (Settings > Alerts > CUSTOM USER ALERT HTML). There's also a preview option for the template. However, sometimes the alert might not show exactly as the preview on the user's computer:

This is due to how the HTML text is rendered by the Teramind Agent. For security reasons, we have restricted the use of some tags and others are rendered a bit differently than a typical browser.

A warning will now be displayed on the alert preview so that customers are aware of this:

Previously, only OCR nodes were displayed on the Settings > Server Management tab under the Nodes section. Now, the dashboard will display information for all nodes including the Master and BI nodes:

Previously, the server would create folders on a daily basis for screen and audio recordings even when the Monitoring Settings > Screen and Monitoring Settings > Audio were disabled. This would unnecessarily exhaust nodes on the storage volume. We have updated the recording mechanism so that the server will create folders only when required (e.g., before writing a recording).

Teramind Server sends a screen update request to the Agent periodically. We have optimized the process so that the requests are sent only as needed - reducing both the memory and network loads.

LDAP users containing space(s) in their usernames (e.g., John [email protected]) can now log into the Teramind Dashboard without any issue. Previously, this option wasn't supported.

Now the Fetch Attributes will only be shown if a successful fetch took place. Otherwise, they will be kept hidden:

Previously, if a user had no First Name or Last Name on their profile, the User Menu would only show the avatar. Now, it will show the avatar and the email address if the user has no names:

At the moment, the Mac Agent automatically requests permissions for the NetApp extension (used by the Agent to monitor network connections) during:

For some customers, this might be unexpected and others might not want to monitor the network connections at all.

We have implemented the ability so that the customers can now enable the network permission using the sudo command on the Terminal. The option is available to both the Stealth and Revealed Agents:

Revealed Agent:

Stealth Agent:

Here are a few things to note when installing, updating or uninstalling the Agent:

We have updated the documentation to reflect this change. Please see the article, How to download and install the Teramind Agent for more information.

Previously, special keystrokes such as <Space> were captured differently on Windows and Mac. For example, on Windows, it would show as " ", but on Mac, it would be captured as a special key, <Space>.

This would lead to differences in the Keystrokes reports on Mac and Windows:

We have made changes to the keystrokes monitoring on Mac so that it now captures input similar to the Windows Agent.

The Live Montage widget on the Dashboards allows you to open it on a pop-up window. However, when trying to refresh the window, it wouldn't refresh and just show a "Waiting for data" message:

The bug is fixed now so that, the pop-up window of the Live Montage widget can be refreshed.

Due to a bug, you might not be able to add time (by clicking the ADD TIME button) from the Time Tracker > Time Records or the Time Tracking > Time Cards reports. When trying to SAVE the time, it would show a "Forbidden" error message:

The bug is fixed now. You can add time from these reports as usual.

Due to a bug, if you had a chart widget with a large dataset or with a very long reporting period (e.g., 20 years!), the chart might fail to load.

The bug is fixed now.

Several bugs that would generate an incorrect rule depending on what filters were selected on the BI Reports > report > Filter panel. For example:

All the bugs are fixed now so that a correct rule will be generated when you select any filters and press the CREATE BEHAVIOR RULE button.

Due to a bug, the Description column on the BI Reports > Behavior Alerts and Behavior > Alerts reports wouldn't display time information for some Agent Schedule rules containing conditions like Arrives Late, Ends Late, etc.:

The bug is fixed so that proper time (HH:MM:SS) is now shown in the alert description.

Due to a bug, BI Reports > Behavior Alerts, Behavior > Alerts, and Employees > Alerts report would show "No action" on the Action column for some Agent Schedule rules like the one below:

The bug is fixed now.

Due to a bug in the end-of-day processing of work hours, an Agent Schedule rule using the Daily Work Time condition might trigger prematurely, e.g., before an employee finishes their scheduled hours:

The bug is fixed now so that the rule will not trigger for an employee whose scheduled work hour hasn't ended yet.

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 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:

Due to a bug, Advanced Mode actions in a rule would trigger prematurely. For example, in a rule like the one below, instead of the 6th and subsequent violations, the rule would trigger at the 1st violation or other random times:

This was happening because the rule would count up internal web page requests that would lead to triggering the rule action unintentionally. The bug is fixed now.

Due to some recent updates, the Set User's Active Task action for a rule like the one below wouldn't work as expected:

For example, it would switch the user's task to the Default Task and then back to the task assigned by the rule.

We have fixed the changes so the action would work as it used to before:

In some situations you might have noticed the screen recordings on the Session Player has visual artifacts and frozen frames. Sometimes, skipping to a different time wouldn't update the playback either:

The bug is fixed so that video recordings will display correctly and the timeline changes will update the video playback as expected.

After updating to Windows 11, you might have noticed the screen recordings/live view on the Session Player has visual artifacts similar to the example below:

There are three ways to fix this issue:

Due to a bug, automatic switching to Daylight Saving Time (DST) for some Cloud customers didn't work. As a result, the Session Player and some reports would show wrong timestamps. The bug is fixed now.

Due to a bug, new email notifications on the Outlook on the Web/Outlook Web Access (OWA) wouldn't work and any arriving email 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.

Long text without any line or space breaks (e.g., an URL) would overflow on the Conversation window when you opened a message from the Monitoring > Instant Messaging report:

The bug is fixed now so that the text would stay within the window frame.

Due to a bug, the tasks list on the Add/Remove Time window from the Monitoring > Screen Snapshots report wouldn't show all tasks and it would look different than the tasks list available on the Time Tracking > Time Records or the Time Tracking > Time Cards reports:

The bug is fixed now so that the tasks list on the Screen Snapshots report will show all tasks and it will look similar to the ones available on the other two reports.

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.

When you enable the User can login to Teramind Dashboard option from the Employees > Action menu > Bulk Edit screen, it would turn on monitoring for all the selected employees:

This could be a problem, for example when you want an employee to access the Teramind Dashboard without them being monitored (e.g., Admins, Supervisors).

The bug is fixed now so that changing the User can login to Teramind Dashboard option will not change the monitoring status of the employees.

Due to a bug, if an employee’s computer was controlled via the VNC session, keyboard events wouldn't be captured by the Agent. This means that such events won’t appear on the Keystrokes reports (e.g., BI Reports > Keystrokes), Keystrokes rules wouldn't get triggered, Productivity/Time Tracking reports would show wrong active/idle time, the Online Employees widget would show the employee is idle, and the Freeze Inputs feature on the Session Player wouldn't work. The bug is fixed now.

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.

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: only a browser window displaying a website not listed in the shared list should be blacked out on the Session Player/screen recordings. However, due to a bug, the Agent would black out all windows:

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, wikipedia.org wouldn't work. But https://wikipedia.org would work as expected:

The bug is fixed now.

Due to a bug, the File Driver setting (available on the Monitoring Settings > Advanced window) wouldn't get applied to the user's computer. Even if you turned the setting off, you could still see the service (tmfsdrv2) still running:

The bug is fixed now.

Currently, when you delete an employee (e.g., from the Employees > Action menu), and the employee then tries to log in through the Revealed Agent, the Notifications report shows "Bad password" as the cause of their failed login attempt:

The notification is fixed so that it now shows "Employee is deleted" as the cause of the notification:

If you had multiple statuses with the same project name (e.g., team-managed projects) in Jira, and only selected a few of those statuses (e.g., 2 out of 5), then it would cause Teramind to miss tasks when syncing with Jira. Teramind might also fail to log back time tracking into Jira.

We fixed the integration so that, Teramind will now correctly correlate projects and statutes and sync the tasks accordingly. The resulting task will show in this format: status (project). For example, To do (BUG), In progress (TEST), Resolved (TEST), etc.:

Due to a bug, the agent download links on the User Menu > Download Teramind Agent or the Welcome screen would not include the ports if a custom Hostname (Settings > Security) and Server ports (Settings > Server Management) were used.

The bug was fixed so that the links will now include the Hostname and Server ports:

Due to a bug, you might not be able to add a new employee by choosing the Invite users to download the Revealed Agent option from the User Menu > Download Teramind Agent or the Welcome screen. When you clicked the ADD USER AND SEND INVITATION button, nothing would happen:

The bug is fixed now so that when you add a new user and click the button, it will show a, Your invite was successfully sent! Invite more users now or head to the dashboard to continue! message and the user will receive an email to install the Agent.

The Agent would periodically crash and restart when there's no audio device installed on the computer. The bug would affect some of the older versions of the Agent (ver 6.1, 7.0, etc.). The bug is fixed now.

Due to a bug, server updates sometimes wouldn't show any confirmation when it finished the update and it wouldn't refresh the page either. Even though the update finished successfully, the update message would stay stuck at some random step such as “updating scripts":

The bug is fixed now so that Teramind will show an "update" message when the server update process completes successfully and then within a few seconds it will refresh the page automatically.

On rare occasions, you might not get a new PIN after clicking the RENEW button from the My Account > SUPPORT PIN tab. Or, the system would show an "Expired" message:

This could happen if the system date/time were configured incorrectly. We updated the mechanism so that it will check server time to verify the validity of a PIN. However, you should also ensure the date/time at the user's computer is also valid to avoid any other issues.

Some of the icons on the Daily Digest/Teramind Snapshot email would have a black background on some email clients such as Gmail:

The bug is fixed now so that the icons are displayed correctly.

Due to how international languages are encoded, you might have noticed missing characters, garbled text and missing translations in the Spanish version of the daily digest email:

The bug is fixed now so that Spanish text is properly displayed.

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

You might have noticed that when using a long message with rule actions such as Warn, Block, etc., part of the message is truncated (cut off):

The bug is fixed now.

This is related to the <Space> bug above. If a Keystrokes rule contained space (" ") either in the Text Typed or Word Types condition, the rule wouldn't work. For example, the following rule wouldn't get triggered:

The bug is fixed now.

Due to a bug, documents captured from the printer (when the CAPTURE ACTUAL DOCUMENT option on the Monitoring Settings > Printed Doc is enabled) would show a black background for files printed from TextEdit. This can be seen when choosing the View document option from the BI Reports > Printing or clicking the Document from the Monitoring > Printing report:

The bug is fixed now.

On the BI Reports > Keystrokes or Monitoring > Keystrokes report, you might have noticed the spaces were being captured as <Space> whereas it should be captured as a normal space, " ":

The bug is fixed now.

Due to a bug, if an employee’s computer was controlled via the VNC session, keyboard events wouldn't be captured by the Agent. This means that such events won’t appear on the Keystrokes reports (e.g., BI Reports > Keystrokes), Keystrokes rules wouldn't get triggered, Productivity/Time Tracking reports would show wrong active/idle time, the Online Employees widget would show the employee is idle, and the Freeze Inputs feature on the Session Player wouldn't work. The bug is fixed now.

Due to a bug, process names were missing for some daemons and console apps (e.g., the Terminal) on reports like the Monitoring > Network:

The bug is fixed so that the process names are captured now.

Due to a bug mouse pointer/cursor wasn't visible on the remote desktop control or video recordings (on the Session Player). The bug is fixed now.

The Mac Agent would crash when using the built-in screen recorder tool (Command + Shift + 5). We've noticed this on macOS Catalina (version 10.15), but other versions might be affected too:

The bug is fixed now.

The Mac Agent would crash if you switched to the Login Window (User > Login Window). Or, you tried to switch the user from the Lock screen:

The bug is fixed now.

Some versions of the Mac Agent (prior to ver 1.234) would crash when an external monitor is connected or disconnected:

The bug is fixed now.

When screen recording is enabled, sometimes the user might see a message, "Your screen is being observed" on their lock screen:

This could happen randomly when the Mac was locked, when it's about to enter the sleep state, or when the user would switch account from the fast user switching menu. Sometimes, the message would go away within a few seconds and other times it would remain on the screen.

The bug is fixed now so that the message is no longer shown.

When you hover your mouse over a task on the Tasks or History tab, a Play button is shown. Clicking the button should let you start a new task. But due to a bug, nothing would happen when you clicked the button:

The bug is fixed now so clicking the play button will let you start a new task.

In some rare cases, the Agent would crash if you visit certain websites. The problem would occur if the NetApp (the network extension) weren't able to resolve the IP addresses and DNS names. The bug is fixed now.

If you tried to use any IPv6 service or resource, it would crash the Agent. This is because currently, the Mac Agent doesn't support IPv6 network monitoring. However, to fix the crash, we have implemented measures to disregard any IPv6 connections (e.g., no such connections will show up on the Monitoring > Network Monitoring report).

The problem would arise when a Mac has more than one user account, and one of those accounts has been locked out from the Teramind Dashboard (Employees > Action menu > Lock). In this case, when user selection screen is opened, the Agent will attempt to lock the screen preventing the user from logging into another, unlocked account.

The bug is fixed now so that logging into an unlocked account is allowed even if the other account(s) are locked.

The Lock action on the Employees > Action menu would lock out a user on the Revealed Agent when they try to log in. The Lock action is supposed to work on the Hidden Agent only. The bug is fixed now.

Currently, if a user tries to log in from multiple computers on the Revealed Agent, the Agent would go into an infinite reconnect loop. For example, a user first logs in on a PC and then tries to log in on a Mac. In this situation, the following might happen:

Both of these events would repeat indefinitely. You could terminate the Agents to prevent this. However, if you forgot to log out on your second computer and don’t have access to it, that could be a problem.

We have fixed the bug and also improved how a situation like this will be handled. Now, when the user tries to log into two computers simultaneously:

1. The Agent on the first computer will show a notification and the user will be logged out:

2. The Agent on the second computer will log in successfully.