Microsoft System Center Operations Manager (SCOM) vs. Nexthink

More appropriate for:

• Pure Microsoft ecosystem environments (Windows Server and SQL server) and the most common Linux and UNIX platforms.
• Environments where cost is less of a factor than settling on a single platform for monitoring
• Environments where the administrators are familiar with the setup and installation of SCOM.

Less appropriate for:

• Pure UNIX/Linux shops, especially versions not supported out of the box by SCOM.
• Shops that cannot afford the engagement to setup/configure and maintain on a continuous basis.
• Shops that cannot dedicate personnel to the care and feeding of SCOM, especially when supporting larger environments.

Incentivized

I've been managing desktops for 20+ years and Nexthink was the missing tool out of my toolbox. Just to give some perspective, if you were building and maintaining a house, Nexthink would be comparable to switching up from a hammer and nails and to full blown using a nailgun. Nexthink is a solution accelerator and a well thought out toolset to give you the customer experience at a glance. It allows for so much more visibility just with the default set of data points the Collector (agent) gathers, which is A LOT, and grants you the ability to gather even more data with remote actions. All of this evidence cuts how the "it could possibly be this" and "maybe it's that" discussions when you're troubleshooting an issue. It may not provide the exact answer all the time, but it gives you a "compass point" on where you need to start looking to resolve the issue. Also the service monitoring, activity monitoring, and critical event thresholds really empower the teams to know when a problem is happening and they can get ahead of it before the first call even reaches the Help Desk. Nexthink is a cornerstone tool in our environment for end user experience and I'm excited to see where the go next.

• Allows us to visualize our systems in a single interface and see the status of health as well as relevant performance metrics.
• A flexible and powerful interface with active alerting covering domain controllers, SQL servers, etc...
• Allows you to customize your views and workspaces for specific tasks and needs.
• Reporting is powerful and flexible.

Incentivized

• It allows for an IT department to be proactive with finding/solving issues before they happen
• It allows for a company to have a great tool for engaging with end users using campaigns/surveys
• It shows the full overall picture of a device/network connections when troubleshooting user issues.

• One of the biggest drawbacks to SCOM is the sheer scope and complexity of the system. This can be a pro and a con. The system is very customizable, what you put into it is what you'll get out of it. That said, the learning curve is fairly steep. An organization needs to be committed to putting time and resources into SCOM to get the most out of it. I've heard stories from colleagues of several different companies that invested in SCOM and then abandoned it due to the excessive time and care required.
• SCOM is expensive. Not only is the enterprise licensing costly, SCOM requires it's own servers, operational and warehouse databases to be maintained.
• The OOB SCOM reports are a bit clunky and feel outdated.

Incentivized

• The on-premise solution can be slow at times and resource-demanding even on newer laptops. (This isn't the case with the cloud offering.)
• Some useful features are only available to cloud customers.
• Library pack configuration could be made easier, often these packs require some customization and it's not always clear how to get them up and running after importing.

Hard to get support. The product is not being actively developed anymore, so it is hard to get new features for the product.

Incentivized

We used Altiris and WSUS and in the beginning Altiris had the better admin interface than SCOM, but it is no longer the case as SCOM has refined their admin interface. Altiris still has better and more robust group assignments for management roles and those two other tools can better manage non Windows OS devices than SCOM but for a large enterprise Windows shop, if you can afford it, SCOM is the way to go.

Incentivized

Nexthink had better integration and a better user interface. 1E did not have the engagement capability which is so critical to many of the actions we complete using Nexthink. Nexthink had better trending data capabilities. 1E did not capture and hold data the way Nexthink does so all data assumes you are able to pull information from all systems at any time. with remote systems it is unlikely you will capture all systems at the same time so it makes any actions less effective. this review was performed 4 years ago so 1E may have addressed some of these limitations but Nexthink has also grown and continues to add and improve on their industry-leading capabilities.

Incentivized

• It has allowed us to provide an Enterprise Event/Alert management solution to the Global company
• It has taken a long time to get it to provide valuable alerts and information, lots of user resources and investment.
• It assists with 24/7 monitoring and out of hours support

Incentivized

• SCCM proactive remediation: Automatically resolving hundreds of SCCM issues per month
• Hardware: Identification of over $5m cost avoidance by seeing a lack of usage for 128GB SSDs - no need to upgrade to 256GB... coupled with OneDrive migration packs in the Nexthink library this is valuable.

Incentivized