Radius clients are not listed after migrating from 7.1 to 8.1
Originally Published: 2014-12-03
Article Number
Applies To
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.1.0
Issue
Cause
Resolution
Edit the top level realm via clicking it, then clicking edit.
Change the name to SystemDomain then save it.
NOTE! - The above name is case sensitive, make sure it's SystemDomain NOT systemdomain
Once that's been saved, download the latest patch for 8.1 which includes the migration utility for 7.1, re-run it on the 7.1 primary, then migrate into 8.1.
NOTE! - Make sure you are running the correct version of the 7.1 migration utility. If your AM server is running AM 8.1 Patch 8, you have to run the migration utility included in the patch zip file. If you are running AM 8.1 SP1 P1 the same principal applies, you have to use the 7.1 migration utility included with the SP1 P1 zip file.
Make sure when you migrate to 8.1 you pick "Remove all existing data, and import data from the migration package"
Related Articles
Advisory for Migrating credentials from RSA SecurID Software Token 4.2.3 to SecurID Authenticator 5.1 for macOS 197Number of Views Migrating from RSA Authenticate App to SecurID Authenticator App 140Number of Views 'ORA-28000: the account is locked' error when migrating an imported database in RSA Identity Governance & Lifecycle 186Number of Views Migrating users across identity sources in RSA Authentication Manager 8.x 1.92KNumber of Views Why does the restore of the backup fail when migrating from an earlier key manager appliance backup? 46Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.9 Release Notes (January 2026) Deploying RSA Authenticator 6.2.2 for Windows Using DISM RSA MFA Agent 2.4 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?