GroupWise 4.1 Installation on Windows NT

  • 1203771
  • 23-Jan-1996
  • 26-Jun-1996
  • 3


RDS#546 GroupWare Support

GroupWise 4.1 Installation on Windows NT Last Revision 10/30/95

  Instant Expert Guide 546

System Requirements

   Client/Admin Pack or Packs.
    Admin Admin Diskettes 1-2
    Windows Client Windows Client Diskettes 1-8
  System specifications for DOS Administration
          Required Recommended
    Ram 500k free 600k free
    Operating System DOS 3.3 DOS 5.0 or higher
    Machine 386 or higher 486 or higher
    Disk Drives 3" High density drive and a hard disk are required
    Network Network application only
    Hard Disk Space 40 Megs

Disk space required for following programs:
    Admin Program 4.1 Megs
    WP Office compatibility .9 Megs
    Windows Client 10 Megs
    DOS servers with MFC 2 Megs
    OS/2 Servers 2.3 Megs

Prerequisites to Installation

   Understanding Terms used with the GroupWise System
  Domain: Conceptually, a grouping of one or more post offices. Physically, a directory structure and a database that controls one or more post offices.
  Post Offices: Conceptually, a collection of mailboxes for a set of users. Physically, a directory structure on a file server. The directory structure contains subdirectories and databases that store users' messages.
  User: A person who can send and receive messages in GroupWise. Users are assigned to post offices.
  Mailbox: Conceptually, a place where users store and retrieve messages. Physically, a database within the post office directory structure assigned to an individual user.
  Client program: The GroupWise program that users run to access their mailboxes and exchange messages. Client software is available for Windows, Dos, Macintosh, and UNIX platforms.
  Message Server: The GroupWise program that routes messages between post offices and domains. The Message Server also routes messages to gateways.
  Admin.: The GroupWise program (AD.EXE) that you use to set up and maintain your GroupWise system. Using Admin, you can create domains and post offices, add users, and perform many other tasks.
  System Admin: The person responsible for setting up and maintaining the GroupWise system.

Design your system:
  Decide on how to set up your system by following examples in the GroupWise Administration Guide (pages 7-16)

Know how your network is setup.
  If running a NT Server, you will need a Message Server with message delivery set to server always. There are two type of Message Servers that will work with NT.

    1. DOS-you can run the DOS Message Server in a DOS window under NT, with this option all your administration has to be done on the NT server.

    2. OS/2-This is a high performance Message Server, highly recommended for high volume message delivery. This will only work with IBM Lanserver 4075 requesters.

  If running a NetWare server, you will need to access the NetWare server using IBM Lanserver 7045 requesters.

  Windows NT is currently an unsupported network type. You will need to set network type to other, and will have to set post office security to low. This means you will want to have users set a password to keep their mailbox private.

Installation Steps

A. Installation of Admin
  1. Open the client/Admin Pack or Packs, then refer to the following table to help you assemble the disks you need to complete the installation.

  Get these disks


Windows Client

Admin 1 - 2

Windows client 1 - 8

  2. Make sure you are logged in to the network with full control (permissions) to the directory where you want to install GroupWise.
  3. Insert the Admin 1 disk int a drive and run the installation program. For example if the disk is in drive A, you would type a:\install then press Enter.
  4. Follow your setup worksheet, that you previously created, for creating your domain directory and which files to install.
  5. The client files you mark will first be copied to the Domain directory. Later, when you create a post office, the Admin program will prompt you to copy the client programs to the post office directory where users can access them.
  6. After the installation copies all the files from the installation disks to your domain directory, a special version of the Admin program starts to guide you through setting up a basic GroupWise system. You are asked a series of questions and are prompted to enter information that is unique to your site. When prompted for network type you will need to select O for other. If the Welcome to Novell GroupWise Setup screen does not appear, change to your domain directory and type ad.exe.
  7. For every GroupWise system there is a domain, a post office, and some users. The Admin program will prompt you through creating the domain, post office and will also help you in adding users. You then exit Admin and set up your users to run the client software from their workstations. Note (The domains and post offices both require a name and a directory.)

B. Installation of the Windows Client.
  1. If any of your users plan to run the Windows Client from the network, or if they want the Notify tunes, you must first decompress the Windows Client files at the post office. To do this,
    a. Log in to the network with full control permissions to the post office directory.
    b. Start Windows, then choose File, from menu of Program Manager, then choose Run.
    c. At the command line, enter the full path to the post office directory, then append \SETUPWIN.EXE /A. The /A startup option runs the setup program in Administration mode.
    d. If you have an application that is presently installed using shared code 2.0 or later you will want to choose custom and verify that the shared dll's, and initialization files are going to the same directory.
    e. After the Administration setup is complete you need to run just the SETUPWIN.EXE on each workstation. At this point you can choose workstation, standard, custom, or minimum.
  2. If running from the local drive,
    a. Start Windows, then choose File, from menu of Program Manager, then choose Run.
    b. At the command line, enter the full path to the post office directory, then append \SETUPWIN.EXE
    c. If you have an application that is presently installed using shared code 2.0 or later you will want to choose custom and verify that the shared dll's, and initialization files are going to the same directory.
    d. After the Administration setup is complete you need to run just the SETUPWIN.EXE on each workstation. At this point you can choose standard, custom, or minimum.

Troubleshooting Steps

Problem When running AD.EXE from a DOS prompt under Windows NT, the customer is getting the error "Insufficient File Handles."
Solution Increase the file handles to 60 in the CONFIG.NT file

Problem Customer is prompted for the user ID, but the user does not want to be prompted.
Solution Currently, Novell GroupWise does not support the Windows NT Advanced Server as a specific network or when working with the DOS client of Office. As a work around, the customer can choose not to use the /NT- switch (or to use /NT-0); instead, the customer can use the /@U-USERID switch.

Problem Running Windows NT 3.1 the user receives the error "User Not Found" when attempting to Mail Current Document as a Message from WP51+ DOS. Novell GroupWise is the user's mail Messaging system.
Solution Add the command SET WPC=/U-<<three character ID>> to the AUTOEXEC.BAT. This problem cannot be duplicated using Windows NT 3.5. Windows NT 3.1 does not fully support Novell NetWare user authentication. Novell NetWare user authentication is built into Novell GroupWise.

Problem Users receive D101 Entering GroupWise.
Solution GroupWise cannot determine who the user is. You will need to add a /@U-<<USERID>> to the command line, or it can be set as an environment variable ie SET OFWIN=/@U-<<USERID>>

Problem Post Office Closed.
Solution 1. Highlight the Post Office and press F6. This will bring up the Post Office Edit screen. Tab down to Post Office Directory and make sure that you have (Drive letter:\Post Office directory).
Solution 2. Exit Admin and in file manager change to the Post Office directory go to security|permissions you should be able to add & read a file.

Problem When exiting ADMIN it says that message server is not enabled.
Solution This error could mean that you have more than one post office which means that you need to select a message server option, or there are index problems with the 0 wpdomain.db and you need to rebuild the indexes.

Problem When I double click on my GroupWise icon to start the client I get the following error "GroupWise Error [CA2], The views for your installation are not installed correctly. Contact your System Administrator.
Solution An ASCII text file called OFVIEWUS.INI is either missing or damaged or has incorrect information in the \Post Office\OFVIEWS\WIN\ directory. The .VEW files may be missing also. The best way to get it or the .VEW files back is to have the E-mail administrator run SETUPWIN/A from the Post Office again unless there has been a backup made of the Post Office directories structure the previous day or so, in which the .VEW files and or the OFVIEWUS.INI file may be able to recovered in this manner. This file contains the available default Windows client view selections to users of this Post Office.

Problem Running Setupwin/A I get the error "Unable to overwrite the file SHWIN20.DLL. Or I get Sharing violations.
Solution To avoid the possibility of this occurring make certain that when performing a Network Server install that no one is using Shared code that is normally used by most all Novell Windows applications. A quick check can be made if the files are in use by attempting to rename a major shared code file such as SHWIN20.DLL

Problem Getting 8209 "path not found"errors when the user tries to start the client.
Solution The client software requires access to the Post Office database, and if the client software is not being run from the ofwin40 directory directly under the Post Office directory, the /ph-(path to Post Office directory) switch is required.

Problem Notify will not notify users that running the dos client in a dos window from a Windows workstation.
Solution The dos notify does not work in a graphical environment. When GroupWise loads it will send a message to Notify to go to sleep for one hour if it is running under Windows. To get notified while running the dos client in Windows, the client must be running in a full screen dos session.

Problem User tries to modify an item on the shelf and the Icon disappears. Icons disappear even if the cancel button is selected.
Solution This problem is specific to NT at the current time there is no work around. Items modified will still work, click on the caption and the program will run.