RSA Security 6.1 Manual de usuario descargar pdf (Pagina 29)

RSA SecurID Software Token 4.1 Administrator’s Guide

2: Installing the Application 29

Repair an Installation on Multiple Computers Using the Command Line

You can repair an installation on multiple computers using the msiexec command line.

To repair an installation using the command line:

Use the msiexec command with the /f option. The following command silently repairs

an installation and logs the results to a file.

msiexec /qn /f “pathname\RSASecurIDToken410.msi” /lv c:\install.log

Upgrading RSA SecurID Software Token for Windows

You can upgrade to RSA SecurID Software Token 4.1 for Windows from

RSA SecurID Software Token 3.0.7 or from RSA SecurID Software Token 4.0. After

an upgrade, users can continue using their existing 128-bit tokens. For more

information, see “Transferring Tokens from a Previous Version

” on page 31.

Restrictions on Upgrading from Version 3.0.7

Observe the following restrictions when upgrading your software from version 3.0.7:

• Upgrades from version 3.0.7 are not supported on Windows Vista.

• The following features are not carried over after an upgrade from version 3.0.7:

– Login Automation

– Transfer of tokens stored on smart cards

– Administration Tool

Delete 64-Bit Tokens

If you attempt to upgrade from version 3.0.7, and the version 4.1 installation program

detects 64-bit tokens on the computer, the installation fails.

In an interactive upgrade, a message is displayed stating that the system has not been

modified because the application does not support 64-bit tokens. A silent upgrade

exits without sending a message to the screen. RSA recommends using the /lv option

(log verbose) in silent upgrades so that you can review the event log to determine if

the installation failed due to the presence of 64-bit tokens.

To identify and delete 64-bit tokens:

1. Instruct the user to start the SecurID desktop application and provide you with the

serial numbers of all installed tokens.

2. After you obtain the token serial numbers, access the Edit Token screen in

RSA Authentication Manager to determine the algorithm for the tokens (SID or

AES).

3. Delete all 64-bit tokens from the affected desktops, and then rerun the installation

program.

1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 100 101

Sin comentarios

RSA Security 6.1 Manual de usuario Pagina 29