One of the really cool features of Lync Server 2013 is the Lync Room System. LRS is comprised of a single or dual screen system, video camera, and control unit. This system provides for a rich conferencing experience by providing HD video, touch screens with white-boarding, audio & video inputs, and more. For more information on Lync Room system, see the Product Group’s blog post. To see the systems optimized for Lync, see the catalog.
Deploying a Lync Room System involves several steps, and is outlined (albeit poorly) in the LRS Deployment Guide. I say poorly because from a PowerShell perspective, the 10 steps outlined can be combined down to about 6. Some are Exchange related, some are Active Directory related, and some are Lync related.
What I’ve done is to automate & streamline the process, add a ton of error checking, optimization, and validation. Instead of picking an Exchange server, the script will automatically find and connect to Exchange. It then performs the following tasks:
- Create an Exchange mailbox configured as a room resource. Additionally, the description is defined, and the company name on the account is configured (see http://www.ehloworld.com/2266 for why this is important). The room account is enabled. You’re prompted for a password for the account, and that password must conform to the organizations’ password policy for complexity. If the mailbox already exists, which would be common in most scenarios, the script will handle it gracefully, ensuring it’s configured properly.
- The mailtip for the account is defined. It merely reminds users to make meeting requests a Lync meeting.
- Set calendar processing to AutoAccept so that when the room account is added to meetings, it will automatically accept the request.
- The AD account is enabled
- The Lync Meeting room is created, and uses the email address for the SIP address. This is important to avoid Exchange Web Services (EWS) issues.
- If a LineURI is defined, the meeting room is enterprise voice enabled. LineURI should be specified in E.164 format.
Any other configuration, such as conferencing policies, etc., can be set after the script runs. I’ve used this script to deploy a 70″ dual display SMART Room System.
See the assumptions section below for more info.
New-CsLyncRoomSystem.ps1 [[-Alias] ] [[-Name] ] [[-UPN] ] [[-SamAccountName] ] [[-RegistrarPool] ] [[-LineURI] ] [[-CompanyName] ] [-WhatIf] [-Confirm] 
New-CsLyncRoomSystem.ps1 -alias nycconfroom -name "New York City Conference Room" -upn "firstname.lastname@example.org" -registrarpool "frontendpool.contoso.com"
The SamAccountName only needs to specified if it needs to be different than the alias.
Execution Policy: Third-party PowerShell scripts may require that the PowerShell Execution Policy be set to either AllSigned, RemoteSigned, or Unrestricted. The default is Restricted, which prevents scripts – even code signed scripts – from running. For more information about setting your Execution Policy, see Using the Set-ExecutionPolicy Cmdlet.
- The SIP address is set to match the SMTP address. This is to avoid issues where the two don’t match and Exchange Web Services (EWS) calls fail.
- Exchange 2010 or 2013 exists in the environment
- The user running the script has the appropriate rights in Exchange (Recipient Management or higher) and Lync (RTCUniversalUserAdmin or higher)
- The machine that the script runs on has both the Lync and Active Directory modules installed.
v1.1 – 02-08-2014 – New-CsLyncRoomSystem.v1.1.zip
v1.0 – 01-28-2014 – New-CsLyncRoomSystem.v1.0.zip
See the changelog for information on what’s changed/included in each version.