Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Server & Application Monitor (SAM) > SAM 6.4 Administrator Guide > Monitor with Orion agents in SAM > Migrate certificates to a new server for SAM

Migrate certificates to a new server for SAM

Updated: 3-9-2017

SolarWinds encrypts your sensitive data with a security certificate stored on the original SolarWinds server. To grant a new server access to this encrypted data, you must copy the original security certificate to the new server.

If you do not replicate the original certificate, the new server cannot access any credentials used by agents.

Export the credential from the original server

  1. Open the Certificates MMC snap-in.
  2. Click Certificates (Local Computer) > Personal > Certificates group, and then export the SolarWinds Agent Provision certificate.
  3. Export the private key.
  4. When prompted, type and confirm a password for the private key, and complete the wizard.

The certificate is saved with a .pfx file name extension.

Import the certificate to the new server

  1. Copy the .pfx certificate file to the new server.

  2. Open the Certificates MMC snap-in.
  3. Click Certificates (Local Computer) > Personal > Certificates.
  4. If there is a SolarWinds SAM Engine item in the list, delete the SolarWinds Agent Provision certificate.
  5. Select the Certificates (Local Computer) > Personal > Certificates node, and import the .pfx certificate file.
  6. When prompted, enter the password for the private key, and select Mark this key as exportable.
  7. Select Place all certificates in the following store, and then select Personal as the Certificate Store.
  8. Complete the wizard.
 
Last modified
13:48, 10 Mar 2017

Tags

Classifications

Public