Your changes will require approval by an administrator before they are published.
The article has been updated successfully but requires approval before it is published.How can I migrate my credentials when upgrading Orion APM 3.5 to Orion APM 4.0 on a new server?
Issue:I upgraded Orion APM 3.5 to Orion APM 4.0.1 on a new server, and now the credentials for all my component monitors are failing. Also the string ‘(NEED TO RE-ENTER PASSWORD)’ was appended to the names of all my credentials. And when I view my credentials in the Credentials Library, they are marked with the message Invalid, re-enter password. Do I have to re-enter all of my passwords on the new server?
Answer:
Yes, it is recommended to re-enter all passwords. It was not possible to decrypt the original passwords to the new credentials format during migration, because the security certificate was missing. Therefore all passwords were blanked (set to the empty string) and the credentials marked with the message Invalid, re-enter password.
A workaround exists so that you do not need to re-enter all the passwords, however you will lose all your data polled since the APM upgrade (including all NPM data). This is because the workaround requires restoring your old APM 3.5 database backup.
Workaround to avoid re-entering passwords:
1. Restore the old Orion database to the new server (using a backup that was made before you upgraded APM).
2. Transfer the certificate to the new server.
Follow the procedure "Moving Orion APM to a New Server" below for copying the original security certificate to the new APM server.
3. Run the Configuration Wizard again and on the first step, check Database. Then proceed and let the Configuration Wizard finish.
Moving Orion APM to a New Server:Orion APM encrypts your sensitive data with a security certificate stored on the original Orion APM server. To grant a new server access to this encrypted data, you must copy the original security certificate to the new server.
WARNING: If you do not replicate the original certificate, Orion APM on the new server cannot access any credentials used by your component monitors, and all of those component monitors will fail.
To replicate the original certificate:
1. Export the credential from the original server.
a. On the Start Menu, click Run, type MMC, and then click OK.
b. On the File menu, click Add/Remove Snapin, and then click Add.
c. Select Certificates and then click Add.
d. Select Computer account and then click Next.
e. Select Local computer and then click Finish.
f. Click Close.
g. Click OK.
h. Expand the Certificates (Local Computer) group.
i. Expand the Personal group.
j. Expand the Certificates group.
k. Right-click SolarWinds APM Engine, point to All Tasks on the shortcut menu, and then click Export.
l. Click Next in the Certificate Export Wizard.
m. Select Yes, export the private key, click Next, and then click Next again.
n. Type and confirm a password for this private key, and then click Next.
o. Specify the file name to which you want to save the certificate, click Next, and then click Finish—the certificate is saved with a .pfx file name extension.
2. Copy the .pfx certificate file to the new server.
3. Import the certificate to the new server.
a. On the Start Menu, click Run, type MMC, and then click OK.
b. On the File menu, click Add/Remove Snapin, and then click Add.
c. Select Certificates, and then click Add.
d. Select Computer account, and then click Next.
e. Select Local computer, and then click Finish.
f. Click Close.
g. Click OK.
h. Expand the Certificates (Local Computer) group.
i. Expand the Personal group.
j. Expand the Certificates group.
k. If there is a SolarWinds APM Engine item in the list, right-click SolarWinds APM Engine and select Delete from the shortcut menu.
l. Right-click the Certificates—Personal—Certificates node, point to All Tasks in the shortcut menu, and then click Import.
m. Click Next in the Certificate Import Wizard.
n. Specify the .pfx certificate file you copied to the server and then click Next.
o. Enter the password for the private key, check Mark this key as exportable, and then click Next.
p. Select Place all certificates in the following store, and then select Personal as the Certificate Store.
q. Click Next and then click Finish.
This article applies to: upgrading APM from version 3.5 to version 4.0.1 (where the credentials format has changed)
Related Articles
No related articles were found.Attachments
No attachments were found.Visitor Comments
No visitor comments posted. Post a commentPost Comment for "How can I migrate my credentials when upgrading Orion APM 3.5 to Orion APM 4.0 on a new server?"
If this article does not provide the solution you need, please consider visiting our community forums on thwack or contacting SolarWinds Support. Please use the following form to provide comments that help us improve this KB article. Fields marked with an asterisk are required.Article Details
Last Updated
10th of February, 2011
