Build a Microsoft Teams Rooms image
This article describes how to build a Microsoft Teams Rooms image for mass deployment of Teams Rooms.
The following steps should only be used when creating a WIM-based image for mass deployment. If you are recovering individual devices, contact your Original Equipment Manufacturer (OEM) for support.
You should only perform these steps if the necessary Microsoft Teams or Skype for Business and Exchange accounts have already been created and tested as described in Deploy Microsoft Teams Rooms. You will need the hardware and software described in Microsoft Teams Rooms requirements. This topic contains the following sections:
- Prepare the installation media
- Install a private CA certificate on the console
- Install Windows 10 and the Microsoft Teams Rooms console app
- Initial set up of the console
- Microsoft Teams Rooms deployment checklist
Prepare the installation media
Installing the Microsoft Teams Rooms console app requires a USB storage device with at least 32GB of capacity. There should be no other files on the device; any existing files on the USB storage will be lost.
Failure to create your Microsoft Teams Rooms installation media according to these instructions will likely result in unexpected behavior.
The process below is for creating installation media to image new Microsoft Teams Rooms devices. Existing devices, by default, update automatically from Windows Update and the Windows Store.
The Windows 10 machine used to create the Microsoft Teams Rooms installation media must be on the same or later version of Windows as the target installation media.
- Download 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 Microsoft Teams Rooms USB setup disk.
Each time the CreateSrsMedia.ps1 script starts, the screen output will include the name of a log file or transcript for the session. If there are issues with running the script, make sure to have a copy of that transcript available when requesting support.
The CreateSrsMedia.ps1 script automates the following tasks:
- Download the latest MSI installer for Microsoft Teams Rooms.
- Determine the build of Windows that the user must supply. The most recently released versions may or may not be tested and supported for use with Microsoft Teams Rooms devices.
- Download necessary supporting components.
- Assemble the needed components on the installation media.
A specific version of Windows 10 is required, and this version is only available to volume licensing customers. You can get a copy from the Volume Licensing Service Center.
When finished, remove the USB disk from your computer and proceed to Install Windows 10 and the Microsoft Teams Rooms console app.
Install Windows 10 and the Microsoft Teams Rooms console app
You now need to apply the setup media you've created. The target device will run as an appliance and the default user will be set to only run the Microsoft Teams Rooms app.
If the target device will be installed in a dock (e.g., a Surface Pro), disconnect it from the dock.
Ensure the target device is not connected to the network.
Ensure the target device is connected to AC power.
Plug your USB setup disk into the target device.
Boot to the USB setup disk. Refer to the manufacturer instructions. If your target device is a Surface Pro, use the following steps to boot to the USB setup disk:
a. Press and continue to hold the volume down (-) button.
b. Press and release the power button.
c. 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 target device in its dock (if using a dock-based product), attach the peripherals needed for your meeting room, and connect to the network. Refer to the manufacturer instructions.
Software updates for Microsoft Teams Rooms are automatically downloaded from the Microsoft Store for Business. See Prerequisites for Microsoft Store for Business and Education to verify that the room console will be able to access the store and self-update.
Selecting a language
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 console app to come up in French, but it's coming up in English).
The following instructions work only for consoles created using Windows Creator's Update (Windows 10 20H1) or later.
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 Add a language.
Select the language you wish to add.
Install language features.
Do not check Set as my Windows display language.
Select the language you just added to the "Languages" list.
Set as default- Move up arrow to set 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 Microsoft Teams Rooms console.
Initial set up of the console
After Windows is installed, the Microsoft Teams Rooms app will go into its initial Setup process.
The User Account screen appears. Enter the Microsoft Exchange Resource account sign-in address (in user@domain format) of the room account to be used with the console.
Enter the password for the room account, and re-enter it to verify.
Select the supported meeting mode - Microsoft Teams Only, Skype for Business Only, or one of the two mixed-mode options. If necessary, enable Modern Authentication.
If using Skype for Business and if the Skype for Business SIP domain is different from the Exchange domain of the user, set the FQDN for the Skype for Business Server in the Advanced section. If you are not using Skype for Business or the SIP domain matches the Exchange domain, leave this section blank.
The Microsoft Teams Rooms app should signing in to Microsoft Teams or Skype for Business Server with the credentials entered above, and should also begin syncing its calendar with Exchange using those same credentials. For details on using Teams Rooms, refer to the Microsoft Teams Rooms help.
Microsoft Teams Rooms relies on the presence of certified console hardware. Even a correctly created image containing the Microsoft Teams Rooms console app will not boot past the initial setup procedure unless the console hardware is detected. For Surface Pro based solutions, the Surface Pro must be connected to its accompanying dock hardware to pass this check. For more information about supported hardware, see Microsoft Teams Rooms requirements.
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 console
The following only applies if connecting Teams Rooms to Skype for Business.
Microsoft Teams Rooms needs to trust the certificates used by the servers it connects to. 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 Microsoft Teams Rooms in a couple of ways:
You can join the console 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 console 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 Microsoft Teams Rooms to your domain. Microsoft Teams Rooms should be placed in a separate OU from your PC workstations because many workstation policies are not compatible with Microsoft Teams Rooms. A common example is a password enforcement policy that will prevent Microsoft Teams Rooms from starting up automatically. For information about the management of GPO settings, refer to Manage Microsoft Teams Rooms.
To join Microsoft Teams Rooms 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 Microsoft Teams Rooms consoles to be in a "Microsoft Teams Rooms" OU that is a child of a "Resources" OU, the command will be:
Add-Computer -DomainName redmond.corp.microsoft.com -OUPath "OU=Microsoft_Teams_Rooms,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.
Microsoft Teams Rooms deployment checklist
Use the following checklist while doing a final verification that the console and all its peripherals are fully configured:
|☐||Room account name and phone # (if PSTN enabled) are correctly displayed|
|☐||Windows computer name is set correctly (useful for remote administration)|
|☐||Administrator account password set and verified|
|☐||All firmware 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|
|☐||Console can swivel freely|
Submit and view feedback for