Configure a Skype Room Systems v2 console
This article describes how to set up the Skype Room Systems v2 console device and its peripherals.
You should only perform these steps if the necessary Skype for Business and Exchange accounts have already been created and tested as described in Deploy Skype Room Systems v2. You will need the hardware and software described in Skype Room Systems v2 requirements. This topic contains the following sections:
Skype Room Systems v2 will only work in a properly configured Skype for Business environment where the device accounts are set up correctly as described in Deploy Skype Room Systems v2.
Prepare the installation image
Installing the Skype Room Systems v2 app on a Surface Pro 4 or Surface Pro requires a USB storage device with at least 32GB of memory formatted as a FAT32 disk. There should be no other files on the device, any existing files on the USB storage will be lost.
Failure to create your console image according to these instructions will likely result in unexpected behavior. Windows 10 Enterprise Anniversary Update (Version 1607) is no longer supported for Skype Room Systems v2 image creation.
An existing Skype Room Systems v2 with Windows 10 Enterprise Anniversary Update moving to Skype Room Systems v2 update 3 by way of the Windows Store will work, but a new installation should be done as described below.
- Download the MSU for KB4056892.
- Download the CreateSrsMedia.ps1 script.
- Place the MSU for KB4056892 in the same directory as the CreateSrsMedia.ps1 script.
- Run the CreateSrsMedia.ps1 script from an elevated prompt on a Windows 10 machine.
Follow the script's instructions to create a Skype Room Systems v2 USB setup disk. When finished, remove the USB disk from your computer and proceed to Install Windows 10 and the Skype Room Systems v2 console app .
Install Windows 10 and the Skype Room Systems v2 console app
You now need to apply the image you've created. The tablet will run as an appliance and the default user will be set to only run the Skype Room Systems v2 app.
The tablet should be connected to a power source. Start from a completely powered-off state. If necessary, press and keep pressing the Power button until the tablet switches off.
Plug your USB Setup disk into the tablet.
Press and continue to hold the volume down (-) button on the tablet.
Press and release the power button on the tablet.
Once Windows setup is booted, release the volume down (-) button.
The system will shut down once installation is complete.
After the system has shut down, it is safe to remove the USB Setup Disk. At this point, you can place the tablet in the dock and attach the peripherals needed for your meeting room. Refer to the manufacturer instructions.
Selecting a language in Creator's Update
In Creator's Update, you will need to use the ApplyCurrentRegionAndLanguage.ps1 script in scenarios where implicit language selection does not provide the user with the actual application language they want (e.g., they want the app to come up in French, but it's coming up in English).
The following instructions work only for devices created using Windows Creator's Update. Legacy/in-market systems that have not been re-imaged properly to the new provisioning system will not be able to use these instructions, but should also not suffer from the initial issue that requires this manual intervention (Anniversary Edition let you pick your app language explicitly as part of setup).
To apply your desired language
Switch to Admin mode.
Select the Start menu.
Select the gear icon to launch the Settings app.
Select Time & language.
Select Region & language.
Select Add a language.
Select the language you wish to add.
Select the language you just added to the "Languages" list.
Select Set as default.
For any languages you wish to remove:
a. Select the language you wish to remove.
b. Select Remove.
Start an elevated command prompt.
Run the following command:
powershell -executionpolicy unrestricted c:\Rigel\x64\scripts\provisioning\scriptlaunch.ps1 ApplyCurrentRegionAndLanguage.ps1
Restart the system.
Your desired language is now applied to the Skype Room Systems v2 device.
Initial set up of the Console
After Windows is installed, the Skype Room Systems v2 app will go into its initial Setup process when it is started next or if the /reboot option was chosen.
The User Account screen appears. Enter the Skype sign-in address (in user@domain format) of the room account to be used with the device.
Enter the password for the room account, and re-enter it to verify.
Under "Configure Domain," set the FQDN for the Skype for Business Server. If the Skype for Business SIP domain is different from the Exchange domain of the user, enter the Exchange domain in this field.
Select the indicated devices on the Features screen and click Next. The default is to have Auto Screen sharing set to On and Hide meeting names set to Off. The devices to select are:
Microphone for Conferencing: the default microphone for this conference room.
Speaker for Conferencing: the default speaker for conferencing.
Default Speaker: the speaker used for audio from the HDMI ingest.
Each item has a drop-down menu of options to select from. You must make a selection for each device.
The app should immediately start signing in to Skype for Business Server 2015 with the credentials entered above, and should also begin syncing its calendar with Exchange using those same credentials. For details on using the app, refer to the Skype Room Systems version 2 help.
Skype Room Systems v2 relies on the presence of certified console hardware (the Logitech SmartDock). Even a correctly created image containing the Skype Room Systems v2 app loaded on a Surface Pro 4 or Surface Pro will not boot past the initial setup procedure unless the console hardware is detected.
Some non-English language users may need a physical keyboard connected to the Console during initial setup in the event that symbols are not supported on the touch keyboard.
Install a private CA certificate on the tablet device
The Skype Room Systems v2 device needs to trust the certificates used by the Skype for Business and Exchange servers it connects to. For O365 this is done automatically, since these servers are using public Certificate Authorities and these are automatically trusted by Windows 10. In a case where the Certificate Authority is private, for instance an on-premises deployment with Active Directory and the Windows Certificate Authority, you can add the certificate to the Skype Room Systems v2 device in a couple of ways:
You can join the device to Active Directory and that will automatically add the required certificates given the Certificate Authority is published to Active Directory (normal deployment option).
You can install the certificate manually after the imaging process. Before you do this, you must complete Initial set up of the Console .
To manually install the certificate
Download the CA certificate to your computer and save it to "C:\Skype Room Systems\x64\Scripts\Provisioning\CAcertificate.cer".
Place the Surface 4 in admin mode (see Admin mode and device management).
Run the following command:
certutil -addstore -f -enterprise root "C:\Skype Room Systems\x64\Scripts\Provisioning\CAcertificate.cer"
Join an Active Directory Domain (Optional)
You can join Skype Room Systems v2 devices to your domain. Skype Room Systems v2 devices should be placed in a separate OU from your PC workstations because many workstation policies are not compatible with Skype Room Systems v2. A common example are password enforcement policies that will prevent Skype Room Systems v2 from starting up automatically. For information about the management of GPO settings, please refer to Manage Skype Room Systems v2.
To join Skype Room System v2 to a domain
Sign into the console from the admin account (see Admin mode and device management).
Launch elevated Powershell command prompt.
Enter the following command in Powershell:
Add-Computer -DomainName <Fully qualified domain> -OUPath "OU=<Child OU>, … ,OU=<Top level OU>,DC=<child domain>,…,DC=<top level domain>"
For example, if your fully qualified domain is redmond.corp.microsoft.com and you want your Skype Room Systems v2 devices to be in a "Skype Room Systems v2" OU that is a child of a "Resources" OU, the command will be:
Add-Computer -DomainName redmond.corp.microsoft.com -OUPath "OU=Skype_Room_System,OU=Resources,DC=redmond,DC=corp,DC=microsoft,DC=com"
If you would like to rename the computer when joining it to a domain, use the -NewName flag followed by the computer's new name.
Skype Room Systems v2 Deployment Checklist
Use the following checklist while doing a final verification that the console device and all its peripherals are fully configured:
||Room account name and phone # (if PSTN enabled) are correctly displayed in top right of console screen
||Windows computer name is set correctly (useful for remote administration)
||Administrator account password set and verified
||All Surface Pro 4 or Surface Pro System Updates have been applied
||Camera peripheral firmware version is correct (if applicable)
||Camera functional and positioned optimally
||Settings for Playback Default Device and Playback Default Communications Device set to intended audio peripheral
||Settings for Recording Default Communication Device set to the intended audio peripheral
||Audio peripheral firmware version is correct (if applicable)
||Audio input device functional and optimally positioned
||Audio output device functional and optimally positioned
||Cables are secure and not pinched
||Audio ingest over HDMI is functional
||Video ingest over HDMI is functional
||Dock can swivel freely
||Display brightness is acceptable for environment