SCOM Reviews

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.

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.

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.

I have been involved with SCOM for seven years.

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

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.

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.

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

In 2012, Microsoft's support was good.

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.

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.

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.

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.

Our primary use case for the solution is monitoring the health of our Windows servers. We deploy the solution on-premises.

The solution has improved our overrides and the ability to start services if they're stopped.

We have been using the solution for approximately one year and currently using the latest version, SCOM 2022.

The solution is stable. I rate it a ten out of ten.

The solution is scalable. I rate it a ten out of ten.

We have had a good experience with customer service and support. I rate them a ten out of ten.

The initial setup is straightforward.

We have not seen a return on investment.

I rate the pricing an eight out of ten. The price could be improved.

I rate the solution an eight out of ten. I recommend it for users considering implementing it and advise them to do some research.

We use SCOM for monitoring our servers in one place.

The most valuable features in SCOM are Azure monitoring and integration with Azure Monitor for monitoring Azure-hosted servers from SCOM on-premises.

In terms of improvement, direct integration with third-party tools, like ticketing systems, is lacking but would be beneficial.

I have been working with SCOM for a year.

SCOM is generally stable with occasional glitches, particularly during patching when downtime occurs. We provide DR services from one data center, which increases scalability but lacks redundancy. Overall, I would rate the stability at around nine out of ten.

I would rate the scalability of SCOM as an eight out of ten. In our company, we manage 500 servers using SCOM.

The technical support is good.

Setting up SCOM is straightforward. We decide on the number of servers to monitor, configure management servers and gateway services, and install SCOM using the setup executable. Onboarding servers involves scripting or installing the SCOM console, making the process easy with no complexity.

Compared to competitors like AppDynamics, SCOM is better for monitoring Microsoft services and roles. It has agent-based pricing, with no bulk license options, but generally reasonable.

SCOM improves system monitoring by centralizing server monitoring.

The alerting capabilities in SCOM are helpful for our organization. The notification feature works well and is beneficial for keeping us informed.

We use the default reporting tool in SCOM, which is Microsoft Server Reporting. It is user-friendly and integrates well with SCOM.

Integrating SCOM into our current IT environment was easy.

Overall, I would rate SCOM as a nine out of ten. I would recommend it to others.

We use SCOM for proactive monitoring that we code ourselves. We code it with a management pack, which is the actual logic of all monitoring experiences. We develop our own monitoring capabilities instead of using Microsoft's. We could use them as a base but always add extra deliverables with our own code.

The most valuable feature of SCOM is the capability of using classes within your management pack development.

The solution’s initial setup is difficult. SCOM should include more in-depth trend analysis.

I have been using SCOM for 15 years.

I rate SCOM an eight out of ten for stability.

More than 100 users are using SCOM in our organization. I rate SCOM ten out of ten for scalability.

It took one day to deploy SCOM.

We have seen a return on investment with SCOM, and the solution is worth its money.

SCOM's pricing is average.

I am using the latest version of SCOM. Users should do a POC for the solution.

Overall, I rate SCOM a nine out of ten.

I primarily use SCOM to monitor services, logins, devices, and workstations and get notifications when there's a problem.

SCOM's most valuable features are the network path feature, reporting, and integration with business intelligence.

SCOM's feature that notifies us when a server is down is not present in recent updates, which has weakened the product. In the next release, SCOM should add more and simpler integration with other software.

I've been using SCOM for eight years.

SCOM is stable.

SCOM is scalable, but it can be difficult if you don't fully understand the product.

Microsoft's technical support employs a lot of remote workers as support engineers. While some of them are very good, sometimes they can't handle the problems and will procrastinate until the time is up before referring you to someone else. This means that our time is wasted by people who are not technically sound and can't help with our problems.

Neutral

The initial setup is complex if you're using the cloud elements because not every part of SCOM works in the cloud, and some need to be integrated in different formats, which not everyone will know how to do. If everything is complete when you start the deployment, it will take an hour or two, but the cloud-based part will increase it to about six hours.

I implemented SCOM by myself.

SCOM is very cheap because it's included in the license for the System Center suite, which is around $8,400 per CAL. Support is initially free but will incur an additional fee once you exceed a certain level.

I would recommend SCOM to those using a Microsoft operating system, but those who don't would be better looking for another solution, like ServiceDesk. I would rate SCOM eight out of ten.

Our primary use case is to monitor the extensive system of services that we operate for clients.

SCOM (System Center Operations Manager) has helped improve our organization through reporting capabilities. The reporting is very good. We're an outsourcing company, so we provide services and manage service and as a service. We have a multi-service environment, so it is complicated to monitor and maintain. 

The alerting with SCOM is incredible. The product works well with multiple environment integration, and if there is an issue, the system forwards alerts to different service desk systems so that the issues are handled appropriately. There are actually numerous things the solution does for our company to automate processes, and, to top it off, it's a stable application.

I'm the operational manager for Business Connections Monitoring Toolsets. We do installations of this product. We do the configuration. We take care of changes in threshold if needed, and supply additional expertise for critical projects as needed. We monitor everything to be sure things continue to work optimally and do things like monitor hard drive space, etc.

The integration with Power BI from the SCOM database offers incredible possibilities for enhancing user experience. That integration is added value to our services because of what it can do and what we can make it do for clients.

People don't have to log on to the console to see what's going on. They get all the data through the integration between Power BI (Business Intelligence) and SCOM. It is extremely flexible and can be adjusted to meet specific operating criteria. 

If I compare the SCOM solution with the CA UIM (CA Technologies Unified Infrastructure Management) products, the CA products are horrendous in comparison. It's not stable in the way that they do their aggregation and their roll-ups. Really the methodology doesn't make sense. SCOM handles these things without a problem.

Many of the features in the SCOM product have been valuable to us as an organization. Basically most of the main features like the alerting, the reporting, the discovery, the automation, the auto-discovery of products installed on a server and the grouping that it does automatically have all simplified the way we work. The automation in SCOM is incredible, and because I have some exposure now to other, similar products, I can make a good comparison between them. 

The CA products — which is in direct competition with SCOM — is not as good at all. I also have exposure to SolarWinds and a local product here called Syntelligence. None of those products can touch SCOM as far as general versatility. It is just a far superior application for general monitoring.

You can expand on the SCOM automation. But its power is more than just in the segment of automating things. If services stop, you can run recovery tasks and you can use disaster recovery scripts. That is just an example. There are numerous things that you can do with this product.

There are so many features in SCOM it has possibilities that are essentially longer than your arms can reach. You can monitor third-party applications, you can monitor services, you can collect events and you can trigger reports and send alerts based on those events. It's integration capabilities are very good. For me, it is the ultimate unified solution. It is a very nice product and I love it because of the capabilities it provides. The unification of services makes it easier to deploy and maintain.

Even though I think there are ways that this product is superior to most other solutions on the market, there are quite a few things that it does not do alone. This is where the product can be improved. One of the facets is in network monitoring. In fact, it can use quite a lot of improvement in that area. That's where products — like CA Technologies Performance Manager — are much better. You can do a lot with it that you can not with the reporting in SCOM. However overall that CA product is not as well rounded and complete.

The Scrum files that you set up can be made better. For example, you may want accounts that have access to the SCOM console to have more granular access. For example, you may have a situation where you prefer that only certain engineers will be able to add agents to the server — and only the server. But you can't set up the permissions that are this granular. Likewise, it may be that you want to assign someone the right to do threshold changes or to the environment of certain places of certain management groups. It is not part of the standard solution.

With other monitoring tools, you have the ability to set the permissions granularly, which SCOM actually doesn't do. So I hope that they would add that feature and support granularity. There are other ways in which to do it, but if you can do it in the monitoring tool itself and in the administration, then it'll make things much easier and make it a far more complete, unified solution.

One more thing would be better application monitoring. Products like AppDynamics do that very well and exceed the capabilities of SCOM. What I think I would like to see is for SCOM to be more of a complete end-to-end solution so there is no need to look to other solutions or work outside of the singular product. 

SCOM is stable. We have never had a problem with system stability.

I think that SCOM is a very scalable solution. It depends on what hardware or virtual environment you're running on, but the scalability of SCOM is practically endless, I think. You can certainly go very far with it. 

I know of a client in a banking institution that's working on 12,000 servers and their SCOM system is humming along without fail. So scalability on the environment of SCOM itself is very good, or at least it has proven to be scalable in that instance. 

Technical support from Microsoft for SCOM is always excellent. 

By comparison, I've been fighting with CA Technologies and how they do things. It is not the same kind of experience. If you log requests for technical support to tell them what the problem is, they ask a few questions in the investigation. You supply them with the information and from there on you do not know the response time. Depending on the severity of the issue you report on the call, it will be handled more quickly. If it's urgent, then they react very quickly. If it is not urgent, it is not quick even if the answer is simple.

What I like about the SCOM technical support is that they tell you what causes the issue when they find the resolution. They give you a report, they tell you what caused it and what the solution is. That helps make the solution make sense and maybe can help avoid other issues in the future.

We actually have not switched to this solution from another as we are evaluating and using several at the same time. We have used SolarWinds and then there's a new product called eSight that we have to use. The latter product is from Huawei and it is their monitoring tool for their network equipment. We basically were forced to start to support it because of client need. So there are four products that we supporting in our server for various reasons. 

But if I have to choose any one product for server monitoring to take care of all aspects of monitoring out of the box, SCOM is number one. That is it can do application monitoring, like SQL Server Stack Exchange, Active Directory, SharePoint, third party stats, VMware or VLAN — you name it. It's really an excellent product.

So that is why my number one choice is SCOM. Put simply, it is the most complete.

The installation of the product was the easiest thing about using it. If you just follow the instructions and do exactly what it tells you, you don't have to be a trained network surgeon to do it. You can teach a seven-year-old to do the installation. If you can read, you can do the installation. It's really that easy. 

Managing the system depends on the size of the environment for the most part, but I think it depends on the environment and the client as well. When their needs are more demanding or specialized the work will be harder. We've got a client that's got nearly 2,000 servers and they have only one engineer working on the entire thing. There is no need for additional personnel.

We work on our own systems and installations.

We, as a company, are using four products for monitoring, one of which is SCOM. We use multiple products because we are an outsourcing company and not everyone needs or wants the same thing. The other products are from CA Technologies. That is Performance Management, NFA, and UIM Unified Integration Management. These products just enhance the options we have to service our clients.

As far as meeting our needs for a solution, I give it a nine out of ten. But it is interesting to rate the tool. My rating doesn't really have a context. It is mostly engineers that are using the product. In a sense, it doesn't matter what monitoring tool you use, the success of a monitoring tool is dependent on the engineers using it. The engineer has to make it work.

I'm really not aware of the total number of users that we service and with SCOM I don't really need to know. I don't know much about the actual numbers except that we've got 28 clients. Each of the 28 clients has a different number of employees and different engineers that are working on different environments to solve different issues. If I had to guess, I'd say there are really only 100 to 120 only. I wish it was more, and I think we can easily scale to meet additional demand. But the point is that we are responsible for monitoring and identifying issues in a variety of environments, and that is exactly what SCOM helps us do, with efficiency.

We basically use everything we can that is included in the package and have found a real use for every module that's available. That said, we don't do a lot of network monitoring. Server monitoring, absolutely. That we use extensively. Reporting, we use a lot, event collections we use quite extensively. But we bring to the clients what they need most.

We have confidence in the solution and we are going to put all or most of the clients on to Scrum 2019 if they are willing to accept the upgrade path. We are busy working on that in a project to upgrade it to 2019. It all depends on how well test upgrades go and the willingness of clients to enhance their services. We need to test it in the development area first, and then, depending on the type of environment that is running, we have to plan the upgrade in the proper sequence. Say the environment is a 2012 version, the upgrade path is to 2016, from 2016 to 1801, from 1801 to 1807 and then you must make sure that you're on the correct sequel version for 2019. But to do it at all depends on the license agreement that the particular clients have with Microsoft. Right now we are busy taking the environment up to 1807 and then we going to upgrade the sequel version, and then from there, we can go to 2019.

So we are busy the whole time trying to better service our clients. We do our UI updates quite often. We are quite busy with our upgrade paths and testing to make sure everything goes smoothly for the clients in the implementation. 

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.

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.

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.

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

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

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

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.

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

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.

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.

We use this solution for infrastructure monitoring and application monitoring. Predominantly, it is for infrastructure monitoring in the Microsoft space.

This solution helps our application teams by allowing them to drill further into issues and perform a root cause analysis. This is possible because we first built out the monitoring platform and made sure that all of the components were being monitored. Then, we created a distributed application view, which is a drawing of all of the components being monitored for each application. This is what we then provide to the application teams. 

The most valuable feature is the reporting, and the customization is quite flexible.

The end-user components, including the dashboards, the administration console, and the web console, need to be improved.

I would like to see more focus on application monitoring in the next release of this solution.

The stability is pretty good, although it depends on the infrastructure. We normally end up having issues with hypervisors and SQL servers, but it comes down to how those platforms are being administered, as well. From an application point of view, this solution is pretty stable.

This solution is scalable and very good in terms of availability and performance capability. It is very flexible, but you need to have your training properly done beforehand. If so, then it will benefit you a lot. If you need to expand at a later stage then you can do that as well.

We currently have more than three thousand users that vary from managers to developers and engineers.

I have never had to contact technical support.

Personally, I have used an in-house solution and I have used SolarWinds before. It was not a case of switching because these were with different companies.

The initial setup depends on the size of the environment, but on average, it will be more complex than straightforward.

The complexity comes from understanding the various components that contribute to monitoring a specific item on the server. First, you have to understand the Management Pack. Then, you move on to the workflows, and this leads to understanding the rules and monitors. There are bits and pieces that you need to understand in order to make it work properly in your particular environment. This will further depend on things like whether you have restrictions in place, or whether the networking is good or bad. All of these things play a role.

While the deployment time varies depending on the environment, on average, deployment takes about five months.

All of the companies that I have worked for have handled it internally.

One person is suitable for deployment, although this again depends on the company and the environment. If one person is in charge of the SQL environment and the hypervisors then they can do it alone. Obviously, if other departments are in charge of these things then they will need to be relied upon, but generally, it can be done with one person.

With respect to maintaining the solution, a team of three people, with two juniors and one senior, might be ideal.

If you have a Microsoft Enterprise Agreement, then this is part of the agreement.

My advice to anybody looking to implement this product is to plan properly.

Overall, this is a good solution, but there is room for improvement in application monitoring and the dashboard.

I would rate this solution a seven out of ten.