If you plan to upgrade all previous versions to SecureLogin 3.51.2, use information in this section. If you plan to have a mixed environment, where some workstation are running SecureLogin 3.51.2 but other workstations are running earlier versions, see Running SecureLogin 3.51.2 in Mixed Environments.
Before upgrading from SecureLogin 3.0.x to SecureLogin 3.51.2, close SecureLogin. The installation program can normally handle locked files. However, some problems can occur on Windows 9x computers due to the short-name limitation of 8.3 filenames.
SecureLogin 2.5 could be deployed to run in standalone mode or with eDirectoryTM. Even if SecureLogin 2.5 was deployed to work with eDirectory, a cache most likely exists on the workstation, unless the administrator turned that capability off. After you upgrade, the later version of SecureLogin recognizes the cache left by SecureLogin 2.5 and automatically works with it.
If all SecureLogin 2.5 data was stored in eDirectory, and if SecureLogin 3.51.2 is installed to work with Novell SecretStore®, SecureLogin 3.51.2 is able to use the data from SecureLogin 2.5. This usage occurs because SecureLogin 3.51.2 still uses the Prot:* attributes in the directory, even if it is deployed to use SecretStore.
To upgrade from SecureLogin 2.5:
To upgrade from SecureLogin 3.0.x versions:
Make sure that SecureLogin isn't running on your workstation.
The installation program can normally handle locked files. However, some problems can occur on Windows 9x computers due to the short-name limitation of 8.3 filenames.
Run setup.exe.
SecureLogin 3.51.2 overwrites earlier files but preserves data in the cache. The installation program detects the previous installation settings and uses them as the default.
For example, the cache option defaults to the profile directory, unless the previous installation placed the cache elsewhere.
Setup.exe is in the \securelogin\client directory on the Novell SecureLogin 3.51.2 image or CD.