Our client needed a solution outside of the native SCOM interface. The native web page was too slow for their needs and it required the users to understand how it worked before they could successfully use it. The fat client required too much processing power on the server side for the number of connections needed, and required some advance training or knowledge as well before it could be useful to the end users.

The solution we designed for them pulls data from the Microsoft Systems Center Operation Manager (SCOM) Web Services API and populates a tile grid with information obtained from the SCOM Web Service, but filters based on a list of rules defined by the client. Each tile is clickable and carries underneath it either another set of tiles, or a list of servers in the defined group. The tiles were designed to be easily understood by the end user with categories they were used to using and allowed interaction (both reading and writing) with SCOM without ever having to touch the native interface.

Once a server list is reached, the servers are listed in a grid style presentation with expandable rows for additional data, as well as indicators, text, and links to provide information on the errors or warnings associated with each server. Links are provided to triage and create tickets in the Service Desk application to begin work-flow processes.

The triage page for server alerts pulls the Knowledgebase articles and Context from the SCOM database and provides additional information to the technician or system admin to determine the cause and resolutions.

The ticket creation tool auto-populates the ticket data form with the alert data. The form code-behind attempts to find the owner of the application and other information to auto-fill fields in the form.