We have added the Instant Messaging report under BI Reports. This is more powerful than the previous Monitoring > Instant Messaging report because the BI report comes with enhanced reporting and analytics capabilities:

The report comes with two pre-configured tabs: Basic and Attachments. The Basic tab gives you an overall report on the IM activities while the Attachments tab shows detailed information about attachments.

In addition to the common BI data points/dimensions (e.g., Date, Employee, Department, Computer, etc.), the following IM-specific data points/dimensions are available on the report:

As part of the feature, an Instant Messages Data Source is also added which can be used on your own (cloned) reports with a Grid or a Chart widget:

The Grid widget supports all the data points/dimensions mentioned above. The Chart widget supports the following Dimensions:

The Chart widget also supports the following Measures:

You will be able to use all the features available in a BI report such as customization, advanced filters, search, export, etc. with this BI report.

We have added the Network Monitoring report under BI Reports. This is more powerful than the previous Monitoring > Network Monitoring report because the BI report comes with enhanced reporting and analytics capabilities:

The report comes with a single pre-configured Grid widget but you can also add other widgets including Chart widgets to a cloned report (custom report).

In addition to the common BI data points/dimensions (e.g., Date, Employee, Department, Computer, etc.), the following Network-specific data points/dimensions are available on the report:

As part of the feature, a Network Monitoring Data Source is also added which can be used on your own (cloned) reports with a Grid or a Chart widget:

Both the Grid widget and the Chart widget support all the data points/dimensions mentioned above.

The Chart widget also supports the following Measures:

You will be able to use all the features available in a BI report such as customization, advanced filters, search, export, etc. with this BI report.

We have added the Camera Usage report under BI Reports. This is more powerful than the previous Monitoring > Camera Usage report because the BI report comes with enhanced reporting and analytics capabilities:

The report comes with a pre-configured tab: Basic. The tab gives you an overall report on the camera usage activities.

In addition to the common BI data points/dimensions (e.g., Date, Employee, Department, Computer, etc.), the following camera usage-specific data points/dimensions are available on the report:

As part of the feature, a Camera Usage Data Source is also added which can be used on your own (cloned) reports with a Grid or a Chart widget:

The Grid widget supports all the data points/dimensions mentioned above. The Chart widget supports the following Dimensions:

The Chart widget also supports the following Measures:

You will be able to use all the features available in a BI report such as customization, advanced filters, search, export, etc. with this BI report.

We have added a new Chart widget, Geo that will let you plot geolocation coordinates on a map.

You can add a Geo widget to any custom/cloned BI report by clicking the +WIDGET button. Select Chart as the widget TYPE, Geolocation as the DATA SOURCE and then select Geo as the CHART TYPE:

Notes:

Windows events are all the activities tracked by the OS. These include Applications, System, Security, Hardware, etc. The ability to detect these events is a very powerful tool, because it allows an administrator to identify issues with the computer, discover security gaps and stop potential threats.

We have added a new rule type, Windows Log Event that will help you detect Windows events as they are logged by the OS. The rule is available on the Rules Editor under the Activity rule type:

On the Rules Editor, under the Windows log event tab, it accepts only one criterion, Event ID and the following actions: Notify, Lock Out User, Warn, Set User's Active Task, Record Video, and Command. Note that the Block action isn't supported because by the time the event is logged by Windows, the activity already happened and there's no way to block a past action!

An event ID is a special number assigned by Windows to all the events it logs. You can see the IDs on the Windows Event Viewer.

A Windows Log Event rule will allow you to detect these Windows events by their IDs. For example, the rule below will detect event ID 4738 which is triggered every time a user object is changed (for example, when a user's account is modified) and send a notification to an administrator:

This type of change might indicate malicious intent or a sign of an attacker when they have successfully reset the password of a user, etc.

As an example, here you can see an administrator is changing the account type of a Standard User and giving them the Administrator privilege:

The event can be viewed on the Windows Event Viewer:

Teramind Agent will trigger the rule as soon as the event is logged by Windows. The rule alert can be viewed on the BI Reports > Behavior Alerts report:

We have added a new Content Sharing rule, Keystrokes that will help you detect sensitive content typed by a user. The rule is available on the Rules Editor under the Content sharing rule type:

A Keystrokes Content Sharing rule works similarly to the Activity-based Keystrokes rule. Except, it also comes with the Content tab with support for the Data Content and the Predefined Classified Data definitions. This allows you to detect two sets of specialized contents easily.

Notes:

We are adding support for multiple servers/domains in Active Directory*.

The Plus + button will let you add a new tab. You can set up each tab to refer to a different server/domain and configure it independently. The Delete button will let you delete a tab.

To learn how to set up an Active Directory integration, please check out the Settings > Active Directory section on the User Guide.

We are adding support for Active Directory integration on Cloud deployment*. You will also be able to add multiple domains/servers. Once enabled, you will be able to set up the AD integration from the Settings > Active Directory tab:

To learn how to set up an Active Directory integration, please check out the Settings > Active Directory section on the User Guide.

Previously, only administrators received the Daily Digest / Daily Snapshot email report.

Now, the Department Managers can receive the report too. You can use the SEND DAILY SNAPSHOT EMAILS TO DEPARTMENT MANAGERS option under the Access to exported data section on the Settings > Security screen to enable/disable this feature:

The email looks similar to the one received by the admins except that the data is shown only for the users under the department manager's direct supervision.

We have added a new option, AGENT ATTRIBUTES TO USE FOR NOTIFICATIONS to the Settings > Alerts screen. This option will allow you to choose LDAP attributes that will be added to the rule alert notification emails:

The rule alert notification email is sent when a rule is violated that uses a Notify action. With this new option, the email will now include selected LDAP attributes in addition to the usual alert details:

Note that the rule alert notification email will include the LDAP attributes if you have an Active Directory integration set up and for only the users who have the LDAP attributes set in their profile:

We have added a new tab, License Alerts on the Settings screen which will let administrators receive email alerts when their monitored users/computers exceed the allotted number of licenses:

You will receive slightly different emails based on your license type. If you are under an endpoint-based licensing option (e.g., On-Premise deployments), then the email will list the endpoints (computers) that exceeded the license count. While a user-based licensing option (e.g., Cloud deployments) will list the users (agents). Both emails will show which logins were unsuccessful due to insufficient licenses:

Previously, Mac Agent could monitor user activities on the Apple Safari, Google Chrome and Brave browsers.

From this version, we are adding support for Mozilla Firefox. You will be able to see the user's browsing activities on the BI Reports > Applications & Websites, Monitoring > Web Pages & Applications reports, etc.:

Previously, the Mac Agent only supported activity monitoring on Safari, Chrome, Brave, and Firefox.

Now, we are adding support for the Opera browser too.

You will be able to see website activities on reports like BI Reports > Applications & Websites, Monitoring > Web Pages & Applications, etc.:

Previously, the Webpages rules only supported the Webpage Url, Request type and Query argument name criteria.

Now, we are adding support for the Webpage Title criterion. Using it you can create a rule like the following:

Here, all visits to YouTube will be blocked, unless it contains "Teramind" in the title. Meaning, the user will be able to visit the "Teramind" channel.

Previously, you couldn't monitor any locked sessions. A locked session is when the user chooses the "Lock Screen” command, a screen saver is activated, or an RDP (remote desktop session) window is minimized.

Now, we are enabling the RECORD LOCKED SESSIONS option on the Monitoring Settings > Monitoring Profile > Screen panel that will let you toggle monitoring of the locked sessions:

Notes:

In Mac Agent 1.237, we introduced support for offline screen recordings. However, until now, you could only configure the OFFLINE RECORDING'S BUFFER LENGTH (HRS) option from the Monitoring Settings > Monitoring profile > Offline Recording panel.

Now, we are adding support for the OFFLINE RECORDING BUFFER SIZE (MB) option too:

With this option, you will be able to configure how much disk space the Agent will use before it stops capturing the screen recordings in offline mode. The default value of 0 means, there will be no limit.

Note that, if you use both the OFFLINE RECORDING'S BUFFER LENGTH (HRS) and the OFFLINE RECORDING BUFFER SIZE (MB) options, the lowest value will be prioritized. For example, if you specify a 24-hour buffer length but a 10-MB buffer size, the Agent will only capture a few minutes of screen recordings (depending on the screen resolution, number of desktops/monitors, user activity, etc.). Same way, if you specified a 999999-MB buffer size but only a 1-hour buffer length, only 1 hour's worth of screen recordings will be captured even though the buffer can hold a much longer duration of recordings.

In Mac Agent 23.35.4749, we introduced support for File Transfers monitoring. However, you could only monitor the Users folder.

Now, we are enabling the TRACK EXTERNAL DRIVES option on the Monitoring Settings > Monitoring Profile > File Transfers panel that will let you toggle file transfers on external drives:

You will be able to view the file transfer activities on reports like the BI Reports > File Events, Monitoring > File Transfers and Employees > Employee's Details > File Transfers tab:

Many organizations and individuals use SOCKS proxy for security, compatibility, performance, or anonymity purposes. Previously, the Agent couldn't connect to its server if you were using any SOCKS proxy.

From this version, we are adding support for SOCKS proxy.

You can configure the proxy settings from the agent.conf file (usually located in your Agent installation folder, e.g., Macintosh HD > usr > local > teramind > agent > etc):

Here's an explanation of each parameter:

For more information about these and other parameters, please see the Agent Installation/Configuration Parameters (Mac) section on the Agent Installation article.

We have introduced a new Agent Installation/Configuration Parameter, network-exclude-bundles that will let you exclude application bundles from the network driver. You can add the parameter to the agent.conf file to exclude applications by their bundle IDs. For example:

You can add multiple bundle IDs separated by commas (no spaces), for example:

Notes:

You are presented with a few options when trying to delete a time/screen record from the Time Tracking > Time Records, Time Tracking > Time Cards, Monitoring > Screen Snapshots reports, etc., Out of these options, the "Remove time and screens records" option permanently removes the screen records. This is why we are adding an additional warning dialogue box to ensure that you do not accidentally delete the record:

Previously, when you filtered the BI Reports > Login Sessions report by date, it would only show sessions that started at the selected date. If you had any login sessions spanning multiple dates, the report wouldn't show those sessions. For example, if you filtered the report for October 2 and you had a session that started on October 1 and ended on October 3, the report would ignore the session.

We made some changes to the filtering mechanism so that sessions that have any overlap with the filtered data range will now be shown on the report.

We have added support for the Common Filters (e.g., Computer, Department, Employee and Task) on the Filter panel of BI Reports > Audit report:

We have added the Position (Title) dimension to the Chart widgets. It can be used with DIMENSION #1 or DIMENSION #2 on the widget's settings:

Previously, if you had any Widget Filters applied to a widget and then used any Global Filters, the widget wouldn't accept the Global Filters and continue to use only the Widget Filters resulting in unexpected results:

We have improved the filtering mechanism so that any Global Filters will be applied (mixed) with the Widget Filters:

In the above example:

As can be seen, both types of filters were combined to show the data on the report.

Previously, if you entered an invalid passphrase when trying to decrypt the keystrokes or screen recordings on reports like the BI Reports > Keystrokes, Monitoring > Keystrokes, Monitoring > Screen Snapshots, Session Player, etc. the Dashboard wouldn't show any error.

Now, if you enter an empty/invalid passphrase, it will show an error message, "Decryption failed":

Previously, if end-to-end encryption was enabled, the Keystroke Log widget on the Dashboard would just show empty text for the keystrokes. This could lead to confusion (e.g., you might think the user just entered the Space character or that the keystrokes weren't captured for some reason).

Now it will show the "<Encrypted>" message making it clear that the keystrokes are encrypted:

Now, whenever you try to delete employee(s) either from the Employees or the Employees > Employee's Details screen, you will see the Confirm dialogue box:

You will have to authenticate and confirm before the delete operation will take place.

Note that, the confirmation method will depend on what option is set on the CONFIRMATION METHOD FOR DASHBOARD CHANGES setting located under the Dashboard authentication section on the Settings > Security screen:

Previously, there were some outdated and duplicate items on the SHOW URLS filter on the System > System Log report. Some filters were displayed that shouldn't apply to the instance type (e.g., options shown for Cloud deployments that were only applicable to the On-Premise deployments).

We have cleaned up the filter list so that only relevant filters will be shown:

A Decrypt button is shown on the Session Player if end-to-end encryption is enabled.

Previously, this button would still be visible even after the user decrypted the video:

Now, it will be hidden if the video is successfully decrypted.

Currently, it takes several seconds for the Session Player to load past recordings (History Mode). It also causes some delays when seeking through the timeline.

We made some improvements to speed up the process.

We introduced conditional audio recording (record microphone input only on select apps) in Windows Agent 12.0. However, a user could configure the RDP Client in such as way that any audio playback or microphone input on the RDP Server would pass through the local, Client computer.

Before this feature, such audio input wouldn't be captured by the Agent.

Now, we are improving the feature to support conditional audio recording in a remote session (RDP) such as Windows Remote Desktop Connection. For example, you can now capture meeting audio on an application like Zoom that's running on a remote computer:

Any captured audio can then be played back on the Teramind Session Player.

Previously, a user could enter invalid regular expressions in the DO NOT MONITOR THESE LOCATIONS (REGEX) file on the Monitoring Settings > Monitoring Profile > File Transfers window causing unexpected results.

We have now added regex validation checks so that when an invalid value is entered in the field, it will show an error, "Invalid regex expression" and prevent you from saving the settings:

Previously, the ENABLE MONITORING FOR NEW AGENTS BY DEFAULT option under the Default settings section on the Settings > Agent defaults screen would allow you to toggle monitoring of newly added users and computers.

Now, we have separated it into two separate options. The existing ENABLE MONITORING FOR NEW AGENTS BY DEFAULT option will now toggle the monitoring of new users while a new option, ENABLE MONITORING FOR NEW COMPUTERS BY DEFAULT will toggle the monitoring of new computers:

In Platform Release 643, we added a remove dialogue box that would be shown when you tried to delete time and screen recordings from the Monitoring > Screen Snapshots, Time Tracking > Time Records reports, etc.

We have now added an option, DEFAULT ACTION FOR SCREEN RECORDS DELETION under the Screen records management section on the Settings > Agent defaults screen that will let you set the default selected option for the delete dialogue box:

Previously, whenever a new Agent version was available, a UPDATE AVAILABLE! CLICK TO APPLY NOW button would be shown on the Settings > Autoupdate screen. You could press the button to roll out the remote update. However, pressing the button would also make it disappear and there would be no visual feedback about the update status.

Now, when you press the update button, it will show a note at the top of the screen and change the button to display a message like, "AUTOMATIC UPDATE IS SET FOR VERSION xx.xx.xxxx":

We have made some improvements, so that the user can no longer enter an invalid value (e.g., length > 5,000 bytes) in the MAXIMUM EMAIL BODY LENGTH field located under the Access to exported data section of the the Settings > Security screen.

Previously, you could enter an invalid value and the Dashboard would show that the setting was successfully saved (even though it wasn't!).

Now, it will show a red border around the field and deactivate the SAVE button if you enter an invalid value:

The User can login to Teramind Dashboard option on the User Menu > My Profile > ACCOUNT INFO tab will now be hidden from the currently logged-in admin:

Additionally, if a currently logged-in admin tries to turn off their own dashboard access via the /tm-api/agent call (with the 140125 On-Premise or 80 Cloud flags), they will now get a "400 Bad request" status with the error message, "EMPLOYEES.ERROR_CANT_DISALLOW_SELF_LOGIN":

Without these measures, an admin could accidentally lock themselves out from accessing their Dashboard. Another admin would then have to re-enable their access. And, if there was only a single admin, they would be out of luck.

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.

In Platform Release 643, we introduced a few options that would allow you to delete time and screen records from the Monitoring > Screen Snapshots, Time Tracking > Time Records reports, etc:

However, the delete operation simply marked the screen recordings in the database and hid them from the Dashboard without actually removing them.

We made some changes so that the screen recordings will now be permanently removed from the database(s), local storage, and any external storage (e.g., S3 buckets) - freeing up space and ensuring better privacy/security.

We have made some changes to how the daily digest/snapshot emails are processed. The changes will reduce database load spikes and overall improve server performance when processing a large volume of emails.

We have made some changes so that the OCR Miner will now use the full CPU processing power (cores) for servers with more than 6 cores resulting in faster processing of the OCR data.

Previously, there was no email validation mechanism on the password reset form (the Forgot your password? option on the dashboard Login screen). A user could leave the email field empty or enter an invalid email address and still get the "We've sent you a link..." message.

We made improvements so that the form will now validate the email address and show error messages if a blank or invalid email address is entered:

To better reflect the purpose of the feature, we renamed the Onboarding Wizard menu to Initial Installation:

Previously, temporary databases were created for each offline session and then removed when the Agent finished uploading the data to the server once the connection was restored. This could cause performance penalties and integrity issues.

We have updated the offline storage mechanism so that now only one offline database will be maintained for each user. The database will no longer be deleted, instead, it will be updated on each successful upload. This will improve both performance and data integrity.

In rare situations, the time bars on the Time Tracking > Time Cards report would be shown incorrectly. In the example below, the time bar was shifted by two hours from where it should have been:

The bug is fixed now.

On reports like Screen Snapshots, Task Costs, Time Cards, Time Cards, etc., a dialogue box is shown when deleting entries.

However, due to a bug, this dialogue box would show incorrect/irrelevant options when deleting manually added time entries:

These options aren't relevant since manually added time entries do not have any screen recordings.

The bug is fixed now so that the dialogue box will just show a simple confirmation dialogue without any of the irrelevant options:

Additionally, the delete option will no longer be displayed if the logged-in user does not have the Edit work hours access control policy enabled:

Due to a bug, the BI Reports > Geolocations report would report multiple locations if a user connected to the internet through their Wi-Fi even though the user didn't change their geographical position:

The bug is fixed now.

Due to a bug, one or more chart widgets on any of the BI Reports would show the loading icon even after the chart data was loaded. The widget would also remain inactive/faded:

The bug is fixed now.

Due to a bug, if you grouped rows on a Grid widget by Date on the BI Reports > Login Sessions and then tried to expand a row, the widget would display a "Something went wrong" error:

The bug is fixed now.

Due to a bug, if you tried to expand a row group on the BI Reports > All Events report, the grid widget would display a "Something went wrong" message and an error code 504 (Gateway Time-out) could be seen in the browser's console log:

The bug is fixed now.

Due to a bug, you might see a few empty options in the Computer and Task filter lists under the Common Filters on the BI Reports > Filter panel:

The bug is fixed now so that the empty items will no longer be shown on the filter lists.

Due to a bug, when a user tried to create or edit a Heatmap Chart widget, they would see a "Something went wrong" message and the browser's console log would show a 500 error code (Internal server error):

The bug seemed to occur when multiple Data Sources were selected. Usually, you should be able to select only one data source with the Heatmap Chart.

The bug is fixed now.

Due to a bug, any email sent from the Outlook Web would generate duplicate entries on the BI Reports > Emails, Monitoring > Emailing, etc.:

However, the attachment column would only be shown for the first entry.

The bug is fixed now.

Due to some recent changes introduced by WebEx, the Agent had been unable to capture online meeting activities on WebEx Web. As a result, no incoming or outgoing meetings on WebEx Web would be displayed on the Monitoring > Online Meetings report.

The bug is fixed now.

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 seem to be affected but there might be other domains too:

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

Due to some recent changes introduced by RingCentral, the Agent had been unable to capture online meeting activities on RingCentral. As a result, no incoming or outgoing meetings on RingCentral would be displayed on the Monitoring > Online Meetings report.

The bug seems to affect Agent version 6.1 but other versions might be affected too.

The bug is fixed now.

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.

Due to a bug in the Agent's IM parser module, sometimes it would cause the server to crash if a user engaged in conversations with a large group (e.g., about 50 or more participants) on WhatsApp Web. As a result, the Agent wouldn't be able to connect to the server and the group conversation wouldn't show up on the Monitoring > Instant Messaging report.

The bug is fixed now.

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.

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.

Due to a bug, sometimes the Agent would fail to capture IM activities for Microsoft Teams. As a result, you wouldn't see these activities on reports like Monitoring > Instant Messaging. For the same reason, IM-based rules involving MS Teams might also fail to trigger.

This could occur when MS Teams used some special domains or web sockets to initiate the communications.

The bug is fixed now.

Due to a bug, if you tried to search for a user that belonged to a department in the EXPORT TO EMAIL(S) field on the Report Settings > DAILY EXPORT tab, the browser console would throw an error, "RangeError: Maximum call stack size exceeded":

This would affect all the Monitoring and BI reports.

The bug is fixed now.

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:

When you tried to download a report from the Monitoring > OCR report that had multiple pages (e.g., more than 1,000 rows), the report would export up to the first 1,000 rows only. Both the CSV and PDF exports would be affected:

The bug is fixed now.

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.

Due to a bug, sometimes a Files-based rule with the RDP File Transfer condition like the one below would fail to detect any file transfer activity between an RDP Server (computer hosting the Remote Desktop) and an RDP Client (computer accessing the Remote Desktop):

The bug is fixed now.

Due to a bug, an Emails rule (Activity or Content Sharing rule) with a Has attachments criterion like the one below wouldn't get triggered on Outlook Web or Outlook Desktop:

The bug is fixed now.

Due to a bug, Files Content Rules would ignore the File operation condition causing the rules to get triggered for any file operation. For example, the rule below would incorrectly block all file operations such as Copy, Access, Write, Upload, Rename, Delete, etc. instead of just blocking the Copy operation:

The bug is fixed now.

If you had a rule like the one below, it would crash the Windows Calculator app when the rule was triggered:

In the above example, when you tried to copy a set of numbers that looked like a credit card number from an app (say, Microsoft Excel) and pasted it into the Calculator app, it would crash. No alert would appear on the BI Reports > Behavior Alerts or Behavior > Alerts reports either.

The issue seemed to affect Agent version 21.0, but other versions might be affected too.

The bug is fixed now.

Due to a bug, some customers were unable to turn behavior rules on/off from the Behavior > Policies screen. The rule wouldn't toggle and an "Error occurred" message would be shown:

The bug is fixed now.

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.

Due to a bug, if you tried to add tags to a rule, it would show an error, "Invalid arguments: tags[0] should be number":

The bug is fixed now.

Due to a bug, some customers on Cloud instances were experiencing some issues when playing session recordings on the Session Player. Notably, the time display would be out of sync with the user's local time and sometimes the video would show some glitches:

The bug is fixed now.

Due to a bug, there would be intermittent issues with the Session Player not loading any video when launched from the Dashboard. The player would show a black screen. However, it would start playing the video if the user navigated elsewhere on the Dashboard.

The bug is fixed now.

When the user locks their computer or minimizes the RDP window the Session Player should show a "SESSION LOCKED" message and when the RDP connection is lost, it should show a "Disconnected" message:

However, due to a bug, the Session Player would just show a blank/black screen or a frozen frame instead.

The bug is fixed now so that the right message will be displayed on the Session Player.

Due to a bug in how time zones are handled, the Session Player would skip to the previous day if you enter a date (bottom-right corner):

The bug is fixed now.

Due to a bug, the Enter key wouldn't work when you tried to enter a date/time in the Date/Time input field of the Session Player. Instead, you'd have to click on the player or press the Tab key:

The bug is fixed now.

Due to a bug, the Language field on the Employees > New Employee > Account Info tab would show empty when adding a new employee.

The bug is fixed now so that the Instance's Default option will be selected by default:

Due to a bug, when creating a new employee from the Employees screen, the MONITORING OPTIONS tab wouldn't show any of the monitoring options and instead showed a loading icon:

The bug is fixed now.

Due to a bug, when creating a new employee from the Employees screen, with a Custom profile (i.e. changing the options on the MONITORING OPTIONS tab) would show a "Internal Server Error" message:

The bug is fixed now.

Due to a bug, when bulk editing a large number of employees (e.g., more than 50), the selection filters (e.g., Status, Role, Department) on the Employees report wouldn't work as expected. It would include employees who were not selected. For example, if you tried to edit all users except the ones with the "Administrator" role, the administrators would be included too:

The bug is fixed now.

If a user had the Can see own online presence option disabled on their monitoring profile (the ACCOUNT INFO tab on Employees > Employee's Details > Edit Info or User Menu > My Profile screen) they shouldn't be able to view their online presence:

However, due to a bug, the option wouldn't work and users who had the option disabled could still see their online presence. The bug is fixed now.

Due to a bug, the EXCLUDE PROCESSES FROM FILE DRIVER and EXCLUDE PROCESSES FROM NETWORK DRIVER options would be missing from the user profile (the Settings for monitoring: Advanced window on Employees > Employee's Details > Edit Info and User Menu > My Profile):

The bug is fixed now so the options should be displayed (if available*).

When you change any monitoring settings from a user profile (Employees > Employee's Details > Edit Info or User Menu > My Profile), a Custom monitoring profile is automatically created for the user. Any changes are then saved in this custom profile instead of the Default settings profile or the previously selected general/common profile:

However, due to a bug, the custom profile wouldn't be created when you changed any of the Advanced settings. Instead, the changes would be saved to the previously selected default/general profile.

The bug is fixed now so that any changes to the Advanced settings will also be saved in the Custom profile.

Due to a bug, if you turned on Geolocation monitoring on a user's Custom profile (Employees > Employee's Details > Edit Info or User Menu > My Profile), it wouldn't turn on geolocation tracking:

The bug is fixed now.

Due to a bug, when you selected the "All" option from the MONITOR WHEN THESE APPLICATIONS USE MICROPHONE field on an employee's monitoring settings (Employees > Employee's Details > Edit Info > Monitoring Options > Audio or User Menu > My Profile > Monitoring Options > Audio), it wouldn't clear any existing apps from the field:

The bug is fixed now so that when the "All" option is selected, it will clear other apps from the field.

Due to a bug, if you left the OCR Languages field on an employee's monitoring settings ((Employees > Employee's Details > Edit Info > Monitoring Options > OCR or User Menu > My Profile > Monitoring Options > OCR), it wouldn't show any error message. Only after pressing the APPLY CHANGES button twice, it would show an error.

The bug is fixed now so that leaving the OCR Languages field empty will show an error immediately after pressing the first APPLY CHANGES button:

Due to a bug, if you searched for a user from the Employees screen using the Search option, it would return a "No matches found" result even though the user existed:

The bug is fixed now.

Due to a bug, some customers would just see a message, "Loading data..." when trying to access the Configure > Departments screen and the page would never load:

The bug is fixed now.

Due to a bug, privileged user(s) from one policy would have access to targets from another policy. For example, suppose you created two policies from the Configure > Access Control screen like the ones below:

In this case, Manager A and Manager B would be able to access both User 1 and User 2. Even though Manager A was supposed to have access to User 1 only and Manager B to User 2 only.

The bug is fixed now.

Some log items on the System > System Log report have a Click to view details link that should show additional details related to the item/activity. However, due to a bug, when you clicked this link, it would pop up an empty window.

The bug is fixed now so you will be able to see the details as expected:

Due to a bug, details for the Session Playback activities (e.g., Live or History playback) wouldn't be displayed on the System > System Log report. Instead, a Click here to view details link would be displayed in the Details column. However, clicking it would pop up just an empty window.

The bug is fixed now so the Details column will now display the correct details for the Session Player activities:

Due to a bug, the Enable Monitoring and Disable Monitoring filters on the System > Session Log would fail to show the associated action(s).

The bug is fixed now so the filters will work as expected:

Due to a bug, websites monitoring settings (Monitoring Settings > Monitoring Profile > Websites) that accept a URL (for example, MONITOR ONLY THESE WEBSITES, DON'T MONITOR WEB TRAFFIC FOR THESE WEBSITES, SUSPEND MONITORING WHEN THESE WEBSITES ARE VISITED, etc.) wouldn't work for some websites/URLs that contained special characters (for example, #).

The bug is fixed now so that website addresses/URLs with special characters will be detected properly and the monitoring settings will work as expected.

Due to a bug, the MONITOR KEYSTROKES FOR PASSWORD FIELDS option (Monitoring Settings > Monitoring Profile > Websites) might get ignored when certain applications (e.g., MS Access, inora.exe, Data Maintenance.exe, etc.) were opened. As a result, even if you turned off the MONITOR KEYSTROKES FOR PASSWORD FIELDS option, password fields on websites might get captured. Additionally, other, unusual behavior might occur in those apps (e.g., cells getting duplicated).

The bug is fixed now.

When SUSPEND MONITORING WHEN THESE WEBSITES ARE VISITED option is used on the Monitoring Settings > Websites, instead of showing the actual activity (e.g., the actual web page visited by a user), the activity reports should the application/browser used.

However, due to a bug, nothing is shown in the Current Activity column on the Dashboard > ONLINE EMPLOYEES widget. Here's the actual result vs. the expected result:

And, on the Employees > Activity Log, the activity wouldn't show up at all. Here's the actual result vs. the expected result:

The bug is fixed so the activities will be displayed according to the expected results.

Due to a bug, websites monitoring settings (Monitoring Settings > Monitoring Profile > Websites) that accept a URL (for example, MONITOR ONLY THESE WEBSITES, DON'T MONITOR WEB TRAFFIC FOR THESE WEBSITES, SUSPEND MONITORING WHEN THESE WEBSITES ARE VISITED, etc.) wouldn't work for some websites/URLs that contained special characters (for example, #).

The bug is fixed now so that website addresses/URLs with special characters will be detected properly and the monitoring settings will work as expected.

Due to a bug, a user's geolocation would be tracked while the user had their computer set to the Lock mode and the RECORD LOCKED SESSIONS option on the Monitoring Settings > Monitoring Profile > Screen was disabled:

The bug is fixed now.

Due to a bug, the installation instructions email (sent when you choose the E-MAIL INSTRUCTIONS TO ME option from the Agent Download screen) would contain incorrect links for downloading/installing the Agent:

The bug is fixed now.

Due to a bug in the network interception mechanism, the Revealed Agent would continue to capture IM activities even when the user stopped the Agent (by pressing the "Stop" button):

The bug seems to affect Agent versions 5.0 and 4.1 but other versions might be affected too.

The bug is fixed now so that the Revealed Agent will not monitor any IM conversations if it's stopped.

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

The Agent would crash without showing any error message during the 4th step.

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.

Due to a bug, the user wouldn't be able to start any task on the Revealed/Visible Agent after the Mac woke up from sleep. After the wake-up, the Agent would reconnect to the server as expected and continue to track the last task, but the UI wouldn't show any task in progress ("Not active" status) making the user believe they weren't active. Additionally, the Agent wouldn't allow the user to start a task by either using the Play icon or the Start button.

The bug seems to affect Agent version 23.37.4752 but other versions might be affected too.

The bug is fixed now.

Due to a bug, newly created users were unable to log into the Revealed Agent soon after they were added. They would see a message, "Login failed: invalid username or password":

After some delay (about an hour or so), the login would work normally.

The bug is fixed now so that new users will be activated as soon as they are added without causing any delay in the login process.

Due to a bug, if you tried to uninstall a Protected Agent, it wouldn't work. The Agent would remain online.

The Agent Removal Tool might show a message that "Teramind Agent was successfully removed". However, the Agent installation folder would remain with several folders/files still inside:

The bug is fixed now so the Protected Agent would be removed as expected.

By default, the Hidden/Stealth Agent uses \ProgramData\{4CEC2908-5CE4-48F0-A717-8FC833D8017A} as its default installation folder.

However, the TMROOTDIR installation parameter can be used to change this default location. For example, if you used the command below, all the Agent components should be placed inside the myagent folder:

But, due to a bug, the installer would create both the default folder and the myagent folder. It would then put some resources in the default folder and the rest in the myagent folder:

The issue seemed to affect Agent version 16.0, but other versions might be affected too.

The bug is fixed now so the Agent will place its resources only in the specified folder.

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.

Due to a bug, user activity data might not be captured when working in offline mode using a Remote Desktop Connection. This could happen if the Agent went offline after the RDP window was minimized or restored.

The bug is fixed so the Agent will capture RDP activities as expected, even when offline.

Due to a bug, the Agent would crash if a user tried to upload a file to SharePoint or OneDrive. Windows Event Log would show a Fatal Error: EXCEPTION_ACCESS_VIOLATION_READ / 0x48 message. This could happen if any of the Instant Messaging, File Transfers or Network monitoring options were enabled.

The bug seems to affect Windows Agents 13.0 to 19.0. But other versions might be affected too.

The bug is fixed now.

Due to a bug, you might have encountered an error when saving files to a network (shared) folder. The error message would read something like, "... was modified by another user since you opened the file. To prevent losing your changes, please save the file with a new name...":

The bug is fixed now.

Due to a bug, the Revealed Agent would sometimes close automatically without any message. The user might not notice this if the Agent was minimized or hidden behind another window causing the user to lose work time. Additionally, the bug might also cause network slowdown in some cases.

The bug seems to affect Windows Agent 19.0 but other versions might be affected too.

The bug is fixed now.

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.

Due to a bug, the Agent would have issues connecting to the server if you used the MAX UPLOAD BANDWIDTH and/or TIMEFRAME TO UPLOAD COLLECTED DATA on the Monitoring Settings > Monitoring Profile > Advanced panel:

The bug is fixed now.

Due to a bug, when updating the Hidden/Stealth Agent, Windows would sometimes restart/reboot the computer without any notice. You might see a message on the Windows Event Log with the reason 0x80040002 Application: Installation (Planned):

The bug is fixed so that the Agent updater will not reboot the computer.

Due to a bug, if you used the SSO button to log into the Dashboard, a warning message, "You are about to follow an external link" would pop up. If you pressed the CONTINUE button, it would redirect you to the SSO link:

The bug is fixed now so that you will be immediately logged in (if you are already logged into the SSO provider's system) or taken to the SSO authentication page without showing the warning message.

Due to a bug, when using the guided tour (EXPLAIN THIS PAGE feature on the Dashboard), it would show a 500 error code (Internal Server Error) in the browser's console:

The bugs seem to occur when using a read-only agent (e.g., the Teramind Demo Dashboard).

The bug is fixed now.

In Platform Release 643, we introduced some changes in how the OCR transactions are processed to improve performance. However, this introduced a bug that would cause the OCR server to skip OCR records in some rare situations such as when the server crashed/rebooted.

The bug is fixed now.

Due to a bug, you might see a long SESSION MINING DELAY on the Settings > OCR screen:

The bug is fixed now.

Due to a bug, it was possible to create a new monitoring profile via the /tm-api/monitoring-settings POST request with a null or empty name field and an empty/invalid (for example, longer than 255 characters) description field resulting in a blank profile on the Settings > Monitoring Settings screen:

The bug is fixed now so that when an invalid name and/or description field is passed, the API will return a "422 Unpossessable Entity" status and a description of the error(s):

Due to a bug, the Daily Digest email/Snapshot report would show incorrect values for the Emails Received / Sent section:

The values wouldn't match the BI Reports > Emails or the Monitoring > Emailing reports. The email report would only show values for the displayed employees instead of the total received/sent count.

The bug is fixed now.

We are adding support for the DON'T MONITOR WEB TRAFFIC FOR THESE IPS option on the Monitoring Settings > Monitoring profile > Websites panel:

You can use this option to exclude network traffic inspection for any IP address(es).

Here are some additional notes about this option:

Due to a bug, if you enabled Monitoring Settings > Monitoring Profile > File Transfers, and there were multiple users, the Revealed Agent would crash:

The bug is fixed now.

Due to a bug, the Mac Agent installation link on the Cloud dashboard was missing the security token parameter (the t variable in the URL). The bug is fixed now so that the correct link will be displayed:

Depending on the scenario, there were several issues identified when installing, uninstalling or reinstalling the Agent:

The bugs seem to affect Agent version 1.234 but other versions might be affected too.

The bugs are fixed now.

In some situations, the Agent might take a long time to detect that it was disconnected from the server and needed to reconnect. For example, after waking up from sleep, VPN connection reset or other network disruptions.

During this period, the Revealed/Visible Agent would continue to run the task timer, but it wouldn't be recorded on the Agent's History tab or on the web Dashboard. As a result, the user would lose time for that period:

On the other hand, the Silent/Hidden Agent would treat this as an offline session and active offline recording (if Offline Recording was enabled).

After the Agent recognized it was disconnected, it would reconnect and work as expected.

The bug seems to affect Agent versions 1.227, 1.239, 1.240 and 1.241.

The bug is fixed now so the Agent should try to reconnect as soon as it detects that it's disconnected from the server without losing any task time.

If you started a new task (that was never started during the current day) and try to view the task history soon after that (i.e., within 30 seconds or so), then the task will not be shown on the History tab:

This could happen due to a server lag. The Agent would request task history from the server and in some situations, there might be a delay due to a slow server/network connection.

We have made improvements so that the current task will immediately show up on the History tab.

Due to a bug, the Hidden/Stealth Agent would crash if two or more users were using the Agent and one of them went offline. This could happen in the following scenario:

The bug would be caused due to a synchronization issue with the offline recording feature. It's now fixed so that user switching and offline mode wouldn't cause the Agent to crash anymore.

If any Shared List was used, for example, in Monitoring Settings or Behavior Rules, the Agent would crash when switching between user accounts:

The bug seems to affect Agent version 1.244 but other versions might be affected too. It's fixed now.

Note: A similar bug was fixed on Agent version 1.244 (affecting version 242), but the root cause was different.

Due to a bug, the Hidden/Stealth Agent would collect offline data even if monitoring was disabled for a user on the Dashboard:

This would usually happen if you disabled the monitoring when the user was online/active. After restarting the computer or relaunching the Agent, the problem would go away.

The bug is fixed now.

Due to a bug, the NetApp (Teramind network extension) would ask for permission during the uninstallation of the Agent, even though network monitoring was disabled and network permission was never enabled on the computer:

We made improvements so that if network permission is disabled, the Agent uninstaller will not ask for permission to remove the Agent.

The Agent supports a few optional installation parameters. However, due to a bug, if none of the installation parameters were used (or, there is no agent.conf file, or the config.conf file is empty) the uninstallation process would get stuck at the delete_network_permissions stage:

The bug is fixed now.

Due to a bug, an inactive user would be shown as Online (e.g., a green dot next to the user's profile picture) on the Dashboard after the Agent reconnects from a network disconnect event:

After a few moments, the status would change to Idle (e.g., a red icon next to the user's profile picture) and the time would be counted towards the user's idle time. This would happen when there were multiple users on a computer.

The bug is fixed now.

Due to some changes introduced in macOS Sonoma (macOS 14), it would show a pop-up message, "System Monitoring is capturing your screen" on the menu bar:

The Agent is updated so this message will not be displayed anymore.

Usually, near the end of the installation process, the Agent asks for the Accessibility and Screen Recording Permissions. After granting the permissions, the user can click the Quit & Reopen button on the settings dialogue box to restart the Agent:

However, due to a bug, the Agent wouldn't restart and the user was forced to manually restart the Agent by using a command like: sudo killall "System Monitoring".

The bug is fixed now so that the Agent will restart after pressing the Quit & Reopen button.

Due to a bug, the user would be unable to stitch tasks after the first time on the Revealed/Visible Agent. For example, when a task was in progress and the user clicked the small Play icon to start another task, the currently running task would stop (as expected) but it wouldn't start the new task (bug). The Start button wouldn't work either:

The bug seems to affect Agent version 23.37.4752 but other versions might be affected too.

is fixed now so that when the Play button next to a task is clicked, it will stop the currently running task and start the new task. The Start button will also work now.

Due to a bug, if you updated the macOS, the Hidden/Silent Agent would be shown as "Teramind Inc." on the Allow in the Background list under System Settings > General > Login Items:

This would make it possible for a user to detect the running of the Agent mitigating the benefits of the stealth mode.

The bug is fixed so that the Agent will no longer be displayed on the Allow in the Background list.