Setting Up SecureLogin for NT 4 Domains

To set up SecureLogin for NT 4 domains:

• Set up a shared folder
• Administer a corporate script

Setting Up a Shared Folder

1. On the NT 4 Domain server, create a shared folder on your shared drive.

   Each user must have access to this shared folder. Users' workstations read the corporate script file in this shared folder.

   You (the administrator) can assign this folder any name (for example, userdata). This folder handles all prebuilt scripts.

2. On the server, create a home directory for each user.

   Every user who logs in to an NT 4 domain must access a home directory created on the server.

   From the administrative server, click Start > Administrative Tools > User Manager for Domains, then click New User.

3. Type a name (for example, mkurz).

4. Assign a password.

5. Under Profile, map the home directory to a drive.

   You must map a home directory to drive:\servername\sharename. In the Connect field, enter the drive letter. In the To field, enter a sharename, which is the IP address, NetBIOS name, or DNS name that distinguishes the server.

   The following figure illustrates these fields.

   
   

   The client logs in to the domain and maps a drive (for example, Z) to the home directory (for example, mkurz). The domain automatically maps the users's home directory. The user's data goes into this directory.When the user logs in, the user has rights to the area.

Administering Scripts for NT

To administer corporate scripts in an NT environment:

1. Run the NT Corporate Script Editor from the Start menu.

2. From the NT Corporate Configuration Editor screen, select an option.

   
   

   To create a new corporate script for your environment, select Create New Configuration File.

   To modify an existing corporate script for your environment, select Open Existing Corporate Script.

3. Select a current corporate script or define a name for a new corporate script.

   
   

   This corporate script (for example, CORP_SCRIPTS.FCS) must be in a shared directory that users have access to. Access to the corporate script files is governed by the standard NT file permissions.

   IMPORTANT:  Ensure that users have Read Only access to this file.

4. Select a configuration to edit.

   
   

   To edit the current corporate scripts, select Edit Scripts.

   To edit the current preferences for this corporate script, select Edit Preferences. The following figure illustrates the Preferences property page:

   
   

   To browse for another script to edit, select Edit Another Script.

The following figure illustrates the main NT script editor window:

This editor operates in the same manner as the user script editor. However, no user variables are stored at this location and there is no Display Passwords option.

To set up a user's configuration to load a corporate script, do one of the following:

• Pass in the path to the script as the argument to proto.exe.

  Edit the registry and change the setting HK_CURRENT_USER/Software/Microsoft/Windows/Current/Run so it has the corporate script location after proto.exe.

• Remove the above key and create a shortcut similar to the following:

  c:\program files\novell\securelogin\proto.exe s:securelogin\production.scs

  Place this shortcut in the user's startup folder.

  To ensure that SecureLogin will also read from this location, another registry setting exists to keep track of the last location a corporate script was run from. The location for this registry setting is HKEY_CURRENT_USER\Software\\Protocom\\SecureLogin\\LastNTCORPLocation.

  If you close and reload SecureLogin, it will load the corporate script from the last known location.