ControlUp does not currently offer direct insights into Microsoft Teams meeting recordings or their access logs. Meeting recordings in Teams are stored in the organizer's OneDrive or SharePoint, depending on the meeting type. For private meetings, recordings are saved to the organizer's OneDrive, while channel meetings store recordings in the SharePoint site associated with the channel. ([learn.microsoft.com](https://learn.microsoft.com/en-us/MicrosoftTeams/tmr-meeting-recording-change?utm_source=openai))
To monitor access to these recordings, organizations can utilize Microsoft Purview, which provides auditing capabilities for Teams content. Purview allows administrators to track activities related to meeting recordings, such as who accessed or shared the recordings. This functionality is particularly useful for compliance and security purposes. ([learn.microsoft.com](https://learn.microsoft.com/en-us/purview/edisc-search-teams?utm_source=openai))
Additionally, meeting organizers can manage access permissions for their recordings directly within Teams. By default, access is set to "Everyone," but organizers can customize this setting to restrict access to specific individuals or groups. This control ensures that only authorized users can view or download the recordings. ([support.microsoft.com](https://support.microsoft.com/en-us/teams/meetings/customize-who-can-access-a-recording-or-transcript-in-microsoft-teams?utm_source=openai))
In summary, while ControlUp does not provide direct insights into Teams meeting recordings, organizations can leverage Microsoft Purview for auditing access and utilize Teams' built-in features to manage recording permissions effectively.
Read the entire article here...
Microsoft Teams
How to Diagnose Microsoft Teams SlimCore Optimization in Citrix and Other VDI Environments Using PowerShell Scripts
This discussion highlights two PowerShell scripts developed to aid tracking and diagnosing Microsoft Teams SlimCore Optimization specifically within Citrix environments, with potential applicability to Azure Virtual Desktop (AVD), Windows 365 (W365), and VMware Horizon sessions. SlimCore is an optimized media stack used in virtual desktop infrastructure (VDI) scenarios to enhance Teams call performance by offloading audio and video processing to the client side.
Read the entire article here...
Read the entire article here...
Utilizing Microsoft Teams API with ControlUp UCC dashboards
A user named Seb shared three ControlUp UCC dashboards that use Microsoft Teams API data only - no CU4D agent needed. The dashboards show real Teams call quality and usage before the agent reaches the endpoints. It includes graphs for daily, weekly, and monthly trends, as well as MOS bands and per-user statistics. These dashboards can be customized to specific needs. Other users showed appreciation for Seb's contribution.
Read the entire article here...
Read the entire article here...
Formatting Message Text on Microsoft Teams
A discussion about formatting message text on Microsoft Teams was had, with the suggestion to use the "Send Message to Channel" integration to define titles and flag messages as important using Markdown or Adaptive Cards. A sample JSON payload was provided for reference. The user who brought up the question was encouraged to try it out and report back on their experience.
Read the entire article here...
Read the entire article here...
How to Track Resource Usage for Microsoft Teams with ControlUp
A user asks for help in tracking resource usage from Microsoft Teams with ControlUp. Another user suggests looking at the App Trends report to compare usage before and after implementing Teams redirection. The link to the report is provided. The suggested report allows for viewing data points over time for CPU, RAM, and IO usage.
Read the entire article here...
Read the entire article here...
Troubleshooting Pagerduty Integration in Scoutbees
A user shared their experience trying to set up a Pagerduty integration in Scoutbees. They mention encountering difficulties as Pagerduty's webhook is considered more of a REST API call instead of following the "webhook standard." However, it is possible that Pagerduty has updated this. A workaround suggested is to use Pagerduty's email integration. URL mentioned: https://buttercms.com/blog/webhook-vs-api-whats-the-difference/
Read the entire article here...
Read the entire article here...
Troubleshooting Error 500 in ControlUp’s Microsoft Teams Integration
Multiple users discussed an error 500 that occurs when configuring Microsoft Teams integration under UC&C. A support article was shared and it was recommended to open a ticket for further investigation. It was also suggested that the error may be due to incorrect use of keys.
Read the entire article here...
Read the entire article here...
Effective Deployment of the New Teams VDI Optimization Agent
A user discussed deploying the New Teams VDI optimization agent successfully with the help of a provided PowerShell script. Another user suggested using the agent for app patch management and version consistency across devices. Custom software scans and deployments were also mentioned.
Read the entire article here...
Read the entire article here...
Troubleshooting App Crashes on Windows 11 Devices
Users discussed issues with MS Teams, Edge, and Chrome crashing on Windows 11 devices. The event log showed a Fault bucket event without a corresponding 1000 event, indicating a possible app vendor issue. The ControlUp team has alerted Microsoft and is working to find a solution. The team has also created an alert for the 1001 event, but it does not provide helpful information for resolving the problems.
Read the entire article here...
Read the entire article here...
New Release of ControlUp’s SIP Agent (2.13.1.3428) with Teams Monitoring Bug Fix
A new SIP Agent (2.13.1.3428) has been released with a bug fix for Teams monitoring in VDI sessions, including support for the new MS Teams. A user encountered issues with Teams and SIP, leading them to disable SIP on their Terminalserver and VDI. The ControlUp support team can be contacted for further assistance.
Read the entire article here...
Read the entire article here...
