CSM Customers’ Wishes Heard: Deploy Your Own Software Package Via CSM

We at Centero have always paid close attention to our customers’ hopes and made note of all the new features on their wish list. The list is long, and as much as we hate to admit it, we haven’t been able to answer all of the wishes – at least not yet.  But now we are happy to release one of the most requested Centero Software Manager feature our customers have been asking for, and I there’s a little something I want to say about the feature.

Thanks to the new feature, our customers can upload their own application package or installation media via Centero Portal to CSM. This application can then, in turn, be deployed on desired devices (groups/collections), with a desired schedule, using CSM’s deployment processes.

Most of our customers using CSM appear to deploy the most common applications with CSM (the ones on the Supported Applications list), and for anything more specialized, package/script it themselves and deploy straight through the deployment system (MECM/Intune).

Now, thanks to the new feature, the latter can also be taken care of with CSM. And I also want to mention our APaaS (Application Packaging as a Service) option, where with an additional fee you can get the packaging of almost any application’s new versions straight from Centero.

Well, how does this help in real life, then? Here’s how Centero’s CSM expert, Aapo Kettunen, puts it: “MSP customers benefit the most: they can add the software they want to a hundred end customer environments at once, if needed. This will definitely save dozens of hours of work compared to deploying the software to each of these environments manually.”

The new feature is useful to direct customers as well, especially if a software gets frequent version updates, and especially if the customer has several environments integrated into CSM.

This will definitely save dozens of hours of work compared to deploying the software to each of these environments manually.

You can find more detailed instructions on how to use the new Custom Applications feature from our Knowledgebase, but I want to point out a few details that I’m sure the admin folk will find interesting. The feature itself works in MECM and Intune integrations, but not in WSUS integrations. The installation media can be in MSI or EXE form, and the MSTs and installation media’s other additional files can be included in the same package if needed. The application’s identification rule can be the MSI package’s product code, or, alternatively, the information of a folder, file, or register on the device. For you own application we’ll also configure installation and uninstallation commands, and depending on the application, you can also configure different settings and installation behavior.

We’ve also taken the release of new versions into account: when importing a software’s next version, deployment will automatically align with the previously configured deployment process, and CSM will of course delete any old versions and deployments of the software. As a general remark, I should point out that with this feature it’s a good idea to read the instructions pretty carefully. One could even say that using this feature requires some level of knowledge on packaging/deployment/scripting. And remember, if you do not have the time or the skills to do it yourself, you can always ask for your software APaaS for an additional fee.

Hannu Laitinen

Partner Account Manager