• There are a pool of users and a pool of Windows machines.
• The end user needs to be able to access the token for each individual user from any machine without reimporting each token on each machine. 
• The home of the users on the server is set to a remote location, such as \\fileserver\users\%USERNAME%.

• SETCOPYPROTECTION=FALSE to remove the binding of the token to the specific machine on which the token is imported; and thus to be able to find it on any other machine.
• SETSINGLEDATABASE=TRUE to remove the binding of the token to the specific user accessing the machine.  The installation is still secured as the token is stored in the home drive of each user and cannot be accessed by any other user.
• SETDATABASEDIR=%AppData%\RSA to install the database containing the user’s software token to a location other than the default directory.

• The database location above is for the Roaming folder which is shareable, if a user changes his actual workstation.
• The database location can be different if you want to put it on a shared drive, which is sort of a permanent but remote location, for example \\fileserver\users\%USERNAME%. 

Standard RSA SecurID Software Token desktop application

msiexec /qn /i pathname\RSASecurIDToken500.msi /lv c:\install.log SETCOPYPROTECTION=FALSE 
SETSINGLEDATABASE=TRUE SETDATABASEDIR=%AppData%\RSA

RSA SecurID Software Token with Automation

msiexec /qn /i pathname\RSASecurIDTokenAuto500.msi /lv c:\install.log SETCOPYPROTECTION=FALSE 
SETSINGLEDATABASE=TRUE SETDATABASEDIR=%AppData%\RSA