How to Enable a SVM on-premise Vendor Patch Module

How to Enable a SVM on-premise Vendor Patch Module

Vendor Patch Module License File Generation 

We need the below information from the customer to generate the Vendor Patch Module license file. 

  • Login to your SVM on-premise via command line 
  • Run the following command to open the SVM on-premise configuration file

           nano /usr/local/Secunia/config.ini

  • Note down the CST_ID field from the configuration file

           CST_ID = xxxxxxxx

  • Login to SVM on-premise database

    mysql -u [user] -p

  • Run the following command to cross-check the customer ID from the database and make sure the customer ID from the configuration file and database match.

     select cst_id from ca.csi_pdb_info;

  • Create a ticket with Flexera SVM Support via your community account > cases 

Add the below details to the ticket and submit: 

  • Customer ID
  • Entitled Host Licenses
  •  SVM Module ( VPM ) 

Please Note: If you have bought more than one SVM module then add the names accordingly. For Example, Threat Intelligence (TI), etc.

Enable Vendor Patch Module

  • The Flexera Support will create and attach the Vendor Patch Module license file to your ticket
  • Download the VPM license.lic to you machine
  • Connect to your SVM On-premise server via WinSCP
  • Copy the file to this location /usr/local/Secunia/csi/api/config
  • Login to SVM console via Internet Explorer (IE)
  • Recompile the All host Smart Groups from SVM>Results> All host smartgroups>Right Click Recompile>Make sure the Smart Groups are recompiled
  • Go to SVM> Patching > Vendor Patch Module> Try to download a VPM package

Please Note: If you manage to download the VPM package, this means the license has been successfully enabled.



Was this article helpful? Yes No
No ratings
Version history
Revision #:
3 of 3
Last update:
‎Nov 20, 2020 09:13 AM
Updated by:
 
Contributors