Novell Doc: Novell SecureLogin 6.0 - Deploying SecureLogin

1.2 Deploying SecureLogin

This section provides information on the following:

1.2.1 Installing Java

SecureLogin 6.0 SP1 supports Java applications. However, during installation the Java Applications component is displayed and available only if Java is installed on your workstation. To check if Java is installed in your system and to download the Java Application:

Go to Add/Remove Programs in the Control Panel and verify if Java is installed in your system.
If Java is not installed, download and install the Java Runtime Environment from the Java Download Web site.

1.2.2 Selecting Modify, Repair, or Remove

If you previously installed SecureLogin, InstallShield detects the installation and displays the following dialog box:

Figure 1-1 InstallShield Wizard

You can use the Modify operation to change components listed in the Select Components dialog box.

However, you can’t change options that aren’t listed. For example, you can't use Modify to change the platform.

Scenario: Changing a SecureLogin Platform. You previously installed the Standalone option to evaluate SecureLogin. After a successful evaluation, you install SecureLogin throughout the company, which is using eDirectory. Because you can’t migrate from Standalone to eDirectory, you select Remove, uninstall SecureLogin, restart the workstation (if prompted), then reinstall.

You can select the Repair option if you want to install any missing components. The installation program detects previously installed components and reinstalls them.

1.2.3 Selecting a Setup Language

You can install SecureLogin by inserting the CD or by running setup.exe found in the securelogin/client directory. The following dialog box is displayed.

Select a language for installation, from the list and click Next. The installation proceeds in the language of your choice.

1.2.4 Using a Silent Install

A silent install provides InstallShield Wizard with instructions for installing SecureLogin. To use a silent install, you have to create and use a response file. The response file contains your responses to the dialog boxes that you encounter during the installation.

Run the installation in the environment that you want the silent installation to run.

Do this before you create a response file, so that you are familiar with the installation process.
Set up a response file by typing
```
Setup.exe –r -f1”c:\setup.iss”
```
The -r parameter instructs InstallShield to record the installation.

The -f1 parameter specifies a filename and absolute path where the response file will be saved. If you omit this parameter, InstallShield saves the file to a default directory.

No space exists between f1 and the first double quotation mark (f1"). Even if you choose not to use double quotation marks, don’t place a space after f1.

Although the double quotation marks aren’t always required, they are required for long paths. You’re safer by always including them.

The path must be absolute, rooted with a drive letter (for example, c). Don’t use a relative path.

The default filename is setup.iss. However, you can specify any name, including the extension. Setup.iss is a text file.

Also, the data in the response file depends on the workstation and options that you select to create the response file.

Scenario: Incompatible Workstations. You create the response file on a Windows 2000 workstation and then silently install on a Windows 2003 workstation. The installation fails.

Scenario: Missing Software. You create a response file on a workstation that has the Novell Client. You then install silently on a workstation that doesn’t have the Novell Client. The installation fails.
(Optional) Set up a log file by adding the following parameters:
```
-f2”C:\setup.log”
```
The path to the log file is also absolute.

The complete entry, with the command, parameters for a response file, and parameters for a log file, appears as follows:
```
Setup.exe –r -f1”C:\setup.iss” -f2”C:\setup.log”
```
A silent install doesn’t display the user interface. If problems arise, you need some mechanism to identify what isn’t working as expected
Run the installation.

InstallShield records all your responses to options in the dialog boxes.
Use the response file and the log for silent installs.

A log file captures install information as result codes. If the result code is 0, the installation was successful. If other result codes appear, refer to the InstallShield documentation.

If you run setup.exe on a workstation that already has SecureLogin, the installation program goes to the Modify/Repair/Remove dialog box. Therefore, if you test the response file by running the silent install on the same workstation, uninstall SecureLogin first. Otherwise, the installation launches the maintenance dialog box and then writes an error code to the log file, indicating that the .iss file wasn’t able to respond to the dialog boxes.

IMPORTANT:After a silent install, you have to reboot the system for SecureLogin to take effect. Otherwise, you might encounter the error message Unable to instantiate ScriptBroker module: 80040154.

You can also create silent Modify, Repair, and Remove response files.

Scenario: Using Silent Modify to Update Workstations. During a Phase 1 rollout, you silently installed SecureLogin on users’ workstations, but didn’t install the Secure Workstation component. Wanting users to have Secure Workstation functionality during the Phase 2 rollout, you create a response file by selecting Modify and the Secure Workstation component. You then update users’ workstations by running silent installs with the new response file.

1.2.5 Automating the Installation

By editing the automate.ini file, you can automate parts of the installation and customize it before distributing SecureLogin to users or other installers.

Open automate.ini, found in the \securelogin\client directory

Read the explanatory paragraphs so that you understand how to customize the installation.
Make changes.

The following figure illustrates the dialog box that enables you to pre-select a Complete or Custom installation.

The [SetupType] section in automate.ini determines whether the dialog box appears
```
[SetupType]
```
```
;ShowDialog=No
```
```
;Selection=Complete
```
```
;Selection=Custom
```
By default, the dialog box displays. If you uncomment the ShowDialog line, the dialog box does not appear, and the installation program installs the Complete option by default.

The following figure illustrates the dialog box that enables users to select a platform:

Figure 1-2 Choosing a Platform

The [Platform] section in automate.ini determines whether the dialog box appears:
```
[Platform]
```
```
;ShowDialog=No
```
```
;Selection=eDirectory
```
```
;Selection=LDAP
```
```
;Selection=ADAM
```
```
;Selection=ActiveDirectory
```
```
;Selection=Standalone
```
By default, the Choose a Platform dialog box displays. If you uncomment the ShowDialog and Selection=eDirectory lines, the dialog box does not appear. Instead, the installation program installs the eDirectory option by default.
Save and exit.

Smartcard Configuration for automate.ini

If you want to use smart card and if ActivClient is installed on your workstation do the following:

Comment the lines that begin with Selection and Location.
Uncomment the line that begins with SecondaryStorage.
Change SecondaryStorage to SmartCard.

NOTE:Make sure you write SmartCard exactly the way shown above as it is case sensitive.

If you want to use smart card and if ActivClient is not installed on your workstation do the following

Uncomment the lines that begin with Selection, Location, and SecondaryStorage.
Change SecondaryStorage to SmartCard.

NOTE:Make sure you write SmartCard exactly the way shown above as it is case sensitive.
Change Selection to the required Cryptographic Service Provider.
Change Location to the path where the PKCS#11 compatible library is present.

If you do not want to use smart card, then do the following:

Comment the lines that begin with Selection and Location.
Equate SecondaryStorage to FILE.

NOTE:Make sure FILE is written in upper case as it case sensitive.

NMAS Methods Configuration for automate.ini

If you want to install NMAS methods, uncomment and equate the corresponding method to Yes.

If you do not want to install NMAS methods, leave the corresponding method commented.