How do I install SecureLogin updates and provide a custom module?
(Last modified: 06Feb2004)
This document (10091034) is provided subject to the disclaimer at the end of this document.
Novell SecureLogin version 3.5
How do I install SecureLogin updates and provide a custom module?
Everytime I perform an installation of SecureLogin, it overwrites my tlaunch.ini
SecureLogin version 3.51 utilizes install shield to perform it's installation of the main program and updates. Because of the initial install design only files that were included in the installation package are updated. This functionality would cause the package version of files that can be customized by the customer to be overwritten.
New functionality was added in the field test patch sl351002.exe to give more control to the administrator and allow the distribution of customized files during the patch install. To implement this new change you would copy the text below into a text file with the filename automate.ini and place the file into the same location as the patch. You would also modify this file with the correct information for the custom file and place the custom file also in the same location. This automate.ini is self documented so for instructions on making the modifications just follow the directions within the file.
; The Novell SecureLogin Client Install Automation File
; Copyright (c) 2003 Novell, Inc. All Rights Reserved
; The SecureLogin Client Install uses this file (automate.ini) to automate
; install tasks. For the install to recognize automate.ini, this file must
; be in the same directory as the install executable file and must be named
; automate.ini. If the install doesn't find automate.ini, the install uses
; the default behavior.
; Most of the sections in this file are used only during an initial install. The
; [FileOverrides] section is used by subsequent updates.
; This section includes information as to where external components can be found
; on the CD. If a drive letter is not specified, the paths are considered to be
; relative to the root of the CD image. Absolute paths can also be specified.
; These sections pertain to the dialogs that are displayed during the install.
; Each key in a dialog's section represents a setting that is exposed in that
; To instruct the install to not show a dialog, uncomment the ShowDialog line
; in the desired dialog section. Uncomment the line that contains the setting
; that you want set as the default. When a dialog is not shown, the default
; setting is used because the person installing doesn't get the opportunity to
; change the setting. For example, uncommenting "ShowDialog=No" and
; "Selection=eDirectory" in the [SecureLoginOption] section results in the
; SecureLogin Option dialog not being displayed during the install, and the
; SecureLogin client is installed with the eDirectory option.
; The install uses the default setting for a line that is commented out. Note
; that the keys within a section must be unique. For example, both the
; "Selection=Typical" line and the "Selection=Custom" line in the [SetupType]
; section should not be uncommented at the same time.
; The section names, keys, and values are case insensitive. The values "Yes"
; and "No" are recognized. The values "True" and "False" are not. The values
; must be spelled correctly in order to be recognized by the install.
; Not showing the reboot dialog causes the install to never reboot the machine
; after the install.
; Turning on a setting that is not displayed during the install will not abort
; the install. For example, the Java support in SecureLogin requires that a Java
; Runtime Environment 1.4 be installed. This component is not displayed during
; the install if Java is not installed. Uncommenting the "SecureLogin\JavaApp"
; line in the [Component] section will not cause the install to fail on
; workstations that do not have Java. The install will just ignore that setting.
; Turning on a setting that is displayed during the install that conflicts with
; the system results in an error message. For example, suppose that the
; "Selection=eDirectory" line in the [SecureLoginOption] section and the
; "Selection=Novell Client" line in the [Protocol] section are uncommented and
; the install is run on a machine without Novell Client 32 being installed.
; Because this protocol setting requires Novell Client 32, the install will show
; an error message. If the "ShowDialog=No" line in the [Protocol] section is also
; uncommented, the install will then abort. Otherwise the user is shown the
; Protocol dialog, and the LDAP setting is automatically selected.
; This section controls whether the modify operation is permitted. To disallow
; any modifications to SecureLogin after it is already installed, the
; AllowModify key must equal No during the initial install.
; The following section is used to override the default files that are built
; into the SecureLogin install. A file override always overwrites the default
; file. The typical use of this section is to distribute, during an initial
; install or during subsequent updates, a custom tlaunch.ini file. The
; file overrides must be located in the same directory as the automate.ini file.
; The file overrides are processed after all the default files are installed but
; before registration occurs. The file overrides are always processed, even if
; the corresponding component wasn't selected. For example, if a file override
; for tlaunch.ini is specified in automate.ini and the Terminal Launcher
; component is not installed on the system, the tlaunch.ini file is still
; copied to the system. All file overrides are included in the uninstall
; operation regardless of whether or not the corresponding component was
; The OverrideCount key specifies the number of file overrides listed in the
; FileOverrides section. Each file override has an entry in this section that
; is made of two keys: OverrideFile# and OverrideDestination#. The # should be
; replaced by a number, starting with 1, that corresponds to the index of the
; file override. The OverrideFile# specifies the name of the file, and the
; OverrideDestination# specifies the directory the file override will be copied
; to. The OverrideDestination# can contain the following macros that will be
; expanded by the install when the file overrides are processed:
; <TargetDir> expands to the path to where SecureLogin is installed.
; <WinSysDir> expands to the Windows system or system32 path.
; <LotusNotesDir> expands to the path that nslasst.dll is copied to.
; The override information is saved in the InstallShield log file and is used
; for Repair and Modify operations. When an update is applied, the file
; overrides included in the update will be added to any existing file overrides
; in the log file. To remove a file override that was specified during a
; previously applied update, specify <Delete> as the destination for that
; override. For example, to remove a file override for tlaunch.ini, use the
; following lines:
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
- Document ID:
- Solution ID: NOVL95417
- Creation Date: 06Feb2004
- Modified Date: 06Feb2004
- NovellNetware Client
Did this document solve your problem? Provide Feedback