Software

Installing GroupWise snap-ins in NetWare Administrator

GroupWise is a great program, but the installation process can be a bit tedious. Eric Toll has already shown you how to install GroupWise on your server. Now he shows you how to use the GroupWise Setup Advisor in NetWare Administrator.


In the Daily Drill Down “Installing GroupWise screen by screen,” I walked you in painful detail through every screen associated with installing GroupWise on your server. In case you thought you were done, guess again. After you’ve installed GroupWise to your NetWare server, you must also do some work in NetWare Administrator to complete the installation. In this Daily Drill Down, I’ll walk you through the steps you’ll follow.
Although we’re going to cover installing the GroupWise system in NetWare Administrator and the other things you must do in NetWare Administrator to get GroupWise up and running on your system, we’re not going to do an exhaustive screen-by-screen walkthrough. Instead, we’ll describe what you’re going to be doing and show you the most relevant screens.
Running NetWare Administrator with the GroupWise Setup Advisor
After you’ve done the basic installation outlined in the previous Daily Drill Down, the very next time you start NetWare Administrator from your administrative workstation, you’ll see the GroupWise Setup Advisor appear, as shown in Figure A.

Figure A
The GroupWise Setup Advisor appears the first time you start NetWare Administrator after installing GroupWise on your server.


The initial screen only gives you two choices. You can either have the GroupWise Setup Advisor create a new GroupWise 5 server in your NDS tree or migrate an existing 4.x server to GroupWise 5. For the purposes of this Daily Drill Down, we’ll be configuring a brand-new GroupWise 5.5 server, so we’ll keep the default choice of Create A New GroupWise 5 System and click OK to continue.

Next, you’ll see the GroupWise Setup Progress screen. This screen only displays where you are in the installation process. Click Next to bypass it.

You’ll then see the Software Distribution Directory screen. Here you only need to verify the location of your software distribution directory (that you specified in the previous Daily Drill Down). Verify that you’ve chosen the proper distribution directory and click Next to continue. If for some reason the directory is wrong, you can either type the proper path into the Software Distribution Directory field or click the folder to the right of the field and navigate to the proper directory.

You’ll then see the NDS Tree screen. This should be a no-brainer. Simply verify that the Current Tree contains the name of the NDS tree where you’re installing GroupWise. If you have more than one NDS tree, make sure you have the correct one indicated. Then click on Next.

When you do, you’ll see the System Name screen appear. Here you get to do something creative by choosing a name for the system. Don’t get too fancy, though. The name should be chosen carefully because after you choose one, you can’t change it. I recommend using less than eight characters and no spaces. Enter the name in the System Name field and click Next to continue.

Mastering your domain
The next screen is the Primary Domain screen. No, this doesn’t have anything to do with Windows NT, so don’t worry. It’s the term that Novell uses to describe a collection of commonly managed GroupWise servers. A primary domain will consist of a few NLMs and a subdirectory on your server’s volume. Most changes and administrative happenings involve the primary domain. When you create users or other objects in NetWare Administrator, they are stored in NDS and in the GroupWise domain. This information then gets transferred from the GroupWise domain to other post offices in your organization.

On this part of the install, we are just looking for a name for our primary domain. Enter a name in the Domain Name field. Name ideas you can use include Corp, Headquarters, Quality_Assurance, GWDOM, or something personable like Larry.

The name of the domain may not include the following:
  • ASCII characters 0-13
  • At sign @
  • Braces {}
  • Parentheses ()
  • Colon :
  • Comma ,
  • Period .
  • Space
  • Double quote "

After you click Next, you’ll see the Domain Directory screen. This will be a new directory on your file server that will contain the domain database. I never put anything on the SYS: volume when I make a server. I usually set aside 5 GB for the SYS: volume and then set up other areas to hold files and data. I like to name the domain directory GRPWISE.DOM. That way, when I am at a DOS prompt or just looking around the server, I have no question about what this subdirectory’s purpose is. Type the name of the subdirectory you want to use in the Domain Directory field. Please stick with the 8.3 format and don’t use any of the characters listed above. Click Next to continue.

Next, you’ll see the Domain Context screen. Setup Advisor wants to know where to put all of the objects it will create. You can dump them into the root of your tree, but you probably have many single leaf objects in the root already. It will make using NetWare Administrator more difficult if there are too many objects to wade through. Placing all of the GroupWise objects in the root of your NDS tree will only complicate things.

If you don’t already have a separate organizational unit (OU) for GroupWise, you can toggle to NetWare Administrator and create one. The name I like to use is—yes, you guessed it—GroupWise. Now all of the objects from the GroupWise system will have their own OU. This keeps things organized, and if later you want to give another administrator help-desk entity the ability to administer the GroupWise system, you can grant them access to just the GroupWise OU instead of the whole tree.

Enter the name of the NDS context you want to use in the Domain Context field. Click Next to continue. The next screen you’ll see is the Domain Language screen. Click U.S. English or the language of your choice and click Next to continue.

Next, you’ll see the Domain Time Zone screen. Again, this is a simple screen. Select the correct time zone for your server from the list and click Next to continue.

Playing post office
You’ll next see the Post Office Name screen. Here, we get to choose the name of our first post office. A post office represents a group of users. Its name should be based on a physical location or the group of users that it represents. If you have WANs, each remote office (if it has a local server) should have the Post Office NLMs installed. Enter the name in the Post Office Name field and click Next.

The Post Office Directory screen will appear next. I like to use Grpwise.poa as the name of the post office directory. Again, from a DOS prompt, you’ll be able to tell what the respective GroupWise directories are for. Enter the path in the Post Office Directory field and click Next to continue.

Next, the Post Office Context screen will appear. Here, you tell Setup Advisor where in your NDS tree you want the post office created. Click on the NDS browse button and select the GroupWise OU. Click Next to continue.

On the Post Office Language screen, select your language from the list and click Next to continue. After that, you’ll see the Post Office Time Zone screen. Select the time zone where the Post Office Agent (POA) will reside and click Next.

Next, the Post Office Access Mode screen appears, as shown in Figure B. Here, you specify how clients will be allowed to contact the GroupWise server. Choices include:
  • Client/Server Access Or Direct Access
  • Client/Server Access Only
  • Direct Access Only

Figure B
Decide how your clients will connect to your server.


When you select Client/Server Access Only you must have TCP/IP loaded and bound to a NIC in your server. This is an easy task and can be done with NetWare 4.x and 5.x server operating systems. Direct Access mode requires that you map network drives to the post office directory to send, receive, and delete e-mails. Naturally, Client/Server Access Or Direct Access allows you to do things either way.

The biggest problem with Direct Access is file corruption. We have all seen a Microsoft desktop operating system crash for no apparent reason. If the client PC is running GroupWise in Direct Access mode when it crashes, it will leave files open on the server. This presents the chance for corruption when the PC reboots. Also, if you choose Client/Server Access Or Direct Access or Direct Access Only, the users of your GroupWise system will have file rights to the post office subdirectory (Grpwise.poa) and may be able to accidentally cause trouble by deleting files and/or folders in the post office directory.

I recommend that you set up the post office for Client/Server Access Only. Users will have no access rights to any of the post office directory structure. The server that runs the Post Office NLM will listen for TCP/IP GroupWise requests, take the request, do the work, and return the results to the respective GroupWise e-mail client. I think this is the cleanest and fastest way to set up a GroupWise post office. Click Next to continue.

You’ll then see the Post Office Link screen, shown in Figure C. Here, you determine how the Message Transfer Agent will communicate with the post office. Novell recommends you use Direct Link if the MTA and post office are on the same server. Otherwise, select TCP/IP Link and click Next.

Figure C
You must decide how the MTA will communicate with the post office.


Next, you’ll see the POA Network Address screen, shown in Figure D. Here, we have the option of choosing a DNS name or an IP address for the server that will be running the POA. If you already have a DNS server on your network, you can use a DNS host name to address the GroupWise POA. This way, if you decide to change the server that the GroupWise POA exists on, you can easily move the post office and update the DNS host file with the new server’s IP address. The default port for GroupWise is 1677; I always use this default port, but you can change it if you need to. For NetWare, keep away from reserved port addresses and addresses above port 32000. Click Next to continue.

Figure D
You must enter the IP address or DNS address of the server running the Post Office Agent.


The Post Office Users screen will appear next. If you already have NetWare users in NDS that you want to have GroupWise accounts, click the Add button and select the context. You may press [Ctrl] and click multiple objects or click on the first user in the list and press [Ctrl][Shift][End] to select an entire list. You may then keep adding users from different OUs, as necessary. After you’ve entered the users, click Next to continue.

Now you’ll see the GroupWise Setup progress screen again. The Install program is about to perform all of the requests we have made using the configuration options that we provided during the input screens of the installation. Click Next to view the Summary screen. After you’ve verified that the summary is correct, click Create.

You will get the following dialog box during system creation:
GroupWise Administrator Can Set The Respective Users Rights So That They May Access The Post Office.

I always click Yes, just in case for some reason I had to switch my post office access to mapped or direct. If you are setting up GroupWise in a Client Server Only mode, then this isn’t really an issue, as users will only need NDS file access to the files that allow the GroupWise clients to be installed.

Secret agent man
Congratulations; our system has been created. Now you’ll get the GroupWise Setup progress screen. The next bullet item will be used to install and run the agent software. For this Daily Drill Down, I will be using the NetWare platform for my agents. (Agents are items like the Post Office and Domain processes, which need to run on some type of server.) GroupWise agents can run on UNIX, Solaris, and even Windows NT, which makes GroupWise a good e-mail system for enterprises with different platform needs. Click Next to continue.

You’ll see the Agent Information screen. Setup at this point indicates which agents must be installed and tells a bit about the role of each. The Message Transfer Agent (MTA) routes messages between domains, post offices, and gateways. The POA delivers messages to users’ mailboxes. Click Next to continue.

The GroupWise Agent Platform screen appears next. You can choose to host GroupWise on an NT server or NetWare server. In my opinion, NetWare is faster and more reliable than the other choice, but it’s nice to know that it will run on another platform. Select NetWare NLM and click Next to continue.

You’ll then see the NetWare NLM Agent Setup screen. Click Install Agents to get the NLM agent program running. After the agents have been installed, click Next to continue.

You must then select the path and volume where Setup is going to locate the agent program files. Make sure you pick the correct server’s SYS: volume. Click Next to continue.

Now you must select the Agent Language. As with the other language selections you’ve made, pick your language and click Next.

That will display the Summary page. Make sure that everything’s correct and click Install.

Are we there yet?
We’re almost done. You only have to verify two last items. After the installation completes, you’ll see the Installation Complete screen. By default, Setup will place a check mark on two items: Update AUTOEXEC File and Launch GroupWise Agents Now. I recommend that you leave the check on both of these items.

When you click Finish, the server will load the NLMs to make your system come to life. After the POA and MTA NLMs are loaded, you’ll see the Load GroupWise Agents screen. You can click the Remote Console button to launch Rconsole to verify that the agents have loaded properly. Naturally, you’ll need to have Rconsole loaded on the target server as well.

At your server’s console prompt, press [Alt][F3] to jump from screen to screen. Check to see if you have two new screens available: GroupWise 5.5 POA and GroupWise 5.5 MTA. You should not be concerned about the fact that the MTA has already transferred some messages; these are special administrative messages that give the MTA and POA the configuration options we chose during installation. When you make changes to these GroupWise NDS objects in NetWare Administrator, special messages are sent to the respective agent telling it what to change or how to behave.

If for some reason the agents haven’t started, you can force them to start by typing GRPWISE at the console prompt and pressing [Enter]. When you’ve confirmed that everything loaded properly, close the Rconsole session and return to Setup Advisor. Click Next to continue.

When the GroupWise Setup Progress screen reappears, click Next to bypass it. You’ll then see the GroupWise Client Setup screen. You don’t need to worry about installing it right now so click Next. When the System Creation Complete screen appears, click Done.

Conclusion
Installing GroupWise on your NetWare server can be a long process. As you’ve seen, there are many steps you must go through to get it up and running. However, most of them are fairly straightforward. Once you get GroupWise running, you’ll quickly forget about the pains of installation.
The authors and editors have taken care in preparation of the content contained herein but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for any damages. Always have a verified backup before making any changes.

Editor's Picks

Free Newsletters, In your Inbox