IBM Support

Resetting licenses in SiteProtector

Question & Answer


Question

What is the procedure for resetting your licenses in SiteProtector?

Answer

There are primarily two conditions that exist in which resetting the licenses in SiteProtector is required:

Note: Other conditions might exist where this procedure is required, but these are the two most commonly seen scenarios.
  • Certain conditions might exist where some SiteProtector sensors can be consuming more licenses than there are actual sensors in the environment. This can lead to some sensors not being able to get a license due to no further licenses existing resulting in the sensor being unable to update.
    For example, let's say you may have five IBM Security NIPS (GX) devices being managed by SiteProtector in which you have five total licenses available. However, when going to Tools > Licenses > Agent/Module and looking in the Summary tab, the In Use column might reflect six licenses in use with a License Limit of five.
  • When adding an Agent/Module license, the license remains in a Newly Added state even after refreshing the view multiple times.
To resolve either of these issues, follow the instructions below to reset your Agent/Module licenses.

Note: You must have your license key files to successfully add these back into the environment. If you do not, you can export them by right-clicking on each license under the License tab and choosing Export license (in version 3.0, the option is Retrieve license file). Make sure that you only re-add current license keys.


To reset the Agent/Module licenses:
  1. In the SiteProtector Console, go to Tools > Licenses > Agent/Module. Under the Licenses tab, select and remove all licenses by clicking the Remove button (again, be sure that you have a backup copy of each of these licenses before removal as stated in the note above).
  2. Stop the following SiteProtector services via services.msc:
    • SiteProtector Application Server
    • SiteProtector Sensor Controller Service
    • SiteProtector Web Server
  3. Open SQL Server Management Studio on the database server and click on the New Query button in the upper left side.
  4. Enter the following and press F5 to execute it:
    use RealSecureDB;
    select count(*) from License where LicenseType=0;
  5. Confirm that the output returns 0 before proceeding with the remaining steps. If it does not, ensure that all licenses are removed from Step 1 or contact Customer Support for further guidance.
  6. On the Application Server machine, go to \Program Files\ISS\SiteProtector\Application Server\License\Repository\ and move the three .xml files in that directory to a backup directory of your choice so that they no longer reside in this directory.
  7. Start the following SiteProtector services via services.msc:
    • SiteProtector Web Server
    • SiteProtector Application Server
    • SiteProtector Sensor Controller Service
  8. Back in the SiteProtector Console, add the license keys back by going to Tools > Licenses > Agent/Module, click on the Licenses tab, and click the Add button.


To reset the OneTrust licenses:
  1. Go to Tools > Licenses > OneTrust and find any/all tokens that are the needed for your desired products. You can find a list of products that use OneTrust in Technote 1435290: Proventia OneTrust Licensing .
  2. Remove the current tokens (take note of it just in case).
  3. Restart the SiteProtector Web Server service via services.msc.
  4. Add the correct tokens back by going to Tools > Licenses > OneTrust, click the Licenses tab, and click the Add button.

[{"Product":{"code":"SSETBF","label":"IBM Security SiteProtector System"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Console","Platform":[{"code":"PF033","label":"Windows"}],"Version":"3.0;3.1.1","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Historical Number

2258

Document Information

Modified date:
20 January 2021

UID

swg21434750

Page Feedback