Plan Skype Room Systems v2 management with OMS

Skype for Business Server 2015
 

Topic Last Modified: 2017-03-20

This article discusses planning considerations for using Operations Management Suite to administer Skype Room Systems v2 devices in your Skype for Business Server 2015 implementation.

Operations Management Suite (OMS)is a collection of management services that were designed in the cloud from the start. Rather than deploying and managing on-premise resources, OMS components are entirely hosted in Azure. Configuration is minimal, and you can be up and running literally in a matter of minutes. With some customization work, it can aid in managing Skype Room System v2 (SRS) conferencing systems by providing real-time notifications of system health or faults for individual room systems, and it can potentially scale up to managing thousands of SRS conference rooms.

This article provides a discussion of the requirements, design/architecture, and implementation best practices needed to implement OMS management of SRS conference devices, and provides links to detailed articles on implementing OMS management for SRS and critical reference information for ongoing OMS management of SRS rooms.

diagram of SRS management using OMS

The SRS app on the console device writes events to its Windows Event Log. An OMS agent, once installed, passes the information to OMS.

Once properly configured, OMS parses the JSON payload embedded in the event descriptions to describe how each SRS system is functioning and what faults are detected.

An administrator using OMS can get notifications of SRS systems that are offline or are experiencing app, connectivity, or hardware failures as well as knowing if a system needs to be restarted. Each system status is updated every five minutes, so these notifications are close to real-time updates.

You must have a valid subscription for OMS to use this feature. See Get started with a Log Analytics workspace to create a subscription for your organization.

You should familiarize yourself as necessary on how to use the OMS View Designer. See Views in Operations Management Suite (OMS) management solutions for those details.

  1. Once subscribed to OMS, create custom fields (described in Map custom fields) needed to parse the information that will be sent from SRS consoles. This includes understanding the JSON schema documented in Telemetry Event Schema.

  2. Develop an SRS management view in OMS (see Define the SRS v2 views in OMS) using the View Designer mentioned earlier.

Each SRS console is an app running on a Surface 4 device in kiosk mode (normally, it's configured to be the only app that can run on the device). As with any Windows app, the SRS app writes events like startup and hardware faults to the Windows Event Log. Adding an OMS agent on your SRS v2 device allows these events to be collected by OMS. (See Connect Windows computers to the Log Analytics service in Azure for details.)

While using OMS to manage your SRS conference devices, you'll need to understand the information contained in the event logs used by OMS. See Telemetry Event Schema for details on these health messages.

 
Show: