We just raised a $30M Series A: Read our story

Schedule a 30-minute demo or reference call with a real user from the PeerSpot community. Available only to members that are in a buying process for this product and have contributed a review that's then published.

SCOM OverviewUNIXBusinessApplication

SCOM is #1 ranked solution in top Event Monitoring tools and #9 ranked solution in best Network Monitoring Tools. IT Central Station users give SCOM an average rating of 8 out of 10. SCOM is most commonly compared to Zabbix:SCOM vs Zabbix. The top industry researching this solution are professionals from a computer software company, accounting for 27% of all views.
What is SCOM?
System Center Operations Manager provides infrastructure monitoring that is flexible and cost-effective, helps ensure the predictable performance and availability of vital applications, and offers comprehensive monitoring for your datacenter and cloud, both private and public.

SCOM was previously known as System Center Operations Manager, SCOM 2012.

SCOM Buyer's Guide

Download the SCOM Buyer's Guide including reviews and more. Updated: November 2021

SCOM Customers
Dialog Telekom
SCOM Video

Pricing Advice

What users are saying about SCOM pricing:
  • "It is more expensive than the competition."
  • "Our Enterprise Agreement includes the price."
  • "We have an EA with Microsoft, and it comes as part of the EA."
  • "SCOM is part of the System Center suite and I am satisfied with the pricing."

SCOM Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
MB
Manager at a financial services firm with 1,001-5,000 employees
Real User
Top 20
Feature rich, scalable and user-friendly, but open-source products are free and do the same thing

Pros and Cons

  • "It is a user-friendly product that requires almost no maintenance."
  • "It would be a much better product if Microsoft provided management packs with the product."

What is our primary use case?

We are using SCOM for service monitoring integrated with some third-party dashboard. It is our end-to-end service monitoring solution.  

What is most valuable?

The feature I like most about SCOM is that it is easy-to-use. I find it very user-friendly. I also like the knowledge base which it has. You can find the resolution to questions or issues directly within the SCOM itself. It will alert you with a recommendation of what you need to do at the same time. This sort of self-diagnosis or prompting is one of the great values you get from SCOM compared to other solutions.  

What needs improvement?

The dashboard is one place where the product can be improved. We finally needed to get a customized dashboard from the NOC (Network Operation Center) team. The dashboard that was included with the product just did not do what we wanted it to do.  

I am not sure, exactly, what should be included with future releases. There are already a lot of features there in the product. The main thing I can suggest is that Microsoft also provides management packs for monitoring third-party products with the product. If that were included with SCOM, that would make the product even greater. For example, to monitor an Oracle database, you need to look around to get a management pack separately. It could just be included instead.  

You can monitor any non-Microsoft product with Microsoft SCOM if you have the management pack for that product. You need to purchase that management pack. You can get them sometimes from Microsoft and other times from the third-party vendor.  

For how long have I used the solution?

I have been using System Center Operations Manager (SCOM) from Microsoft for almost five years.  

What do I think about the stability of the solution?

From the time we did the configuration, the product has been stable. It may be different in other cases. It really depends on the design you implement. If you want to add functionality, you can add it. It depends on the business. If you want Apache or you want a singular-server implementation you configure it as you need to. If it is configured correctly it should remain stable.  

What do I think about the scalability of the solution?

SCOM is scalable. We do not have an issue with the number of users or with the number of machines and the devices we are monitoring. It does not have any issues in that respect.  

We support the product with a system admin team which is the only group that deals with SCOM directly for maintenance issues. Right now, the team is only five people. Even there, these five people do not use the product on a daily basis. The configuration is something that you do one time if you do it correctly. There is monitoring, which is done by the NOC team and that is ongoing. 

In case some maintenance is required like a change in business requirements or addition of services, then the SCOM team will do it. This does not happen all the time. But monitoring is done by another team separate from the maintenance.  

How are customer service and technical support?

We have not had to use the Microsoft support since maybe four or five years ago. It was during the time we were doing the implementation. We had a few calls with them — maybe two or three calls — for some configuration-related questions. That was all. It was handled efficiently and we got the answers we needed. But we have not had to use the support team since.  

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

I have had the opportunity to use other products in this category. Not at the current organization, but in other organizations before this. One was WhatsUp Gold. If I were to compare these two solutions, SCOM has more advantages and is really the better product.  

How was the initial setup?

It is actually pretty simple to do the setup. I think it really can be implemented on the same day that you get it. You can do the complete installation and configuration in one day.  

But adding services, that takes time. It depends on the business and your scope, what you need to add, what you need to configure when it is added. I consider that as a separate part because it is not the fault of the product that you have additional requirements. The additions made for service monitoring depends on the customer, the requirements that they have, and what they need to add.  

What about the implementation team?

The installation was done by our company with an in-house team. We did not need help from the vendor or an integrator except for some basic questions.  

We do maintenance as required also in-house and we handle the upgrades from one version to another version. All those maintenance details are managed by the system admin team.  

What's my experience with pricing, setup cost, and licensing?

If you compare the pricing of SCOM to some solutions now available — like ManageEngine — I think it is a bit more expensive. But at that price, you get more in Microsoft System Center. SCOM is a bundled product, it is not only SCOM. You get a complete suite of Microsoft System Center products. There are five products in the bundle. There are no additional costs for SCOM itself and everything is included in the license. The only additional costs that you may have is in getting management packs.  

On the other hand, open-source solutions are available that are mature or maturing and they are very good. They may pose a better solution because they are free.  

What other advice do I have?

My advice to people who are looking for a solution like SCOM would actually be to advise them to move from licensed software to open-source. You can go to Nagios or most other open-source products and they do the same thing as SCOM. There is no need to pay additional money to get the same services.  

On a scale from one to ten where one is the worst and ten is the best, I would rate SCOM as a seven-out-of-ten. It is a good product, but so are the free open-source products it competes with.  

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.
Zahari Zahariev
Information Technology Auditor at a financial services firm with 10,001+ employees
Real User
Top 20
Has good capacity and ability to send notifications but lacks agentless monitoring

Pros and Cons

  • "Availability monitoring is the feature I have found most valuable, as well as the capacity and ability to send notifications."
  • "In terms of features that could be improved, I would say the agent integration into the operating system. We are having difficulties integrating Linux into some of the networking devices."

What is our primary use case?

My primary use case for SCOM is to monitor service availability and performance, such as operating systems. We also integrate some Linux based operating systems to monitor our databases. We also monitor the Microsoft Exchange. We are having some difficulties in the case of the monitoring a couple of our networking devices, so I wouldn't say that monitoring networking devices is also part of the primary use cases. 

I also have Internet Information Server and Application Service from Microsoft Monitor.

What is most valuable?

Availability monitoring is the feature I have found most valuable, as well as the capacity and ability to send notifications. There is a mechanism to set up a notification from the SCOM and whenever there is a drop in the availability the notification alerts not only for availability but for other issues as well.

You can align thresholds according to the speed of your environment and you can have a threshold related notification, which is one of the useful features.

What needs improvement?

In terms of features that could be improved, I would say the agent integration into the operating system. We are having difficulties integrating Linux into some of the networking devices. We have not seen the collected data so it makes it challenging.

I would also say that agentless monitoring needs to be included. Something like this is pretty difficult if you don't have a particular agent.

It's not so easy if you have to use something like a proxy to implement a work around. They should include a solution for discovering devices and something like an agentless monitoring solution for a particular device - just to understand what your environment looks like.

I'm not saying that they should provide all the information for the device, but at least availability and partial monitoring based on SNMP. Because I know that other solutions have it. Maybe Service Center Operations Manager has already provided those things in the latest version, but I'm not familiar with it.

For how long have I used the solution?

I have been using Microcoft SCOM for roughly five years.

What do I think about the stability of the solution?

Our whole department that maintains SCOM is five people, so the IT department is pretty small and it's relatively integrated. Plus, we have only two dedicated System Administrators. Basically, a few people are doing many things.

We are doing the usual maintenance, patching, and updating. Alignment and configuration are also needed because we are trying to support a higher version of the application, Exchange 2016, with the previous 2012 version of Service Center Operations Manager. It's quite difficult and some type of maintenance is performed internally as we try to align as much as possible. 

Generally speaking, SCOM is stable from an operations point of view. Once it's set up and established and all the configuration is in place, there is no significant amount of time needed for stability or to support the availability of the solution itself. It's relatively simple to support.

What do I think about the scalability of the solution?

In terms of scalability, we increased the amount of supported devices from 50 to 150, but it's not a significant scale. I couldn't say yet how it would behave for a thousand or 2,000 devices.

We have a pretty simple setup for SCOM, we are not using any kind of clustering or virtualization.

How are customer service and technical support?

Microsoft support can vary. It's great for people that are used to other types of support. Meaning, software vendors usually provide a little bit more focused and dedicated Microsoft support teams. For general support, it's okay from my perspective. But to really understand the deep and the intense nature of your issue, it's a little bit tricky to get to that level.

Overall, technical support needs some alignment. The technical support should be separated from general support. They should start with the general support for people that are end-users or a single user in a simple environment. Then, to reach to the real technical integration-related support later because it's a little bit tricky. Usually, we use our integration partner as someone that is really dealing with those kinds of discussions with the vendor. But if you go directly as a single enterprise, it will be a little bit challenging.

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

In my previous work I had experience with Network Node Manager, a new solution from HP. It's more focused on agentless monitoring. Also, there is a capability for a monitoring device without any kind of agent installed, which is a little bit more professional. It's not the general solution for monitoring, so I wouldn't say that are comparable. My perception is that Microsoft is just focused on the software stack layer they provide. While Network Node Manager is more of an umbrella, it's much more focused on enterprise level devices and environments. So they should not be compared.

How was the initial setup?

As far as I can remember, the initial setup was pretty simple, but we started with pretty easy devices to monitor. We started with a couple of servers and almost all of them had the same version of the operating system. So it was simple to figure out how things were progressing.

I would say it took a couple of days or a week for the whole setup. It took about five days to install all the servers, and installation and all the integration, and the checks probably took a week.

What about the implementation team?

Initially we implemented on our own. But for a couple of integrations, we used integrators for support, especially for particular application servers and installations, Exchange and partially for SQL Server.

What other advice do I have?

My recommendation to anyone looking to use SCOM is that they should start with the latest version because it's pretty difficult to update later. From an operational perspective and regarding migrating many devices and whole environments, it's better to start with the latest version for Service Center Operations Manager.

On a scale of one to ten I would rate Microsoft SCOP 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.
Learn what your peers think about SCOM. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
555,139 professionals have used our research since 2012.
BW
Sr. Systems Engineer at Arapahoe County Government
Real User
Top 20
Easy to scale, offers helpful maintenance schedules, and free online training is available

Pros and Cons

  • "I like some of their newer features, such as maintenance schedules, because SCOM records SLA and SLO time."
  • "I would like to see them improve their network monitoring."

What is our primary use case?

We use SCOM for all server applications, as well as service monitoring, such as Windows services, and auto-recovery of those services if they fail. Some of the processes that we monitor at the .exe level can also be restarted with SCOM. Then we use it all to monitor availability, health, and performance.

What is most valuable?

Personally, I enjoy it all. It's fairly powerful.

I like some of their newer features, such as maintenance schedules, because SCOM records SLA and SLO time.

When we patch, things are automatically put into maintenance mode so that the numbers for our systems being down, do not count against us.

What needs improvement?

I would like to see them improve their network monitoring.

We use Solar Winds, and it has a direct interface into SCOM. We can see all the Solar Winds dashboards from the SCOM interface, which is nice to have.

For how long have I used the solution?

I have been involved with SCOM for seven years.

We just completed a major upgrade from 2012 R2 to 2019.

What do I think about the stability of the solution?

I have had a lot of success with the 2019 product. When we were on 2012 R2, I had to reboot the servers, particularly the database servers, at least once every two weeks. I believe we've been up and running for about three months in 2019 and have only rebooted once a month for monthly patching.

What do I think about the scalability of the solution?

The scalability is good. It's very easy to scale.

It can support up to a thousand nodes per management server, and we are nowhere near that number. I have three management servers in place for a 400-node network. Load balancing is simple, stable, quick, and efficient.

In terms of speed and agility, I believe it is significantly better than the 2012 version.

Our systems team and then the applications team, use this solution, totaling approximately 75 people within our government. We have 2,000 employees, and our IT department has about 100 people, and about 75 of them use it.

How are customer service and support?

For 2019, I haven't used technical support yet. I've never had to call him. 

In 2012, Microsoft's support was good.

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

We were using HP Open View at the time, and their technology was quickly becoming obsolete. They weren't keeping up, particularly when the 2012 operating system was released. They just couldn't keep up, and their pricing was spiraling out of control.

How was the initial setup?

It's quite complicated. I would call it complex.

On a scale of one to five, I would give it at least four or four and a half.

There are a lot of customizations, and it's quite noisy out of the box.

You have a lot of alerts, which is normal for most of them. 

I have tried some of the other monitoring systems as well, and they all seem to work in the same way. Basically, all you have to do is tune it. That is what requires time.

What's my experience with pricing, setup cost, and licensing?

Our Enterprise Agreement includes the price.

All of the Systems Center products have a backup, which we don't use, but SCCM is included in the pricing. As a result, we can afford it because we have the Enterprise agreement.

What other advice do I have?

We do use SolarWind, but I am not on that team; it is used by the network group.

I use the Operations Manager to manage my server infrastructure. 

The most important thing would be to go to Microsoft and get some training. They provide a lot of free classes in the form of webinars and other similar events. It has a multitude of different deliverables that most people never get into. 

It's a lot more powerful than people realize, and I believe people become dissatisfied with it because of the complicated setup, but once it's up and running, it's pretty amazing at what it can do.

I am pretty happy with the way it works right now, I would rate SCOM a nine out of ten.

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.
Flag as inappropriate
SA
Project Manager at a tech services company
Real User
Enables us to monitor our internal work

Pros and Cons

  • "The advantages of SCOM are that it is definitely user friendly and a more appropriate solution for what we need."
  • "I would like more customized reports. People should have some customization option on the dashboards for whenever they put multiple lists into it. Beyond customizing the content, there should be the ability to customize the colors so that they can engage some priority and mark challenges separately."

What is our primary use case?

We use it to monitor our internal work.

What is most valuable?

The feature I have found most valuable is the book feature. While we run the Sprint one we can add some setups for multiple sprints.

What needs improvement?

Some checking issues could be improved. Checking some activators. It would help if we could export in some cases, because it may be that some people want to move the screen from the book to share reports. If it was possible to embed it in a report, that would be good. In other words, I would like more customized reports.

I would definitely like to see the ability to go through the total life-cycle in the next release of SCOM, to cover everything. But in some cases, especially retrospectively, this is not happening, or not happening well. I'd like to see the retrospective outcome in the knowledge base. It would be good if it could accommodate some learning out of the box, together with information from the recording session. There are levels to it, but some of the records we keep often go to quickly deliver the project. But in most cases, they skip the retrospective part and lessons learned. It would be good to declare something in the knowledge base where people can easily put it and access their input of lessons learned. We've yet to see that in previous projects. But I'd like to get to the level where whenever a new person starts a project, they could visit the knowledge base and the retrospective section, and get some knowledge out of the box, which was not covered in the process.

On a scale of one to ten I would definitely rate SCOM an 8. That's because people should have some customization option on the dashboards for whenever they put multiple lists into it. Beyond customizing the content, there should be the ability to customize the colors so that they can engage some priority and mark challenges separately.

For how long have I used the solution?

I have been using SCOM for almost three years.

What do I think about the scalability of the solution?

There are less than 100 people in my organization using SCOM. It is not widely used in the company. Just some individuals from different departments.

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

Before SCOM we were using Microsoft Project or Excel. The advantages of SCOM are that it is definitely user friendly and a more appropriate solution for what we need.

How was the initial setup?

The initial setup did not take more than five minutes. It was activated in general, initially. 

What about the implementation team?

The setup was implemented with help from our internal colleagues.

What other advice do I have?

One thing I would recommend to anyone considering this solution is to give more people access to it so that whenever people want to use the solution they can get information from past experiences and what's currently going on. Say for example I raised one concern in your query box, I don't know how it's progressing because it doesn't record that. You should give some ticket number to it and update it. In other words, sharing feedback even on issues you are not directly working on.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
TM
Systems Engineer at a educational organization with 11-50 employees
Real User
Top 5Leaderboard
A cross-platform data center monitoring system with a valuable reporting feature

Pros and Cons

  • "Because it's Windows-based, it actually reports quite well. It reports everything you can think of on the Windows server and allows you to monitor anything. It's excellent for those in the Windows world as it's very good at it."
  • "The configurations could be better. There are multiple tests where you can do something, but they can be a trigger as well. The overriding methodologies are not that easy. The configurations are difficult. The configuration and thorough day-to-day operations to get them to the level you want takes some time. It's very difficult."

What is our primary use case?

We use it mainly for partitioning systems. All the systems' utilization and compute, uptime, and downtime. I also monitor a few applications through it.

What is most valuable?

Because it's Windows-based, it actually reports quite well. It reports everything you can think of on the Windows server and allows you to monitor anything. It's excellent for those in the Windows world as it's very good at it.

What needs improvement?

The configurations could be better. There are multiple tests where you can do something, but they can be a trigger as well. The overriding methodologies are not that easy. The configurations are difficult. The configuration and thorough day-to-day operations to get them to the level you want takes some time. It's very difficult.

I think certain things, like management packs, should also be built into the solution. They should be built into your installation or deployment so you can decide whether to keep them in the list of products that you want. You can just unpick the ones you don't want and install this with the latest management technologies. Installing the solution and then looking for management technologies and custom solutions, like your HP and the hardware, you have to go through an HPE port file to download that management pack and add it. I think their whole packaging of the software can be made a little bit easier.

For how long have I used the solution?

I have been using SCOM for about three years.

What do I think about the stability of the solution?

SCOM is a stable product. Once you get it off the ground, it's very stable.

How are customer service and technical support?

Technical support is fine. Not that I need it that much, but normally they do help.

How was the initial setup?

The initial setup is straightforward. But configurations and maneuvering around it and getting things to a level you want is very difficult. Installing and deploying it properly takes close to a week. It takes time to take out things that are just unnecessary. It also takes time to customize things according to the environment. You need to read a lot of documentation, even with the management packs. You need to go back to the documentation all the time.

It doesn't take many people to implement this solution. You have to know math and the Microsoft server platform for you to manage it properly.

What's my experience with pricing, setup cost, and licensing?

We have an EA with Microsoft, and it comes as part of the EA.

What other advice do I have?

If new potential users want to monitor a Windows platform or Microsoft Server-related platforms, I would recommend it. But if they want to manage anything else, they have to create a lot of custom things for them to work properly.

On a scale from one to ten, I would give SCOM an eight.

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.
Flag as inappropriate
NJ
SCOM Administrator at a government with 201-500 employees
Real User
Top 20
An extensible and versatile product with good community support

Pros and Cons

  • "The most valuable feature is the extensibility, as there are really no limits as to what you can do with it."
  • "The interface is a little bit cumbersome and certain actions could be simplified."

What is our primary use case?

Our primary use case is to monitor infrastructure and the Windows ecosystem. We also create distributed applications within SCOM to monitor our custom applications. It is deeply integrated into our systems.

What is most valuable?

The most valuable feature is the extensibility, as there are really no limits as to what you can do with it.

The fact that you can use PowerShell is a big plus.

What needs improvement?

SCOM has a lot of powerful features but it is not simple to use. We are using a third-party presentation layer to show all of the data because SCOM does not show it in a very nice and easy way. It is not an interface that you would expect to see in 2020. 

The interface is a little bit cumbersome and certain actions could be simplified. For example, many of the things that we do require clicking through many menus.

Maintaining this product is very hard to do.

For how long have I used the solution?

We have been using SCOM for about four years.

What do I think about the stability of the solution?

This product is quite robust.

What do I think about the scalability of the solution?

I don't have much experience in scaling out and adding more servers, although I think that it's fairly straightforward. It may not be great, but it's better than many products.

How are customer service and technical support?

I have not personally dealt with official technical support, but non-official support from various blogs and websites is excellent. There are a few bloggers that are really dedicated to the products, as they are Microsoft people, but this is not official support per se.

Overall, I would say that product support is good and better than expected.

How was the initial setup?

Deploying SCOM itself is of medium difficulty. I would say that it is not too easy and not too complicated. However, configuring all of the monitoring and all of the management packs is somewhat complex. It's an ongoing job and requires more than one person. Actually, in our case, it requires that everybody contribute.

If you want to configure SCOM to work properly and bring value to your organization, it is very hard, which is one of the bad things about it.

What's my experience with pricing, setup cost, and licensing?

SCOM is part of the System Center suite and I am satisfied with the pricing. The entire suite is expensive but it comes with a lot of functionality.

What other advice do I have?

Overall, I find that this is a good solution but the presentation layer is really bad. If the interactive part of the console were improved then it would be better.

I would rate this solution an eight out of ten.

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.
OmidKoushki
Solution Architect at KIAN company
Real User
Top 5Leaderboard
User friendly with lots or upgrade options and a straightforward initial setup

Pros and Cons

  • "They have great integration with the active directory."
  • "System Center just provided upgrade and update features for Windows clients, and Windows systems, and did not support Linux, Android, or iOS, and other operating systems. They need to provide better integration with other operating systems if they don't already."

What is our primary use case?

We are using the System Manager in a state university. They have around 1000 workstations and clients, that were using a System Center Configuration Management to upgrade only those clients and Windows servers, as well as the WHS server.

What is most valuable?

The solution is very user-friendly, and it offers upgrade options and updates features with a simple click.

I personally found the initial setup to be straightforward.

There are excellent simple options on offer.

They have great integration with the active directory. You can see active directory users in the System Center.

What needs improvement?

In recent years, no doubt it's improved. 

That said, at the time I used it, System Center just provided upgrade and update features for Windows clients, and Windows systems, and did not support Linux, Android, or iOS, and other operating systems. They need to provide better integration with other operating systems if they don't already.

The initial setup should be a bit more straightforward.

For how long have I used the solution?

I have experience working with the solution for about one year or so. I only have one experience with SCOM.

What do I think about the scalability of the solution?

At any given time, 10 members of the IT department, all engineers, would be working on the Assistant Manager Console.

How are customer service and technical support?

I never dealt with technical support in the past. I can't speak to how knowledgeable or responsive they are in general. 

How was the initial setup?

The initial setup was a very simple process. That said, in general, the installation process is not very straightforward, as you need to install it and then secure the server, and configure the database, and you need to provide different specific options in the configuration process. It can be a bit tricky. It should be improved to provide a straightforward installation.

What about the implementation team?

I handled the installation myself. I did not use a consultant or integrator. I was able to handle it in-house.

What's my experience with pricing, setup cost, and licensing?

I can't speak to the actual cost of the solution. It was more or less handled by the sales department. The licensing aspect was not my responsibility.

What other advice do I have?

We are using System Center 2016.

I'd rate the solution at an eight out of ten. It was mostly a very positive experience working with it.

I would recommend the solution to other users and organizations.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
KM
DevOps Engineer at a insurance company with 10,001+ employees
Real User
Top 5
Stable with good technical support but needs a better user interface

Pros and Cons

  • "We have found the scalability capabilities to be okay."
  • "The solution should be more user-friendly and offer a better user interface."

What is our primary use case?

We're using SCOM to monitor the health checks for the Windows servers in our organization.

What is most valuable?

It would be hard to talk about features. In maybe four months, in January, there is downtime for service, where we're able to look for the issues and proactively check everything.

The stability has been very good so far. 

Technical support has been very responsive.

We have found the scalability capabilities to be okay.

What needs improvement?

What we need in SCOM is the ability to share a lab console with our customers so that our end-users or customers in SCOM can navigate by themselves. It could be similar to how we use DRDG in PRTG where all of our customers can set up their monitoring on their own. Right now, in SCOM, only our team can set up their monitoring. 

The initial setup could be easier. 

The solution should be more user-friendly and offer a better user interface.

For how long have I used the solution?

I've been dealing with the solution for two years. 

What do I think about the stability of the solution?

The stability is very good. We haven't had any issues. It doesn't crash or freeze. There are no bugs or glitches. It's reliable.

What do I think about the scalability of the solution?

The scalability potential is good. If a company needs to expand it, it can.

How are customer service and technical support?

The technical support on offer has been great, generally. When we have questions for Microsoft, they respond to us quickly. It's good for our end. We are quite satisfied.

How was the initial setup?

The initial setup could be more straightforward and the deployment could be simplified in SCOM.

What's my experience with pricing, setup cost, and licensing?

In terms of pricing, I'm not sure how much the company pays. As far as I know, our company gets a Microsoft package and SCOM is already included in the package. It's not separated out.

What other advice do I have?

I'm just a customer and an end-user.

I'd rate the solution at a seven out of ten.

SCOM is a great monitoring tool. It's just pretty complex to set up, however, if you invest your time in learning SCOM, you can understand how it works and it will make things much easier.

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.
Flag as inappropriate
Buyer's Guide
Download our free SCOM Report and get advice and tips from experienced pros sharing their opinions.