We use SCOM mostly for server performance monitoring in historical metrics.
Systems Engineer at a financial services firm with 1,001-5,000 employees
A cross-platform data center monitoring system with a useful historical reporting feature, but lacks real-time monitoring
Pros and Cons
- "I like the historical reporting of observer metrics."
- "It'll help if they can provide real-time or closer to real-time monitoring."
What is our primary use case?
What is most valuable?
I like the historical reporting of observer metrics. It's a fairly user-friendly solution.
What needs improvement?
It'll help if they can provide real-time or closer to real-time monitoring.
For how long have I used the solution?
I've been using SCOM for at least five years.
Buyer's Guide
SCOM
October 2024
Learn what your peers think about SCOM. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,562 professionals have used our research since 2012.
What do I think about the stability of the solution?
SCOM is a stable solution.
What do I think about the scalability of the solution?
SCOM is scalable, and it's easy to add resources.
How are customer service and support?
I believe we have had issues. I'm not the primary administrator of it, but in general, I think they've been able to get back to us relatively quickly.
What's my experience with pricing, setup cost, and licensing?
The pricing is good, and it's part of their system center suite. I believe we pay for the license on a yearly basis.
What other advice do I have?
I would tell people looking to implement this solution that it's great for any historical tracking. But if they're looking for real-time, within-the-minute monitoring of servers from a console, then I would say that it falls short there.
On a scale from one to ten, I would give SCOM a seven.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Technical Consultant at a tech consulting company with 51-200 employees
Deep integration with Windows provides in-depth monitoring and the management packs model ensures that products in the environment are supported or will be supported.
What is most valuable?
Deep integration with Windows provides in-depth monitoring and the management packs model ensures that products in the environment are supported or will be supported.
How has it helped my organization?
Proactive monitoring has helped us prepare and mitigate potential issues before they even happen. This comes in the monitoring of general server health and custom alerts for event log entries that are known indicators of potential issues.
What needs improvement?
GUI performance is the one aspect where I can see that improvement on it will make customers happy.
3rd Party Plugins for SCOM are also great, but some of them are quite expensive to implement due to the depth of function they provide. Maybe Microsoft should integrate the basic functionalities of some of them.
For how long have I used the solution?
I've used it for two years.
What was my experience with deployment of the solution?
The deployment of SCOM is pretty straightforward. You just need to make sure that the pre-requisites have been installed correctly and then SCOM itself should be a breeze to install.
What do I think about the stability of the solution?
Stability is subjective and based from experience. It is directly affected by the server hardware where SCOM is installed.
What do I think about the scalability of the solution?
No. SCOM is scalable as you can add Management Servers as needed. You can also add more resources to the host server and it will not cause issues in SCOM.
How are customer service and technical support?
Customer Service:
For enterprise customers, Microsoft is one of the best providers of customer service. The system in place for the customer service ensures that customers will get the value they have paid for.
Technical Support:As with the Customer Service, the technical support of Microsoft is very good since they are the ones who develop the product itself. It follows a process where you will be first served by level 1 support but they will escalate to the product team as need to ensure the issue is resolved.
Which solution did I use previously and why did I switch?
Free tools found online are good but require a lot of knowledge in scripting. The SCOM Management Packs takes in the lead in this space.
How was the initial setup?
It was straightforward. You just follow the setup guide provided but just need to make sure the pre-requisites are installed properly.
What about the implementation team?
I have experienced both as part of in-house team and also as part of the vendor team. The vendor was experienced in the deployment and management of SCOM and have been since the early versions of it.
What was our ROI?
We did not calculate the ROI as our SLA is internal only. However, the fact that we can proactively monitor issues that may cause downtime is a statement of the benefit of SCOM.
What's my experience with pricing, setup cost, and licensing?
Please contact your Microsoft Account Manager regarding this. It is different for each customer and for each country. The System Center licensing has different criteria and you should get the most applicable for your environment.
Which other solutions did I evaluate?
We have evaluated some of the "free" monitoring solutions. Some are easy to use while others are a bit complicated. We implemented SCOM because not only it was included in our System Center License, its usage was also straightforward.
What other advice do I have?
SCOM can monitor a whole lot of products, not just generic server components. Make sure that you contact the product vendor and ask if they have Management Packs for SCOM.
Disclosure: My company has a business relationship with this vendor other than being a customer: I have both been a user and a Systems Integrator for the System Center products.
Buyer's Guide
SCOM
October 2024
Learn what your peers think about SCOM. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,562 professionals have used our research since 2012.
BI Analyst at a tech services company with 11-50 employees
It can be implemented in an environment which hosts critical information.
Valuable Features:
We used SCOM for monitoring the health of the servers. The SCOM agent was very reliable in our environment and used to trigger alerts immediately, which helped us to take care of the servers without any critical impact to the client.
Improvements to My Organization:
SCOM has helped us to reduce the time taken to address the issue and identify the false alerts triggered in an efficient manner. It's a reliable tool when it comes to monitoring and can be implemented in an environment which hosts critical information and has high revenue for the organization.
Room for Improvement:
I feel that the stability of the tool has room for improvement and I would like to see that in the next version.
Deployment Issues:
We've had no issues with deployment.
Stability Issues:
There have been issues with instability.
Scalability Issues:
It has scaled for our needs.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Infrastructure Expert at a healthcare company with 501-1,000 employees
Good for Microsoft-centric environments.
Valuable Features:
Does a great job with Microsoft technologies. Decent with other technologies (Unix/Java).
Room for Improvement:
Very expensive now that you are forced to buy entire System Center suite, although comparable to other monitoring solutions that include basic APM. Dashboards are pretty weak.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Head of ICT at JAROLA
Enables us to monitor the system to check that it's healthy and running well
Pros and Cons
- "The solution is scalable. If you want to monitor more you have to buy more licenses, but you can add on. We don't plan to increase usage."
- "Of course, price is always an issue with Microsoft and could be improved."
What is our primary use case?
Our primary use case is to monitor if the system is healthy and running well.
What is most valuable?
The features we find most useful would be the automatic thresholds when disks are running full. If CPUs are causing high CPU load then we will be notified with triggers.
What needs improvement?
Price is always an issue with Microsoft and could be improved.
For how long have I used the solution?
I've been using the solution for two years.
What do I think about the stability of the solution?
The solution is stable. It's working fine.
What do I think about the scalability of the solution?
The solution is scalable. If you want to monitor more you have to buy more licenses, but you can add on. We don't plan to increase usage.
How are customer service and technical support?
I haven't called technical support yet.
Which solution did I use previously and why did I switch?
We had nothing essential in an enterprise managing console. This is relatively simple tooling, but we didn't have another solution on this scale.
How was the initial setup?
The initial setup was straightforward. Deployment wasn't that long. Maybe a couple of days. We needed half a day for the installation and then three to four days for implementing and configuring all the monitoring agents. Deployment is not a big job, so you just need one person and then after that, you just need someone for an hour a day on the system.
What about the implementation team?
Initial setup was done with a bit of additional support and then we added more and more services.
What other advice do I have?
It's a Microsoft product so if you are using a lot of other vendors, other operating systems, then it's less compatible. For us, we're 99% Microsoft so it's not an issue. On this solution, the things we monitor are fine and perhaps other users will want more, but for our purpose and what we use it for, it's enough.
Once it's completed, you only get triggered by emails and you can respond to those emails so when the system does its thing it's not that complex. It's very simple.
I would rate this solution eight out of 10.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical IT Manager at a engineering company with 1,001-5,000 employees
Performance data on Windows VMs is a valuable feature but perfomance management needs to be improved.
What is most valuable?
- Performance data on Windows VMs
- Ability to have a lot of out of the box management packs with key monitors in place
- Ease of use
How has it helped my organization?
Ability to know when servers are offline through agent heartbeats.
What needs improvement?
Dashboarding and application performance management.
For how long have I used the solution?
Three years.
What was my experience with deployment of the solution?
No we did not.
What do I think about the stability of the solution?
Yes we did have some, but with Microsoft's assistance (RAS) we were able to gain more insight and improve.
What do I think about the scalability of the solution?
No we did not.
How are customer service and technical support?
Customer Service:
8/10.
Technical Support:8/10.
Which solution did I use previously and why did I switch?
Used Foglight but it was extremely difficult to learn and pick up as a monitoring solution.
What about the implementation team?
It was all done in-house.
What's my experience with pricing, setup cost, and licensing?
Included as part of MS ELA.
Which other solutions did I evaluate?
Yes - Quest Foglight and Nimsoft
What other advice do I have?
If you are a large Microsoft shop then this product excels in monitoring Microsoft services.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior IT Consultant at a tech consulting company with 51-200 employees
My customers use it because they can more easily integrate it with their current Microsoft IT infrastructure, and because the monitoring power of SCOM is enough for servers, services and some apps.
Valuable Features:
I’m an IT consultant. My customers are using SCOM because they can more easily integrate it with their current Microsoft IT infrastructure, and because the monitoring power of SCOM is enough for servers, services and some apps. Some of my customers are monitoring their network devices with SCOM. More specialized monitoring for network devices require other tools (most of the time) like SolarWinds and/or Fluke, etc. My customers are using SCOM to avoid business disruptions.
Room for Improvement:
Microsoft SCOM can be improved about the way it is presented. Microsoft needs to train more people about how to sell SCOM (and other System Center family products) because there are a lot of emerging technologies that are replacing Microsoft. The vendor could create better training campaigns to avoid their replacement by other emerging technologies.
Other Advice:
Think about the cloud. Try to move everything (if it is possible) to the cloud. You will save a lot of money on monitoring themes because most of the cloud services include it, so you don’t have to worry about monitoring. (Azure is an example.)
Microsoft is currently more valuable because this brand is wide used. Microsoft is also cheaper than Riverbed’s APM offering, but it is a matter of time because there are another brands conducting successful marketing / testing / training campaigns to replace Microsoft.
Disclosure: My company has a business relationship with this vendor other than being a customer: We are Microsoft Partners (gold).
Director at a tech company with 501-1,000 employees
We see how IT teams are able to exert control and adapt quickly with it. Most of the time, a third-party tool is required for presentation.
Valuable Features:
Asset monitoring and auto alerts are the most valuable features of this product to me.
Improvements to My Organization:
We are a service provider of these solutions to our clients. And we can see the change, how the IT team were able to have control and adapt quickly with SCOM.
Room for Improvement:
The dashboard is still not so great and, most of the time, a third-party tool is required for presentation. There is a lot of room for improvement here.
Other Advice:
Thorough analysis of the current environment and the goals that need to be achieved should be defined (from an end-results point of view) before rolling out SCOM. If the groundwork is not properly done, SCOM implementation can cost the organization.
Disclosure: My company has a business relationship with this vendor other than being a customer: We are SMB partner for MS for these implementations.
Buyer's Guide
Download our free SCOM Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2024
Popular Comparisons
ServiceNow IT Operations Management
ScienceLogic
BMC TrueSight Operations Management
OpsRamp
IBM Tivoli NetCool OMNIbus
Zenoss Cloud
OpenText Operations Bridge
IDERA SQL Diagnostic Manager for SQL Server
OPS/MVS Automation Intelligence
IBM Tivoli NetCool Impact
Buyer's Guide
Download our free SCOM Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Do you think there is a minimum critical threshold that justifies the deployment of the System Center suite?
- What are the top pros and cons of SCOM?
- What is the difference between IT event correlation and aggregation?
- When evaluating Event Monitoring, what aspect do you think is the most important to look for?
- What questions should companies ask vendors when researching event monitoring solutions?
- What insider threat detection tool do you recommend to a company with a modest budget?
- Have you successfully migrated from a best-of-breed enterprise management/monitoring & automation/orchestration platform to the ServiceNow framework?
With 2007R2 we've done some basic monitoring: The out of the box disk and service monitoring, some text log monitoring and remote port monitoring for service availability of databases, WebSphere, etc. We're moving to 2012 soon and will expand on what we've currently done. Text log monitoring is supposed to be a little better (Monitors instead of just Rules via the MP templates), plus 3 state (green, yellow, red) disk instead of 2 state (green, red). Plus we're going to use the JMX monitoring. Today we're using Quest Management Extensions for WebSphere "monitoring" (mostly just perf stats collection).