Troubleshooting guide

96 A: Migration Data Conversion
RSA Authentication Manager 6.1 to 8.1 Migration Guide
User agent activation data Existing user-agent associations are maintained by creating
a new group, adding the user to the group, and activating
the group on the agent. If a user group is activated on an
unrestricted agent, any migrated access time restrictions do
not apply to the agent in version 8.1. In version 8.1, access
time restrictions only apply to user groups that are
associated with restricted agents.
In cases where multiple users are activated on the same
restricted agent, the groups are created based on the access
time restrictions. For example, if three users are activated
on an agent, and their access times are between 8 a.m. and
5 p.m., and the other user’s access time is between 3 p.m.
and 11 p.m., two groups are created: one with access times
between 8 p.m. and 5 p.m., and one with access times
between 3 p.m. and 11 p.m. The appropriate users are then
added to the groups, and the groups are activated on the
agent.
Agent data Agent data is migrated, including agent name, primary
IP address, alternate IP addresses (secondary nodes), and
group activations. Individual user activations on agents are
migrated to new activated internal groups.
Agent auto-registration settings are migrated. For
RSA SecurID for Windows Authentication Agent 6.1.2,
this includes the ability to allow auto-registration to
change the primary IP address of an agent. For
RSA SecurID for Windows Authentication Agents prior to
version 6.1.2, you can choose to protect the IP addresses of
auto-registered agents during the migration process as part
of the advanced configuration options.
RADIUS connection parameters stored in the agent record
are not migrated.
Any version 6.1 authentication agent that is configured
with the same hostname and IP address as a RADIUS
client is migrated as a RADIUS client agent.
Token data Token records and their user assignments are migrated.
Secondary node data Secondary nodes for authentication agents are migrated.
One-time password data One-time password data is migrated, both lost token fixed
passwords and one-time tokencode sets.
Data Migration Result