PC go! 1996 January

home *** CD-ROM | disk | FTP | other *** search

/ PC go! 1996 January / Image.iso / pcgo / demo / lotus / lwp95gr / readnet.txt < prev next >

Wrap

Text File | 1995-08-16 | 22.9 KB | 557 lines

Installing Lotus Products on a Network Server ---------------------------------------------------------------------- This file contains information for network administrators who are installing Lotus products on a network file server. Contents of this file: 1. Supported Networks 2. Why Use a Lotus Application on a Network? 3. Steps to Complete a Network Installation 4. Designing a Directory Structure for Lotus Applications 5. How to Install on a File Server 6. How to Install on a Network Node 7. Creating Personal Directories 8. Creating Shared Data Directories 9. Automated Install 10. Automated Uninstall 11. Information to Give Users 12. Custom Distribution of End User Files 13. If You Have a Problem 14. Network-Specific Information for XXX ---------------------- 1. Supported Networks ---------------------- Lotus supports the following networks. Artisoft LANtastic versions 5.0 and 6.0 Banyan VINES version 5.5x and 6.0 DEC PATHWORKS version 4.1 and later IBM LAN Server versions 3.0 and 4.0 Microsoft LAN Manager versions 2.1a, 2.2, and later Microsoft Windows NT Advanced Server versions 3.51 and later NCR StarGroup 3.5 version 2.1A Novell NetWare versions 3.x, 4.0x, and 4.1 --------------------------------------------- 2. Why Use a Lotus Application on a Network? --------------------------------------------- The benefits of using Lotus applications on a network include: * Conserve hard disk space by having only one copy of a Lotus application on the file 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. * Back up files centrally. * Save time when upgrading to a new release of a Lotus application, because you upgrade the software on the file server instead of on individual computers. ------------------------------------------ 3. Steps to Complete a Network Installation ------------------------------------------ You must complete the following steps to install a Lotus application on a file server. 1. When upgrading from a previous release of a Lotus application, copy files that you want to save to another directory before erasing the program files from your server. 2. Determine the location and names of the server directories. 3. Use the Lotus Install program to install the Lotus application on the server. Please keep in mind that if you are not installing to a UNC path, node users must use the same drive letter(s) during the node install as you use during the file server install. Also, these drive letters must refer to the same level in the directory hierarchy as they do on the file server. 4. Create any personal or shared data directories on the file server. 5. Make printers and network directories available to users. 6. (Optional) Create a batch file, or update the system or user login script, to connect users to network directories. 7. Give users the information listed in section 11, "Information to Give Users," of this document. ---------------------------------------------------------- 4. Designing a Directory Structure for Lotus Applications ---------------------------------------------------------- There are several required and optional directories that you and Lotus Install create. Before you install Lotus products, you should decide where you want to put the directories. We recommend that you use the directory structure shown here: Main Lotus directory (\LOTUS) Program directory - XXX Release N (\LOTUS\XXX) ----------------------------------- 5. How to Install on a File Server ----------------------------------- To run a File Server Install: 1. Insert Disk 1 or the CD-ROM into the appropriate drive. 2. (Windows 95) Choose Run from the Start menu. (Windows NT 3.51) Choose File Run from the Program Manager. 3. Enter X:\INSTALL in the Run dialog box, where X: is your floppy or CD-ROM 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. Note that if you do a Distribution Install to the file server, you can run subsequent standard and file server installs from the Distribution Install. When running Install: * Use the Node User Feature Access dialog to specify whether node users can copy any product features to their personal directory. (The features are available to node users whether they can copy them or not.) * After you install a Lotus application on the file server, you must run a Node Install before you can run the application. * If you are not installing to a UNC drive, node users must use the same drive letter(s) during the node install as you use during the file server install. Also, these drive letters must refer to the same level in the directory hierarchy as they do on the file server. ------------------------------------ 6. How to Install on a Network Node ------------------------------------ Once you have installed a Lotus application on a network file server, the Lotus Node Install program resides on that server. To install the application on a node, you must run a Node Install. NOTE: If you want to run a Lotus application from the file server rather than from a node, you must complete the Node Install on the file server. To run Node Install: 1. (Windows 95) Choose Run from the Start menu. (Windows NT 3.51) Choose File Run from the Program Manager. 2. Enter X:\PATH\INSTALL in the Run dialog box, where X:\PATH is the drive letter and path for the main Lotus directory of the Lotus application on your file server. 3. Choose OK. NOTE: Node users must map to the same drive letter(s) used during the File Server Install. --------------------------------- 7. Creating Personal Directories --------------------------------- Users who run a Lotus application from a file server must have a personal directory. This directory can reside on either the file server or a node, and contains the application configuration files. If you selected features during the file server install that node users could copy, the personal directory contains these also. Users can also store data or other files in their personal directories. NOTE: Users must have a separate personal directory for each Lotus application. When deciding where to locate personal directories, determine if the file server or node has enough disk space for personal directories. Also, the file server may be the more convenient location for personal directories if you are 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 file server, create the directories yourself, because you must assign network names and access privileges to those directories. ------------------------------------ 8. 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 file server, and must be available to node users. After you install the Lotus application(s) on the file server, 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 user 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). --------------------- 9. Automated Install --------------------- Automated install is a feature that allows users to run the Lotus Install program without the user interface. This feature is particularly useful for network administrators who must manage installs and upgrades for large groups of users. You use this feature by filling in the fields in the response file (instxxx.rsp), and then making that file available to users. The information you supply in this file provides input to the Install program so it can run without user intervention. NOTE: Only network administrators should edit the response file. Individual users should use the response file provided to them by their network administrator. To use the automated install feature, first prepare the response file: 1. Back up the response file by copying it to a new name (instxxx.sav, for example). 2. In the original response file, provide the information for each field. Examine each default value to make sure it is the value you want. Read the comments for each field for information about legal values and possible interactions with other fields. 3. Validate your response file by running an Install that uses the response file as input. (See the command line information below). The Install program displays any errors that occur. Remember that if you are testing Node Installs, you must run a File Server Install first. When your response file has no errors and performs the install as you intend, make it available to your users with instructions about how to run the Install program. You might want to tell them what command line to type, or you might choose a different method. The best distribution strategy depends on the tools available at your site. To run an automated install: 1. (Windows 95) Choose Run from the Start menu. (Windows NT 3.51) Choose File Run from the Program Manager. 2. Type the install command: <path>\install /A <ResponseFilePath> [/U ["UserName"]] [/O [<LogFilePath>]] [/?] where: * path is the location of the install program executable. * /A turns on the automated install feature. * ResponseFilePath is the location of the response file. Always specify the full path to this file. * /U allows you to specify the name of the user. * "UserName" is the name of the user to which this copy of the program is registered. See the comments for the UserName field below for information about defaults. * /O turns on status logging. * LogFilePath is the full path and name of the status log file. If you do not specify a path, this defaults to lotinst.log in the directory where Windows was installed. * /? brings up the command line usage message Hints and Tips: * Do not change the field names to the left of the equal signs (=) in the response file. Changing the field names will cause errors. * Do not remove fields from the response file. Removing fields will cause errors. ------------- 10. Uninstall ------------- The Uninstall feature of the Lotus Install program is new in this release. You can run Uninstall from the Start menu (Windows 95) or the Program Manager (Windows NT 3.51). To run Uninstall from Windows 95: 1. Choose Settings - Control Panel from the Start menu. 2. Select Add/Remove Programs. 3. Choose the program to be removed. 4. Click Remove. In this release, you can uninstall Word Pro, Approach, and Freelance Graphics. You cannot uninstall 1-2-3 for Windows or Organizer. Network administrators can run an automated Uninstall by using the Uninstall command line. LUNIN10 /T <ProductName> /V <ProductVersion> /I <INF_file_path> /C <CINSTALL.INI_file_path> [/A] [/O [<LogFilePath>]] [/L <LanguageCode>] [/U <UserName>] where: * /T <ProductName> is the product name, exactly as found in the Registry. * /V <ProductVersion> is the product version, exactly as found in the Registry. * /I <INF_file_path> is the the complete path and name of the file that lists the product files. This file always has an .INF extension. * /C <CINSTALL.INI_file_path> is the complete path and name of the install configuration file, CINSTALL.INI. * [/A] causes an automated Uninstall. * [/O [<LogFilePath>]]] specifies the name and location of the message log file Uninstall creates. This file will include a record of each item removed and any error messages encountered. If you omit this parameter, it defaults to LOTUNIN.LOG in the Windows directory. * [/L <LanguageCode>] specifies the language in which Uninstall will run. If you omit this parameter, Uninstall defaults to English. Valid codes are the 2-character ISO standard language codes. You can enter any language code here, as long as you have installed the product in that language on this system. * [/U <UserName>] specifies the user name to place in the Uninstall log file. This parameter is for informational purposes only. If you omit this parameter, Uninstall defaults to the current user. For example, the following Uninstall command line would invoke the English version of Uninstall to remove ABC release 2.1. In this example, the main Lotus directory is called LOTUS, the main product directory is ABC, and the log file will be written to the root of C instead of the Windows directory. LUNIN10 /T ABC /R 2.1 /I C:\LOTUS\ABC\ABC.INF /C C:\LOTUS\ABC\CINSTALL.INI /A /O C:\LOTUNIN.LOG /L EN /U NETADMIN NOTE TO CIT CLIENTS: Before you distribute this information, be sure to review the parameter information carefully. Make the example specific to your product, or at least provide your product name and version exactly as they appear in the Registry, so the network administrator doesn't have to search for this information. Also confirm that the stated paths for the .INF and CINSTALL.INI files are correct for your product. Do not change the information provided for the /A, /O, /L, or /U parameters. You can view and change the command line for your Add/Remove item or Uninstall icon, if necessary. On systems using Windows 95, you can find the Uninstall command line in the following Registry location: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\<product name & version>\UninstallString On systems using Windows NT 3.51, complete the following steps to find the Uninstall command line: 1. In the Program Manager, highlight the Uninstall icon for the product to be removed. 2. Select File - Properties. NOTE: Only network administrators should view or change the Uninstall command line. Individual users should run Uninstall from the Start menu (Windows 95) or Program Manager (Windows NT 3.51). ----------------------------- 11. Information to Give Users ----------------------------- Provide users with the following information: * Instructions on how to connect to: - The network - File server directories, such as the Lotus application program, personal, and shared data directories NOTE: Node users must use the same drive letter and path when they connect to the program and shared tools as you used when you performed the file server install. 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 drives and directories. - Network printers, and how to print on a network * Information on using the Lotus Install program * Information on starting Lotus applications * Information on other applications, as required ----------------------------------------- 12. Custom Distribution of End-User Files ----------------------------------------- The Lotus Install program allows you to distribute your own files to node users when they perform a Node Install. For example, you can distribute your company's standard SmartMasters through the Node Install. To distribute your files along with a Lotus product Install, you must modify the Install program's .INF file. You can get more information about this feature through CompuServ, the World Wide Web, Lotus Automated Support, or from a Lotus Customer Support representative. See your Lotus Customer Support Guide for information about accessing Customer Support or Lotus online support information. ------------------------- 13. If You Have a Problem ------------------------- PROBLEM: A user cannot run a Lotus application from the assigned node. SOLUTION: Ensure that the user has completed the Install successfully, that the network connections are valid, and that users have read-only access to the program directory. PROBLEM: (Windows 95) When selecting the folder to start a Lotus application, a user receives an error message saying the path is invalid or the file is not found. SOLUTION: Check the drive letter specified for the Lotus application folder. To do this: 1. Click Start on the Taskbar. 2. Choose Settings. 3. Choose Taskbar. 4. Select the Start Menu Programs tab. 5. Click Advanced. This loads the Explorer. 6. Under Programs, select the Lotus Node Install. 7. Choose File - Properties. 8. Select the shortcut tab. 9. Select the appropriate Lotus Application folder. 10. Make sure that the drive letter in the user's network connection to the Lotus program directory is the same as that specified for the Lotus application folder, or change the properties of the folder to use the drive letter specified in the user's network connection. PROBLEM: (Windows NT 3.51) When clicking the icon to start a Lotus application, a user receives an error message saying the path is invalid or the file is not found. SOLUTION: Check the drive letter specified for the Lotus application icon. To do this: 1. Click the program icon. 2. Choose File Properties from the Program Manager. 3. Make sure that the drive letter in the user's network connection to the Lotus program directory is the same as that specified for the Lotus application icon, or change the properties of the icon to use the drive letter specified in the user's network connection. PROBLEM: A user tries to gain access to a shared data file in the shared data directory on the file 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. ---------------------------------------- 14. Network-Specific Information for XXX ---------------------------------------- Artisoft LANtastic versions 5.0 and 6.0 --------------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory access - read (R) Lotus Shared Tools directory recommended share name - COMPNENT access - read (R) NOTE: After installing XXX, users will not be able to use XXX unless you make each file in the Lotus Shared Tools directory a read-only file. To do so, use the DOS ATTRIB command. Banyan VINES versions 5.5x and 6.0 ---------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory recommended StreetTalk item name - XXX@GROUP@ORGANIZATION access - read (R) Lotus Shared Tools directory recommended StreetTalk item name - COMPNENT@GROUP@ORGANIZATION access - read (R) NOTE: After installing XXX, users will not be able to use XXX unless you make each file in the Lotus Shared Tools directory a read-only file. To do so, use the DOS ATTRIB command. DEC PATHWORKS version 4.1 and later ----------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory recommended application file service name - XXX access - read (R) Lotus Shared Tools directory access - read (R) IBM LAN Server versions 3.0 and 4.0 ----------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory recommended alias - XXX access - read (R) Lotus Shared Tools directory access - read (R) Microsoft LAN Manager version 2.1a, 2.2, and later -------------------------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory recommended share name - XXX access - read (R) Lotus Shared Tools directory access - Read (R) Microsoft Windows NT Advanced Server, version 3.51 or later ----------------------------------------------------------- Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory recommended share name - COMPNENT access - read (R) Lotus Shared Tools directory access - Read (R) NCR StarGroup 3.5 version 2.1A ------------------------------ Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory recommended share name - XXX access - Read (R) Lotus Shared Tools directory access - Read (R) NOTE: After installing XXX, users will not be able to use XXX unless you make each file in the Lotus Shared Tools directory a read-only file. To do so, use the DOS ATTRIB command. Novell NetWare versions 3.x, 4.0x, and 4.1 ------------------------------------------ Lotus recommends that you organize the server directories as follows: Lotus parent directory XXX program directory access - Read-File Scan (RF) Lotus Shared Tools directory access - Read-File Scan (RF)