Previously, if you had a slow network connection, the Agent would frequently disconnect, cause poor performance, or cause 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, 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.

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, in some rare cases, the network would become inaccessible when MS Teams was being used. As a result, no webpages would load and other network activities would be halted. The Agent would also become frozen and crash.

The bug is fixed now.

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, 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 event might 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.