Software Vulnerability Manager (SVM) can create an update package for a product identified as vulnerable in scan results. An update package combines the software installer with an execution flow that controls how SVM installs the update.
Understanding the package structure can help you customize installers, select supported languages, reuse package configurations, and troubleshoot deployment problems.
Update package components
An SVM update package contains at least:
- A software installer that SVM downloads automatically or that you add manually.
- A Flexera-provided JScript or PowerShell execution-flow template.
The installer source depends on the package type:
- Automatic updates: SVM obtains the vendor installer and combines it with the execution flow. The execution flow provides installation options and controls the update process.
- Other packages: You obtain the vendor installer and add it in step 2 of the SPS Package Wizard.
This flexibility allows you to prepare update packages for applications that don’t have an automatic update package.
Export package configurations
You can export an SPS package configuration as an XML template.
An exported template can help you:
- Preserve a working package configuration.
- Reuse the configuration for a future deployment.
- Transfer the configuration to a compatible deployment tool that supports the exported XML format.
-
Important: An XML template contains the package configuration. Confirm whether the installer file is included before relying on the template as a complete package backup.
Customize the package language
SPS uses an English-language installer by default. When a product supports localized packages, you can select another language in either of the following ways.Add a localization file
In the SPS Package Wizard, use Add Localization (Language) File to add the supported language file.
-
Select a language before opening the wizard
Right-click the package and select the required language before opening the SPS Package Wizard.The language option appears only for packages that support localization.
Troubleshoot package deployment
SPS packages create diagnostic information during installation. Review the applicable log files when a package fails to deploy or install.
SPS package log
C:\Windows\SecuniaPackage.log
According to the source article, the package writes installation status to this log regardless of the deployment method.
Windows Update log
C:\Windows\WindowsUpdate.log
Review this log when the package is deployed through Windows Server Update Services (WSUS).
Configuration Manager client logs
C:\Windows\CCM\Logs\UpdatesHandler.log
C:\Windows\CCM\Logs\UpdatesDeployment.log
C:\Windows\CCM\Logs\WUAHandler.log
C:\Windows\CCM\Logs\UpdatesDeployment.log
C:\Windows\CCM\Logs\WUAHandler.log
Review these logs on the endpoint when Microsoft Configuration Manager manages the deployment.
Configuration Manager server log
C:\Program Files\Microsoft Configuration Manager\Logs\wsyncmgr.log
Review this log on the Configuration Manager server when investigating software-update synchronization.
When you open a Flexera Support case for a package deployment or installation problem, attach the relevant logs to the initial request. Include the affected package, deployment method, endpoint operating system, and approximate failure time so Support can identify the relevant log entries.
Test an exported package
You can export an SPS executable and run it on a test endpoint when you need to reproduce or investigate an installation problem.
Use a non-production endpoint that represents the target environment. Review the resulting package and deployment logs after the test.
Was this helpful?
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago