Microsoft System Center is an enterprise-grade IT Operations Management (ITOM) suite designed for the centralized administration of data center infrastructure, virtualized environments, and hybrid cloud workloads. The platform provides unified management across heterogeneous environments, including support for Windows Server, Linux, and Azure Stack HCI.
System Center is Microsoft's ITOM stack for organizations that maintain a significant on-premise footprint, vs the company's Azure-based…
$1,323
ScienceLogic AI Platform
Score 8.8 out of 10
Enterprise companies (1,001+ employees)
ScienceLogic provides a unified IT Operations platform designed to manage operational workflows using high-fidelity Telemetry Data and explainable automation.
The ScienceLogic AI Platform is deployable across On-Premises, Cloud, and Hybrid Environments. The platform consolidates monitoring tools to provide Observability and enables engineers to automate manual processes using Machine Learning capabilities.
The platform utilizes automation for Closed-Loop Remediation and provides insights…
N/A
Pricing
IT-Conductor
Microsoft System Center
ScienceLogic AI Platform
Editions & Modules
Basic
$150
per month
Standard Edition
$1323
Datacenter Edition
$3607
No answers on this topic
Offerings
Pricing Offerings
IT-Conductor
Microsoft System Center
ScienceLogic AI Platform
Free Trial
Yes
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Required
Additional Details
—
—
ScienceLogic SL1 offers four tiers:
SL1 Advanced – Application Health, Automated Troubleshooting and Remediation Workflows
SL1 Base – Infrastructure Monitoring, Topology & Event Correlation
SL1 Premium – AI/ML-driven Analytics, Low-Code Automated Workflow Authoring
SL1 Standard – Infrastructure Monitoring – with Agents, Business Services, Incident Automation, CMDB Synchronization, Behavioral Correlation
SCCM is often considered superior to Intune because it is more predictable and transparent in day-to-day operations. Errors in SCCM are clearer and easier to troubleshoot, whereas Intune issues can feel vague and harder to diagnose. SCCM also offers rich, built-in features such …
Microsoft System Center really integrated with our windows system better than any other 3rd party product which obviously you would expect to a certain extent. Our main reason to procuring System Center (apart form the options)was licensing costs. We already had a Microsoft …
None. We are a Microsoft business, and this is THE tool for imaging, packaging, remote support, and antivirus management. Microsoft's tool is the best for managing its software, systems, and antivirus clients. I will say that Microsoft Intune, the cloud platform, can be used …
The capability of SCOM as far as monitoring Windows systems is concerned is far greater than any monitoring product out there as both are a Microsoft product so integration and discoveries work well and fast.
The versatility of the suite of application provided by the Microsoft experience center was way above the other competitors , it helped gained leverage over the other products in the market . That why we made the decision of choosing Microsoft system center as a infrastructure …
We use Azure, we have lisences, so we have no needs any other cost. And also, we want to save backup data in Azure. Veritas ask additional cost reagurally and have to rebuild bakcup environment.
Because Datadog was too small, we decided quickly to use Microsoft System Center. We use a lot of other Microsoft products so that discussion was quickly set internally.
We have used Ghost from Symantec (licensed), FOG and Clonezilla which are freeware products. All three products had their pros and cons. The two freeware products were functional but did lack some polish, and Ghost was a good product for imaging of desktop computers. All did …
We previously used a mix of FOG and Clonezilla to image machines. The biggest issues with these products is that changing one piece of the image required you to rebuild the entire image itself. These pieces of software also did not allow you to manage applications and Windows …
We are using Microsoft products for a long time, so the overall confidence played a part in the decision, the feature set and licensing cost was also very high when compared with above products, so we decided to use System Center for our environment, so far it has solved many …
We selected it simply because it is less expensive than the competition, but yet just as good. We saw no reason to go outside the walls of Microsoft for this task. We are satisfied with the product.
This was used to monitor uor non-Windows systems and was cumbersome. Their licensing was per device with how many agents you needed; however, with System Center Operations Manager, their billing was a lot easier for their product.
All comparative features are way expensive and complex to configure in all other competitors. Value to money and ease of deployment for Microsoft based environment
Microsoft System Center has more options. Microsoft System Center has the ability to image PCs as well as remotely connect to PCs, and software installation and patching where Symantec Ghost Solution Suite didn't handle all of these options as well. We haven't looked at many …
Much better UI for system center. Also, Tivoli was discontinued, so it was an easy decision. Altiris was acquired by Symantec but was unreliable and painful. It's UI was unresponsive and generally outdated. It wouldn't clean up old packages and would hog GB of disk space, …
SCOM is better than OMi for Windows-based servers monitoring. You need to know how to use Visual Studio to customize the management pack. Dynatrace is way better for all Application Performance Manager.
It has its similarities between the two from a ticketing standpoint but as a primarily Microsoft shop it is nice to have a product that was created to play along with other tools that we are using such as SCCM. We like Jira for the project management tools and Cherwell for …
It is an excellent product for monitoring features like Exchange, Active Directory, DNS. Monitors are custom designed and can be adjusted to any system. Great monitors can be created even when monitoring open-source systems.
How SCEP stacks up against some of the other AV solutions/products is that it does a pretty good job overall (not the best in the industry) at detecting/removing malware, which is the main focus for a product like this. It is also easy to use on the end-user side, which can't …
real-time data monitoring, scalability of a complex environment is the key feature. For any new requirement, powerpack installation is very easy & handful.
Both of the tools we used before were with agents, so there was a need to configure the agent initially, before it could be used. Sometimes, there were issues with the service or the configuration of the agent, and deep troubleshooting was necessary to find the mistake in …
Restorepoint is a great tool and perfectly integrated with ScienceLogic SL1. However, PowerFlow implementation is not smooth and don't have enough resources to help build out the features necessary for a successful implementation. Also, documentation is not well written.
ScienceLogic SL1 supports large scale of IT Infrastructure devices and vendors. Was the single tool providing multiple functionalities at same time and allowed to remove additional legacy tools used for monitoring. Allowed integration with incident management and CMDB. Allowed …
From a capability perspective they stack up very similar but from a look and feel, ScienceLogic SL1 one is miles behind the curve on all three. We chose SL because we already had elements of the service in place on our infrastructure from our previous MSP so they were a …
I see great potential and infact i do strongly beleive it offers even beter capabilities than the traditional tools out there but again it comes down to how well you have trained us on how to unlock these capabilities. I suggest incentives for techs for providing feedback for …
Geneos is more complicated and 'heavy' to setup. It requires a lot of expertise in setting up. Also the dashboards are not great. ScienceLogic SL1 works well for customer facing dashboards.
Entuity was lacking a lot of custom reporting and also the out of the box automation and RBA was also less. Our customers were mainly looking for devices which are next gen like sdwan which Entuity doesn't support. When it come to ScienceLogic SL1 it will support all sets of …
As a fresher, this is my first organization, and they use SL1. So, I don’t have more knowledge of other tools. But I do know Grafana, which is predominantly used for dashboards. I think compared to that, the SL1 dashboard gives more details about devices. So, I feel SL1 would …
Galileo analyzes storage arrays and backups more thoroughly, but SL1 is much better for host and network monitoring. SL1 has some storage monitoring features for some storage arrays, but they are not as detailed.
I was not part of the team selecting ScienceLogic SL1. Our goal was to increase event visibility in our server environment. We were using scripting which created many false events. SolarWinds is primarily used in the Network space to monitor network gear.
Agentless product that can integrate easily with other product and also allow us to automate tasks, example closing tickets when events are cleared automatically which user interactions.
Just because Science logic provides much more better enhancement and getting improved everyday. The autonomous integration and overall customization provided by the SL1 Platform is outstanding. In every sections be it in Monitoring or checking system logs and provide the best …
We used a product before that was designed to prevent users making changes and saving files to the desktop computer. This required a renewal of the license. By using SCCM in our environment we were able to discontinue using that product because SCCM allows us to completely restore a machine back to the original configuration. We have taught our users to save their individual work on either a network drive or a cloud drive. By doing this, if we do a re-image of their machine they have lost no data, and it makes for a faster resolution. In some instances having a computer in our SCCM environment it can become cumbersome when creating new users for very specific purposes. It can be done by creating new organizational units and applying new policies but when in a pinch it can be frustrating. For the most part we have tried to make "new" purpose images and groups to at least accommodate a quick install.
Appropriate if you are setting up a monitoring suite in new Infrastructure Environment. Definitely NOT suited for Migration Projects. ScienceLogic SL1 cannot cater to a lot of monitoring requirements which already would have been configured in old monitoring suite. Plus, limited support for customizations and having to go to "Feature Requests" route makes in extremely complicated.
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.
Creating powerpacks from scratch for new devices may be straightforward but will rarely be easy. Rewarding when completed, but not easy.
Developer documentation needs a rethink. While the information may be there (it isn't always) it is not easy to find. This is not helped by using different terms for the same things.
A developer console/dashboard for monitoring data collection from powerpacks instances without having to switch webpages or have to monitor multiple webpages.
We migrated away from our 20-year-old homegrown solution and have no back-tracking capability. ScienceLogic is demonstrating new capabilities that we would not have been able to do on our own using our legacy system. We understand the capabilities of competitors based on our bake-off selection where ScienceLogic won on capabilities and future near-term potential (expandability, platform growth). We know that those competitors are not really close to where we have been able to push ScienceLogic (as a partner).
It is not user-friendly for the most part. With IT infrastructure, sometimes it cannot handle excess requests. Every few months, you will need an upgrade in terms of server resources to keep up with incoming alerts and requests. This does not happen all of the time, but it does happen when there are too many requests.
We use ScienceLogic SL1 in our organization to serve effective monitoring solutions to our external customers. Our customers depend upon us for critical events/alerts related to their IT infrastructure gears and using SL1, we're able to provide them with a proactive monitoring solution that resolves an issue before an impact is noticed by the customer. There are very few monitoring solutions that can cater to a variety of Cloud platforms like Public Cloud (AWS, Azure) and private cloud simultaneously and SL1 addresses this business problem very well
Science Logic SL1 provides the option of Distributed deployment where multiple instances of each appliance can be deployed to manage the load and availability. SL1 provides a High Availability feature for Database Servers and Data Collection. If one of the Data Collectors in the collector group fails, it will automatically redistribute the devices from the failed Data Collector among the other Data Collectors in the Collector Group. The high availability feature for the Database server ensures that SL1 performs failover automatically to another server without causing the outage to the application.
The performance is entirely dependent on the complexity of the environment/network being used to host the platform. Outside of those factors, the platform runs very efficiently and quickly out of the box. We have integrations with other platforms and neither seem to take a hit from our moderate API usage. Any issues with performance would be experienced by choices made in infrastructure or complexity of things built by the customer to display in the GUI (overly complicated and cluttered dashboards for example)
There is a fair amount of documentation out there to help you when you have questions or run into issues with this product as well as tutorials on some of the more common tasks. Between the documentation and the overall ease of use we haven't had to deal with direct Microsoft support for this product.
So far, it's good as part of my overall experience, except for a couple of use cases. The support team is well knowledgeable, has technical sound, and is efficient. When support escalates to engineering, the issue gets stuck and takes months to resolve.
When I joined our company, I did not know about the in person training at firts. Logging onto the SL University, I realised that there were different sessions being held at different times throughout the year. The training itself was good, but being in a different time zone, made it difficult to attend, but the sessions that I attended was great!
There are a lot of educational materials and courses on the SL1 training site (Litmos university). However the recording quality is sometimes not very good - screen resolution is low. There is a lack of professional rather than user-oriented documents and there are mistakes in documentation and education is not well structured.
Along with the purchase of the solution, we purchased a statement of work with their Professional Services organization to meet our outcomes and fill our critical gaps. The PS team was outstanding, very professional and allowed us to screen share while they built our integrations. In many cases they would teach us how they did certain things within the platform.
None. We are a Microsoft business, and this is THE tool for imaging, packaging, remote support, and antivirus management. Microsoft's tool is the best for managing its software, systems, and antivirus clients. I will say that Microsoft Intune, the cloud platform, can be used for those with heavy 365 usage, but for us, that does not meet our current company needs.
Both of the tools we used before were with agents, so there was a need to configure the agent initially, before it could be used. Sometimes, there were issues with the service or the configuration of the agent, and deep troubleshooting was necessary to find the mistake in configuration before the communication with the endpoint was restored. Once the tools were running, they enabled very smooth reporting of what is running and what not, and the performance impact was lover than with WINRM monitoring.
Our deployment model is vastly different from product expectations. Our global / internal monitoring foot print is 8 production stacks in dual data centers with 50% collection capacity allocated to each data center with minimal numbers of collection groups. General Collection is our default collection group. Special Collection is for monitoring our ASA and other hardware that cannot be polled by a large number of IP addresses, so this collection group is usually 2 collectors). Because most of our stacks are in different physical data centers, we cannot use the provided HA solution. We have to use the DR solution (DRBD + CNAMEs). We routinely test power in our data centers (yearly). Because we have to use DR, we have a hand-touch to flip nodes and change the DNS CNAME half of the times when there is an outage (by design). When the outage is planned, we do this ahead of the outage so that we don't care that the Secondary has dropped away from the Primary. Hopefully, we'll be able to find a way to meet our constraints and improve our resiliency and reduce our hand-touch in future releases. For now, this works for us and our complexity. (I hear that the HA option is sweet. I just can't consume that.)
The positive impact it has had on ROI is that it has been a solid AV product in our environment, meaning it has worked well when running on client computers. It doesn't use a lot of system resources on the client-side, so that helps end-users productivity of not being slowed down.
It has been good for the end-user, since they really don't need to take additional training or consult user manuals, in how to use the product.