--------------------------------------------------------
Installing SmartSuite Applications on a Network Server
--------------------------------------------------------

This file contains information for network administrators who 
are installing SmartSuite applications on a network server.

Contents of this file:
   Supported Networks
   Why Use a SmartSuite Application on a Network?
   Steps to Complete Network Installation
   Designing a Directory Structure for SmartSuite Applications
   How to Install on a Network Server
   How to Install on a Network Node
   The Lotus Licenser Utility
   Notes about Using the Licenser Utility
   Creating Personal Directories
   Creating Shared Data Directories
   Information to Give Users
   If You Have a Problem
   Network-Specific Information for SmartSuite Applications

------------------
Supported Networks
------------------
Lotus supports the following networks.
   
   Artisoft LANtastic version 5.x
   Banyan VINES version 5.5
   DEC PATHWORKS version 4.1
   IBM LAN Server version 3.0
   Microsoft LAN Manager version 2.1a or 2.2
   NCR StarGroup 3.5 version 2.1A
   Novell NetWare 386 version 3.11
   Novell SFT NetWare 286 version 2.15c
   Novell Advanced NetWare 286 version 2.15c
   Novell NetWare 286 version 2.2

----------------------------------------------
Why Use a SmartSuite Application on a Network?
----------------------------------------------
The benefits of using SmartSuite applications on a network 
include the following:

   *  Conserve hard disk space by having only one copy
      of a SmartSuite application on the server instead of 
      a copy on each personal computer.
  
   *  Allow users to share files, computer equipment, 
      printers, backup devices, and other networked resources.

   *  Quickly distribute files, templates, and applications 
      while users access files immediately.
 
   *  Easily support workgroup applications such as customer 
      tracking.

   *  Back up files centrally.

   *  Save time when upgrading to a new release of a SmartSuite 
      application because you upgrade the software on the 
      server instead of on individual computers.

   *  Allow use of diskless workstations.

--------------------------------------
Steps to Complete Network Installation
--------------------------------------
You must complete the following steps to install a SmartSuite
application on the server.

   *  When upgrading from a previous release of a SmartSuite 
      application, copy files that you want to save to another 
      directory before erasing the application files from your server.
 
   *  Create a directory OLDLOTUS and copy all of the files in your
      LOTUSAPP directory to OLDLOTUS.

   *  Determine the location and names of the server directories.

   *  Use the SmartSuite Install program to install the SmartSuite 
      application on the server.

   *  Determine and set the number of network licenses for each 
      SmartSuite application.

      The Licenser utility allows you to set the number of licenses 
      and monitor use to ensure that you have purchased an adequate 
      number of licenses.  See "The Licenser Utility" below.

   *  (Optional) Create a custom help message.
  
   *  Create any personal or shared data directories on the server.

   *  Make printers and network directories available to users.

   *  (Optional) Create a batch file, or update the system or user 
      login script, to connect users to network directories.

   *  Give users the information listed below in "Information to Give 
      Users."

-----------------------------------------------------------
Designing a Directory Structure for SmartSuite Applications
-----------------------------------------------------------
There are several required and optional directories that you and 
SmartSuite Install create. Before you install Lotus products, 
you should decide where you want to put the directories.

   Program directory for 1-2-3 for Windows  (\LOTUS\123R5W)
   Lotus Common directory                   (\LOTUS\LOTUSAPP)
   Licenser Utility Directory               (\LOTUS\LICENSE)
   LOTSHARE                                 (\LOTSHARE)
   License directory for 1-2-3              (\LOTSHARE\123W.V50)


   Program directory for Ami Pro            (\LOTUS\AMIPRO)
   Lotus Common directory                   (\LOTUS\LOTUSAPP)
   Licenser Utility Directory               (\LOTUS\LICENSE)
   LOTSHARE                                 (\LOTSHARE)
   License directory for Ami Pro            (\LOTSHARE\AMIPRO.V30)


   Program directory for Approach           (\LOTUS\APPROACH)
   Lotus Common directory                   (\LOTUS\LOTUSAPP)
   Licenser Utility Directory               (\LOTUS\LICENSE)
   LOTSHARE                                 (\LOTSHARE)
   License directory for Approach           (\LOTSHARE\APR.V30)


   Program directory for Freelance Graphics (\LOTUS\FLW)
   Lotus Common directory                   (\LOTUS\LOTUSAPP)
   Licenser Utility Directory               (\LOTUS\LICENSE)
   LOTSHARE                                 (\LOTSHARE)
   License directory for FLW                (\LOTSHARE\FLW)

----------------------------------
How to Install on a Network Server
----------------------------------
To run Install:

   1.  Insert Disk 1 in drive A.
   2.  From the Program Manager, choose File Run.
   3.  Enter A:\INSTALL in the Command line text box, where A: is
       your floppy drive.

Install consists of a series of dialog boxes that are generally 
self-explanatory. If you need more information when using a 
dialog box, choose Help by clicking the Help button or pressing ALT+H.

When running Install:
  
   *  When you specify a location for the Licenser utility, 
      choose a location to which users do not have access, such 
      as your local hard disk or a secure network directory. 
      If the directory you specify does not exist, Install creates
      it for you.

   *  After you install a SmartSuite application on the network server,
      you must run Node Install before you can run the application.

--------------------------------
How to Install on a Network Node
--------------------------------
Once you have installed SmartSuite on a network server, SmartSuite 
Install resides on that server. To install the applications 
on a node, you must run Node Install.

NOTE: If you want to run a SmartSuite application from the server 
rather than from a node, you must complete Node Install at the server.

To run Node Install:
  
   1.  Open the Windows Program Manager.
   2.  Choose File Run.
   3.  Enter X:\PATH\INSTALL in the Command Line text box, where
       X:\PATH is the drive letter and path for the SmartSuite 
       application program directory on your server.
   4.  Choose OK.
       
--------------------------
The Lotus Licenser Utility
--------------------------
Before network users can start a SmartSuite application, you must set 
the license count to the number of licenses your organization has
purchased.  The license count determines the number of users (from 1 
to 1000) who can run the SmartSuite application at the same time. 

To set the license count:
   1.  If you are working at a node, connect to the server where the 
       license directory resides. If you are working at the server, go
       to step 2.
   2.  Make sure that the license directory appears at either the 
       current directory or the root directory of any drive. For 
       example, connect or map directly to the license directory and 
       call it drive H so that the license directory looks like the 
       root directory of drive H.
   3.  Open the Windows Program Manager.
   4.  Make the window that contains the Licenser application icon 
       the active window.
   5.  Choose the application icon for Licenser.

--------------------------------------
Notes About Using the Licenser Utility
--------------------------------------
   *  Although the license count limits how many users can use a 
      SmartSuite application simultaneously, it does not limit the 
      number of nodes you can set up to use the application.
   *  When the number of users exceeds the license count, the 
      Licenser utility creates a log file to track them. Check the 
      log file to ensure that users are not denied access to the 
      network. If users are denied access often, you may need to 
      purchase additional licenses. You can only increase the license 
      count when your organization purchases additional licenses.
   *  You can create a custom help message to give users additional
      assistance after a SmartSuite application displays a message 
      indicating that no licenses are available. This message appears 
      after the application's message and should include helpful 
      information such as instructions for connecting to another server 
      or for contacting the network administrator. To create a custom 
      help message, type up to 400 characters in a text editor and save 
      it with the file name LOTUS.LOM in the application's program 
      directory.
   *  You can split the total number of purchased licenses between 
      two or more directories or servers (license pools). For example, 
      if you purchased 23 licenses, you can create a license directory 
      on one server and install 15 licenses in that license directory. 
      You can create another license directory on another server and 
      install the remaining 8 licenses in that directory. When a user 
      starts a SmartSuite application, that application searches all 
      visible license pools on accessible remote drives for an available
      license.
   *  If you need more information when using Licenser, use Help.

-----------------------------
Creating Personal Directories
-----------------------------
Everyone who runs a SmartSuite application from a server must have a 
personal directory, either on the server or on a node. A personal 
directory contains the application configuration files. Users can 
also store data or other files in their personal directories. 
(Each SmartSuite application requires a separate personal directory.)

When deciding where to locate personal directories, you should 
determine if the server or node has enough disk space for personal 
directories. Also, the server may be the more convenient location 
for personal directories if the system administrator is responsible 
for regularly backing up and archiving data files.

If you decide to put personal directories on nodes, let users create 
them because they are familiar with the directory structure of their 
hard disks. During installation on a node, Install prompts users for 
the name and location of their personal directory, and creates the 
directory if it does not already exist.

If you decide to put personal directories on the server, you should 
create the directories because you must assign network names and 
access privileges to those directories.

--------------------------------
Creating Shared Data Directories
--------------------------------
Shared data directories contain data files users create. One copy of a 
shared data file may serve many users. Shared data directories can 
have any name, can be in any location on the server, and should be 
available to node users.
 
After you install the SmartSuite application(s) on the server and set 
the license count, make the server directories available to network 
users.  The procedure differs for each network; however, you generally need 
to give users read-only access to directories in which you don't want 
them to write over, delete, or create files, and give each full access 
to a personal directory. Additionally, if applicable for your network, 
make directories shareable by giving the directory location on the 
server a network name (share name).

-------------------------
Information to Give Users
-------------------------
You should provide users with the following information:
   *  instructions on how to connect to
      - the network
      - server directories, such as the SmartSuite application program,
        license, personal, and shared data directories
        NOTE: Users must use the same drive letter and path when they
              connect to the program and personal directories as they
              used when they first installed the SmartSuite application. 
              It is a good idea to tell them which letter and path to use
              when they install and then provide them with a batch file 
              to connect to these directories.
      - network printers, and how to print on a network
   *  information on using the SmartSuite Install program
   *  information on starting SmartSuite applications
   *  information on other applications as required

---------------------
If You Have a Problem
---------------------
PROBLEM: A user cannot run a SmartSuite application from the assigned node.
SOLUTION: Ensure that the user has completed the SmartSuite Install 
successfully, that the network connections to the SmartSuite 
application program and license directories on the server are 
valid, and that users have read-only access to the program directory, 
but both read and write access to the license directory.

PROBLEM: When clicking the icon to start a SmartSuite application, 
a user received an error message saying the path is invalid or 
the file is not found.
SOLUTION: Before starting Windows, connect to the SmartSuite application 
program directory. Use the same drive letter that exists in the 
Command Line text box in the Windows Program Item Properties dialog box. 
To check this, click the program icon and choose File Properties from 
the Windows Program Manager. If you used a different letter to connect 
to the program directory, reconnect using the correct letter or start 
the program using File Run from the Program Manager instead of clicking 
the program icon.

PROBLEM: No user can use a SmartSuite application from any node.
SOLUTION: Use the Licenser utility to verify that the license count 
is set correctly. If it is, make the program and license directories 
network shared with the correct access privileges.

PROBLEM: A user is denied access to a SmartSuite application on the 
network and receives a message saying that a license cannot be obtained.
SOLUTION: Use the Licenser utility to generate a log file to see if the 
user couldn't get a license because none were available. If you run 
Licenser at the node and no license directories are found, the node is 
not properly connected to the license directory.  If users are denied 
access frequently, there are probably more users trying to access the 
SmartSuite application than the number of licenses available. 
You may need to purchase additional licenses to allow more users 
access to the program.

PROBLEM: The Licenser utility does not include a SmartSuite application 
license directory in the list of license directories it displays.
SOLUTION: The Licenser utility looks in the following four locations,
in the order listed, for the license directory:
   *  the current directory
   *  LOTSHARE, a subdirectory of the current directory
   *  the root directory
   *  LOTSHARE, a subdirectory of the root directory
Licenser searches each logical drive from C through Z. If the license 
directory does not appear in one of the locations listed above, run the 
SmartSuite Install to make one of the pre-defined locations the 
license directory.

PROBLEM: A user tries to gain access to a shared data file in the 
shared data directory on the server and receives a message indicating 
that no reservation is available.
SOLUTION: This problem could be caused by any of the following:
   *  Another user has the file reservation.
   *  The directory is a read-only directory and does not allow users 
      to write to files.
   *  The file is a read-only file.


--------------------------------------------------------
NETWORK-SPECIFIC INFORMATION FOR SMARTSUITE APPLICATIONS
--------------------------------------------------------

--------------------------------------
--------------------------------------
NETWORK-SPECIFIC INFORMATION FOR 1-2-3
--------------------------------------
--------------------------------------

------------------------------
Artisoft LANtastic version 5.x
------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   recommended share name - 123R5W
   access - read (R)
Lotus Shared Tools directory
   recommended share name - LOTUSAPP
   access - read (R)
   NOTE: After installing 1-2-3, users will not be able to use 1-2-3
         unless you make each file in the Lotus Shared Tools directory 
         a read-only file. To do so, use the DOS ATTRIB command.
Licenser Utility directory
   recommended share name - LICENSER
   access - none
License directory
   recommended share name - LOTSHARE
   access - Read-Write-Create-Delete (RWCD)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

-------------------------------------
Banyan VINES version 5.1 (0) or later
-------------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   recommended StreetTalk item name - 123R5W@GROUP@ORGANIZATION
   access - read (R)
Lotus Shared Tools directory
   recommended StreetTalk item name - LOTUSAPP@GROUP@ORGANIZATION
   access - read (R)
   NOTE: After installing 1-2-3, users will not be able to use 1-2-3
         unless you make each file in the Lotus Shared Tools directory 
         a read-only file. To do so, use the DOS ATTRIB command.
Licenser Utility directory
   recommended StreetTalk item name - LICENSER@GROUP@ORGANIZATION
   access - none
License directory
   recommended share name - LOTSHARE@GROUP@ORGANIZATION
   access - Modify (M)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

----------------------------------
DEC PATHWORKS version 4.1 or later
----------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   recommended application file service name - 123R5W
   access - read (R)
Lotus Shared Tools directory
   recommended application file service name - LOTUSAPP
   access - read (R)
Licenser Utility directory
   recommended application file service name - LICENSER
   access - none
License directory
   recommended application file service name - LOTSHARE
   access - Read-Write-Create-Delete (RWCD)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

--------------------------
IBM LAN Server version 3.0
--------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   recommended alias - 123R5W
   access - read (R)
Lotus Shared Tools directory
   recommended alias - LOTUSAPP
   access - read (R)
Licenser Utility directory
   recommended alias - LICENSER
   access - none
Path to License directory
   recommended alias - LOTSHARE
   access - Read-Write-Create-Delete (RWCD)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

--------------------------------------------------
Microsoft LAN Manager version 2.1a or 2.2 or later
--------------------------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   recommended share name - 123R5W
   access - read (R)
Lotus Shared Tools directory
   recommended share name - LOTUSAPP
   access - Read (R)
Licenser Utility directory
   recommended share name - LICENSER
   access - none
License directory
   recommended directory path - x:\LOTSHARE
   recommended share name - LICENSE
   access - Create-Delete-Read-Change Attributes-Write (CDRAW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

------------------------------
NCR StarGroup 3.5 version 2.1A
------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   recommended share name - 123R5W
   access - Read (R)
Lotus Shared Tools directory
   recommended share name - LOTUSAPP
   access - Read (R)
   NOTE: After installing 1-2-3, users will not be able to use 1-2-3
         unless you make each file in the Lotus Shared Tools directory 
         a read-only file. To do so, use the DOS ATTRIB command.
Licenser Utility directory
   recommended share name - LICENSER
   access - none
License directory
   recommended share name - LOTSHARE
   access - Read-Write (RW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

-------------------------------
Novell NetWare 386 version 3.11
-------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   access - Read-File Scan (RF)
Lotus Shared Tools directory
   access - Read-File Scan (RF)
Licenser Utility directory
   access - none
License directory
   access - Create-Erase-File Scan-Modify-Read-Write (CEFMRW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

------------------------------------
Novell SFT NetWare 286 version 2.15c
------------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   access - Read-Open-Search (ROS)
Lotus Shared Tools directory
   access - Read-Open-Search (ROS)
Licenser Utility directory
   access - none
License directory
   access - All (RWOCDPSM)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

-----------------------------------------
Novell Advanced NetWare 286 version 2.15c
-----------------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   access - Read-Open-Search (ROS)
Lotus Shared Tools directory
   access - Read-Open-Search (ROS)
Licenser Utility directory
   access - none
License directory
   access - All (RWOCDPSM)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

------------------------------
Novell NetWare 286 version 2.2
------------------------------
Lotus recommends that you organize the server directories as follows:
1-2-3 program directory
   access - Read-File Scan (RF)
Lotus Shared Tools directory
   access - Read-File Scan (RF)
Licenser Utility directory
   access - none
License directory
   access - Create-Erase-File Scan-Modify-Read-Write (CEFMRW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 
         

----------------------------------------
----------------------------------------
NETWORK-SPECIFIC INFORMATION FOR AMI PRO
----------------------------------------
----------------------------------------
         
When creating shared data directories, users will need 
read-write-modify-erase-file scan access to the license
directory.

Users will need read-write-create-modify-erase-file scan access 
to use documents on the network.

Users will need read-file scan access to the Ami Pro 
executable files.


---------------------------------------------------------------
---------------------------------------------------------------
NETWORK-SPECIFIC INFORMATION FOR FREELANCE GRAPHICS FOR WINDOWS
---------------------------------------------------------------
---------------------------------------------------------------

------------------------------
Artisoft LANtastic version 4.1
------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   recommended share name - FLW
   access - read (R)
Lotus Shared Tools directory
   recommended share name - LOTUSAPP
   access - read (R)
   NOTE: After installing Freelance Graphics for Windows, users will not 
         be able to use it unless you make each file in the Lotus Shared 
         Tools directory a read-only file. To do so, use the DOS ATTRIB 
         command.
Licenser Utility directory
   recommended share name - LICENSER
   access - none
License directory
   recommended share name - LOTSHARE
   access - Read-Write-Create-Delete (RWCD)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

-------------------------------------
Banyan VINES version 5.1 or later
-------------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   recommended StreetTalk item name - FLW@GROUP@ORGANIZATION
   access - read (R)
Lotus Shared Tools directory
   recommended StreetTalk item name - LOTUSAPP@GROUP@ORGANIZATION
   access - read (R)
   NOTE: After installing Freelance Graphics for Windows, users will not 
         be able to use it unless you make each file in the Lotus Shared 
         Tools directory a read-only file. To do so, use the DOS ATTRIB 
         command.
Licenser Utility directory
   recommended StreetTalk item name - LICENSER@GROUP@ORGANIZATION
   access - none
License directory
   recommended share name - LOTSHARE@GROUP@ORGANIZATION
   access - Modify (M)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

----------------------------------
DEC PATHWORKS version 4.1 or later
----------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   recommended application file service name - FLW
   access - read (R)
Lotus Shared Tools directory
   recommended application file service name - LOTUSAPP
   access - read (R)
Licenser Utility directory
   recommended application file service name - LICENSER
   access - none
License directory
   recommended application file service name - LOTSHARE
   access - Read-Write-Create-Delete (RWCD)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

--------------------------
IBM LAN Server version 3.0
--------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   recommended alias - FLW
   access - read (R)
Lotus Shared Tools directory
   recommended alias - LOTUSAPP
   access - read (R)
Licenser Utility directory
   recommended alias - LICENSER
   access - none
Path to License directory
   recommended alias - LOTSHARE
   access - Read-Write-Create-Delete (RWCD)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

--------------------------------------------------
Microsoft LAN Manager version 2.1a or 2.2 or later
--------------------------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   recommended share name - FLW
   access - read (R)
Lotus Shared Tools directory
   recommended share name - LOTUSAPP
   access - Read (R)
Licenser Utility directory
   recommended share name - LICENSER
   access - none
License directory
   recommended directory path - X:\LOTSHARE
   recommended share name - LICENSE
   access - Create-Delete-Read-Change Attributes-Write (CDRAW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

------------------------------
NCR StarGroup 3.5 version 2.1A
------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   recommended share name - FLW
   access - Read (R)
Lotus Shared Tools directory
   recommended share name - LOTUSAPP
   access - Read (R)
   NOTE: After installing Freelance Graphics for Windows, users will not
         be able to use it unless you make each file in the Lotus Shared 
         Tools directory a read-only file. To do so, use the DOS ATTRIB 
         command.
Licenser Utility directory
   recommended share name - LICENSER
   access - none
License directory
   recommended share name - LOTSHARE
   access - Read-Write (RW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

-------------------------------
Novell NetWare 386 version 3.11
-------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   access - Read-File Scan (RF)
Lotus Shared Tools directory
   access - Read-File Scan (RF)
Licenser Utility directory
   access - none
License directory
   access - Create-Erase-File Scan-Modify-Read-Write (CEFMRW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

------------------------------------
Novell SFT NetWare 286 version 2.15c
------------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   access - Read-Open-Search (ROS)
Lotus Shared Tools directory
   access - Read-Open-Search (ROS)
Licenser Utility directory
   access - none
License directory
   access - All (RWOCDPSM)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

-----------------------------------------
Novell Advanced NetWare 286 version 2.15c
-----------------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   access - Read-Open-Search (ROS)
Lotus Shared Tools directory
   access - Read-Open-Search (ROS)
Licenser Utility directory
   access - none
License directory
   access - All (RWOCDPSM)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself. 

------------------------------
Novell NetWare 286 version 2.2
------------------------------
Lotus recommends that you organize the server directories as follows:
X:\LOTUS\FLW program directory
   access - Read-File Scan (RF)
Lotus Shared Tools directory
   access - Read-File Scan (RF)
Licenser Utility directory
   access - none
License directory
   access - Create-Erase-File Scan-Modify-Read-Write (CEFMRW)
   NOTE: Share the directory that contains the license directory rather 
         than the license directory itself.
