SCOM Review

The reports provide high-level summaries and detailed information about your systems and can be e-mailed on a specified schedule or simply exported and printed out.


What is most valuable?

One of the most important features of SCOM is the Reporting Server role which runs on the SQL Server Reporting Services (SSRS). It’s responsible for rendering and scheduling reports. With Operations Manager, you have extract reporting capabilities and multiple report libraries that you can select from to customize reports to your own granular requirements.

It will help you to visualize the data in your environment. The reports provide high-level summaries and detailed information about your systems and can be e-mailed on a specified schedule or simply exported and printed out. The reporting server performs queries against the Operations Manager data warehouse database and returns the results in a number of easy-to-read formats.

Another point, you can import management packs available for Microsoft products, which you can customize thresholds of several counters of each product. Also, you can create your management pack and define your customizations.

How has it helped my organization?

This tool could be improved especially for tasks for our Capacity Planning Team and Monitoring Team. The Capacity Planning Team collect data through the reports from the Operations Manager for the memory, CPU and disks during the month. The use this to make dashboards to show their customers about their environment. With this, it’s possible to show environment of each customer.

For the Monitoring Team, it helps monitor a simple and complex environment in IT sending determinate alerts. For example, if your team receives a determined kind of alert, they will work on the solution before that problem occurs. Through the Operations Console, the Monitoring Team can see critical and warning alerts and if necessary, dispatch for a responsible team is the Database Team, Operating System Team or Exchange Team, etc. It’s clear that it's also possible to send alerts creating split groups for Database Team, Operation System Team, and send alerts for the respective products to the team responsible. It depends on each organization.

What needs improvement?

I think that it should be made possible to monitor private systems, which are developed in each company. In my opinion, this option already exists in SCOM 2012, however we have a lack of resources to develop this.

For how long have I used the solution?

In this company, SCOM has been in place since 2006, starting with MOM in 2005 and after that, it was upgrade to SCOM 2007.

I've used it to monitor several Microsoft Servers, which I've customized thresholds to support in Exchange, File Servers, SQL Servers, Clusters and others products.

What do I think about the stability of the solution?

I had issues with SCOM 2007 and MOM 2005, regarding the view of alerts in the Console Operations. It delayed showing critical alerts to the monitoring Team, because they could not see alerts in the Operations Console. For this kind of issue, I had issues with database maintenance as well.

How are customer service and technical support?

I have a contact at Microsoft Premier, and I find it necessary to us them to open a case with Microsoft, if they think that it's possible to fix the issue.

Which solution did I use previously and why did I switch?

In another company, I’ve had experience with BMC Patrol, Tivolli and SiteScope as NETQoS products, but this tool I’ve worked with administration.

How was the initial setup?

There were no issues with setting up SCOM.

What other advice do I have?

Follow the best practices and there should be no issues.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email