Configuring your Lync Server 2013 environment for the Lync Room System Administrative Web Portal
Topic Last Modified: 2014-05-22
To use the Lync Room System (LRS) Administrative Web Portal, you will need to install or configure the following prerequisites.
If the server is configured with both Kerberos and NTLM authentication, and LRS is running on a computer that is not joined to the domain, Kerberos authentication will fail and the user will not see the status of LRS in the administrative portal. To resolve this issue, configure the server with NTLM authentication or both NTLM and TLS-DSK authentication (without Kerberos), or join the LRS computer to the domain.
Install Lync Server 2013 Cumulative Updates: July 2013 in the Lync Server topology.
To get the update or see what’s included with it, see Updates for Lync Server 2013.
Create a SIP-enabled Active Directory user.
The LRS Administrative Web Portal uses these credentials to query information from Lync Server. The recommended username is LRSApp.
Create an Active Directory security group with name LRSSupportAdminGroup.
Create the group with Group Scope as Global and Group Type as Security. SIP enabled users who are added to this group will be authorized to see the list of rooms and execute certain commands, such as collecting logs.
Create an Active Directory security group with name LRSFullAccessAdminGroup.
Create the group with Group Scope as Global and Group Type as Security.SIP enabled users who are added to this group are authorized to use all admin portal functionality.
Add LRSFullAccessAdminGroup as a member of LRSSupportAdminGroup.
Create a SIP enabled Active Directory user with name LRSSupport. Add this user to LRSSupportAdminGroup.
Install ASP.NET MVC 4 for Visual Studio 2010 SP1 and Visual Web Developer 2010 SP1, available in the Microsoft Download Center at http://go.microsoft.com/fwlink/p/?LinkId=323967.
Send feedback about: