SCOM Reviews

We work with our global team to produce software delivery packages and patches. We push the changes to the servers as well as to the computers of the end users.

I enjoy its integration with the Microsoft Active Directory functions, which means users, computers, or other group policies can connect with Windows Active Directory.

There are some negative points about this product. Sometimes, the capabilities of the software don't appear, and you can't directly see the results. You have to wait for a long period to refresh the policy to push it to the software or other patches.

I have been using this solution for five years.

It is very stable.

We can easily scale-up when we have a new global site. It is just so easy to extend this solution to other sites, which is an advantage. 

On the IT side, we have 30 people working on this platform, and on the user side, we have 600 people. We use it every month to push down new patches.

We used LANDESK and Manager Engine. Both of these solutions are similar to SCOM and suitable for the simple purpose of management. 

SCOM is just one user interface. It is a Microsoft service user interface. However, it is not user friendly like Manage Engine, which has a self-service desktop where users can log in and change their password themselves. The software also sends out an automatic notification. Manage Engine has a user-friendly interface.

It is very complex to install because you have to plan the whole deployment. You have to design the central server, the deposit server, and the domain. It is a little bit complex as compared to other common server installations. The deployment took two months.

We have a consultant.

This is a good software. I would definitely recommend this software.

I would rate SCOM an eight out of ten.

Our primary use of SCOM is for monitoring deployments of Windows. It is also used for monitoring applications, and it reports information if there is a problem.

It is very good at monitoring Microsoft Server.

SCOM is not a flexible product.

The initial setup should be easier to complete.

We have been working with SCOM for three years.

This is a very stable product and we plan to continue using it in the future.

This solution is very scalable. It can change the configuration for management and performance. We have two people who use it. One is a manager and the other is an engineer.

When I need external support, I can open a case with Microsoft. I have opened between two and four support cases and I am satisfied with the support I received.

We don't use any other product for deployments. 

I would say that the initial setup is 50-50. It is not easy and it's not hard to set up. It should be easier to install. It took us between three days and a week to deploy.

The length of time for deployment depends on the size of your environment. If I am installing a new System Center Operations Manager for 100 servers, it will take maybe two weeks. The process requires implementing monitoring agents, and I need to change the configuration as well.

I deploy this product myself.

We have an enterprise agreement that includes this product as part of it.

This is a good product and I recommend it. When it comes to monitoring Microsoft servers, it is very useful.

I would rate this solution an eight out of ten.

System Center Operations Manager is basically for windows monitoring. We use SCOM to monitor metrics, such as CPU and memory disk, and a lot of applications, such as Microsoft Exchange Server, Office 365, Active Directory, RDBMS, Skype, and Citrix.

It discovers the components automatically, which is a fantastic thing. The discovery works in an automatic way, and it has a dynamic way of discovering the components, assets, and applications. It doesn't require any manual intervention.

They can focus more on cloud monitoring instead of on-premise monitoring. We should be able to monitor cloud-related applications. They can include this feature in the next release.

If it is in the cloud, we can have scalability by using Kubernetes. The container is containerized, packaged, and managed using Kubernetes. This feature is not there in SCOM. Going forward, if they can focus on that, it will be great.

Its scalability works well. In our environment, we are monitoring 150,000 Windows Servers by using System Center Operations Manager. Its usage keeps increasing.

I am satisfied with their support.

Its initial setup is straightforward. It doesn't take long.

We evaluated other options. We found SCOM to be suitable for Microsoft Windows applications, so we decided to go for it.

I would rate System Center Operations Manager an eight out of ten.

We use SCOM to deploy images.

We like the deployment of the machines and the features that they have.

It's easy to use.

The management of the servers could be better.

Also, the user interface could be improved.

We have used SCOM for a couple of years.

We are using the latest version.

It's a stable solution.

It's a scalable product. We have 1,000 users in our organization.

We have plans to continue using this solution.

Technical support is fine. We have no issues with them.

We did not use any other solution. It's a group standard for us.

The initial setup is straightforward. It's easy for us.

We have a team of four to deploy and maintain it.

We completed the installation ourselves.

It took one week to deploy and customize it.

We have to pay for a license and the price is fine for us.

I would recommend this solution to others who are interested in using it.

I would rate this solution a nine out of ten.

We use SCOM mostly for server performance monitoring in historical metrics.

I like the historical reporting of observer metrics. It's a fairly user-friendly solution.

It'll help if they can provide real-time or closer to real-time monitoring.

I've been using SCOM for at least five years.

SCOM is a stable solution.

SCOM is scalable, and it's easy to add resources.

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.

The pricing is good, and it's part of their system center suite. I believe we pay for the license on a yearly basis.

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.

We are using the SCOM server for monitoring our network devices, our Windows servers, and Linux servers.

The most valuable feature is the monitoring of Windows and Linux servers.

The dashboard features are not user-friendly for our management team, only for the technical department. We are currently looking for a plugin for the dashboard to assist in monitoring the dashboard in the SCOM server.

At this time, SCOM is only being used in our IT department. Digital console is not available to our users, management team, or senior persons, and they are not allowed their own login to see what is happening in the network system. The only access that we have is to dump the reports to provide them to our management team.

It doesn't monitor the Fortinet devices well.

I have been using the Microsoft SCOM server for six years.

Because we work in a financial institution, we are not allowed to remove the SCOM server and replace the new monitoring software. We have been given permission by management to search for third-party software to provide us with the missing features, which is something that we require to make it easier.

I would rate this solution a seven out of ten.