Workflow: MS Teams compliance
Compatability
This workflow, and the remote actions it triggers, are designed to operate on older Teams clients, now referred to as “Microsoft Teams classic”. To check the compliance of the “new” version of Microsoft Teams, now referred to as “Microsoft Teams (work or school)”, please refer to this dedicated workflow: Workflow: MS Teams (work or school) compliance
Overview
As a vital collaboration tool, productivity and satisfaction are critically impacted when Microsoft Teams is not working as intended. This is often due to common L1-level compliance issues: presence, versioning, or incorrect configurations. Regardless of the issues(s) detected, L1 agents must find and treat each type of problem separately to ensure compliance.
Trigger an automated workflow across any group of devices to perform a series of automated compliance checks to ensure that MS Teams is present, compliant, and up-to-date. If any issues are detected, the workflow automatically performs the necessary remediation.
This workflow automatically enables you to resolve and filter out common compliance issues. This saves significant time for any support team, enabling them to investigate and focus on more serious problems.
Changelog
V1.0.0.0 - Initial Release
Dependencies
In order to use this flow the following content needs to be installed into your Nexthink Infinity tenant using the Nexthink Library.
Remote actions
Get Microsoft Teams client status
Reinstall Microsoft Teams Windows
Clear Microsoft Teams cache
Set Teams GPU hardware acceleration
For more details about remote actions in workflows see https://docs.nexthink.com/platform/latest/workflows-designer#id-(2023.8-05)Designer-RemoteActions .
Campaigns
Reinstall Microsoft Teams - Invoke
Reinstall Microsoft Teams - Completed
Close Microsoft Teams (short maintenance) - Invoke
Close Microsoft Teams (short maintenance) - Completed
For more details about campaigns see https://docs.nexthink.com/platform/latest/campaigns and campaigns in workflows see https://docs.nexthink.com/platform/latest/workflows-designer#:~:text=the%20remote%20action.-,Campaigns,-The%20Campaign%20Thinklet .
Configuration
Remote action and campaign configuration
Please note: To be used in a workflow, the following remote actions must be configured with a manual trigger. It can be combined with other execution triggers if the remote action is also used outside of a workflow.
To be used in a workflow, campaigns must be specified in the input parameters of the corresponding remote actions and published.
The following remote actions require campaigns.
Set Teams GPU hardware acceleration
[CloseTeamsCampaignId]: Close Microsoft Teams (short maintenance) - Invoke
[OperationCompletedCampaignId]: Close Microsoft Teams (short maintenance) - Completed
Clear Microsoft Teams cache
[CampaignId]: Close Microsoft Teams (short maintenance) - Invoke
[OperationCompletedCampaignId]: Close Microsoft Teams (short maintenance) - Completed
Reinstall Microsoft Teams Windows
[CampaignId]: Reinstall Microsoft Teams - Invoke
[OperationCompletedCampaignId]: Reinstall Microsoft Teams - Completed
Trigger configuration for the workflow
This workflow was designed primarily to be run manually to ensure that client fixes can be submitted quickly. However, it can be configured to run on a schedule.
When configuring the scheduler we recommend the following settings as a baseline:
NQL:
devices during past 7d
| where operating_system.platform == Windows
and operating_system.name !in ["*server*"]Recurrence: Weekly - select at least one day.
Please note: Once all the prerequisites and workflow are installed and configured, you can use the built-in validation feature that runs every time you save the workflow.
Workflow Structure
Please note: The workflow uses campaigns that alert users before every step that affects their Microsoft Teams client software. Users can cancel a workflow if it's not the right time to work with their Microsoft Teams client (for example, they're in a Teams call).
This section describes the key steps in this workflow:
At the start of this workflow, there is a "Get Microsoft Teams Client Status" thinklet configured to automate the retrieval of Microsoft Teams client status information using a remote action;
Based on the results of this analysis, the workflow determines whether the following issues need to be addressed with additional remote actions:
Does the device have the Microsoft Teams client installed?
Is the Microsoft Teams client up to date (updated less than a month ago)?
Once these issues are identified and resolved, the workflow checks to see if GPU acceleration is enabled in the Microsoft Teams client on the device. In case it is enabled, the workflow calls a remote action to disable it.
RELATED TOPICS