Microsoft Teams Rooms maintenance and operations

Read this topic to learn about management of Microsoft Teams Rooms, the next generation of Skype Room Systems.

Microsoft Teams Rooms is Microsoft's latest conferencing solution designed to transform your meeting room into a rich, collaborative experience. Users will enjoy its familiar Microsoft Teams or Skype for Business interface and IT administrators will appreciate an easily deployed and managed Windows 10 Skype Meeting app. Microsoft Teams Rooms is designed to leverage existing equipment like LCD panels for ease of installation to bring Microsoft Teams or Skype for Business into your meeting room.

With additional configuration, remote management is possible using Microsoft Azure Monitor as described in Plan Microsoft Teams Rooms management with Azure Monitor, Deploy Microsoft Teams Rooms management with Azure Monitor, Manage Microsoft Teams Rooms devices with Azure Monitor. You may also Manage Microsoft Teams Rooms console settings remotely with an XML configuration file, which includes applying a Custom display theme.

Collecting logs on Microsoft Teams Rooms

To collect logs, you must invoke the log collection script that ships with the Microsoft Teams Rooms app. In Admin mode, start an elevated command prompt, and issue the following command:

powershell -ExecutionPolicy unrestricted c:\rigel\x64\scripts\provisioning\ScriptLaunch.ps1 CollectSrsV2Logs.ps1

The logs will be output as a ZIP file in c:\rigel.

Front of Room Display Settings

Configure the Front of Room display to Extended mode. Doing so will ensure that the console UI is not duplicated on that display when you cycle power on the display.


If you desire a front of room display to automatically switch to an active video source (such as an MTR console) when the source wakes from standby mode, certain conditions must be met. This feature is optional but supported by Microsoft Teams Rooms software, provided underlying hardware supports the feature. A consumer TV used as a front of room display needs to support the Consumer Electronics Control (CEC) feature of HDMI. Depending on the dock or console selected (which might not support CEC, refer to manufacturer support documentation), a controller such as an HD-RX-201-C-E from Crestron or Extron HD CTL 100 from Extron may be needed to enable the desired behavior.

Microsoft Teams Rooms Reset (Factory Restore)

If Microsoft Teams Rooms isn't running well, performing a factory reset might help. To do this, use the Microsoft Teams Room recovery tool and follow the factory restore instructions.


There is a known issue where the Microsoft Teams Rooms can become unusable if the Keep my files - Removes Apps and settings, but keeps your personal files option is selected during the Windows Reset process. Do not use this option.

Supported Remote Options

The following table summarizes the possible remote operations and the methods you can use to accomplish them.

Workgroup Not domain joined Domain joined
Teams admin center
Remote desktop
Remote Powershell

Remote desktop (requires further configuration)
Remote Powershell (requires further configuration)
Configuration Manager
Update OS
Windows Update
Windows Update
App update
Windows Store
Windows Store
Configuration Manager
Account Config
Teams admin center
Teams admin center
Access logs
Teams admin center
Teams admin center

Configuring Group Policy for Microsoft Teams Rooms

This section covers system settings that Microsoft Teams Rooms depends on to function properly. When joining Microsoft Teams Rooms to a domain, ensure that your group policy doesn't override the settings in the following table.

Setting Allows
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon AutoAdminLogon = (REG_SZ) 1
Enables Microsoft Teams Rooms to boot up
Power Management -> On AC, turn screen off after 10 minutes
Power Management -> On AC, never put system to sleep
Enables Microsoft Teams Rooms to turn off attached displays and wake up automatically
net accounts /maxpwage:unlimited
Or equivalent means of disabling password expiration on the local account. Failure to do this will eventually cause the Skype account to fail logon complaining about an expired password. Note that this impacts all local accounts on the machine, and thus failure to set this will also cause the administrative account on the box to eventually expire as well.
Enables Skype account to always log in

Transferring files using Group Policies is discussed in Configure a File Item.


When Microsoft Teams Rooms device is compatible with the next version of Windows 10 OS, the device automatically updates to the next version through Windows Update. Microsoft Teams Rooms device should not be upgraded to next release of Windows 10 manually or via enabling Windows Update for Business (WUFB) group policies “Select the Windows readiness level for the updates you want to receive” and "Select when Preview Builds and Feature Updates are received" through GPO. A device with these group policies enabled is known to run into issues with Windows 10 OS update by Microsoft Teams Rooms app.

Remote Management using PowerShell

You can perform the following management operations remotely by using PowerShell (see the table below for script samples):

  • Get attached devices
  • Get app status
  • Get system info
  • Reboot system
  • Retrieve logs
  • Transfer files (requires a domain-joined Microsoft Teams Rooms)


This functionality is off by default. You need to enable remote PowerShell for your environment on the Microsoft Teams Rooms system to perform the operations below. Refer to the documentation on Enable-PSRemoting for information about how to enable remote PowerShell.

For example, you can enable Remote PowerShell as follows:

  1. Sign in as Admin on a Microsoft Teams Rooms device.
  2. Open an elevated PowerShell command prompt.
  3. Enter the following command: Enable-PSRemoting -SkipNetworkProfileCheck -Force
  4. Open the Local Security Policy and add the Administrators security group to Security Settings > Local Policies > User Rights Assignment > Access this computer from the network.

To perform a management operation:

  1. Sign in to a PC with account credentials that have permission to run PowerShell commands on a Microsoft Teams Rooms device.
  2. Open a regular PowerShell command prompt on the PC.
  3. Copy the command text from the table below and paste it at the prompt.
  4. Replace <Device fqdn> fields with FQDN values appropriate to your environment.
  5. Replace <path> with the file name and local path of the master SkypeSettings.xml configuration file (or Theme image).

To Get Attached Devices

invoke-command {Write-Host "VIDEO DEVICES:" 
gwmi -Class Win32_PnPEntity | where {$_.PNPClass -eq "Image"} | Format-Table Name,Status,Present; Write-Host "AUDIO DEVICES:" 
gwmi -Class Win32_PnPEntity | where {$_.PNPClass -eq "Media"} | Format-Table Name,Status,Present; Write-Host "DISPLAY DEVICES:" 
gwmi -Class Win32_PnPEntity | where {$_.PNPClass -eq "Monitor"} | Format-Table Name,Status,Present} -ComputerName <Device fqdn>

Get App Status

invoke-command { $package = get-appxpackage -User Skype -Name Microsoft.SkypeRoomSystem; if ($package -eq $null) {Write-host "SkypeRoomSystems not installed."} else {write-host "SkypeRoomSystem Version : " $package.Version}; $process = Get-Process -Name "Microsoft.SkypeRoomSystem" -ErrorAction SilentlyContinue; if ($process -eq $null) {write-host "App not running."} else {$process | format-list StartTime,Responding}}  -ComputerName <Device fqdn>

Get System Info

invoke-command {gwmi -Class Win32_ComputerSystem | Format-List PartOfDomain,Domain,Workgroup,Manufacturer,Model
gwmi -Class Win32_Bios | Format-List SerialNumber,SMBIOSBIOSVersion} -ComputerName <Device fqdn>

Reboot System

invoke-command { Shutdown /r /t 0 } -ComputerName <Device fqdn>

Retrieve Logs

$targetDevice = "<Device fqdn> "
$logFile = invoke-command {$output = Powershell.exe -ExecutionPolicy Bypass -File C:\Rigel\x64\Scripts\Provisioning\ScriptLaunch.ps1 CollectSrsV2Logs.ps1
Get-ChildItem -Path C:\Rigel\*.zip | Sort-Object -Descending -Property LastWriteTime | Select-Object -First 1} -ComputerName $targetDevice
$session = new-pssession -ComputerName $targetDevice
Copy-Item -Path $logFile.FullName -Destination .\ -FromSession $session; invoke-command {remove-item -force C:\Rigel\*.zip} -ComputerName $targetDevice

Push an XML configuration file (or theme graphic)

$movefile = "<path>";
$targetDevice = "\\<Device fqdn> \Users\Skype\AppData\Local\Packages\Microsoft.SkypeRoomSystem_8wekyb3d8bbwe\LocalState\SkypeSettings.xml"; 
Copy-Item $movefile $targetDevice 

Software updates

By default, Microsoft Teams Rooms attempts to connect to the Windows Store to get the latest version of Microsoft Teams Rooms software, so the device will require regular internet access. Before contacting Microsoft with support issues, be sure the Microsoft Teams Rooms device is loaded with the latest version of the app.

By default, Microsoft Teams Rooms connects to Windows Update to retrieve operating system and USB peripheral device firmware updates, and installs them outside of configured business hours. You can configure business hours by signing into the administrator account and running the Settings app.

If you want to manage updates manually, and are unable to follow the normal procedure for Microsoft Store for Business to Distribute offline apps, you can acquire the appropriate APPX file and dependencies from the deployment kit (from the instructions to Configure a Microsoft Teams Rooms console) that can be used with Configuration Manager. The deployment kit release lags behind the store release, so it might not always match the latest available build.

To update using Powershell

  1. Extract the package from the installation MSI to a share the device can access.

  2. Run the following script targeting the Microsoft Teams Rooms devices, changing <share> to the device share as appropriate:

    Add-AppxPackage -Update -ForceApplicationShutdown -Path '\\<share>\$oem$\$1\Rigel\x64\Ship\AppPackages\*\*.appx' -DependencyPath (Get-ChildItem '\\<share>\$oem$\$1\Rigel\x64\Ship\AppPackages\*\Dependencies\x64\*.appx' | Foreach-Object {$_.FullName})

Admin mode and device management

Some management functions, like manually installing a private CA certificate, require placing the Surface Pro device in Admin mode.

Switching to Admin Mode and back when the Microsoft Teams Rooms app is running

  1. Hang up any ongoing calls, and return to the home screen.

  2. Select the Gear icon and bring up the menu (options are Settings, Accessibility, and Restart Device ).

  3. Select Settings.

  4. Enter the Administrator Password. The Setup screen will appear. If the device isn't domain-joined, the local administrative account (username "Admin") will be used by default. The default password for this account is 'sfb', change the password as soon as possible. If the machine is domain-joined, you can sign in with an appropriately privileged domain account.

  5. Select Windows Settings in the left column.

  6. Choose Go to Admin Sign-in.

  7. Enter the Administrator Password. This will gracefully log off the app and take you to the Windows login screen.

  8. Log in to the desktop with your administrative credentials. You'll have the necessary privileges to manage the device.

  9. Perform the necessary administrative tasks.

  10. Sign out from the Admin account.

  11. Return to Microsoft Teams Rooms by selecting the user account icon on the far left side of the screen and then selecting Skype.

    If the Skype user is not listed, you might have to select other user and enter .\skype as the user name, and sign in.

The console is now back in its normal operation mode.The following procedure requires you to attach a keyboard to the device if one is not already attached.

Switching to Admin Mode and back when the Microsoft Teams Rooms app crashes

  1. Press the Windows key five times in rapid succession. This will bring you to the Windows logon screen.

  2. Log in to the desktop with your administrative credentials.

  3. Perform the necessary administrative tasks.

  4. Restart the machine when you're finished.


    This method doesn't log the Skype user off or gracefully terminate the app, but you'd use it if the app wasn't responding and the other method wasn't available.

    The console restarts into its normal operation mode, running the Microsoft Teams Rooms app. You can remove the keyboard, if it was attached to allow you to perform this procedure.

    Troubleshooting tips

  • Meeting invitations might not appear when sent across domain boundaries (for example, between two companies). In such cases, IT admins should decide whether to allow external users to schedule a meeting.
  • Microsoft Teams Rooms doesn't support Exchange AutoDiscover redirects via Exchange 2010.
  • In general, it's a good practice for IT admins to disable any audio endpoints they don't intend to use.
  • In the event that a mirror image is displayed in room preview, the IT admin can correct by cycling camera power or flipping the image orientation using the camera remote control.
  • Loss of console touchscreen access has been known to occur. In such cases, the issue is sometimes resolved by restarting the Microsoft Teams Rooms system.
  • Loss of local audio when connecting a PC to console via wired ingest has been known to occur. In such cases, restarting the PC can resolve the local audio playback issue.