Get-UcTeamsDevice

Recently, we added a new cmdlet to the UC Lobby Teams PowerShell module. The Get-UcTeamsDevice cmdlet will use MS Graph to query all the Teams Devices registered in a M365 Tenant. Executing it without any parameters will return a table with a summary of all devices. This information is similar to what is shown in … Continue reading Get-UcTeamsDevice

UCLobby Teams 0.2.0

A new version is now available in PowerShell Gallery and here are the changes included: Get-UcTeamsVersion Added Computer parameter to get Teams version on a remote machine. Added Path parameter to specify a path that contains Teams log files. Get-UcTeamsDevice New cmdlet that gets Microsoft Teams Devices information using MS Graph API. Test-UcTeamsDevicesConditionalAccessPolicy New cmdlet … Continue reading UCLobby Teams 0.2.0

UCLobby Teams 0.1.3

A new version is now available in PowerShell Gallery and here are the changes included: Get-UcTeamVersion Fixed the issue where the version was only showing 4 digits.Added information for Ring, Environment, Region. Get-UcTeamUsersEmail New cmdlet that returns a list of users email address that are part of a Team Get-UcTeamsWithSingleOwner This function returns a list … Continue reading UCLobby Teams 0.1.3

Get-UcTeamsForest

Sometimes, we get asked which forest customers should use when moving a user to Microsoft Teams in the Move-CsUser. A quick way to check the forest is to open the following link in a browser: https://webdir.online.lync.com/AutoDiscover/AutoDiscoverservice.svc/root?originalDomain=uclobby.com In the response we can look at the redirect URL and look at the forest, in this case it … Continue reading Get-UcTeamsForest

UCLobby Teams PowerShell Module

After publishing Teams: Check client version using PowerShell I started this module as a side project. Unfortunately, it stayed on draft from some time but now it’s finally here. The plan is to add useful functions related to Microsoft Teams and have them bundled in a single module. The module is available in the PowerShell Gallery: PowerShell Gallery – UCLobbyTeams … Continue reading UCLobby Teams PowerShell Module

Manage Microsoft Teams PowerShell Module

As most of us know, the steps to install and update the Microsoft Teams Powerhell Module are described here: Install Microsoft Teams PowerShell Module However, it is also possible to install, load and remove previous versions. To list all installed versions we need to use the ListAvailable parameter: Get-Module -ListAvailable MicrosoftTeams By default, the module … Continue reading Manage Microsoft Teams PowerShell Module

Teams: Check client version using PowerShell

Update May 18th 2022: Now available as Get-UcTeamsVersion in UCLobby Teams PowerShell Module An easy way to check MS Teams version is in the client by going to About > Version: The version will be displayed near the Command Box: The MS Teams client is installed per user and the version is stored in the settings.json file: %AppData%\Microsoft\Teams\ … Continue reading Teams: Check client version using PowerShell

How to disable Microsoft Teams from Startup

Update 2019/08/22 - Added the initial post methods. Update 2017/03/07 - Now we can control the start up behavior with an application setting. Although we might use Microsoft Teams every day we might not want to run it on startup. In this post we discuss the available methods to disable MS Teams auto-start feature. Method … Continue reading How to disable Microsoft Teams from Startup

Microsoft Teams: Desktop and Web Client Log Location

Update 2017/11/16 - New keyboard shortcuts for Web Client. Microsoft Teams preview was recently released and to help troubleshooting we need to verify the log and media trace files. The Microsoft Teams Desktop Client logs are located in: Windows %AppData%\Microsoft\Teams\logs.txt Mac ~\Library\Application Support\Microsoft\Teams\logs.txt And the Media ETL traces are located in: Windows %AppData%\Microsoft\Teams\media-stack Mac ~\Library\Application Support\Microsoft\Teams If we … Continue reading Microsoft Teams: Desktop and Web Client Log Location