000026911 - How to replace an existing RSA NetWitness Endpoint license

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Apr 3, 2019
Version 4Show Document
  • View in full screen mode

Article Content

Article Number000026911
Applies ToRSA Product Set: ECAT,NW Endpoint
RSA Version/Condition: 4.x
IssueThis article explains how to replace an existing RSA NW Endpoint license.

Please note: The product name "RSA NW Endpoint" was changed from ECAT starting with version 4.2.x
For this KB article, the terms are used interchangeably.

The ECAT license designates the Windows server on which the software can run based on a calculated Computer ID (CID) value. Therefore, if the Windows server hardware changes, the CID may also change. The CID may also change on a VM machine if the VM machine was recreated (or recovered from snapshot).

Refer to article 000026907 - How to activate an RSA ECAT license for instructions on obtaining a new ECAT license file.

NOTE:  This will include copying the new 30-character CID and login to the myRSA website and submitting it, as also explained in the ECAT User Guide. Changes to an existing ECAT server follow a different process internally from this point forward and therefore it is prudent to alert your account team of the change and request.

Deploy the ECAT license file

  1. To deploy a new ECAT license file you first need to remove the license file currently in the ECAT Server folder on the ECAT Server.
  2. Backup or move to another directory any license file(s) which should be the only file in the ECAT Server folder with a .lic extension.
  3. Double click on the ConsoleServer.exe in the ECAT Server folder.  This will display the 30-character CID (Computer ID).  Confirm it is the expected CID value for the new ECAT license file.
  4. Stop the ConsoleServer.exe application.
  5. Move the new ECAT license file with a .lic extension into the ECAT Server folder.
  6. Start the ECAT processes and confirm it works.

If you are unsure of any of the steps above or experience any issues, contact RSA Support and quote this article ID for further assistance.

Legacy Article IDa64627