“OMNI” stands for ‘all’ or ‘universal’. It’s Teramind's AI/ML module that’s currently in public beta.

OMNI provides a snapshot view of the most critical insights and incidents about your organization in a social media-like (think Facebook newsfeed) interface with scrolling video feeds.

It’s an oversight tool that will help business owners and managers keep an eye on the organization’s productivity and security without digging through detailed reports. It’s also a powerful investigation tool that can be leveraged by your analysts for identifying threats, detect anomalies, flag frauds, etc., and conduct forensic investigations, and case management for data leak incidents.

We have added a new Locations sub-menu under the Configure menu. The Locations screen will allow you to create your custom locations. Teramind will then match a user’s geolocation and network information (e.g., Wi-Fi names) to determine if the user is in a particular location.

As part of this feature, a new “Office” Dimension is added to the BI reports. It can be used with any Chart or Grid widget. The Office location will show if a user is in any of the locations created under the Configure > Locations screen. If not, they will be shown as "Out-of-office". For example, here the Application & Websites report is shown with the Office column on the grid widget:

The Online Employees Dashboard widget is also updated to show location information:

We have added support for Google Meet monitoring. You will be able to select it from the Monitoring Settings > Online Meetings window and view the meeting activities on the Monitoring > Online Meetings report:

We have added support for WeChat monitoring. You will be able to select it from the Monitoring Settings > Instant Messaging window and view the IM activities on the BI > Instant Messages and Monitoring > Instant Messaging reports:

You will also be able to select it on the IM-based behavior rules.

We have added an option to adjust the risk severity of all rules. It can be found below the General tab on the Rules Editor:

The severity is also shown on the Behavior > Policy screen:

We have added a new filter, "LDAP Groups" to the Employees and Computers screen.

This will help you filter the report by LDAP groups if you have an Active Directory integration set up.

Previously, you could only monitor keystrokes in password fields on the browsers.

Now, you will be able to monitor password fields in other applications too.

A new option, MONITOR KEYSTROKES FOR PASSWORD FIELDS IN DESKTOP APPS is added to the Monitoring Settings > Applications window that will let you toggle this feature:

We have added a TROUBLESHOOTING button to the Computers > Computer's Details screen:

The remote troubleshooting feature will allow you and Teramind Support Engineers to conduct troubleshooting of a computer and collect diagnostics logs. This feature will let you run troubleshooting from the dashboard instead of accessing the computer locally or through a separate remote session (such as TeamViewer). It works without interrupting the Agent or revealing the troubleshooting to the user:

We have migrated our support system to Intercom. This will let you have a better support experience by giving you direct access to our support agents and Knowledge Base content powered by AI.

Cloud customers will be able to access the support by clicking the T icon near the bottom-right corner of the Teramind Dashboard. On-Premise customer will be able to access the same icon from their Self-Serve portal. The support chat can also be accessed from the Teramind website and Knowledge Base.

We have enabled Mac support for several File Transfers monitoring options.

Under Monitoring Settings > Monitoring Profile:

1. You can now turn File Transfers monitoring on/off by using the YES/NO toggle switch.

Under Monitoring Settings > Monitoring Profile > File Transfers > BASIC SETTINGS tab:

2. FILE TYPES TO TRACK: You can select which file types to track. For example, TXT, DOC(S), etc.

3. FILE EXTENSIONS LIST TO TRACK: If the files you want to track aren't available under the FILE TYPES TO TRACK option, you can manually enter their extensions in this field. For example, pkg, log, etc.

4. DO NOT MONITOR THESE LOCATIONS: You can exclude certain location(s) such as a folder from monitoring. For example, ~/Downloads, ~/Desktop, etc.

Under Monitoring Settings > Monitoring Profile > File Transfers > ADDITIONAL SETTINGS tab:

5. TRACK THE FOLLOWING OPERATIONS: You can track only certain file operations such as Copy, Rename, etc.

6. Monitoring Schedule: You can specify the date and time of the monitoring schedule.

We have added support for the Time Idle (min) criterion in Applications rules:

This will let you detect how long the user has been idle in certain application(s).

You can use the Application Name and Application Caption with this criterion and the following actions: Notify, Block, and Warn.

We have added support for the Total Time Active (min) criterion in Applications rules:

This will let you detect how long the user has been active for the entire day* in certain application(s).

You can use the Application Name and Application Caption with this criterion and the following actions: Notify, Block, and Warn.

*Total active time measures active time accumulated in a day. The time will reset the next day.

We have added support for the Total Time Idle (min) criterion in Applications rules:

This will let you detect how long the user has been idle for the entire day* in certain application(s).

You can use the Application Name and Application Caption with this criterion and the following actions: Notify, Block, and Warn.

*Total idle time measures idle time accumulated in a day. The time will reset the next day.

We have added support for the Time Focused (min) criterion in Applications rules:

This will let you detect how long the user has been focused* on certain application(s).

You can use the Application Name and Application Caption with this criterion and the following actions: Notify, Block, and Warn.

*Time Focused = Time Active + Time Idle. It detects if the user stays on an application for the specified duration. It doesn’t matter whether the user was active (e.g., keyboard/mouse is used) or idle (no keyboard/mouse activity); as long as they stayed on the app without switching to other apps, the condition will be triggered.

We have added support for the Total Time Focused (min) criterion in Applications rules:

This criterion is similar to the Time Focused criterion but detects the total time focused in a day*.

You can use the Application Name and Application Caption with this criterion and the following actions: Notify, Block, and Warn.

*Total focus time measures focus time accumulated in a day. The time will reset the next day.

We have added support for the Time Active (min) and Time Idle (min) criteria in Webpages rules:

This will let you detect how long the user has been active or idle on certain webpage(s).

You can use the Webpage URL and Webpage Title with these criteria and the following actions: Notify, Block, and Warn.

Previously, Files Transfers monitoring would only work for the Users folder, external drives, and Cloud drives (OneDrive).

Now, we have added support for network drives (SMB) too. All the supported file operations, e.g., access, copy, rename, delete, etc. will be captured.

The network drives will appear as "Volumes" on reports like the BI Report > File Events, Monitoring > File Transfers, etc.:

The Files behavior rules will also work for these drives.

Many organizations and individuals use HTTP proxy to detect and block suspicious traffic that can be an intrusion, virus, or malware. It also protects corporate web servers from external cyberattacks.

Previously, the Agent couldn't connect to its server if you were using any HTTP proxy.

From this version, we have added support for the HTTP proxy. You can configure the proxy in two ways:

You can configure the proxy using the Agent Installation Parameters. To do so, you will need to rename the default Agent package file to include the proxy parameters. For example:

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). For example:

Here's an explanation of each parameter with their equivalent config file parameter:

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

In Mac Agent 23.37.4752, we introduced support for the SOCKS proxy. But you could configure them through the Agent Configuration file (agent.conf) only.

Now, you will be able to configure the SOCKS proxy using the Agent Installation Parameters too. To do so, you will need to rename the default Agent package file to include the proxy parameters. For example:

Here's an explanation of each parameter with their equivalent config file parameter:

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

Currently, the Agent only triggers any Windows Log Event rule for the currently logged-in user. To do so, it checks to see if any event generated by Windows has a user ID and matches that with the current user. However, many events such as login, logout, lock, power state changes, starting PowerShell, etc. do not have any user ID associated with them. The Agent wouldn't trigger any rules for those events.

We made changes to the Windows Log Event so that the Agent will now trigger a rule even if it doesn't have a user ID. We have also built a mechanism so that on a computer with multiple users (e.g., a terminal server), it will not duplicate the same event for multiple users and trigger such an event only once.

Previously, WebEx online meetings (both the web and desktop versions) were updated only after the meetings were ended on the Monitoring > Online Meetings.

Now, it will update it continuously, every second, while the meeting is ongoing:
​

We have added the ability to view which LDAP groups an employee belongs to from their monitoring profile, PERSONAL INFO tab:

We have added the ability to view which LDAP groups a computer belongs to from its settings window:

The productivity profiles created from the Configure > Productivity Profiles screen or the BI Reports > Applications & Websites screen will now have the following priority:

This will help clarify how app/web activities will be classified and displayed.

We have made some changes so that the Session Player will perform well under heavy loads (e.g., many players running at once, playing high-resolution videos, etc.).

Previously, the DELETE HISTORY AFTER (DAYS) option on the Monitoring Settings would be unavailable if you were using AWS S3 storage.

Now, the option is enabled for S3:

The Settings > About screen will now show the TMU (platform release) version and the Settings > System Health screen will show the BI classification version:

This will help admins keep track of what versions of the packages are installed.

We have made some changes so the MIN SPACE THRESHOLD and EMAIL MIN SPACE THRESHOLD fields on the Settings > Storage screen will now accept >=0 and <=90 if the THRESHOLD UNIT is set the "%" and >=500 if the unit is set to "MB":

This will help prevent any invalid values accidentally being entered into the fields.

We have implemented a change that will limit the number of email addresses that can be entered in the NOTIFICATION EMAILS field on the Settings > License Alerts screen. The default limit is set to 15 email addresses. If you try to enter more email addresses, it will show an error:

Previously, the settings for Monitoring Settings > ADVANCED > DISABLE BUILT-IN PASSWORD MANAGER OF KNOWN BROWSERS option was saved in Windows Registry:

This could interfere with the Windows Group Policy.

We made changes so that the settings for the password managers will be handled by the Agent and not saved in the Windows Registry.

We introduced a new behavior rule type, Windows Log Event in Platform Release 650. However, for this type of rule to work, the Agent would process the entire event log making this process slow and cumbersome. Especially, if you had multiple users on the same computer.

Now, we have made improvements so that the Agent will subscribe to the OS event channels (e.g., Authentication, Services, Process-Execution, Object-Manipulation, Sysmon, etc.) and listen to the Event IDs specified in the rule. This way, it will not have to scan the event log all the time. This should boost the performance and processing time significantly.

We expect to fix the limitations in a future version of the Windows Log Event rule.

Currently, the Agent Configuration file (config.cfg) is used by both the Agent and the services for reading and writing data. However, in rare situations, both of them might try to update the file at the same time causing a race condition. As a result, the file might get corrupted.

We have made changes to how the config file is handled so that any update/write to it will now be synchronized to avoid any race conditions.

Previously, if you had a slow network connection, the Agent would frequently disconnect, cause poor performance, or other network issues.

We have improved how the Agent handles and transfers heavy workloads such as screen and audio recordings so that it will perform much better on slower networks causing fewer dropouts and other connectivity issues.

Due to a bug with the Windows Location Service (which the Agent uses for the Geolocation feature), on some systems, network performance would drop every time the Agent collected the location data. By default, it was set to 30 seconds. For this reason, the network performance would drop every 30 seconds too.

As a fix, the Agent will now collect Geolocation data based on the TIME THRESHOLD value set under Monitoring Settings > Geolocation. This will reduce the effect significantly.

Due to a recent adaption of a new compression protocol in WhatsApp Web, the Agent's proxy service would fail to capture WhatsApp web meetings. As a result, no incoming or outgoing messages on WhatsApp would be displayed on the Monitoring > Instant Messaging or the BI Report > Instant Messages report.

The bug seems to affect Google Chrome as it had the new compression enabled by default but other browsers might be affected too.

We have made changes to the Agent so it will support the new compression protocol.

Previously, if the connection took more than 10-70 seconds, the Agent would drop the connection and try to initiate a new connection afterward. This was inefficient and would cause more connection attempts than necessary.

We have implemented some changes that will allow the Agent to wait for up to 120 seconds before it terminates a connection attempt. This will help improve the Agent connectivity and reduce network loads.

The location for the Agent Configuration file (config.cfg) has been changed. From now on the file will be located in the following locations:

Hidden Agent:

Revealed Agent:

In rare cases, the Agent crashes would lead to WebEx memory leaks:

As no software can guarantee to never crash and we cannot fix memory leaks in WebEx, hence current fix from the Agent side is to reboot WebEx once Agent restores after a crash.

In upcoming releases, we intend to improve this even more, so that a reboot of WebEx would be optional. We will also change the whole tracking mechanism to bypass triggering WebEx memory leaks.

We have made changes so that if the Agent has to restart for some reason (e.g., the Agent service crashed and recovered), any active task will resume.

If the user has the "Stay logged in" option enabled, the task will automatically resume. Otherwise, the task will resume as soon as the user logs in.

Previously, it would have been impossible to filter a BI report with both Measures and Dimensions together. For example:

Now, it's possible to apply filters by both Dimensions and Measures together. For example:

We are adding support for AD groups in BI Report Dimensions. You can do it with a /activity/query POST. For example:

We have deprecated the /tm-api/agent/:id PUT method to update the user. You will now have to use the PATCH method. For example:

We have added an API command, /tm-api/ldap/groups/content that can be used with a GET method to retrieve a list of Active Directory LDAP groups. A POST method can be used with the same command to change the group:

This will be helpful in situations where you may use solutions like BambooHR to manage employees and computers. With this API call, it will be easy to synchronize user groups and their associated resources, such as computers and employees between Teramind and the other solution.

We have changed how 2-Factor Authentication is performed for better security and convenience. It will now be a separate window instead of configuring it from the employee's profile, AUTHENTICATION tab:

More information can be found in this article.

The UI/Dashboard will now better mark unavailable features under the current subscription and allow the right user to upgrade to a higher package:

From now on the Daily Digest/Snapshot Email data will be loaded from the BI reports instead of the databases directly. The email will be sent when the BI sync is finished for the previous day.

Previously, if you tried to use a self-signed certificate with your AWS RDS deployment, you would get an error, "Error: self signed certificate in certificate chain at TLSSocket.onConnectSecure..." and the Dashboard would return an error 500 for various API endpoints:

This happened because Teramind didn't support self-signed certificates with the RDS databases.

Now, you will be able to use a self-signed certificate with your AWS RDS deployment.

We have added support for multiple history servers in a cluster. Also implemented was load balancing support for multiple WebSocket connections.

This will improve processing a large volume of history data, especially in larger deployments.

From now on, the video export web application can be launched on a separate VM in an On-Premise environment. This will speed up the video export process especially if you export many videos.

Previously, during the auto-update of the Agent, it would simply quit the Agent without showing any message.

Now, during the auto-update, the Agent window will close and a notification about the update progress will be shown. Once the update is completed, the Agent login screen will be displayed. The process is similar to the Windows Agent.

From macOS Sonoma 14.4 Beta, Apple will likely migrate away from the screen capture API causing Teramind Agent to display a warning message similar to one of the examples below (depending on the Agent type) each time the Agent is launched:

As a precaution, we will be migrating away from this older API and adopting a newer method to record the user's desktop. This should mitigate the warning message while making the Agent future-proof.

Previously, a Hidden/Silent Agent would continue to attempt connecting to the server every ten seconds even if its monitoring was disabled:

This would create unnecessary loads on the server especially if there were too many such connection attempts.

From now on, the Agent Service (tmsysd) will check to see if the monitoring is disabled for the Agent and prevent it from trying to connect to the server.

In a multi-level subnet, the Agent will need to trace the route to some target host to find out hops over the gateways. For those gateways, the Agent will now be able to match the IP address with the MAC address for accuracy and granularity.

Due to a bug, sometimes the Time Tracking > Time Cards and Configure > Departments > Edit Department screens would be missing the user's profile picture/avatar:

The bug is fixed now.

Due to a bug, the Department filter wouldn't work on the Time Tracking > Time Records report. Selecting the department wouldn't have any effect on the report:

The bug is fixed now.

Due to a bug, despite having some applications or domains classified, the BI Reports > Applications & Websites report would show them as unclassified:

The bug is fixed now.

Due to a bug, the "Player" object type would show "None" in the Object column of the BI Reports > Audit report:

The bug is fixed now so that the Object column will now show the user's name for whom the Session Player was launched.

Due to a bug, sometimes the Employee filter on the BI Reports > Productivity would show an empty list, and searching for an employee wouldn't return any results even though the employee existed:

The bug is fixed now.

Due to a bug, when you cloned a report and then added a new widget, it wouldn't show filters for the new widget. Instead, it would show filters from the original widget(s). For example, if you cloned an Applications & Websites report and then added the Email widget to it, the report would show filters from the Applications & Websites report only:

The bug is fixed now.

Due to a bug, the activity graph on the BI Reports > Productivity > Time Worked would render the graph incorrectly:

In the above example, the graph shows a 10-minute section of activity while the Time Range filter has the time range for the whole day.

The bug is fixed now.

Due to a bug, the BI sync would stop working in some instances.

The bug is fixed now.

Due to a bug, sometimes some grid widgets on a BI Report would fail to export. The Zip file containing the reports would show a zero-sized file for the widgets:

The bug is fixed now.

Due to a bug, Widget filters would filter the entire report. When trying to remove the widget filter from the global filters, nothing would happen.

The bug is fixed now so that when the global filter is removed, it will remove all filters and update the report.

Due to a bug, sometimes the BI Reports > Audit report would show missing translations:

The bug is fixed now.

Due to a bug, the Outlook desktop app would be captured as MS Edge:

Additionally, the Agent wouldn't be able to suspend monitoring for websites that are used as standalone apps created via MS Edge:

The bug is fixed now.

Due to a bug, the LDAP Attributes filter on the BI Reports would show wrong/missing attributes when attributes were added/removed through the API call /tm-api/ldap/:ldap_server_id/attr:

The bug is fixed now.

Due to a bug, the Camera icons would be missing from some Dashboard widgets:

The bug is fixed now.

Due to a bug, if you resized the Online Employees widget, the column would become disorganized and some columns would disappear:

In the above example, the Location column shows the Current Task information.

The bug is fixed now.

Due to a bug, sometimes the OCR "Contains" search would fail if the indices were too long (too many results). The bug is fixed now:

Due to a bug, the OCR image would be missing when clicking on the image thumbnail on the Monitoring > OCR search results:

The bug is fixed now.

Due to a bug, MS Teams calendar meeting events would appear on the Monitoring > Online Meetings report even when the user didn't join the meeting.

For example:

The bug is fixed now so that unless a user joins the meeting, it will not be shown on their Online Meetings report.

Due to a bug, a person-to-person (1-1) call on Microsoft Teams wouldn't start getting tracked until the meeting was finished.

The bug is fixed now so that the meeting will appear on the Monitoring > Online Meetings as soon as it's started and continue to update until adjourned.

You can add/remove time from the Monitoring > Screen Snapshots and Employee > Employee's Detail > Screen Snapshot screen. However, due to a bug, the removed time would be reported incorrectly.

For example, suppose you manually added time from 9 AM to 10 AM. Then removed time from 8:30 AM to 9:30 AM. In this case, the time removed will be shown 1 hour when it should be 30 minutes:

The bug is fixed now.

Due to a bug, when you select a user on the Monitoring > Screen Snapshots report, the Computer filter would display all computers instead of showing only the computer(s) that were used on the selected date:

The bug is fixed now.

Due to a bug, a Websites-based Activity rule with an Except condition for the Webpage Url criterion and a Block action like the one below would close the browser even if the user opened an empty tab/window:

As the user would be unable to enter any URL on the address bar, this would prevent them from browsing any sites without taking special steps (e.g., Continue where you left off option).

The bug is fixed now.

Due to a bug, it would be impossible to edit some rules in some instances. The Dashboard would show an "Unknown error" when trying to edit the rules:

The bug is fixed now.

Due to a bug, if you used the Advanced action and then changed the rule type (e.g., from an Activity rule to an Agent Schedule rule), the Action tab wouldn't change.

The bug is fixed now.

Due to a bug, it would be impossible to upload the employee profile image/avatar on some instances. An "Internal Server Error" would be displayed:

The bug is fixed now.

Due to a bug, a "0" would be shown on the Employees > Employee's Page screen:

The bug is fixed now.

Due to a bug, icons would be missing from the Employees > Employee's Details > Activity Log report.

The bug is fixed now so that the icons will be displayed as expected:

Due to a bug, the Employees > Employee's Details > Activity Log report would show an additional day from the selected day:

The bug is fixed now.

Due to a bug, the Employees > Employee's Details > Activity Log report would show an error, "Internal server error" for a newly added employee:

The error would go away once the BI sync had finished.

The bug is fixed now.

Due to a bug, some data would be missing from the Employees > Activity Log and Employees > Snapshots reports in some instances.

The bug is fixed now.

Due to a bug, the Employee column on the Employees report would partially hide the employee names. Even maximizing the window wouldn't show the full names:

The bug is fixed now.

Due to a bug, some users wouldn't be able to see real-time data in the Employees > Employee's Details > Activity Log report because the "Click here for real time data" link would be missing.

The bug is fixed now so that the link is shown for all users:

Due to a bug, if you tried to bulk edit employees from the Employees screen, you might see an error, "There was an error while fetching data. Please try again later." while saving or discarding the changes:

Due to a bug, an employee with the right access permissions (e.g., access permissions to view employees and departments) wouldn't be able to use the department filter on the Employees report. The filter would show an empty list:

The bug is fixed now.

Due to a bug, an authorized user with the right access control policy (e.g., departments assigned as targets/subjects under their supervision) wouldn't be able to view all employees they are entitled to. They would only see employees from a certain department.

The bug is fixed now.

Due to a bug, a user with the right RBAC policy (e.g., ability to change employees/computers) wouldn't be able to make changes to the Employees and Computers screen as some features would be missing.

The Employees screen would be missing the Action menu when employees were selected and the Computers screen would be missing the selection check marks:

The bug is fixed now.

Due to a bug, an authorized user with the right access control policy (e.g., edit employees) wouldn't be able to edit the employee.

The Action menu on the Employees report would miss all options, except for the "Bulk Edit" and toggling the "Monitor this user" button from the Employees > Employee's Page page wouldn't change the monitoring status:

The bug is fixed now.

Due to a bug, if you had two employees with the same name, and one of them was assigned as a department manager from the Configure > Departments screen, it would be impossible to change it to another user with the same name.

This happened because the system wouldn't allow the former and new managers from the same department.

The bug is fixed now.

Due to a bug, the "View record" option would be shown on a grid widget's context menu of the BI Reports for users who have the "Play historic screen stream" access control permission disabled:

The bug is fixed now so that a user who doesn't have the right permission will not see the "View record" option.

Due to a bug, a user with the right RBAC level (e.g., admin) wouldn't see the rule alerts for Schedule-based rules on the BI Report > Behavior Rules or the Behavior > Alerts report.

The bug is fixed now:

Due to a bug, the "Play" button would be shown on the Monitoring > Screen Snapshots report for users who have the "Play historic screen stream" access control permission disabled:

The bug is fixed now so that a user who doesn't have the right permission will not see the Play button.

Due to a bug, the Camera icons would be shown on the Monitoring > Sessions report for users who have the "Play historic screen stream" access control permission disabled:

The bug is fixed now so that a user who doesn't have the right permission will not see the Camera icons.

Due to a bug, a user with the right access permissions (e.g., ability to view computers) wouldn't be able to select computers from the Departments > Edit Department window:

The bug is fixed now.

By default, the Subscribe button under the main menu should only be shown for an Administrator or Operational Administrator. However, due to a bug, it would be shown for all users:

The bug is fixed now.

Due to a bug, sometimes it would be impossible to change the playback position using the player timeline. The bug is fixed now:

Due to a bug, the Freeze Input function on the Session Player wouldn't work for some users even when the ALLOW REMOTE CONTROL feature was enabled on the Monitoring Settings > Screen window. An error message would be displayed, "Remote control is disabled in monitoring settings":

The bug is fixed now.

Due to a bug, video exports from the Session Player would fail without any explanation:

The bug is fixed now.

Due to a bug, sometimes the Monitoring Settings page wouldn't load for a user with the account type, Infrastructure Admin. The page would continuously show the "Loading data..." message and nothing would happen.

The bug is fixed now.

Due to a bug, if you made no changes while editing a monitoring profile (Monitoring Settings > Monitoring Profile > EDIT PROFILE INFO) and pressed the APPLY CHANGES button, it would turn some of the monitoring objects (WHAT TO MONITOR) to NO and TRACKING TIME to NEVER:

The bug is fixed now.

Due to a bug, if the buffer size on the Monitoring Settings > Offline Recording wasn't set to 0, it would prevent changing the monitoring object state (WHAT TO MONITOR). On the browser's console, it would return a "400 Bad Request" error.

The bug is fixed now.

Due to a bug, when you clicked the EDIT OBJECTS TO TRACK button on the Monitoring Settings > Monitoring Profile screen, it would throw an error in the browser console, "Wrong column ID specified":

The bug is fixed now.

Due to a bug, some instances would face problems when configuring/adding a new LDAP server from the Settings > Active Directory screen. It would show errors like, "Internal Server Error", "Error while fetching data", etc.:

The bug is fixed now.

Due to a bug, if you had a custom AD sync set up, and you made any changes to the IMPORT CONFIG field ( Settings > Active Directory), and then tried to save the changes, it would show an error, "Invalid arguments: EMPLOYEES.NEED_CONFIRMATION_WITH_PASSWORD":

The bug is fixed now.

Due to a bug, when importing Active Directory groups as OUs (GROUP TO OU ATTRIBUTE option on the Settings > Active Directory screen), the process wouldn't clean up the converted groups afterward - resulting in unexpected behavior:

The bug is fixed now.

Due to how the browser works, the Chrome Password Manager would override the LDAP LOGIN field on the Settings > Active Directory screen:

As a result, the user would have to change the password every time they tried to save any changes.

The bug is fixed now.

Due to a bug, if the user name contained any upper case letters, it would cause the Revealed Agent to cause an authentication failure. When this happened, a "Network error" message would be shown to the user:

The bug is fixed now so that even if a user enters upper cases in their user name, the Agent will automatically convert it to lower cases.

Due to a bug, if you stopped the Agent Service (tsvchst.exe) with a net stop tsvchst or sc stop tsvchst command, it would leave the Clipboard Monitoring (clm.exe) and Outlook Monitoring (mtm.exe/mtm64.exe) processes running.

The bug is fixed now so that all the processes will exist when you stop the Agent Service.

The Agent Service (svc.exe for the Hidden Agent and tmagentsvc.exe for the Revealed Agent) is responsible for running services that monitor the user’s sessions and creates a new Agent Process (dwm.exe for the Hidden Agent and tmagent.exe for the Revealed Agent) for each session. If the Agent Service is stopped, it closes the Agent Process and other support services and then restarts a fresh session.

However, due to a bug, if the Agent Service quit unexpectedly/crashed, it would leave the old Agent Process and other services running while also launching a new set of processes and services.

This would cause unexpected system behavior and might affect the monitoring and reporting on the Dashboard.

The bug is fixed now.

Due to a bug, the Login Agent Scheduled rule like the one below wouldn't work consistently:

Sometimes it would block login attempts with a built-in message, "You are not allowed to work at this time". Sometimes, it would show the custom message but let the user log in after pressing the OK button, etc.:

The bug is fixed now.

If you disabled monitoring of a computer from the Dashboard (e.g., Computers > Action Menu > Disable Monitoring or Computers > Computer's Details > Monitor Computer), the Revealed Agent automatically signs out the user and shows a dialogue box, “You were signed out by server”:

However, due to a bug, if the user didn't click the OK button within the next few minutes, it would become frozen. The user would then need to force quit the Agent.

The bug is fixed now.

Due to a bug, in rare situations, the Agent would clear its configuration file (config.cfg) when it restarted from a crash or forceful closure. This could cause the Agent to behave unexpectedly or prevent it from connecting to the server.

The bug seems to affect Agent versions 24.6.1401 and 24.7.1410, but other versions might be affected too.

The bug is fixed now.

Due to a bug, if the Agent was restarted (e.g., from a crash), it would stop tracking all Microsoft Teams meetings, including one-to-one calls.

The bug is fixed now.

When you upload a file via OneDrive, sometimes it will split the upload into multiple files if the file is big (e.g., > 10 MB). This would cause the Agent to treat a single file upload event as multiple upload events on reports like the BI Report > Web Events and Monitoring > File Transfers report, etc.:

We made changes to the Agent so that it will account for this behavior in OneDrive and only show a single upload activity.

Due to a bug, if you tried to start a Zoom meeting from the browser, it would be blocked by the Agent sometimes. As a result, the user will see an error message, "Joining Meeting Time out or Browser restriction.":

The bug is fixed now.

Due to a bug, outgoings call on the classic web version of Microsoft Teams would be shown as incoming calls on the Monitoring > Online Meetings report:

In the above example, John Doe (JD) was making the call but on the Online Meetings report, the call was recorded as "Incoming" when it should have been recorded as "Outgoing".

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

The bug is fixed now.

Due to a bug, if either the File Driver or Network driver was disabled (from Monitoring Settings > Advanced), it would sometimes show wrong directions for the Zoom Desktop meetings (e.g., Outgoing as Incoming or vice versa):

The bug is fixed now.

Due to a bug, in rare cases, the Agent would fail to track any application activities and fail to show them on reports like the BI Report > Applications & Websites. It would still capture the session recordings (screen recordings).

The bug is fixed now.

Due to a bug, the Agent wouldn't be able to capture the icons for apps when they were launched from the Windows Search. As a result, reports like the Monitoring > Web Pages & Applications would show an empty icon box:

The bug is fixed now.

Due to a bug, sometimes Windows will show the user a dialogue box to install the .NET framework:

The bug is fixed now so that the dialogue box will not be shown.

Due to a bug, trying to create an access token with the API call, POST tm-api/access-token/ would return, "500 – Internal Server Error".

The bug is fixed now.

Due to a bug, trying to execute the API call, GET /tm-api/report/export/status would return "500 – Internal Server Error":

The bug is fixed now.

When an API PATCH https://<server>/tm-api/agent/ command was used to update the LDAP attribute of a user and it failed with an error code 400 (Forbidden), the event woul still be logged as an edit event on the BI Reports > Audit and System > System Log report even though no changes were made:

The bug is fixed now so that the failed API activity will not appear on the System Log report.

Due to a bug, an Operational Administrator wouldn't be allowed to use the Subscribe button (at the bottom of the main menu) or UPGRADE SUBSCRIPTION button from the subscription pop-up windows:

The bug is fixed now.

Due to a bug, the OCR Mining would stop working in some instances. This could happen if the PROCESS SCREEN RECORDS AFTER option on the Monitoring Settings > Screen window had no date set for new profiles:

The bug is fixed now.

Due to a bug, the Zip file generated by the Teramind Diagnostics tool (TMDiag) wouldn't include the Agent and Service logs.

The bug is fixed now.

Due to a bug, the Teramind Diagnostics tool (TMDiag+) would fail to record video as it was missing the ffmpeg.exe in its bundle.

The bug is fixed now.

The Agent wouldn't include browser information when checking Webpages rules, which would lead to the Behavior > Alerts and BI Reports > Behavior Alerts reports missing this information and would display, "n/a" in the browser's name:

The bug is fixed now.

Due to a bug, the All Browser condition of the Webpages >Browser criterion wouldn't work:

When the All browsers condition is chosen, the rule won't trigger for any browser.

The bug is fixed now.

Due to a bug, if you used the Block action with a Webpages rule like the one below, it wouldn't display what browser was used in the alert description on reports like the Behavior > Alerts, BI Reports > Behavior Alerts, etc.:

The bug is fixed now so that the browser information will now be shown in the alert description:

Due to a bug, some versions of the Agent would have issues with the remote control feature on the Session Player. As a result, double clicks, drag-and-drop, text selection and some hotkeys/key combinations wouldn't work on the remote host.

The bug is fixed now.

By default, macOS shows a dialogue box when you select the "Shut Down" option from the system (Apple) menu:

However, due to a bug in a multi-user setup, if one user initiated the shutdown while another user was logged in, the Agent would incorrectly recognize this as a screen lock event and stop any ongoing task. If the user pressed the Cancel button, the Agent would restart tracking any previously paused task.

The bug is fixed now.

Due to a bug in the network extension (NetApp), in rare circumstances, you might face network issues such as webpages not loading, connection slowing down or the network not working at all.

These could happen if you had a large number of plain TCP connections (e.g., HTTP) or have installed any software that used IPP (Internet Printing Protocol) such as PaperCut.

The bug is fixed now.

We have made improvements to the DNS/URL processing, making it asynchronous. This will improve network performance, especially on any systems where the Agent’s DNS resolving would fail frequently due to network lags.

Due to a bug, the browser name, icon, and version no. would be missing from reports like the Monitoring > Web Pages & Applications and BI Reports > Applications & Websites:

The bug is fixed now so that the browser information will be displayed as expected:

Due to a bug, a Webpages rule with the Time Active (min) or Time Idle (min) criteria would get triggered immediately if the user switched between a monitored webpage vs. a non-monitored webpage. Consider this rule:

In the above example, the user opened a tab and visited any website except bbc.com. The user then switched to bbc.com page before 2 min had passed. The rule would get triggered. In reality, it should have reset the counter and only triggered the rule if the user stayed idle on bbc.com for 2 minutes after the user switched from the other tab/webpage.

The same thing would happen with the Time Active (min) criterion. In that case, the rule would trigger if the user was active instead of idle.

The bug is fixed now.

Due to a bug, if you had a rule like the one below that used a Shared List, the Agent would ignore the Total Time Active or Total Time Idle criterion and trigger the rule as soon as the application name(s) matched with items in the Shared List:

The bug is fixed now.

Due to a bug in the screen capture module, the cursor from the users' desktops wouldn't be displayed on the screen recordings in the Session Player (both the Live View and the History View modes).

The bug seems to affect the Agent version 23.41.4797 and above. But other versions might be affected too.

The bug is fixed now so that the cursor is drawn as expected.

Due to a bug, the mouse cursor would be shifted when using the remote control feature on the Session Player. The bug is fixed now:

Due to a bug, the Agent installation package (.pkg file) would be missing the custom port number if you changed your LOAD BALANCER PORT from Settings > Server Management. As a result, the Agent would fail to connect to its server.

The bug is fixed now so that the load balancer port will be added to the file name and also in the configuration file ( Macintosh HD > usr > local > teramind > agent > etc > agent.conf) when the Agent is installed:

Due to a bug, the Mac would lose network connectivity after an Agent crash. The connectivity would return if the Agent was restarted. This would happen if you had the network driver (NetApp extension) enabled.

The bug is fixed now.

Due to a bug, sometimes you might have noticed high CPU usage for the Teramind file monitoring process (com.teramind.systemextension.endpointsecurity):

The bug is fixed now.

Due to a bug, some versions of the Revealed Agent would show high memory usage after running for a while (1 hour+) if screen recording was enabled:

The bug is fixed now.

Due to a bug, if you tried to sign into the Revealed Agent from multiple user accounts using the same credential, the Agent would become frozen. It will show the expected "You were signed out by server" to the previous user but after that, it would become frozen:

The bug is fixed now.

Due to a bug, in rare situations, the Agent would crash if you pressed Command(⌘)+Q to quit the Agent.

The bug is fixed now.

Due to a bug, the Agent would crash when you tried to check the ink supply level on some printers (e.g., EPSON ET-3750 series printers), it would cause the Agent to crash:

The bug would be caused because the Agent treated it as a print job and tried to get printing stats causing it to crash.

The bug is fixed now.

Due to a bug, if you had the network monitoring enabled, TaleScale VPN wouldn't work properly. It would try to connect indefinitely without any success.

While this seems to be an issue with TaleScale, as a workaround the Agent will now automatically exclude it from network monitoring by using the network-exclude-bundles config file parameter:

Due to a bug, the Agent would crash just after starting a task. The user would see an error message, "Teramind Agent quit unexpectedly.":

This seems to happen on macOS Monterey, but other versions might be affected too.

The bug is fixed now.
​