Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.
How can I easily upgrade the version of SecureLogin installed on the workstation?
Before attempting to upgrade SecureLogin you should read the product manuals and release notes so you are aware of all the issues. For example, some versions of SecureLogin may include schema upgrades that need to be run prior to rolling out the client.
This document provides information on how you can use a Startup application definition to upgrade SecureLogin.
Note: You should test thoroughly before rolling into production.
You can force the upgrade for users who have an earlier version of SecureLogin installed on their workstation using a SecureLogin Startup script. The Startup script method is typically used if you donât have a way of forcing the upgrade with your software distribution utilities.
A SecureLogin Startup script similar to the one below checks the version of SecureLogin running on the workstation and runs the upgrade process if it is earlier than v3.5.1 (for example). The following line will display the version of SecureLogin installed on the workstation so you can edit the value to check against.
Startup Script Example
#========================================================== # When SecureLogin loads, Startup scripts run # This script checks the version of SecureLogin installed on the workstation # If it is earlier than v3.5.1 it will close SecureLogin and force the upgrade #========================================================== If ?SysVersion(System) Lt ""3050100""MessageBox ""SecureLogin SSO, which handles automatic logon to your applications, must be upgraded to the newest version for security and maintenance reasons. It takes approximately 3 minutes, will be installed automatically and will reboot your workstation. Click OK to continue.""KillApp ""slproto.exe""KillApp ""slbroker.exe""KillApp ""slwinsso.exe""Run ""Z:\Upgrade.Cmd"" Else EndIf
Note: New application definition commands will not work with old versions of the SecureLogin client. Wait until you upgrade all clients before incorporating new commands. You can use SNMP alerts (see the SecureLogin scripting guide for more information about the SNMP command) to determine if anyone is running an old version of the client.