Chapter 1: Plan Your Basic GroupWise System
Every GroupWise* system, whether it services five users or 50,000 users, starts as a basic GroupWise system. This chapter presents the concepts and information you need to plan your basic GroupWise system.
The GroupWise Basic System Worksheet lists all the information you will need as you install GroupWise and set up your basic system. You should print the worksheet and fill it out as you complete the tasks listed below. If you print this chapter, the worksheet will be printed with it. To print the worksheet only, see Appendix A: Worksheet. Once you have completed the tasks and filled out the worksheet, you will be ready to continue with Chapter 2: Prepare for Installation.
Once you've completed the above tasks, you should review the sample configurations and the summary of GroupWise requirements, and then finish filling out the last few items in the worksheet.
Understand the Components of a Basic GroupWise System
A basic GroupWise system consists of a single domain with one post office and one or more users. Each GroupWise user has a mailbox in the post office; users run the GroupWise client to access their mailbox and to send mail to and receive mail from other users. The GroupWise agents deliver messages between users' mailboxes in a post office, and route messages between post offices in a multiple post office system.
In a basic GroupWise system like the one shown above, it is fairly easy to see why the post office, client, and agents are necessary. The reason for the domain, however, may not be as clear. Basically, the domain serves two purposes:
In a basic GroupWise system, the domain may seem like extra overhead. However, the domain/post office architecture enables you to scale your GroupWise system to meet your current needs and future needs. It also enables you to configure GroupWise to best accomodate your company or network organization.
Make Sure You Have At Least One NetWare 4.1 Server
Here at Novell*, we think everyone should be using IntraNetWare* or NetWare* 4.1. However, if you're running another network operating system or several network operating systems (for example, NetWare 3.x and Windows NT**), you can still set up GroupWise to take full advantage of your network environment and configuration.
Because GroupWise is administered through NetWare Administrator and NDS, your network must have at least one NetWare 4.1 server installed. The GroupWise package includes IntraNetWare/NetWare 4.11 with two user licenses so you can set up a NetWare 4.11 server if necessary. For information about setting up the NetWare 4.11 server, see the Online Documentation CD included in the NetWare 4.11 sleeve.
Decide Which NetWare 4.1 Server You Will Use for GroupWise Administration
GroupWise administration is performed through NetWare Administrator for Windows 95* (NWADMN95.EXE) or NetWare Administrator for Windows NT (NWADMNNT.EXE. When you install GroupWise, the GroupWise Administrator DLLs are copied to the SYS:\PUBLIC\WIN95 or SYS:\PUBLIC\WINNT directory of the NetWare 4.1 server you select. The GroupWise Administrator DLLs extend the functionality of NetWare Administrator to let you administer GroupWise. If necessary, NetWare Administrator 95 or NetWare Administrator NT is also installed.
You need to decide which NetWare 4.1 server you want to run NetWare Administrator to administer GroupWise. This does not have to be the same server on which you install the domain or post office.
|
WORKSHEET Enter the path to the SYS:\PUBLIC directory under Item 3: NetWare Administrator Path. Note: The items in the worksheet are listed in the order you will enter them when running the GroupWise Installation and Setup Advisors. This planning chapter does not follow the same order as the worksheet, but all worksheet items are covered. |
You must make sure that all users who will use GroupWise exist in NDS. GroupWise accounts can only be assigned to network users who have been defined in NDS as users or as GroupWise external entities.
NDS
Users vs. GroupWise External Entities
Network users you
define as users in NDS can log in to NDS to access NetWare 4.1 servers and
services. Each NDS user requires a NetWare 4.1 (NDS) license.
Network users you define as GroupWise external entities can not log in to NDS. They are added to NDS as external entities for the sole purpose of assigning them a GroupWise account. GroupWise external entitites do not require licenses.
You can add users to NDS as GroupWise external entities only after you have installed GroupWise. Instructions for adding external entities are provided in Chapter 3: Set Up Your Basic GroupWise System.
Determine the Contexts for the Domain and Post Office Objects
Using NetWare Administrator and the GroupWise Administrator DLLs, you create, manage, and store all GroupWise objects and information in Novell Directory Services (NDS). You must decide where you want the domain object and post office object located in the NDS tree. The Message Transer Agent (MTA) object and Administration Agent (ADA) object are automatically placed in the same context as the domain. The Post Office Agent (POA) object is placed in the same context as the post office.
The following example shows how the domain, post office, and agents could appear in the NetWare Administrator browser window.
You can place the domain and post office in any context in your NDS tree. In the above example, the domain object and post office object reside in the same organization (Corporate). If all users who you will add to the post office are located in the same organizational unit, the domain could reside in the organization (Corporate) and the post office in the same organizational unit (Accounting, R&D, Sales, or Manufacturing) as the users, as shown below.
If, as in the above example, you have multiple organizational units in the organization, you can create a post office in each unit.
If, rather than mirroring your NDS organization, you would prefer to keep all your GroupWise objects together, you could create an organizational unit, such as GroupWise, and place all GroupWise objects in that organizational unit, as shown below.
Because the domain and post office have directory structures on network servers, you could also choose to place the domain and post office objects in the same context as the servers where the directories will reside. Location of domain and post office directory structures is discussed later in this chapter.
|
WORKSHEET Enter the domain context under Item 10: Domain Context. Enter the post office context under Item 15: Post Office Context. If desired, enter the context for each user under Item 18: Post Office Users. (Note: The GroupWise Setup Advisor lets you select users from the NDS tree to add them to the post office. You may choose not to list all of the users at this time. If you are adding users as GroupWise external entities, you must wait to add them to the post office until after you have finished the installation.) |
NetWorks
with Multiple NDS Trees
The domain and post office (as
well as other post offices created in the domain) must be located in the
same NDS tree. You cannot split a domain across NDS trees. If you have
multiple trees, you must create separate domains in each tree. The domains
can all belong to the same GroupWise system.
|
WORKSHEET Enter the NDS tree in which you're creating the domain and post office under Item 1: Tree Name. |
System,
Domain, and Post Office Names
When you create a domain
object or post office object, you give it a unique name. The name is used
for addressing and routing purposes within GroupWise, and appears in the
GroupWise Address Book as well as in NDS.
Domain and post office names can reflect locations, organizations, and so forth. In the examples above, the domain name (TechIndustries) reflects the company, and the post office names (Research, Accounting, Marketing, and Shipping) reflect the organizational units.
Name your domain and post office carefully. After it is created, the name cannot be changed.
You must also provide a name for your GroupWise system. This can be your company name, GroupWise, or anything else. The system name is displayed only in NetWare Administrator. You cannot change the name after your system is created.
System, domain, and post office names must be one word. Do not use any of the following invalid characters in the name:
|
WORKSHEET Enter the domain name under Item 8: Domain Name. Enter the post office name under Item 13: Post Office Name. Enter the system name under Item 7: System Name. |
A
Look at GroupWise from the GroupWise View
You can also
view GroupWise objects through a window called the GroupWise View, shown
below.
GroupWise View filters out all non-GroupWise objects and also shows how GroupWise objects relate to each other. For example, in GroupWise View, notice the post office object is subordinate to the domain object. The lower window of the view displays the users that have GroupWise accounts on the object selected in the upper window. In the above view, the Research post office is selected, so the lower window displays the users who have accounts on the Research post office.
GroupWise View is particularly useful if your GroupWise objects are placed in different contexts in the NDS tree. For example, the following view shows a multiple post office system. In the NDS tree, the logical locations (fully distinguished names) of the Payroll post office and Research post office are:
marketing.sales.corporate
payroll.accounting.corporate
research.r&d.corporate
shipping.manufacturing.corporate
Even though the post offices are in different organizational units in the NDS tree, GroupWise View displays the entire GroupWise system. If you were administering this system, you would not have to look for GroupWise objects throughout the tree. Instead, you could administer all GroupWise objects from GroupWise View.
Determine the Locations for the Domain and Post Office Directories
From a logical perspective, the GroupWise domain and post office objects reside in NDS and are administered through NetWare Administrator. Physically, the domain and post office require directory structures for the databases, message stores, and other files associated with them.
The domain directory structure and post office directory structure can be located on the same server or on different servers, as shown below.
Domains
and Post Offices on Non-NetWare 4.1 Servers
You can
create domains and post offices on non-NetWare 4.1 servers, such as
NetWare 3.12, Windows NT, and UNIX**. Many different configurations are
possible. See Sample GroupWise Configurations later in this chapter.
Disk
Space Requirements
The domain directory requires less
than 1 MB of free disk space. This requirement could increase as your
GroupWise system grows.
The post office directory holds all the messages, so you should plan a minimum of 2 MB per user. We recommend 10 MB per user.
Directory
Names
You should specify empty directories for both the
domain and post office. If you want, the directories can reflect the
actual names of the domain and post office (for example, TI for the
TechIndustries domain and RESEARCH for the Research post office).
Choose the names and paths carefully. After the directories are created, it is difficult to rename them. If the directories you specify do not exist, they are created during GroupWise installation.
|
WORKSHEET Enter the full path for the domain directory under Item 9: Domain Directory. Enter the full path for the post office directory under Item 14: Post Office Directory. |
Determine the Location for the Software Distribution Directory
During installation, you specify a software distribution directory. This directory contains administration and agent files you use to set up the GroupWise system (for example, to add additional post offices and to set up the GroupWise agents) and client files that users access to set up the GroupWise client.
File
Server Volume vs. GroupWise CD
You can specify a
directory on a file server volume to be used as the software distribution
directory, or you can mount the GroupWise CD as a server volume and have
it be the software distribution directory. You should consider network
access and disk space requirements when deciding which method to use.
Network Access
The method you choose must meet the following criteria:
- Users must be able to map a drive to the location to run the GroupWise client setup program (for Windows 95 and Windows** 3.1).
- When users set up the client, they can choose to install it to their local drive and run it from there or they can run it from the software distribution directory. If you want users to be able to run it from the software distribution directory, they must have a permanent drive mapping to the directory. If users will run the client from the software distribution directory, you may not want to mount the GroupWise CD as the distribution directory. More than likely, running from the CD-ROM drive will be slower than running from a network directory.
- You must be able to access the location when you set up GroupWise agents, when you need to update GroupWise software, or when you run NetWare Administrator to create GroupWise objects such as domains and post offices
Disk Space Requirements
This applies only if you create the software distribution directory on a file server volume.The software distribution directory can be on the same server as the domain or post office directories or on a separate server, as shown below.
The disk space required for the directory depends on the software you install to the directory. You can choose to install the administration files, NLM* agents, NT agents, UNIX agents, Windows 95 (32-bit) client, and Windows 3.1 (16-bit) client. The Macintosh client and UNIX client are not installed to the software distribution directory. Information about installing the Macintosh and UNIX clients is provided in Chapter 3. The maximum disk space required to install everything is approximately 275 MB.
The administration files include the GroupWise Administrator DLLs and Help files, and a program (SETUPGW.EXE) you can use to set up additional workstations to be able to run GroupWise Administrator. The administration files require approximately 17 MB.
The NLM, NT, and UNIX agent files include all files necessary to install and set up the agents. The NLM agents require approximately 7 MB and the NT agents approximately 5 MB. The UNIX agent files are copied as tar files that require approximately 50 MB.
The Windows 95, Windows 3.1, Macintosh and UNIX client files include all files necessary for users to set up the GroupWise client on their workstations. The Windows 95 client requires approximately 50 MB, the Windows 3.1 client approximately 50 MB, the Macintosh client approximately 18 MB, and the UNIX client approximately 40 MB.
You can also copy GroupWise Monitor, GroupWise WebAccess, and GroupWise Internet Agent to the software distribution directory. This enables you to install these products from the software distribution directory rather than from the GroupWise CD.
GroupWise Monitor works with ManageWise* to let you monitor your GroupWise agents and requires approximately 9 MB.
GroupWise WebAccess works with an HTTP server to let users access their GroupWise mailboxes through a Web browser and requires approximately 21 MB. GroupWise WebAccess includes files that use long filenames. If you copy GroupWise WebAccess to the software distribution directory, the directory must be on a network server that supports long filenames.
GroupWise Internet Agent lets users send and receive e-mail through the Internet and requires approximately 12 MB.
WORKSHEET
Enter the software distribution method (GroupWise CD or Network Directory) under Item 4: Software Distribution Method.
If you choose Directory on File Server Volume as the method, enter the software you want installed under Item 5: Software Selection, then enter the path for the software distribution directory under Item 6: Software Distribution Directory. If you plan to copy GroupWise WebAccess to the software distribution directory, make sure the directory is on a network server that supports long filenames.
Decide Which GroupWise Agents to Install
GroupWise uses three agents to route messages within the GroupWise system: the Message Transfer Agent (MTA), the Post Office Agent (POA), and the Administration Agent (ADA). The agents are available as NetWare NLMs, Windows NT executables, or UNIX executables.
MTA
and ADA
The MTA and ADA run at the domain level, which
means that you need to run one instance of each agent for each domain you
create. For a GroupWise system consisting of one domain, you need to run
one instance of the MTA and one instance of the ADA.
When planning a location for the MTA and ADA, you should consider network access, disk space requirements, and memory requirements.
Network Access
The MTA and ADA require direct network access (mapped drive or UNC path) to the domain directory and to the post office directory. The machine on which you run the MTA and ADA must be able to provide this directory access.Some operating systems do not support direct access to the hard drives of machines running another operating system. For example, currently we know of no way for a NetWare server to directly access a Windows NT server.
Disk Space and Memory
To run the NLM MTA and ADA, a NetWare server must have 6 MB of free disk space and 6.5 MB of free memory. This assumes that the MTA and ADA will run on the same server. If they run on separate servers, each server must meet these requirements.To run the NT MTA and ADA, a Windows NT server or workstation must have 4.5 MB of free disk space and 6 MB of free memory. This assumes that the MTA and ADA will run on the same server or workstation. If they run on separate machines, each machine must meet these requirements.
To run the UNIX MTA and ADA, a UNIX server must have 16 MB of available disk space for the MTA, 8 MB of available disk space for the ADA, a minimum of 2.5 MB of real memory per agent, and a minimum of 4 MB of swap space per agent.
IMPORTANT: The memory requirements listed above are for a basic GroupWise system (one domain with a single post office). Memory requirements for the MTA and ADA increase as you add post offices and other domains to your system.
WORKSHEET
Enter the type of MTA and ADA you will use under Item 19: Agent Platform.
Enter the path for the MTA and ADA under Item 20: Agent Path.
POA
The POA runs at the post office level, which means that you need to
run one instance of the POA for each post office you create. For a
GroupWise system consisting of a single post office, you need to run one
instance of the POA.
When planning a location for the POA, you should consider network access, disk space requirements, and memory requirements.
Network Access
The POA requires direct network access to the post office directory. The machine from which you run the POA must be able to provide this directory access. The server where the post office directory resides is a good location, if possible, for the POA.Some operating systems do not support direct access to the hard drives of machines running another operating system. For example, currently we know of no way for a NetWare server to directly access a Windows NT server.
Disk Space and Memory
To run the NLM POA, a NetWare server must have 6 MB of free disk space and 5 MB of free memory. If you run the POA on the same server as the MTA or ADA, the additional memory required is only 1.5 MB (because of the shared engine code used by the NLM agents).To run the NT POA, a Windows NT server or workstation must have 4.5 MB of free disk space and 5 MB of free memory. If you run the POA on the same server or workstation as the MTA or ADA, the additional memory required is only 1.5 MB (because of the shared engine code used by the NT agents).
To run the UNIX POA, a UNIX server must have 8 MB of available disk space, a minimum of 2.5 MB of real memory, and a minimum of 4 MB of swap space.
WORKSHEET
Enter the type of POA you will use under Item 19: Agent Platform.
Enter the path for the POA under Item 20: Agent Path.
Decide Which Languages to Install
The GroupWise CD contains multiple languages. You need to decide which languages you want to install. Your choice affects the following programs:
For example, if you install US English and German, you will be able to run GroupWise Administrator and the agents in either language. By default, GroupWise Administrator runs in the language in which you are running NetWare Administrator. Your users will have the choice of using either the US English client or the German client.
|
WORKSHEET Enter the languages you want to install under Item 2: Languages to Install. |
Domain
and Post Office Languages
In addition to selecting which
client languages you want installed, you also select a default language
for the domain. The domain language determines how times, dates, and
numbers are displayed in the GroupWise client and affects the sorting
order for items in the GroupWise Address Book. The post office assumes the
same language as its domain unless you specify otherwise.
For example, if you set the domain and post office language to English-US, all time, date, and numbers will be formatted according to English-US standards, and the Address Book items will be sorted according to English-US sort order rules. This will be true even if some users on the post office are running non-English GroupWise clients such as German or Japanense. Their client interface and help files will be in German or Japanese, but the time, date, and number formats and sort order will be according to English-US standards.
|
WORKSHEET Enter the language for the domain under Item 11: Domain Language. Enter the language for the post office under Item 16: Post Office Language. |
Decide How Users Will Access the Post Office
The GroupWise client can access mailboxes through a direct connection or a client/server connection. A single post office can support both direct access and client/server access at the same time. When you create a post office, the default access is both direct and client/server.
Direct
Access
GroupWise supports both mapped drives and UNC
paths as direct access methods. With direct access, the GroupWise client
writes directly to users' mailboxes. Direct access requires the user to
have rights to the the post office directory.
You can grant users full rights to the post office directory and subdirectories, or you can restrict users' rights to increase security. For information about restricting rights, search for Network Rights in the GroupWise Help.
Client/Server
Access
GroupWise supports TCP/IP for client/server
access. With client/server access, the GroupWise client does not have
direct access to the users' mailboxes. Instead, it uses TCP/IP to request
services from the Post Office Agent (POA). The POA then accesses the
users' mailboxes and passes the information to the client.
Client/server eliminates the need for users to log in to the server where their post office is located. This avoids problems with login restrictions, changing passwords, and insufficient network rights. Client/server also allows the GroupWise client to maintain multiple simultaneous connections to the post office.
To use client/server, the server on which the POA is running and the user's workstation must both support TCP/IP.
Note: The GroupWise UNIX client only supports client/server access. Direct access is not supported.
Sample GroupWise Configurations
Many different configurations are possible for your GroupWise system. The following diagrams illustrate some of the ways a basic GroupWise system (one domain and a post office) can be set up.
One
NetWare 4.1 Server
The following diagram shows a basic
GroupWise system set up on a single NetWare 4.1 server.
A
NetWare 4.1 Server and a Windows NT 3.51 Server
The
following diagram shows the domain, post office, and software distribution
directory on a NetWare 4.1 server and the MTA, ADA, and POA on a Windows
NT 3.51 server.
A
NetWare 4.1 Server and a NetWare 3.12 Server
The
following diagram shows everything on a NetWare 3.12 server. The NetWare
4.1 server is used to administer the GroupWise system and users.
A
NetWare 4.1 Server and a UNIX Server
The following
diagram shows everything on a UNIX server. The NetWare 4.1 server is used
to administer the GroupWise system and users.
Summary of Requirements for a Basic GroupWise System
The following table summarizes the requirements for a single domain with one post office.
| Item | Requirement |
| NetWare 4.1 | - GroupWise is administered through NetWare Administrator and NDS.
You must have at least one NetWare 4.1 server installed. - NWADMN95.EXE or NWADMNNT.EXE (installed by GroupWise if necessary) |
| NetWare Administrator and GroupWise Administrator | -Windows 95 workstation with NetWare Client 32 for Windows 95 or
Windows NT 4.0 workstation with NetWare Client 32 for Windows NT - 80486 processor - 16 MB RAM |
| Domain Disk Space | - 1 MB |
| Post Office Disk Space | - 2 MB per user (minimum) - 10 MB per user (recommended) |
| Software Distribution Directory Disk Space | - 275 MB maximum on network directory. This will be less if you
choose not to install some GroupWise clients or agents. - No disk space is required if you mount the GroupWise CD as a server volume. |
| NLM Agents | - NetWare 3.12 or 4.x server - MTA and ADA: 6 MB free disk space, 6.5 MB free RAM - POA: 6 MB free disk space, 5 MB free RAM (1.5 MB if running on same server as MTA or ADA) |
| NT Agents | - Windows NT 3.51 server or workstation - MTA and ADA: 4.5 MB free disk space, 6 MB free RAM - POA: 4.5 MB free disk space, 5 MB free RAM (1.5 MB if running on same machine as MTA or ADA) |
| UNIX Agents | - HP 9000 700/800 HPUX 10.20 or - IBM RS/6000 Power/PowerPC 601/604 or - IBM RS/6000 AIX 4.1x or - Sun SPARC Solaris 2.5 with recommended patch bundle - Motiff 2.4 (Common Desktop Environment 1.0.1) - MTA and ADA: 24 MB free disk space (16 MB for the MTA, 8 MB for the POA), 5 MB real memory (minimum) and 8 MB swap space (minimum) - POA: 8 MB free disk space, 2.5 MB real memory (minimum) and 4 MB swap space (minimum) |
| Windows 95 GroupWise Client | - Windows 95 workstation or Windows NT 4.0 workstation - 80486 processor (minimum) - 24 MB free disk space to run from local drive - 5 MB free disk space to run from network drive - 8 MB RAM |
| Windows 3.1 GroupWise Client | - Windows 3.1 workstation or Windows 95 workstation - 80386/33 processor (minimum) - 20 MB free disk space to run from local drive - 1 MB free disk space to run from network drive - 8 MB RAM |
| Macintosh GroupWise Client | - Macintosh IIci (68030 or better) or a Power Macintosh - System 7.1 or better - 15 MB free disk space - 12 MB RAM |
| UNIX GroupWise Client | - HP 9000 700/800 HPUX 10.20 - IBM RS/6000 Power/PowerPC 601/604 - IBM RS/6000 AIX 4.1.x - Sun SPARC Solaris 2.5 with recommended patch bundle - 30-40 MB space available on hard disk (depending on platform) - 5 MB memory for first user; .5 MB for each additional user |
Basic GroupWise System Worksheet
The GroupWise Installation Advisor helps you install the GroupWise software. The GroupWise Setup Advisor helps you set up your first domain and post office. The Advisors will prompt you for the information in the following worksheet (in the order listed). You should print the worksheet and carefully fill in the information for your system.
| Item | Example | Explanation |
| 1) Tree Name: | CORP | Specify the name of the NDS tree in which your domain and post
office will be installed. Because GroupWise introduces new objects into
the tree, the NDS schema must be extended.
See Determine the Contexts for the Domain and Post Office Objects in this chapter. |
| 2) Languages to Install: | English
German |
Specify the languages in which to install GroupWise Administrator,
the GroupWise agents, and the GroupWise clients. Make sure you select
all languages in which you want to run GroupWise Administrator and the
agents, and all languages in which you want users to be able to run the
GroupWise client.
See Decide Which Languages to Install in this chapter. |
| 3) NetWare Administrator Path: | NW41\SYS:\PUBLIC | Specify the path to the SYS:\PUBLIC directory that contains the
NetWare Administrator 95 program or NetWare Administrator NT program you
will run to administer GroupWise. The GroupWise Installation Advisor
installs GroupWise Administrator to the directory. If necessary, it will
also update the NetWare Administrator program.
See Decide Which NetWare 4.1 Server You Will Use for GroupWise Administration in this chapter. |
4) Software Distribution Method:
|
Directory on file server volume | Select the method you want to use for the software distribution
directory. If you choose to use the GroupWise CD, the CD must be mounted
as a server volume.
See Determine the Location for the Software Distribution Directory in this chapter. |
5) Software Selection:
|
Administration NLM agents Windows 95 client Windows 3.1 client |
This option applies only if you chose to create the software
distribution directory on a file server volume.
Select the software you want installed to the software distribution directory. Select the type of agents you want to use (NLM, NT, or UNIX) and the type of client you want available to users (Windows 95 and/or Windows 3.1). See Determine the Location for the Software Distribution Directory in this chapter. |
| 6) Software Distribution Directory: | Z:\SOFTWARE | This option applies only if you chose to create the software
distribution directory on a file server volume.
Specify the directory path for the software distribution directory. If the directory does not exist, it will be created. The path should be from the perspective of the network station you will use to install GroupWise. GroupWise WebAccess requires long filename support. If you plan to copy GroupWise WebAccess to the software distribution directory so that you can run the GroupWise WebAccess Install program from there, make sure the server volume supports long filenames. See Determine the Location for the Software Distribution Directory in this chapter. |
| 7) System Name: | GroupWise | Specify a name consisting of one word. Names can reflect companies,
locations, and so forth.
Name the system carefully. After it is created, it cannot be renamed. See System, Domain, and Post Office Names in this chapter. |
| 8) Domain Name: | TechIndustries | Specify a name. The name can consist of one word. Names can reflect
locations, organizations, and so forth.
Name the domain carefully. After it is created, it cannot be renamed. See System, Domain, and Post Office Names in this chapter. |
| 9) Domain Directory: | J:\TI | Specify the path for the domain directory. The directory you
specify should not have other files in it.
Choose the name and path carefully. After the domain directory is created, it is difficult to rename. If the directory does not exist, it will be created. The path should be from the perspective of the network station you will use to install GroupWise. See Determine the Locations for the Domain and Post Office Directories in this chapter. |
| 10) Domain Context: | groupwise.corporate | Specify the context in the NDS tree where you want to create the
domain object. You should make sure the context you want exists before
you start installing GroupWise.
See Determine the Contexts for the Domain and Post Office Objects in this chapter. |
| 11) Domain Language: | English | Specify a default language for the domain. The language determines
how times, dates, and numbers are displayed in the GroupWise client and
affects the sorting order for items in the GroupWise Address Book. It
does not change interface language or the language of the Help files.
See Domain and Post Office Languages in this chapter. |
| 12) Domain Time Zone: | Mid-Atlantic | Specify the time zone in which the domain is located. The time zone information is used to ensure that times in messages sent between time zones are adjusted properly. |
| 13) Post Office Name: | Research | Specify a name that consists of one or more words. Names can
reflect locations, organizations, and so forth.
Name the post office carefully. After it is created, it cannot be renamed. See System, Domain, and Post Office Names in this chapter. |
| 14) Post Office Directory: | J:\RESEARCH | Specify the path for the post office directory. The directory you
specify should not have other files in it.
Choose the name and path carefully. After the post office directory is created, it is difficult to rename. If the directory does not exist, it will be created. The path should be from the perspective of the network station you will use to install GroupWise. See Determine the Locations for the Domain and Post Office Directories in this chapter. |
| 15) Post Office Context: | r&d.corporate | Specify the context in the NDS tree where you want to create the
domain object. You should make sure the context you want exists before
you start installing GroupWise.
See Determine the Contexts for the Domain and Post Office Objects in this chapter. |
| 16) Post Office Language: | English | The post office language defaults to the domain language. Specify a
different language if you do not want the post office to use the default
domain language.
See Domain and Post Office Languages in this chapter. |
| 17) Post Office Time Zone: | Mid-Atlantic | The post office time zone defaults to the domain time zone. Specify a different time zone if the post office is not in the same time zone as the domain. |
| 18) Post Office Users: | bmiller.r&d.corp | Specify the users who will have mailboxes on the post office. The
Setup Advisor lets you browse the NDS tree to select the users you want.
Adding users at this point is optional. After the Setup Advisor has finished, you can add users to the post office at any time. |
| 19) Agent Platform: | NetWare | Specify the platform (NetWare, Windows NT, or UNIX) on which you
will run the GroupWise agents.
See Decide Which GroupWise Agents to Install in this chapter. |
| 20) Agent Path: | Z:\SYSTEM | Specify the path to the directory in which you want the agents
installed.
The NetWare NLM agents must be installed to the SYS:\SYSTEM directory to simplify the use of startup files and ensure that dependent NLMs will load properly. The Windows NT agents can be installed to any directory on the Windows NT server or workstation. Because the installation is done from the NT machine, the default is C:\GRPWISE. The UNIX agents can be installed to any directory on the UNIX server. |
| 21) Agent Language: | English | Specify the language in which the agents will run. Only languages
that are installed to the software distribution directory will be
available.
See Decide Which Languages to Install in this chapter. |
* Novell trademark. ** Third-party trademark. See Trademarks for more information.