Novell Documentation: Novell SecureLogin 3.51 SP2 - Troubleshooting a Workstation Installation

Troubleshooting a Workstation Installation

Installing Login Extensions to the Workstation

To enable the login so that it can single sign-on to Terminal Services itself, you need to install the SLINA login extensions.

The procedures in the following sections set up your workstations to support the terminal services integration. The files used for the installation are specific to an environment. Therefore, match the appropriate files from the installation source to your environment. Otherwise, the extensions won't function correctly.

Your SecureLogin components for terminal services must match the version of SecureLogin that you are using. When you upgrade to a new version of SecureLogin, you must also upgrade the integration components.

If you install or uninstall a Novell Client^TM after installing the SecureLogin SSO modules, you must install the correct modules for SecureLogin SSO to work correctly. The installation steps will advise which the correct files are.

Your client configuration doesn't need to match your server configuration. For example, you can use a workstation with the Novell Client installed to connect to a server that doesn't have the client installed, and vice versa.

Workstations with the Microsoft Client

NOTE: Windows 95 does not support the GINA credential passthrough without the Novell client installed.

Using the Windows Add/Remove Programs utility, remove earlier versions of SecureLogin.
Launch the installation wizard by executing the SecureLogin Single Sign-On.msi file from the root directory of the installation CD or download image.
In the Welcome dialog box, click Next.
Read the license agreement, select I Accept the Terms in the License Agreement, then click Next.
Select Standard, then click Next.
Select Microsoft Active Directory (ADS) as the installation type from the install options list.
To launch SecureLogin each time the workstation starts, select Run at Startup, then click Next.
Click Install.

A progress meter runs during the installation.
(Conditional) Enter a passphrase.

If you selected Launch SecureLogin After Install, you are prompted to enter a passphrase. Otherwise, you are prompted to enter a passphrase the first time SecureLogin is run. For more information on the passphrase, see "Managing Passphrases" in the Nsure SecureLogin 3.51.2 Administration Guide.
Replace the workstation's GINA by copying wks\ms\sl_tscgina.dll to the Windows System directory (c:\WinNT\System32).
Register the GINA by double-clicking wks\ms\winlogon_client_.reg.
Select Yes, then click OK.
Restart the workstation.

Workstations with the Novell Client (No NMAS)

Using the Windows Add/Remove Programs utility, remove earlier versions of SecureLogin.
Launch the installation wizard by executing the SecureLogin Single Sign-On.msi file from the root directory of the installation CD or download image.
In the Welcome dialog box, click Next.
Read the license agreement, select I Accept the Terms in the License Agreement, then click Next.
Click Change to select an alternative destination folder for SecureLogin, or click Next to accept the default destination folder for SecureLogin (C:\Program Files\Novell\SecureLogin).
Select eDirectory as the installation type from the install options list.
To launch SecureLogin each time the workstation starts, select Run at Startup, then click Next.
Click Install.

A progress meter runs during the installation.
(Conditional) Enter a passphrase.

If you selected Launch SecureLogin After Install, you are prompted to enter a passphrase. Otherwise, you are prompted to enter a passphrase the first time SecureLogin is run. For more information on the passphrase, see "Managing Passphrases" in the Nsure SecureLogin 3.51.2 Administration Guide.
Set up the Novell login extensions by copying wks\nw\slgina.dll to the Windows System directory (c:\WinNT\System32) on the workstation.
Register the login extensions.

If the workstation is running Windows NT, 2000, or XP, double-click wks\nw\register nt loginext.reg.

If the workstation is running Windows 9x or ME, double-click wks\na\register 98 loginext.reg.
Set up Microsoft Layer for Unicode on Windows 9x or ME.

If the workstation is running Windows NT, 2000 or XP, skip this step.

If the workstation is running Windows 9x or ME, copy redistributable\unicows.dll to the System directory (c:\Windows\System).
Restart the workstation.

Workstations with the Novell Client (with NMAS)

Using the Windows Add/Remove Programs utility, remove earlier versions of SecureLogin.
Launch the installation wizard by executing the SecureLogin Single Sign-On.msi file from the root directory of the installation CD or download image.
In the Welcome dialog box, click Next.
Read the license agreement, select I Accept the Terms in the License Agreement, then click Next.
Click Change to select an alternative destination folder for SecureLogin, or click Next to accept the default destination folder for SecureLogin (C:\Program Files\Novell\SecureLogin).
Select eDirectory as the installation type from the install options list.
To launch SecureLogin each time the workstation starts, select Run at Startup, then click Next.
Click Install.

A progress meter runs during the installation.
(Conditional) Enter a passphrase.

If you selected Launch SecureLogin After Install, you are prompted to enter a passphrase. Otherwise, you are prompted to enter a passphrase the first time SecureLogin is run. For more information on the passphrase, see "Managing Passphrases" in the Nsure SecureLogin 3.51.2 Administration Guide.
Copy wks\nw\slnmas.dll to the Windows System directory (c:\WinNT\System32) on the workstation.

NOTE: The slnmas.dll file is not a login extension. It is called by the NMAS client instead. It isn't necessary to run the Registry (.reg) file if you are using the NMAS client with slnmas.dll. However, you need to install the version of NMAS client that comes with SecureLogin v3.0.1 or later. These later versions are slnmas.dll aware.
Set up Microsoft Layer for Unicode on Windows 9x or ME.

If the workstation is running Windows NT, 2000, or XP, skip this step.

If the workstation is running Windows 9x or ME, copy redistributable\unicows.dll to the System directory (c:\Windows\System).
Restart the workstation.

Installing Virtual Channel Drivers On the Workstation

The procedures in this section outline the steps necessary to set up your workstations to support the terminal services Virtual Channel. You must match the appropriate files from the installation source to your environment. Otherwise, the extensions won't function correctly.

Install the Virtual Channel drivers on the workstation, not the server.

Workstation with Citrix Client (ICA)

To install the Virtual channel driver:

Copy vcd\ica\vdPSLSSON.dll from the SecureLogin 3.51 CD or download image to the ICA Client directory (c:\Program Files\Citrix\ICA Client).
Register the driver by making the following changes to the module.ini file located in the ICA Client directory (c:\Program Files\Citrix\ICA Client).
1. Navigate to the Virtual Driver line in the section [ICA 3.0].
2. Add the name of the Virtual Driver to the end of the Virtual Driver line.
  
  For example, add PSLSSO.
3. At the end of the [Virtual Driver] section, add a driver assignment statement.
  
  For the PSLSSO driver, type
```
PSLSSO    =
```
  The extra spaces are for appropriate indentation. The spaces aren't required.
4. Create a new section [PSLSSO] as follows:
```
[PSLSSO] 
DriverNameWin32 = VDPSLSSO.DLL
```
  The vcd\ica directory contains a sample module.ini file for reference.

Workstation with Terminal Server Client (RDP)

Install the driver by copying vcd\rdp\tsPSLSSO.dll from the SecureLogin 3.51 CD or download image to the Windows System directory (c:\WinNT\System32).
Register the driver by double-clicking vcd\rdp\Terminal Server Driver registration on Client workstation.reg.