Windows Teams Rooms PCs (Edge, Beta) — Device Setup Parameters

Monitor Windows-based Microsoft Teams Rooms PCs directly from the Xyte Edge over WinRM: PC model, Windows and Teams Rooms versions, and room peripherals.

🧪

Beta. The Windows Teams Rooms PCs (Edge, Beta) model is in beta: behavior and reported data may change, and it needs the beta Edge driver. Contact [email protected] before you claim your first PC, so your Edge gets the driver.

The Windows Teams Rooms PCs (Edge, Beta) model needs parameters entered in Xyte after the PC is claimed, and a one-time preparation on each PC. This page covers both.

Overview

The Xyte Edge can monitor Windows-based Microsoft Teams Rooms PCs directly on the local network. The Edge connects to each PC over WinRM (Windows Remote Management) and reads the data from the PC itself. No Microsoft cloud API or Teams Rooms Pro portal is involved.

Applies to: Windows-based Teams Rooms compute units, for example Crestron CCC-120-T and CCC-110-T.

Does not apply to: Teams Rooms on Android devices. Those are not monitored by this model.

What it reports

  • PC model, serial number and hostname
  • Windows version and build, and PC uptime
  • Microsoft Teams Rooms app version
  • Whether a room camera, microphone, speaker and touch panel are connected
  • Room peripherals that are in an error state

Only room peripherals count (USB, Bluetooth, and USB touch screens). The PC's built-in camera and display (HDMI) audio are ignored. On PCs with other onboard speakers or microphones, contact support so we limit monitoring to your room devices.

If a camera, microphone, speaker or touch panel is unplugged, Xyte opens a … disconnected incident. Devices that were last connected more than 7 days ago (old devices Windows still remembers) are not reported.

Read-only. The Edge only reads information from the PC (system details and the list of connected devices). It does not change settings, install software, or restart anything on the PC. There are no commands for this model.

Requirements

On each Teams Rooms PC:

RequirementDetails
WinRM enabledWinRM over HTTP, TCP port 5985 (default). See Using the HTTPS listener for HTTPS, TCP port 5986.
A dedicated local administrator accountA Windows account that is a member of the local Administrators group, used only by Xyte. You enter its username and password in Xyte.
LocalAccountTokenFilterPolicy = 1Needed only for local (non-domain) accounts. See step 3 below.
FirewallInbound TCP 5985 (or 5986) allowed from the Edge's IP address, in Windows Firewall and on any network firewall in between.

On the network, the Edge must be able to reach each PC on that port. See Edge networking.

📘

Why an administrator account?

The Edge opens a remote command shell over WinRM to read the PC's details and its device list. Windows allows that shell only to members of the local Administrators group. A member of Remote Management Users can sign in, but the shell fails with Access is denied. Reading the Teams Rooms app version also needs administrator rights.

📘

Authentication

The Edge authenticates with NTLM. You do not need to enable WinRM Basic authentication or unencrypted traffic, and we recommend leaving both disabled.

Prepare the PC

Run the following in an elevated PowerShell window (right-click PowerShell, Run as administrator) on each Teams Rooms PC.

1. Enable WinRM

Enable-PSRemoting -Force

This starts the WinRM service, sets it to start automatically, creates the HTTP listener on port 5985 and adds the Windows Firewall rule for it (winrm quickconfig does the same).

If the PC's network is set to the Public profile, the command stops with a network-profile error. Set the network to Private or Domain (recommended), or run:

Enable-PSRemoting -Force -SkipNetworkProfileCheck

With -SkipNetworkProfileCheck on a Public network, Windows accepts WinRM connections only from the PC's own subnet.

2. Create the Xyte account and give it the permissions

Create a dedicated local account for Xyte (the examples use xyte-monitor) with a strong password, and add it to the local Administrators group. Do not reuse the PC's built-in Admin account, and never use the Teams Rooms (Skype) auto-logon account.

$Password = Read-Host -AsSecureString "Password for xyte-monitor"
New-LocalUser -Name "xyte-monitor" -Password $Password -PasswordNeverExpires -AccountNeverExpires -Description "Xyte Edge monitoring (read-only)"
Add-LocalGroupMember -Group "Administrators" -Member "xyte-monitor"

To use a domain account instead, add it to the PC's local Administrators group (Add-LocalGroupMember -Group "Administrators" -Member "DOMAIN\account") and skip step 3.

3. Allow the local administrator account to connect remotely

Skip this step for a domain account. For a local account, Windows filters the administrator token on remote connections unless this value is set:

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" `
  -Name "LocalAccountTokenFilterPolicy" -PropertyType DWord -Value 1 -Force

This sets HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy to 1 (DWORD). It applies to every local administrator account on that PC, not only the one Xyte uses, so keep the firewall rule in step 4 limited to the Edge.

4. Allow port 5985 from the Edge only

Step 1 created the firewall rule Windows Remote Management (HTTP-In). Limit it to the IP address of the Edge, so no other machine on the network can reach WinRM on the PC. Replace 192.0.2.10 with your Edge host's IP address:

Get-NetFirewallRule -Name "WINRM-HTTP-In-TCP*" | Set-NetFirewallRule -RemoteAddress 192.0.2.10

If the rule does not exist on the PC, create it:

New-NetFirewallRule -Name "WINRM-HTTP-In-TCP-Xyte" -DisplayName "Windows Remote Management (HTTP-In) - Xyte Edge" `
  -Direction Inbound -Protocol TCP -LocalPort 5985 -RemoteAddress 192.0.2.10 -Action Allow

If a network firewall sits between the Edge and the PC, allow TCP 5985 from the Edge to the PC there as well.

5. Check the listener

winrm enumerate winrm/config/listener

The output should list a listener with Transport = HTTP and Port = 5985. To confirm the account works the way the Edge uses it, run this on the PC itself (it prompts for the password):

winrs -r:http://localhost:5985 -u:$env:COMPUTERNAME\xyte-monitor "powershell -Command (Get-AppxPackage -AllUsers -Name Microsoft.SkypeRoomSystem).Version"

A version number means the account works. Access is denied means step 2 or step 3 is missing.

Using the HTTPS listener (port 5986)

By default the Edge connects over HTTP on port 5985. WinRM over HTTPS on port 5986 is also supported. The PC needs a server certificate in the local machine store (its thumbprint goes in the listener command), an HTTPS listener, and a firewall rule for 5986:

$Cert = New-SelfSignedCertificate -DnsName $env:COMPUTERNAME -CertStoreLocation Cert:\LocalMachine\My
New-Item -Path WSMan:\localhost\Listener -Transport HTTPS -Address * -CertificateThumbPrint $Cert.Thumbprint -Force
New-NetFirewallRule -Name "WINRM-HTTPS-In-TCP-Xyte" -DisplayName "Windows Remote Management (HTTPS-In) - Xyte Edge" `
  -Direction Inbound -Protocol TCP -LocalPort 5986 -RemoteAddress 192.0.2.10 -Action Allow

The HTTPS port is not one of the parameters you enter in Xyte. To monitor over HTTPS (port 5986), contact [email protected] and we'll set your devices to use it. The Edge does not validate the listener's certificate, so a self-signed certificate works.

Security

  • Local network only. All WinRM traffic stays inside your local network, from the Edge to the PC. Nothing is exposed to the internet, and no inbound connection from outside your network is needed.
  • Read-only. The Edge reads system details and the list of connected devices. It never changes settings, installs software, or restarts the PC.
  • Use a dedicated account. Create an administrator account used only for Xyte monitoring, with a unique password on each PC. If you manage the account with a password-rotation tool such as Windows LAPS, update the password in Xyte after each rotation, or exclude this account from rotation.
  • Allow WinRM from the Edge only. Limit inbound TCP 5985 (or 5986) in Windows Firewall to the Edge's IP address (step 4), so no other machine on the network can reach WinRM on the PC.
  • Keep Basic authentication off. The Edge uses NTLM, so WinRM Basic authentication and unencrypted traffic can stay disabled.
  • Set LocalAccountTokenFilterPolicy only where it's needed. It relaxes the UAC remote restrictions for every local administrator account on that PC. Apply it only on PCs monitored with a local account, and skip it on PCs monitored with a domain account.

Username, Password

Applies to:

  • Windows Teams Rooms PCs (Edge, Beta)

Parameters

  • Username (required) — the account from step 2 (for a domain account, enter it as DOMAIN\account)
  • Password (required)
📘

On the device first

Complete Prepare the PC above: WinRM enabled, the account in the local Administrators group, LocalAccountTokenFilterPolicy set for a local account, and port 5985 open from the Edge.

The Add credentials dialog for this model shows exactly these fields:

Add credentials ✕
Username *
Password *
👁
CancelSave
⚠️

Account lockout

Windows can lock an account after repeated failed sign-ins, depending on the PC's account lockout policy. Check the username and password before saving them.

Where to enter them

  1. Claim the PC through your Edge as Windows Teams Rooms PCs (Edge, Beta). See Claiming a local network device (Edge).
  2. Enter the parameters. Both routes show the fields above, together with the model's setup instructions.

From the Devices table — select one or more PCs that need these same parameters (they show Missing Credentials), then click Add Credentials in the action bar. The button is enabled only when every selected device has identical requirements (usually the same model).

From the device page — open the device (it shows the isn't reporting data yet banner), then Manage → Edit device credentials.

For the full walkthrough of both routes, see Device Setup Parameters - Edge.

Once saved, the Missing Credentials flag clears. Within a few minutes the device page shows the PC's details. If it shows a Could not authenticate or Could not reach WinRM incident instead, see Troubleshooting.

Troubleshooting

  • Incident Could not authenticate - heartbeat monitoring only: the PC rejected the username or password. Fix the credentials in Xyte (Manage → Edit device credentials).
  • Incident Could not reach WinRM - heartbeat monitoring only: the PC answers ping but not WinRM. Confirm WinRM is enabled (step 1), the listener is running (step 5), and TCP 5985 is open from the Edge to the PC in Windows Firewall and on any network firewall in between (step 4).
  • Device online but no PC details, and no credentials incident: usually the account is not in the local Administrators group (step 2), or LocalAccountTokenFilterPolicy is missing for a local account (step 3). Membership in Remote Management Users alone is not enough. Run the check in step 5: Access is denied confirms it.
  • Incident Camera / Microphone / Speaker / Touch panel disconnected: no device of that kind is connected now, but one was in the last 7 days. Check the device's USB cable and power.
  • Enable-PSRemoting stops with a network-profile error: the network is set to Public. Set it to Private/Domain, or use -SkipNetworkProfileCheck (step 1).
  • A room device is missing from the list, or a built-in one is counted: only USB, Bluetooth and USB touch-screen room peripherals are counted; the PC's built-in camera and display audio are ignored. Contact support if your PC's onboard audio is counted as a room speaker or microphone.

For general Edge issues, see Troubleshooting Edge.


Did this page help you?