This script is intended to serve as a backup management tool to address basic and initial tasks on a Microsoft Teams Room system based on Windows (MTRoW).
Please follow the recommended best practices by Microsoft to setup, manage and maintain this kind of devices: https://docs.microsoft.com/en-us/microsoftteams/rooms/
This script can be helpful in the following scenarios:
- Post OOBE setup basic configuration and maintenance tasks
- Unable to access or manage the device via Microsoft Teams Admin Center (TAC) or Microsoft Endpoint Manager Admin Center / Intune.
- Manage standalone devices
This script requires to enable and allow remote access to the device, which may violate the security guidelines for devices in your environment. Only proceed if you know what you are doing, and feel comfortable to do so.
The script is provided AS IS without warranty of any kind. I do not take any responsability on it's use.
The entire risk arising out of the use or performance of the script and documentation remains with you. In no event shall I or anyone else involved in the creation, development or delivery of the script be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.
Meet the basic prerequisites and you should be ready to go!
- PowerShell (PS) Version 5.1+
- Remote Powershell enabled on remote MTR
- MTR device resolvable and accesible over the network
On local management machine:
-
Run
$PSVersionTableand check if PSVersion matches required version -
Define the trusted remote endpoint(s) where you will connect to:
Set-Item WSMan:\localhost\Client\TrustedHosts -Value "<MTR_IP>|<MTR_Name>" [-Force]
Locally, on remote MTR device:
-
Open an admin elevated Powershell session and run:
Enable-PSRemotingOptional: Use the -SkipNetworkProfileCheck parameter if network is not trusted (public) and still want to force PsRemoting, or directly define your network as private by executing:
Set-NetConnectionProfile -Name "<Network_Name>" -NetworkCategory Private -
Maybe you also want or need to override the Local Security Policy to allow to connect to the MTR remotely from the network:
Open the Local Security Policy by running Secpol.msc and add the Administrators security group to Security Settings -> Local Policies -> User Rights Assignment -> Access this computer from the network.
From here on, you can enter a Powershell session on the remote device (1), or directly run PS commands (2) from your management server/workstation with the appropriate credentials:
$cred = Get-Credential
$MTR_device = "<MTR_FQDN_or_IP_Address>"
(1):
Enter-PSSession -ComputerName $MTR_device -Credential $cred
(2):
Invoke-command { <PS_scriptblock> } -ComputerName $MTR_device -Credential $cred
- Teams App Version 4.15.58.0
Invoke the script, select an option and follow the instructions:
.\MTR_REMOTE_MGMT.ps1
MAIN MENU: (may differ from current release)
(No target MTR!)
================ MTR REMOTE MANAGEMENT ================
1: TARGET MTR device.
2: Change MTR 'Admin' local user PASSWORD.
3: Set MTR resource ACCOUNT (Teams App user account).
4: Set MTR Teams App LANGUAGE.
5: Check MTR STATUS.
6: Get MTR device LOGS.
7: Set MTR THEME image.
8: Run nightly MAINTENANCE scheduled task.
9: Update MTR App VERSION
10: LOGOFF MTR 'Skype' user.
11: RESTART MTR.
Q: Press 'Q' to quit.
Please make a selection:
-
Question: Can I use this tool to operate in batches on multiple MTR devices at the same time?
Answer: No, this script is intended as a backup tool to operate on single MTR devices as of now.
Distributed under the MIT License. See LICENSE for more information.