1.

Delete the token seed record for the problematic token(s) in the database

i)              Logon to the RSA Security Console with a user who has an administrative role.

ii)             Use the Authentication tab > SecurID Tokens > Manage Existing to locate the tokens in question.

iii)            Left-click the Serial Number of token and select Delete or alternatively check a number of Serial Numbers, select Delete (in the action selection) and click the Go button.

2.

Re-import the token seed XML file (ignoring all duplicate tokens already in the authentication manager database).

NOTE: this re-import will require a password if the token seed XML file is password protected.

i)              Logon to the RSA Security Console with a user who has an administrative role.

ii)             Use the Authentication tab > SecurID Tokens > Import Tokens Job > Add New

 - change the Import Job Name to suit the task, select the appropriate Security Domain, Browse to the token seed XML file, enter the File Password (if the token seed XML file is password protected) and ensure ?Ignore all duplicate token? is selected before Submitting the Job (with the Submit Job button).

iii)            Assign the token(s) back to the appropriate end user(s)

Identity tab > Users > Manage Existing ?Search for the user; left-click the User ID, select SecurID Tokens and use the Assign Token button to search for the token and assign it to the end user.