Notes on GroupWise Installation

The actual GroupWise domain, post office and agents configuration that takes place after GroupWise installation (i.e.: setting up a GroupWise server).

  1. Download latest GroupWise from http://download.novell.com/.
     
  2. Run downloaded file to extract files. Choose to extract files to C:\Novell/GroupWise rather than C:. Under VMware, this is a very lengthy undertaking so patience is required.
     
  3. Change to C:\Novell\GroupWise and launch Setup.exe.
     
  4. If you decide to view the installation guide in order to plan your configuration more carefully, you will need Adobe Acrobat Reader. Some of the questions include:
    • Placement of ConsoleOne respective to the GroupWise installation (remote, same host, etc.).
    • Domain name: primary.
    • Domain directory: C:\primary.
    • Domain context—eDirectory issues: tuonela.
    • Post office name: po.
    • Post office directory: C:\po.
    • Post office context—eDirectory issues: tuonela.
    • Post office users: asdf.
    • Post office MTA (message-transfer agent) and POA (post office agent).
    • Post office agent platform.
    • Post office agent location.
    • TCP/IP connection between MTA and POA.
    • Running MTA and POA on Windows as applications or services.
     
     
  5. Otherwise, click on Create or update a GroupWise system to get the actual installation going.
    
    	+---------------------------------------------------------------------------+
    	| If you're not logged into the platform as the eDirectory admin user, do   |
    	| that and then start over here. See GroupWise Installation Guide, page 46, |
    	+---------------------------------------------------------------------------+
    
    
  6. Until eDirectory is installed, running, etc., you will not be able to install GroupWise. Here is a list of things to examine and/or wildly thrash about doing in a frantic effort to fix that:
    • In the Novell client login, in place of the tree name, you can use the IP address, either 127.0.0.1 or the actual IP (192.168.88.128 in my case). (Click on illustration at right.)
    • If installing under VMware, you may discover that your password was typed with the Caps lock active even if you didn't manually press it. Consider that when your eDirectory password doesn't seem to work in the Novell client log-in.
    • Find Start->Control Panel->Novell eDirectory Services for a list of services. Use this in your quest to see that eDirectory is working.
    • Examine also Start->All Programs->Administrative Tools->Services. Scroll down to and double-click on NDS Server .CN=tuonela-server.O=tuonela.T=TUONELA_TREE. You can start and stop the service.
     
  7. When installing GroupWise, squint carefully at the process and do not miss the opportunity to install ConsoleOne (separately, but the installation is invoked from GroupWise). This is to say that the opportunity is not reached by clicking Next, so you may pass it up. You need ConsoleOne to do all the GroupWise server configuration.
     
  8. Name the GroupWise server something other than the eDirectory server name, the computer name, etc. Consider using the xxxxxxx from the notes on how to set up eDirectory, followed by -gw to keep things straight, here, tuonela-gw.
     
  9. Make the GroupWise domain name primary (it can be anything you want, but mine's called this for “primary” domain. Place the domain's subdirectory on the path C:\primary.
     
  10. Make the GroupWise post office name po (it can be anything you want, but mine's called this. Place the post office's subdirectory on the path C:\po.
     
  11. At some point, the installation will say it's skipping the agent install. You have to install the agent separately—outside the GroupWise install by going to C:\Novell\GroupWise\AGENTS\install.exe. You can then come back to the GroupWise install which is still waiting at the same place. This mess happens just prior to the final step in the GroupWise installation.
     
  12. At one or two points, you'll have the opportunity to refer to a directory path on which to install the GroupWise software distribution (where, in the real world, users would come to get the GroupWise client software). The proposal will be to set it up on drive Z:\ which doesn't exist (it's an ancient NetWare thing—don't ask). Make this C:\grpwise instead.
     
  13. The actual GroupWise domain, post office and agents configuration comes here. It is very unintuitive.
     
  14. At some point during the previous step, one (or more) GroupWise users must be created. The complexity of this is that the user has to reside in eDirectory first, then GroupWise. When setting up the user in GroupWise with a password, you finish and the dialog box doesn't give you an OK button to click, so confusingly, you click Cancel instead. This is what you have to do.
     
  15. For testing purposes, set up the GroupWise client to run by installing from the path C:\Novell\GroupWise\client\win32\setup.exe. When you launch this client, don't use the admin user proposed in the login dialog, but one of the GroupWise users you created. Enter the password and also the IP address of the host your on.

Setting up a GroupWise trusted-application key...

To set one of these up, you use an application distributed by the third-party vendor and not by Novell or by way of ConsoleOne.

Steps:

  1. Copy RetainServer/web/Manager/trustkey.exe to the Windows workstation
  2. Ensure Windows log in as eDirectory administrator
  3. Launch trustkey.exe; this is an "installer" that will install a key (and not a utility application you use to generate a key)
  4. Navigate to a domain directory database, something like c:\primary\wpdomain.db; click Open
  5. Click on Create Trusted Key
  6. The key is copied to the clipboard and, after clicking OK, to the middle edit window of the Trusted Application Creator application (in Generated Key); MAKE A COPY OF THIS FIELD!
  7. Test the key by clicking on Test Trusted Key after typing in the name of a GroupWise user and then follow instructions to type in its password

Determining if GroupWise works...

The main port involved is 7191. Attempt to ping the server hardware first, then use telnet to determine whether 7191 is open.

	[email protected]:~> ping 192.168.88.128
	PING 192.168.88.128 (192.168.88.128) 56(84) bytes of data.
	64 bytes from 192.168.88.128: icmp_seq=1 ttl=128 time=3.70 ms
	64 bytes from 192.168.88.128: icmp_seq=2 ttl=128 time=0.143 ms
	64 bytes from 192.168.88.128: icmp_seq=3 ttl=128 time=0.130 ms

	--- 192.168.88.128 ping statistics ---
	3 packets transmitted, 3 received, 0% packet loss, time 2003ms
	rtt min/avg/max/mdev = 0.130/1.326/3.705/1.682 ms

	[email protected]:~> telnet 192.168.88.128 7191
	Trying 192.168.88.128...
	Connected to 192.168.88.128.
	Escape character is '^]'.
	HTTP/1.0 500
	Date: Fri, 02 Jan 2009 20:06:58 GMT
	Server: Windows GroupWise POA 7.0.3
	Content-Type: text/html
	Pragma: no-cache

	Connection closed by foreign host.

Despite the insolite message about the host forcing the connection closed, this result tells us that our server hardware is up and that it is attentive to any I/O we might want to attempt via port 7191. We'll mostly be using the GroupWise SOAP-based communication.