Skip to main content
Mac Agent 24.07.4904 (2024-02-27)
A
Written by Arick Disilva
Updated over 9 months ago

New Features

Support for Monitoring Network Drives

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

Now, we are adding 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.

Support for the Time Idle Criterion in Applications Rules

We are adding 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.

Support for the Time Active and Time Idle Criteria in Webpages Rules

We are adding 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.

Improvements

Migration from Older Screen Capture API

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.

Bug Fixes

High Memory Usage by the Revealed Agent

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.

Did this answer your question?