Manage Skype Room Systems v2

Skype for Business Server 2015
 

Topic Last Modified: 2017-09-20

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

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

With additional configuration, remote management is possible using Microsoft Operations Management Suite (OMS) as described in Plan Skype Room Systems v2 management with OMS, Deploy Skype Room Systems v2 management with OMS, and Manage Skype Room Systems v2 devices with OMS. You may also Manage a Skype Room Systems v2 console settings remotely with an XML configuration file, which includes applying a Custom display theme.

To collect logs, you must invoke the log collection script that ships with the Skype Room Systems v2 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.

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

noteNote:
A consumer TV used as a front of room display needs to support/enable the Consumer Electronics Control (CEC) feature of HDMI so that it can switch automatically to an active video source from standby mode. This feature is not supported on all TVs.

If Skype Room Systems v2 isn’t running well, performing a factory reset may help. This can be done in the Settings app from the “Recovery” tab. Beneath the “Reset this PC” header, select “Get started” followed by “Remove everything.” Follow the remaining prompts as desired to reset the device.

noteNote:
There is a known issue where the Skype Room Systems v2 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.

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

 

Workgroup

Not domain joined

Domain joined

Restart

Remote desktop

Remote Powershell

Remote desktop (requires further configuration)

Remote Powershell (requires further configuration)

SCCM

Update OS

Windows Update

Windows Update

WSUS

App update

Windows Store

Windows Store

SCCM

Skype Account Config

Not currently supported

Not currently supported

Access logs

Not currently supported

Not currently supported

   

This section covers system settings that Skype Room Systems v2 depends on to function properly. When joining Skype Room Systems v2 to a domain, please ensure that your group policy does not override the following settings:

 

Setting

Enables Skype Room Systems v2 to boot up

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon AdminAutoLogon = (dword) 1

Enables Skype Room Systems v2 to turn off attached displays and wake up automatically

Power Management -> On AC, turn screen off after 10 minutes

Power Management -> On AC, never put system to sleep

Enables Skype account to always log in

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.

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

You can perform the following management operations remotely 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 Skype Room Systems v2)

noteNote:
This functionality is off by default. You need to enable remote PowerShell for your environment on the Skype Room Systems v2 system to perform the operations below. Refer to the documentation on Enable-PSRemoting for information on how to enable remote PowerShell.

For example, you can enable Remote PowerShell as follows:

  1. Sign in as Admin on a Skype Room Systems v2 device.

  2. Launch an elevated PowerShell command prompt.

  3. Enter the following command: Enable-PSRemoting -force

To perform a management operation:

  1. Sign into a PC with account credentials that have permission to run PowerShell commands on a Skype Room Systems v2 device.

  2. Launch a regular PowerShell command prompt on your PC.

  3. Copy the command text from the table below and paste it into 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).

 

Operation

Commands

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 

By default, Skype Room Systems v2 will attempt to connect to the Windows Store to get the latest version of Skype Room Systems v2 software, so the device will require regular internet access. Be sure the Skype Room Systems v2 device is loaded with the latest version of the app, before contacting Microsoft with support issues.

By default, Skype Room Systems v2 will connect to Windows Update to retrieve OS as well as USB peripheral firmware updates and install 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 Skype Room Systems v2 console) that can be used with SCCM. The deployment kit release lags behind the store release, so it may not always match the latest available build.

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

Switching to Admin Mode and back when the Skype Room Systems v2 app is running
  1. Hang up any ongoing calls and return to the home screen.

  2. Click on 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.

    noteNote:
    If the device is not domain joined, the local administrative account (username "Admin") will be used by default. The default password for this account is 'sfb' but it is recommended that your organization change this for security reasons as soon as possible. If the machine is domain joined, you can sign in with an appropriately-privileged domain account.
  5. Click on Windows Settings on 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 will have the necessary privileges to manage the device.

  9. Perform the necessary administrative tasks.

  10. Sign out from the Admin account.

  11. Return to Skype Room Systems v2 by selecting the user account icon on the far left of the screen and select Skype.

    If the Skype user is not listed, you may 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 Skype Room Systems v2 app crashes
  1. Press the Windows key five times in rapid succession. This will bring you to the Windows logon screen.

  2. Log into the desktop with your administrative credentials.

    noteNote:
    This method does not log the Skype user off or gracefully terminate the app, but you would only use it if the app was not responding and the other method was not available.
  3. Perform the necessary administrative tasks.

  4. Restart the machine when you are finished.

The console restarts into its normal operation mode, running the Skype Room Systems v2 app. You may remove the keyboard if it was attached to allow you to perform this procedure.

  • Meeting invitations may not appear when sent across domain boundaries (for example, between two companies). In such cases, IT admins should decide whether or not to allow external users to schedule a meeting.

  • Skype Room Systems v2 does not support Exchange AutoDiscover redirects via Exchange 2010.

  • In general, it is a good practice for IT admins to disable any audio endpoints not intended for 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 Skype Room Systems v2 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.

 
Show: