Ascom Desktop Charger Basic for D41/D62/i62
$133.99
Mfg # DC3-AABA
CDW # 1724797
Know your gear
The Ascom Desktop Charger is designed for use with d41, d62 and i62 AU, USA, UK version.
Add to Compare
Enhance your purchase
Ascom Desktop Charger Basic for D41/D62/i62 is rated
4.40 out of
5 by
16.
Rated 5 out of
5 by
Bill Watts from
Easy to scale, offers helpful maintenance schedules, and free online training is available
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
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2021-11-11T00:00:00-05:00
Rated 5 out of
5 by
Richard McLaughlin from
Logical free solution to leverage for management packs
What is our primary use case?
We leverage every component of SCOM. The solution uses monitoring mechanisms to send alerts and notifications for down systems or problematic trouble issues. We use it for all of that. We have dashboards up, customized management packs, and monitors for both Windows and Linux. We use SNMP traps to pull in information forward network devices that are in the enterprise. We use it for everything.
What is most valuable?
Being able to make and customize management packs and send out notifications is very valuable. That's the bread and butter of the solution. That's what we use it for.
What needs improvement?
The SCOM dashboards have room for improvement. They've been improving them in iterations slowly and surely. Third-party tools have had to be created to make SCOM management pack creation more efficient and effective. However, this weighs down the application as it just adds a resource requirement, which is ballooning the size of the necessary storage and all that for essentially substandard components. I would suggest either using the dashboard and management packs to their full potential, so we don't have to go out to third-party vendors to install additional features, or allow them to be truncated during installation so that we're not wasting resources.
For how long have I used the solution?
I've worked with SCOM for about ten years now.
What do I think about the stability of the solution?
SCOM's stability is pretty solid.
What do I think about the scalability of the solution?
SCOM has been scaling pretty nicely for us, which is what it's intended to do. We do have plans to increase usage. It's constantly evolving, developing utility. All new systems go onto it. It's not shrinking anytime soon.
How are customer service and support?
The tech support is good. Our company has Premier Plus in place. They're responsive.
Which solution did I use previously and why did I switch?
This is the only one I've used.
How was the initial setup?
The initial setup is complex. It requires Microsoft's support in many cases. It takes about a month or two to get SCOM up and running and fleshed out so that you have all the configurations. For example, when you're migrating from '12 to '19, you have to look at everything that's already in place and then try to migrate it. Whereas if you're starting fresh, then you have to start one at a time looking at each component and building it out. They're too different.
What about the implementation team?
We deployed in-house, but we did leverage Microsoft.
What's my experience with pricing, setup cost, and licensing?
The solution is provided by Microsoft for free but there are operating costs. Those would be the many hours necessary to prune it. We have a contract for support. If that didn't exist, then the cost of the solution would include paying for support. Because it is a complex system, I will contact support for assistance. I also have the general resource requirements just to have the systems up. This includes several databases and front-end servers running. However, added together, all of these costs are minimal.
Which other solutions did I evaluate?
We did not evaluate any other options before landing on SCOM. The reason for this is that SCOM is a Microsoft solution and we have a significant Microsoft presence in our environment, it's actually provided gratis by Microsoft, so it was just a logical utility to leverage.
What other advice do I have?
My advice to others looking into implementing this product is to make sure that you have a solid understanding of SQL commands, statements, databases, and Visual Studio. This will help you understand how to make the management packs more effective. I rate this solution a ten out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-06-07T00:00:00-04:00
Rated 5 out of
5 by
Robert Hedblom from
A highly scalable solution that can be used for proactive monitoring
What is our primary use case?
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.
What is most valuable?
The most valuable feature of SCOM is the capability of using classes within your management pack development.
What needs improvement?
The solution’s initial setup is difficult. SCOM should include more in-depth trend analysis.
For how long have I used the solution?
I have been using SCOM for 15 years.
What do I think about the stability of the solution?
I rate SCOM an eight out of ten for stability.
What do I think about the scalability of the solution?
More than 100 users are using SCOM in our organization. I rate SCOM ten out of ten for scalability.
What about the implementation team?
It took one day to deploy SCOM.
What was our ROI?
We have seen a return on investment with SCOM, and the solution is worth its money.
What's my experience with pricing, setup cost, and licensing?
SCOM's pricing is average.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclaimer: My company has a business relationship with this vendor other than being a customer:partner/customer
Date published: 2023-08-29T00:00:00-04:00
Rated 5 out of
5 by
GovindarajV from
Has good alerting capabilities and is user-friendly
What is our primary use case?
We use SCOM for monitoring our servers in one place.
What is most valuable?
The most valuable features in SCOM are Azure monitoring and integration with Azure Monitor for monitoring Azure-hosted servers from SCOM on-premises.
What needs improvement?
In terms of improvement, direct integration with third-party tools, like ticketing systems, is lacking but would be beneficial.
For how long have I used the solution?
I have been working with SCOM for a year.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
I would rate the scalability of SCOM as an eight out of ten. In our company, we manage 500 servers using SCOM.
How are customer service and support?
The technical support is good.
How was the initial setup?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-04-17T00:00:00-04:00
Rated 5 out of
5 by
Mike Houser from
Useful for Windows servers but improvement is needed in usability
What is our primary use case?
We use the product in our Windows servers.
What is most valuable?
The tool helps to monitor Windows servers. It offers alerts from a central location.
What needs improvement?
SCOM needs to improve its usability.
What do I think about the scalability of the solution?
I like that the solution is one of the few tools that can seamlessly manage multiple applications or servers. Some other monitoring tools struggle with that.
How was the initial setup?
The tool's deployment is neither easy nor complex. I rate it a five out of ten. It typically takes about a day or so to deploy the infrastructure. After that, deploying the agents depends on how you do it, and multiple methods are available.
We require only about two people for deployment, at most. If you include me, that's four. Depending on the job classification, you need server admins and maybe a network specialist. Someone with a good understanding of computers who can log on to a computer or server and navigate the admin console is also needed.
What was our ROI?
The tool helps us avoid costs by allowing us to use transactions which don't cost anything to build. It's the next best thing to having a help desk when a user reports a problem.
What other advice do I have?
I would recommend the tool for Windows servers and not for Linux ones. I rate it a seven out of ten.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-05-08T00:00:00-04:00
Rated 5 out of
5 by
Philippe Roussel from
A stable solution with adjustable tuning issues that can be resolved
What is our primary use case?
We use this tool to patch laptops, conduct an inventory, and gather information about our systems. We use SCCM and another solution around SCCM to gain a complete view of our laptops and desktops.
What is most valuable?
We use the solution for deployment purposes, including deploying solutions, new products, applications, and patch solutions.
The solution primarily drives system information, and I believe it works fine.
What needs improvement?
Regarding certain issues in the solution, it can be difficult to generate reports if we have a program that is not user-friendly for reporting. While this is not necessarily negative, we may need to use another solution. We can explore alternatives through certain products from Azure, but it may still be difficult to generate reports without specific development.
In short, I feel the reporting feature of the solution needs to be better since it is very difficult to have a report of the best quality.
For how long have I used the solution?
We use the SCOM solution in our company and provide it to clients, if possible. Our role is to build a solution architecture for our clients. While SCOM is not our primary product, we have been using it for ten years, and it remains the latest solution to expedite our system information.
What do I think about the stability of the solution?
I think the solution is stable, but we had to meet with our engineer to address some tuning issues. When the solution gets appropriately tuned, it is a good solution.
What do I think about the scalability of the solution?
I have worked with four big international companies using this solution.
How are customer service and support?
My team uses Microsoft support to assist our clients, but we have a specific link with Microsoft to provide support for certain clients.
Which solution did I use previously and why did I switch?
I work with solutions like Microsoft SCCM and Microsoft Intune.
How was the initial setup?
We use the solution in our work for a big company, but we are rarely involved in the setup of the solution. The company uses and upgrades the solution but is not typically involved in new installations.
I work for a big company and thus have access to a certain piece of system information that can be considered big and vast. Due to its size, we have separated the activities, primarily because there are many activities. Also, we have many engineers working on the solution.
What other advice do I have?
I recommend others to try this solution. Also, I rate this solution a seven out of ten.
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2023-03-08T00:00:00-05:00
Rated 5 out of
5 by
Trevor Watkins from
Helps us monitor the health of our servers and has improved our ability to restart services
What is our primary use case?
Our primary use case for the solution is monitoring the health of our Windows servers. We deploy the solution on-premises.
How has it helped my organization?
The solution has improved our overrides and the ability to start services if they're stopped.
For how long have I used the solution?
We have been using the solution for approximately one year and currently using the latest version, SCOM 2022.
What do I think about the stability of the solution?
The solution is stable. I rate it a ten out of ten.
What do I think about the scalability of the solution?
The solution is scalable. I rate it a ten out of ten.
How are customer service and support?
We have had a good experience with customer service and support. I rate them a ten out of ten.
How was the initial setup?
The initial setup is straightforward.
What was our ROI?
We have not seen a return on investment.
What's my experience with pricing, setup cost, and licensing?
I rate the pricing an eight out of ten. The price could be improved.
What other advice do I have?
I rate the solution an eight out of ten. I recommend it for users considering implementing it and advise them to do some research.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2023-01-26T00:00:00-05:00
Rated 5 out of
5 by
reviewer1423482 from
Great visibility and able to expand but needs better documentation
What is our primary use case?
We use the solution essentially for the management of the endpoint and the management of assets.
What is most valuable?
The fact that I'm able to see all my devices and the status of them has been extremely useful. It's mainly the device visibility and device status.
The stability has been great.
It is very scalable.
What needs improvement?
We haven't upgraded the SCOM version yet, however, there's a few of the versions where we would like to have improvements in terms of more visibility into some of the details of the device.
We'd like to be able to configure and push more granular policies into the device.
Using iOS is an issue for us. It's not as deep as the Microsoft offering. We'd like more detail in the iOS version. They also need more advanced iOS support.
There is a lack of documentation.
We didn't know the solution enough, and therefore, it took a while to set everything up correctly. There was a learning curve. We'd like more help in planning and training.
For how long have I used the solution?
I've been using the solution for eight years.
What do I think about the stability of the solution?
It really is stable. The performance is good. There are no bugs or glitches.
What do I think about the scalability of the solution?
The solution can scale well. It's actually more suited for larger enterprises.
We didn't have any issues with scalability.
We have about 800 users on the product currently. That's about 1,400 devices.
We use the product fairly regularly.
How are customer service and support?
Technical support takes work. They're knowledgeable, yet it takes a lot of time. You have to go through the reseller first - before you get to speak to Microsoft.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We're going to, eventually in the next few years with SCOM, move to the cloud management features of Microsoft.
How was the initial setup?
The initial setup took a lot of time. I can't remember exactly what the timeframe was. However, it took longer than we expected. I'd rate it 2.5 out of five in terms of the ease of setup. While it's not difficult, it does take time. We had to do and redo a few things during implementation. They didn't have any documentation for us to work out of, which would have helped.
What about the implementation team?
We handled the setup ourselves in-house.
What's my experience with pricing, setup cost, and licensing?
I don't have an individual cost for SCOM. We buy all our licenses under the program. We get invoiced for the quantities of each of the products without having an individual cost for SCOM. If you buy certain licenses or servers, SCOM automatically comes with it.
Which other solutions did I evaluate?
At the time, we didn't investigate others. We didn't investigate a lot of other technologies as we're a Microsoft shop. We use Microsoft products. We are resellers. We're distributors of Microsoft. We didn't go much further out from there. Recently, we also haven't investigated a lot. We are starting to research the management of endpoints with the Microsoft cloud platform. That looks a little bit easier right now.
What other advice do I have?
We're using a lot of Microsoft products. We are also resellers and distributors of Microsoft.
Whether this solution works for you or not depends on how you do your model. If you outsource everything, then you don't have the problem even if you're an SMB. However, if you have an IT department inside your organization, you will likely need this.
I'd rate the solution seven out of ten.
Disclaimer: My company has a business relationship with this vendor other than being a customer:Reseller / User
Date published: 2022-08-19T00:00:00-04:00
Rated 5 out of
5 by
Hussein Taha from
We can monitor all the VMs in our environment and access full insight reports for all the VMs, but the solution is not stable
What is our primary use case?
SCOM is used as a monitoring solution for managing Windows-based IT infrastructures within our organization.
How has it helped my organization?
SCOM has helped us to monitor all the VMs in our environment, especially the Windows servers. This is our scoop, we monitor all the VMs that have OS Windows servers. The best part of SCOM is that we have a major comeback with it and can apply something that could act as a counteraction. Once an action appears, there is a counteraction in order to avoid any interruption to the service. This is the best way the solution has improved our organization.
What is most valuable?
The solution provides a full insight report for all the VMs in our environment. SCOM also tells us whether the VMs are healthy or not, as well as provides brief information about the management console in each site and the agents under these management consoles.
What needs improvement?
There is no room for update or enhancement in SCOM because Microsoft has retired it as an on-prem solution and moved it to the cloud. The current version will be the last on-prem given Microsoft's push to move all their solutions to the cloud.
The GI is difficult to work with and the reporting servers are also difficult. Another dimension that makes SCOM difficult is the number of components. The reporting server, the database, and the two components of the database (operational and warehouse) are all difficult to work with. This is why SCOM is a difficult solution to implement, configure, and troubleshoot.
For how long have I used the solution?
I have been using the solution for two years.
What do I think about the stability of the solution?
The solution is not very stable. Sometimes we find alerts in the event viewer that we don't understand. we have to spend hours trying to figure out what the events mean. Sometimes we have to request support from Microsoft engineers, who may take a long time to respond, and the case may take longer than expected to resolve.
I give the stability a six out of ten.
What do I think about the scalability of the solution?
The solution is scalable. We currently have six members, but we should add management consultants depending on our workload. We need to go through the Microsoft documents first. We need to calculate and prepare for our Virtual Machine (VM). We need to identify the storage, memory, and CPUs for our VM. This is important because we don't want to lose our solution or have bad performance. A bad performance will affect our environment. We also need to make sure the latency is less than 12 milliseconds. This is important because the management console needs to communicate with the database. If the latency is more than 12 milliseconds, it will affect the outcome of these records and the management console will be unhealthy.
Which solution did I use previously and why did I switch?
Previously we used SIM by SolarWinds.
How was the initial setup?
The solution is difficult to implement and troubleshoot. Sometimes we need the prerequisites for a task, but we encounter issues that we don't understand or that are not reasonable.
The first time we deployed the solution, there were three of us, but now that we have more experience, we can do it on our own without the requirement of additional people.
What about the implementation team?
The implementation was completed in-house.
What was our ROI?
We have not seen a return on investment. We have a lot of latency issues with the solution that is related to the network coverage between the sites. We have ten data centers using a management console but our database is centralized in the capital of Cairo.
What other advice do I have?
I give the solution a six out of ten.
First-time users of SCOM need to be well prepared. There should not be too many management consoles. The SCOM gateway can be used as a way to transfer data to the management console, and the management console will have low latency so it can act as the management console for these sites. It will handle the queuing for the data through the centralized database. This is the best practice given to me by the Microsoft team because of an issue that occurred in our environment that took some time to be resolved.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-12-14T00:00:00-05:00
Rated 5 out of
5 by
SergiusNkomadu from
Cheap solution with great reporting and business intelligence integration
What is our primary use case?
I primarily use SCOM to monitor services, logins, devices, and workstations and get notifications when there's a problem.
What is most valuable?
SCOM's most valuable features are the network path feature, reporting, and integration with business intelligence.
What needs improvement?
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.
For how long have I used the solution?
I've been using SCOM for eight years.
What do I think about the stability of the solution?
SCOM is stable.
What do I think about the scalability of the solution?
SCOM is scalable, but it can be difficult if you don't fully understand the product.
How are customer service and support?
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.
How would you rate customer service and support?
Neutral
How was the initial setup?
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.
What about the implementation team?
I implemented SCOM by myself.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2022-09-03T00:00:00-04:00
Rated 5 out of
5 by
AJITHH G from
Useful for monitoring, logging purposes, and mounting configurations
What is our primary use case?
We mainly use SCOM for logging purposes and mounting configurations. It alerts us when any services have a problem. It really depends on the products that are being used in the backend. There are different kinds of virtual machines and different kinds of environments like VMware and Hyper-V.
One customer deploys the solution on a hyper conversion input service, and two customers deploy the solution on-premises.
The solution could be used in any sized company. It's been used in the manufacturing, IT, and telecom sectors.
What is most valuable?
The monitoring features are the most valuable. We have seen a major benefit from that so far.
What needs improvement?
There could be more integration of SIM in the solution.
What do I think about the stability of the solution?
The solution is stable.
Previous versions were not very stable. There were some issues while we were configuring the hierarchy.
What do I think about the scalability of the solution?
The scalability is of medium difficulty.
How are customer service and support?
Overall, support is not great but it's not bad. Microsoft's standard support is good. Sometimes, there aren't specific engineers who can help us with SCOM when we have an issue. A knowledge-based environment would help us more.
I would rate technical support 3.5 out of 5.
Which solution did I use previously and why did I switch?
We have also used ManageEngine OpManager to monitor the environment and Solar Wind.
They don't support integration of multiple products. Considering the stability and scalability, Microsoft is a better option. It depends on the use cases.
How was the initial setup?
I would rate the initial setup 4.5 out of 5.
It's a complex process. When we deploy any other solution, it comes with a built-in SQL database. With SCOM, it was more of a complicated process.
If it doesn't have a hierarchy, then it takes about one hour. It's a standard installation. If there are hierarchies, like multiple site deployments, then it would take about three to five hours.
What's my experience with pricing, setup cost, and licensing?
I don't know the exact cost because it's managed by our sales team, but Microsoft is on the higher side.
What other advice do I have?
I would rate SCOM as 8 out of 10.
It depends on how the customer is using the product. My advice is that if you're interested in SCOM, you need to consider the environment, the business case, and what kind of business you are running.
Disclaimer: My company has a business relationship with this vendor other than being a customer:Partner
Date published: 2022-09-09T00:00:00-04:00
Rated 5 out of
5 by
Aymen Dridi from
Effective real-time alerts, scalable, but email alerts are needed
What is our primary use case?
We have installed SCOM in our Windows Server 2020 system. We use the solution to monitor any issues that might happen in our infrastructure and keep them in good health. We have SQL Servers, web servers, and web interfaces.
What is most valuable?
The most valuable feature of SCOM is real-time alerts.
What needs improvement?
In a future release, they should add email notification alerts.
For how long have I used the solution?
I have been using SCOM for approximately three months.
What do I think about the stability of the solution?
SCOM is stable.
What do I think about the scalability of the solution?
The scalability of SCOM is good. We can add other servers or services.
I have approximately eight IT personnel that use the solution in my company.
How are customer service and support?
I have not used the support but others in my company have many times.
Which solution did I use previously and why did I switch?
Before I used SCOM I used Microsoft Azure.
What's my experience with pricing, setup cost, and licensing?
There is a license needed to use this solution and it is paid annually.
What other advice do I have?
We have two system engineers who do the maintenance of this solution, but the number of people needed depends on their knowledge or qualification.
I recommend this solution to others, but I would suggest having some training.
I rate SCOM a seen out of ten.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-10-26T00:00:00-04:00
Rated 5 out of
5 by
Amar Sharma from
Helpful in monitoring web servers, database servers and alerts
What is our primary use case?
It is used for monitoring on-premises servers, and we deploy it on-premises.
How has it helped my organization?
The solution helped monitor web servers, database servers and alerting, which is very useful.
What is most valuable?
The ease of deployment, especially on Windows platforms, is valuable.
What needs improvement?
The solution can be improved by expanding to cloud usage. Currently, a lot of people do not use SCOM because it is limited to strictly being on-premises, and many organizations are moving to the cloud.
For how long have I used the solution?
We have been using the solution for approximately 11 years.
What do I think about the stability of the solution?
The solution is very stable.
What do I think about the scalability of the solution?
The solution is scalable. It has an excellent capacity to monitor 100 to 1,000 servers, based on how the SCOM servers are provisioned. You can easily scale up your monitoring capacity.
How are customer service and support?
I rate my experience with customer service and support a ten out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup was straightforward, and only one person was required for deployment and maintenance.
Which other solutions did I evaluate?
We did not evaluate other options.
What other advice do I have?
I rate the solution a nine out of ten. The solution is good but can be improved by adapting to a cloud environment. I advise users considering the solution to use it if they have on-premise servers and more of a Windows-based environment.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-12-18T00:00:00-05:00
Rated 5 out of
5 by
YasirAhmed from
Provides excellent auto-remediation features and is the cheapest product in the market
What is our primary use case?
One of our customers is an Australian delivery company. They use SCOM to manage their servers, hardware, applications, NAS devices, hand devices, hypervisor, and virtualization environment. Another customer uses SCOM to monitor their clients. They have more than 3000 Windows and Linux servers.
What is most valuable?
The product’s auto-remediation feature helps with automation. It is very good at monitoring Microsoft Stack.
What needs improvement?
Application monitoring must be improved. The product must provide support for monitoring virtualization. It is a complex tool. It is not easy to configure it.
For how long have I used the solution?
I have been using the solution for five years.
What do I think about the stability of the solution?
I rate the tool’s stability a seven out of ten.
What do I think about the scalability of the solution?
I rate the product’s scalability five out of ten. Scalability must be improved. The solution is suitable for enterprise businesses.
How was the initial setup?
I rate the ease of setup a ten out of ten. From planning to POST checks, the whole process takes one week.
What's my experience with pricing, setup cost, and licensing?
It is the cheapest product available in the market. I rate the pricing a one out of ten.
What other advice do I have?
I work for a managed service provider. We provide services for SCOM. We provide in-house support and services to our customers. Overall, I rate the solution a ten out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclaimer: My company has a business relationship with this vendor other than being a customer:MSP
Date published: 2023-11-07T00:00:00-05:00
Rated 5 out of
5 by
GaneshRp from
Provides end-to-end application monitoring, inbuilt reporting and capable of monitoring the operating system
What is our primary use case?
I manage SCOM. We use it mainly for Windows operating system monitoring and especially for Microsoft products, like Active Directory, Exchange, SharePoint, Teams, Skype for Business, System Center, and MECM. Application-level monitoring for these Microsoft products has been taken care of by SCOM because it's a native tool by Microsoft.
So it provides end-to-end application monitoring. Apart from this, it is capable of monitoring the operating system. So this is the tool which we are using as of now.
How has it helped my organization?
One of the good features is the inbuilt reporting in SCOM. It has a reporting tool where you can fetch the performance data and have historical data. By default, SCOM has a data warehouse, so all the data is collected and stored there, and you can use it for future analysis. That is one of the features.
And apart from that, we have the web console. You don't need to have the thick client installed on your laptop. You can just go to the web console URL and see the HTML dashboards and live alerts. You can even see the live data and live performance data, the graphical view of the current performance of your application.
What is most valuable?
It is very quick. The inbuilt management pack that Microsoft provides is really helpful. I know it's a mature product, and they keep upgrading the management pack. The MP, that's the main feature that provides end-to-end monitoring for those applications.
They do keep upgrading the management pack, so that's a good thing. Moreover, the users, the application team, Exchange team, and SharePoint team, feel like they've been getting alerts when there's any issue in that environment before the users report them. SCOM triggers the alerts. So that's the best tool for that.
What needs improvement?
Might be the APM (Application Performance Monitoring) solutions, which it lacks compared to other tools. I don't know what other tools are in the market, so I don't know what SCOM lacks. I need to check, as it depends on the requirements. Once other teams have the requirement, and if that is not fulfilled, maybe they would have chosen another tool.
But for me, whatever requirement my user provided has been fulfilled via SCOM. So there might be a few other requirements, which are from other teams, like software development teams, Java teams, and so on. They might have different requirements, but I haven't got those in my scope. That's the problem.
If they had been in my scope, I would have started exploring it, and then I would have known if it's lacking or if it's already there because I haven't used a few features in SCOM, like distributed application monitoring and other stuff.
In future releases, I would like to see APM solutions and dashboards like Grafana. It's not like Grafana. If it is possible to integrate with Grafana, that would be great because I have a lot of data in the data warehouse. If I get a chance to integrate with Grafana, I can show it there because SCOM collects a lot of data from the servers.
For how long have I used the solution?
I have been dealing with it for over ten years.
How are customer service and support?
The customer service and support are good. I've been at Microsoft, and I've been supporting this tool from that end. So customers are happy. If it's really a bug, it's a bug, and then it'll be fixed and released in the next update. And support is always there.
Now, I've moved out of Microsoft. So I'm a customer now.
Which solution did I use previously and why did I switch?
From the beginning, I worked with SCOM. So I have no idea about other products.
How was the initial setup?
We use an agent-based solution. We have the SCOM agent installed on all the application servers, so it collects the data from those applications. And then for ticketing, we can integrate with ServiceNow and BMC Remedy too.
Recently, the major thing is the maintenance mode scheduling has been a good feature.
And overall, Microsoft has made SCOM a SaaS, cloud-based solution, where you don't need to have the on-premises SCOM infrastructure. You can use it from the cloud itself, and you can use the same management pack there as well.
What about the implementation team?
It's actually implemented by another team, but I've taken care of SCOM. So it's like two different teams.
What other advice do I have?
I would rate it an eight out of ten. I would recommend it to others.
Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2024-08-25T00:00:00-04:00
Rated 5 out of
5 by
Mohamed Tantawy from
Has valuable reporting features and good technical support services
What is most valuable?
The product's availability reports are valuable because they provide feedback on service stability. If a service isn't stable, the team focuses on maintenance or looks for alternative solutions.
What needs improvement?
They could provide better dashboards, detailed logs, and reports crucial for monitoring services in real-time.
For how long have I used the solution?
I have been working with SCOM for over five years.
What do I think about the stability of the solution?
I rate the product stability an eight.
What do I think about the scalability of the solution?
We manage around 2,900 SCOM users. I rate the scalability an eight.
How are customer service and support?
The technical support services are good.
How would you rate customer service and support?
Positive
How was the initial setup?
Sometimes, configuring agents with specific ports can be complex. I rate the setup process a seven.
What about the implementation team?
My team installs web agents on servers and configures them based on service owner requirements.
What was our ROI?
It helps make informed decisions on server upgrades and replacements.
What's my experience with pricing, setup cost, and licensing?
The platform is cost-effective due to our existing Microsoft support.
What other advice do I have?
The performance reports and hardware performance alerts have been critical for maintaining our system's health.
Alerts notify the server or service owner of problems, allowing quick decisions or actions to keep the service running based on configured thresholds.
I rate it a ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclaimer: I am a real user, and this review is based on my own experience and opinions.customer
Date published: 2024-06-30T00:00:00-04:00