The Flexera Software Package System is a powerful tool to deploy security updates, but not only that in fact.
SPS allows you to also configure New Custom Package that can be deployed based on your judgment, and not only based on what SVM detected in your network.
This gives you the chance to utilize the package integration of SVM with WSUS/SCCM to further publish brand new deployment packages to hosts that hadn't had those installed prior to that.
For this purpose, you only need to perform certain configuration of your new Custom Package to be able to utilize it properly.
Even though each package published via SVM requires to be wrapped in a script similarly to how update packages are done, you don't really need to script it yourself, just use a little trick.
You can copy the script from any Update Package in SPS and further place it accordingly in the configuration of your new Custom Package, to get it working just fine.
This functionality is provided and used 'as-is' and Flexera support does not take course to troubleshoot failing custom packages.
The current guide is provided for users' convenience and for usability purposes, but users are strongly advised to perform package testing before deploying.
Using the Create SPS Package function at step 2 allows you to easily export, test and confirm the package applicability. Make sure it is being used each time.
You should expect your package to install at its default directory as being implemented by the vendor.
Sep 18, 2020 01:24 PM