General and deployment
Centero Software Manager was the second integrating product in the comparison. Unlike the two other solutions in the same group, it isn’t based on WSUS catalog, and only needs SCCM to work. CSM is based on SCCM and its application-type application distribution.
Previously WSUS has been an easy way of bringing 3rd party applications available for the System Center Configuration Manager, but today there are other options as well. You can of course compare the differences between these methods; however, that is not what we are concentrating on in this comparison. Nonetheless, Centero Software Manager has some of the benefits you get from using application-type distribution:
- use of dependencies
- use of requirements
- installation behavior
- use of voluntary distribution.
Centero Software Manager (CSM) scores average in the number of supported applications, but it supports all the seven most important applications. As the solution integrates into SCCM, you can also distribute and update business applications. It’s worth mentioning that from Centero, you can order a packaging service for business applications, which means the business applications update just like any other often-used 3rd party application.
CSM does not have Windows update management; instead it’s strictly meant for 3rd party application patch management.
Information security and vulnerability management
Nothing spectacular came up when comparing CSM’s information security. CSM was unlike the other products in vulnerability management, as it doesn’t take a stand on vulnerabilities. Instead, the solution’s idea is to keep all the specified applications up to date on the pre-defined endpoints. This means that instead of installing just the security patches, the solution installs all available application updates.
Deployment and installation of application updates
CSM does not allow a restart before or after update installation. You can, of course, define a restart after installation via the SCCM user interface. But you might want to keep in mind the 3rd party applications almost never require a restart.
Unlike other products, CSM has the option of installing specified applications to endpoints, even if their previous version hadn’t been installed.
Inventory and update verification
The solution’s reporting and inventory are based entirely on SCCM’s features. By operating principle, CSM doesn’t need information on individual devices or their application versions, as the update distribution is targeted to larger entities, known as collections.
Automatic reports on successful updates might have been useful. Currently you need to browse them manually from SCCM inventory or reports.
Capacity for best corporate practices
In this sector, CSM stands out from the crowd. Automatic updates and shortcuts for the updated applications have been disabled. In addition, all the application updates are completely silent, and the end-user doesn’t have a clue they are going on.
Summary on the Compared Features
- Solution type: Integrating on-premises-solutions
- Number of supported applications: 30
- Supported applications: 2.00/4.00
- Pricing, versatility, and infrastructure: 1.14/4.00
- General features and test use: 2.40/4.00
- Information security: 2.00/4.00
- Vulnerability management: 0.00/4.00
- Inventory and evaluation: 2.00/4.00
- Restart management: 0.80/4.00
- Setting management: 4.00/4.00
- Setting adjustments: 2.00/4.00
- Update verification: 3.00/4.00
- Capacity for corporate practices: 4.00/4.00
- Solution deployment: 3.33/4.00
- Price per year for smaller companies: € 4,800
- Price per year for larger companies: € 12,000
In the next post of the blog series we’ll see how Ivanti Patch for SCCM did in the comparison.
For detailed information on the comparison’s results, and the features of the compared applications, check out our Free Patch Management Tools’ Comparison Guide.
Download the guide here »