Microsoft System Center vs. StackState

For companies with more than 10 Windows devices and needing to standardize the OS, AV, access, share resources, and install software. SCCM is the way to go. This software is unnecessary if the business is all remote users and not in an office-type setting. There are cloud offerings or none to accomplish what a business needs.

Incentivized

StackState is suitable for 1000+ hosts. Sometimes specific applications can take higher development time. Well suited for hybrid platforms to build end to end service alarms and service views. Advanced UI navigation might require some training. It is not a simple download and deploy software. It will require development in an agile model. Where newer versions are deployed to suit exact client requirements. Support contract with the StackState Engineer for development of use-cases is required and very useful.

• Allows the grouping of devices by user.
• Allows controlling updates being deployed to user devices.
• Allows for the repurposing of machines by being able to load new or updated software on machines that already are in the system.
• Allows us the ability to wipe a machine clean and restore it back to the configuration that was assigned the machine.

Incentivized

• Giving observability of the entire IT stack
• Custom alerting options.
• Ingesting many different types of data.
• Requesting new features is encouraged and they often add them quite quickly.

• Needs web based storefront for requesting new software
• Needs ability to manage the packaging work flow better
• Sometimes is slow to download and there is no indication the entire catalog is being loaded, resulting in confused users not being able to find common software in the available list.

Incentivized

• Can't think of anything yet.

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.

Incentivized

Some elements of the product haven't had the usability upgrade yet and can be a bit technical. This is to be expected as they are trying to solve complex problems. I am sure that in the future, steps will be made to simplify this as well for the users / administrators / developers of the platform.

If I had to dislike something about the system it would be how much it changes once you upgrade. This could be more of a problem of mine since I get used to one way and don't like it when it changes so much. I am enjoying the newest update, but it is a mess when you are actually going through the upgrades.

Incentivized

It's swift, they're thinking along with us. It's a "collaboration approach" rather than a (traditional) customer-supplier relation. Out new ideas are taken in concern and often ends up in enhancements of StackState

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 Updates, causing IT to have to constantly touch machines after they were imaged and update or manage them with a much more hands on approach.

Incentivized

• We have been able to automate our patch management, firmware and other security concerns.
• We have a standardized "image" ensuring our setup is consistent across the enterprise. This alone has saved us in time to support and time to understand how to use our desktops.

Incentivized

• Increased visibility of all resources in cloud to 100%.
• Deviated stages are able to detect problems before their occurrence. However, [it] needs tunings for false alarms.