Using ConsoleOne to Administer Your GroupWise System

The Set Up GroupWise and Messenger task in iManager installed ConsoleOne and the GroupWise snap-ins to the sys:\public\mgmt\consoleone\1.2 directory. Placing a shortcut to consoleone.exe (located in the bin subdirectory) on your Windows desktop makes accessing ConsoleOne quick and easy.

IMPORTANT:  You cannot administer GroupWise using the version of ConsoleOne available from the GUI interface on the NetWare server console itself. The GroupWise snap-ins do not run correctly in that environment. However, you can run ConsoleOne from a workstation that has a drive mapped to the ConsoleOne directory on the server.

By default, the Domain and Post Office objects are located in the same container where the admin User object is located. In the GroupWise View of ConsoleOne, you can see the structure of your GroupWise system.

By default, the domain directory structure is created in \grpwise\gwdom and the post office directory structure is created in \grpwise\gwpo on the volume you select during system creation.

If you want to perform substantial GroupWise administration, you might want to install ConsoleOne and the GroupWise snap-ins to a workstation for better responsiveness.

1. Do one of the following:

   • Insert the GroupWise 6.5.4 (NetWare) Admin CD into the CD drive of the workstation where you want to install ConsoleOne and the GroupWise snap-[shy ][shy ]ins.
   • Map a drive to the sys:\grpwise\software directory on your Small Business server.

2. Run setup.exe.

3. Click Install Products > Install ConsoleOne.

4. Follow the prompts to install ConsoleOne on the workstation.

5. When you return to the GroupWise Installation program, click GroupWise Administration > Install GroupWise Administration.

6. Follow the prompts until you reach the Administration Options page.

7. Deselect Create a New System or Update an Existing System.

8. Deselect Extend the eDirectory Schema as well as Copy Files to a Software Distribution Directory, so that only Install Administration Files is selected, then click Next.

9. Follow the prompts to install the GroupWise snap-ins to ConsoleOne on the workstation.

10. (Conditional) If you need to install the POP Forwarding Agent snap-in to ConsoleOne, copy the psnap.jar file from the directory\consoleone\snapins directory on the server to the corresponding directory on your workstation.

Creating GroupWise Accounts Manually

If you do not want to run the Small Business Agent (SBA) on your Small Business server, you must manually create a GroupWise account for each new eDirectory user using ConsoleOne. You can create GroupWise accounts individually or for multiple users in the same post office.

• Adding GroupWise Accounts When Adding eDirectory Users
• Adding Multiple eDirectory Users to a Post Office

IMPORTANT:  If you are not running the SBA, LDAP authentication is not enabled automatically. Therefore, users have separate eDirectory and GroupWise passwords.

Disabling LDAP Password Changing

To facilitate easy access to GroupWise mailboxes, the Set Up GroupWise and Messenger task in iManager automatically enabled LDAP authentication for the post office it created if you chose to have it create users automatically. It also configured the LDAP server for use by GroupWise users. This default configuration accommodates SSL if it is in use on the LDAP server.

LDAP authentication allows the same password to be used for network login and mailbox access. When LDAP authentication is enabled, users are, by default, allowed to change their LDAP passwords from the GroupWise client. It is possible that users could change their GroupWise passwords without realizing that they are also changing their network login passwords. To prevent this, you can disable LDAP password changing from the GroupWise client in ConsoleOne.

1. In ConsoleOne, browse to and right-click the post office and then click Properties.

2. Click GroupWise > Security.

   
   

3. Select Disable LDAP Password Changing, then click OK.

   ConsoleOne then notifies the POA to restart so the new LDAP setting can be put into effect.

Assigning a Postmaster

The Internet requires each site to assign at least one user to be the Postmaster. The Postmaster is assigned to be the recipient of messages addressed to postmaster@host. The Postmaster also receives messages that the POP Forwarding Agent is unable to deliver to GroupWise users.

1. In ConsoleOne, browse to and right-click the Internet Agent (GWIA) object for the domain, then click Properties.

2. Click GroupWise > Gateway Administrators.

3. Click Add, select a GroupWise user to be the Postmaster, then click OK.

4. Select the user from the list, then click Postmaster.

5. Click OK to save the information.

   ConsoleOne then notifies the Internet Agent to restart so that applicable messages are sent to the Postmaster as needed.

Adding Post Offices to Your Initial Domain

A GroupWise post office serves as an administrative unit for a group of users and is used for addressing messages. Each GroupWise user has an address that consists of a user ID, the user's post office name, the GroupWise domain name and, optionally, an Internet domain name.

Your Small Business license grants you 100 users. This number of users can fit comfortably on a single post office, but you might consider creating multiple post offices for the following reasons:

• Physical Organization: If your network spans several sites, you might want to create post offices (if not domains) at each physical location. This will reduce the demands on long- distance network links.

• Logical Organization: Processing messages within a post office is faster and typically generates less network traffic than messages traveling between different post offices. As you expand GroupWise, you might find it useful to add post offices in order to group users who frequently send mail to each other. For example, some employees might work in corporate functions like accounting and human resources. Other employees might be involved in sales and marketing and frequently attend meetings together, requiring frequent busy searches. Some areas---for example, the production floor---might not need a workstation or user account for each individual.

• Number of Users: Although a post office can service many more than 1000 users, there are some advantages of setting up multiple, smaller post offices. The impact of a server being down is minimized. The processing times for post office and mailbox maintenance activities including backups is lessened for each post office individually, compared with one large post office. And each post office has room to grow while maintaining best performance.

If you decide to create multiple post offices, each post office should be created on a separate server. There is little advantage to creating multiple post offices on a single server.

1. In ConsoleOne, browse to and select the container where you want to create the new Post Office object, then click New > Object.

2. Select GroupWise Post Office, then click OK.

3. Provide a one-word name for the new post office, browse to and select the location where you want the post office directory structure to be created, then click OK.

4. Click Next to accept the default of a TCP/IP link to the domain, provide the IP address or hostname of the server where the post office will be located, then click Finish.

   You have now created a new Post Office object and Post Office Agent (POA) object in eDirectory, provided configuration information for these objects, and created the post office directory structure on the server where you want the post office to reside. Now you must install the POA on the server.

5. Do one of the following:

   • Insert the GroupWise 6.5.4 (NetWare) Admin CD into the CD drive of your Windows workstation.
   • Map a drive to the sys:\grpwise\software directory on your original Small Business server.

6. Run setup.exe.

7. Select Install Products > GroupWise Agents > Install GroupWise Agents.

8. Follow the prompts to install the GroupWise agents on the server.

9. On the Domains / Post Offices page, add the new post office.

10. Continue following the prompts to install the GroupWise agents.

    At the end of the installation, the Installation program can start the POA for you.

For more detailed instructions, see "Post Office" and "Post Office Agents" in the GroupWise 6.5 Administration Guide in the GroupWise 6.5 online documentation.

Adding Additional Domains

A GroupWise domain functions as the main administrative unit for your GroupWise system. Each GroupWise system has one primary domain, which was created when you first installed GroupWise. All other domains that you add will be secondary domains. The domain serves as a logical grouping of one or more post offices and is used for addressing and routing messages.

Although a single domain can contain as many post offices and users as you want to add, there are some conditions that indicate the need for a new domain:

• Administrative Convenience: To spread out the administrative workload, you can create one or more new domains with their own administrators. Each new domain can be managed by a different administrator as long as each administrator has sufficient rights to connect to it and write to the domain directory.

• Remote Sites: If communication between servers is slow, or if you have remote sites, you can add a new domain to minimize mail traffic between the servers. For example, if you have locations in three separate cities, you might have an organization that represents each location. You could then create a domain in each organization. You could administer all of the domains from one location or you could assign a different administrator for each one.

If you decide to create multiple domains, each domain should be created on a separate server. There is no advantage to creating multiple domains on a single server.

1. In ConsoleOne, browse to and select the container where you want to create the new Domain object, then click New > Object.

2. Select GroupWise Domain, then click OK.

3. Provide a one-word name for the new domain, browse to and select the location where you want the domain directory structure to be created, then click OK.

4. Click Next to accept the default of a TCP/IP link to the domain, provide the IP address or hostname of the server where the domain will be located, then click Finish.

   You have now created a new Domain object and Message Transfer Agent (MTA) object in eDirectory, provided configuration information for these objects, and created the domain directory structure on the server where you want the domain to reside. Now you must install the MTA on the server.

5. Do one of the following:

   • Insert the GroupWise 6.5.4 (NetWare) Admin CD into the CD drive of your Windows workstation.
   • Map a drive to the sys:\grpwise\software directory on your original Small Business server.

6. Run setup.exe.

7. Select Install Products > GroupWise Agents > Install GroupWise Agents.

8. Follow the prompts to install the GroupWise agents on the server.

9. On the Domains / Post Offices page, add the domain.

10. Continue following the prompts to install the GroupWise agents.

    At the end of the installation, the Installation program can start the MTA for you.

For more detailed instructions, see "Domains" and "Message Transfer Agent" in the GroupWise 6.5 Administration Guide in the GroupWise 6.5 online documentation.

Maintaining Your GroupWise System

Depending on the importance and volume of e-mail generated by your users, a number of maintenance tasks might need to be performed to keep your GroupWise system running smoothly. The GroupWise 6.5 Administration Guide in the GroupWise 6.5 online documentation can help you learn to perform the tasks your system needs. The table below summarizes the most common tasks and where they are described.

If you are using GroupWise Messenger, the Messenger 1.0 Administration Guide on the GroupWise 6.5 online documentation can help you learn to perform the tasks your Messenger system needs.

Managing the Small Business Agent

The Small Business Agent (SBA) is an NLM^TM program that performs the following functions automatically so that you do not need to perform the corresponding tasks manually:

• Creates GroupWise accounts whenever you create new eDirectory users
• Creates GroupWise distribution lists whenever you create new eDirectory groups
• Deletes GroupWise accounts whenever you delete eDirectory users
• Deletes GroupWise distribution lists whenever you delete eDirectory groups

This is especially helpful if you prefer to use Novell iManager for administration rather than ConsoleOne, the administration tool required by GroupWise.

If, during the Set Up GroupWise and Messenger task in iManager, you selected Automatic Creation of GroupWise Users and Groups Based on eDirectory, the setup task started the SBA and also added the following line to the autoexec.ncf file of your Small Business server:

gwsba /home-\\server\volume\domain_directory /scan-5

This line starts the SBA each time the server restarts. The /scan-5 switch indicates that the SBA scans eDirectory for new users and groups every five minutes. This means that, when you create a new eDirectory user, it could take as much as five minutes for the corresponding GroupWise account to be created. You can increase or decrease this interval as needed. At the SBA console, you can press F4 to cause the scan to take place immediately. If you do not want to run the SBA, comment out this line in the autoexec.ncf file.

The SBA console on the NetWare server displays messages about the SBA's activities. These messages are also recorded in log files for future reference. You can configure certain aspects of logging at the SBA console. You can also configure logging and other functionality of the SBA using startup switches. To see what startup switches are available, type the following command at the System Console prompt:

gwsba /help

Managing the POP Forwarding Agent

After the PFA is configured and successfully bringing e-mail into your GroupWise system, as described in Setting Up Common Mailbox Forwarding with the POP Forwarding Agent, it is easy to manage.

• Starting the PFA
• Monitoring and Controlling the PFA
• Using PFA Log Files
• Viewing or Changing the PFA Schedule
• Changing the Common Mailbox for Your Company
• Forwarding Personal E-Mail into Your GroupWise System
• Handling Multiple Domain Names
• Troubleshooting the PFA

Monitoring and Controlling the PFA

You can monitor and control the PFA at the console of the server where it is running or from your Web browser.

• Using the PFA Text Console Screen
• Using the PFA Web Console
• Using PFA Management Console Commands

Using the PFA Text Console Screen

The PFA text console screen on the server is available for executing commands quickly from the server console or remote server console.

If the PFA is running, the text console screen is listed as Java Interpreter number: com.novell.popforward in the Current Screens list (Ctrl+Esc) on the server console. You can access the PFA text console screen by entering the applicable screen number or by toggling to it using Alt+Esc on the server keyboard. The PFA text console screen displays PFA$ as its console prompt.

Using the PFA Web Console

The PFA Web console can use any browser that supports UTF-8 character encoding, such as Netscape* Navigator* version 4 or later or Microsoft Internet Explorer version 4 or later.

To access the PFA Web console, enter the following URL in the Address field of your browser:

http://ip_address_or_hostname:8110

Using PFA Management Console Commands

You can execute PFA management console commands by entering them at the PFA text console screen or by clicking the command on the PFA Web console.

The following table lists the command names, the tasks you can perform, and the availability or location in the consoles listed.

Command or Button	Description	PFA Text Console Screen	PFA Web Console
Alias	Displays a list of shortcuts for commands or reassigns command names for the PFA text console screen. Syntax: Alias new_alias old_command_name Example: alias quit shutdown	Available	Not available
Help	Lists and gives a brief description of all available PFA commands.	Available	Not available
List POP Accounts	Displays information about all POP accounts. HINT:  You can check mail immediately using by using the Rush command.	Not available	List POP Accounts link
Loglevel In the Web Console (Set Log Level)	Adjusts the log level to None, Low, Medium, or High. Low, Medium, or High are subcommands that you can enter after entering loglevel. Example: loglevel high This command does not display the current log level. You can view the current log level on the PFA text console screen at the server console using the Status command. For more information about the log levels, see Using PFA Log Files.	Available	Status section (display only)
Schedule	Displays or modifies the PFA polling schedule. This command uses the NetWare server's graphical user interface. The schedule applet shows the weekly polling schedule for the PFA. Light green cells in the schedule indicate the hours when the PFA is active. Dark green cells indicate inactive hours. The default PFA schedule is 6:00 am to 6:59 pm (6:00 to 18:59), polling every 30 minutes. To change the schedule, see Viewing or Changing the PFA Schedule.	Available	Not available
Shutdown	Shuts down the PFA. HINT:  You can restart the PFA manually by entering pfa at the server console prompt.	Available	Not available
Status	Displays the status of the PFA. The status information includes the log level, PFA state, information on the PFA domain and SMTP relay (Internet Agent), and current PFA authentication. Example: PFA Status: Running (or Hold or other error state) Log level is medium Domain: (mycompany.com) SMTP relay (localhost) PFA is authenticated as .pfa groupwise (or PFA is not authenticated) NOTE:  The SMTP and Domain information does not display if the Internet Agent is not running.	Available	Status section
Suspend	Stops mail downloads until the Resume command is entered.	Available	PFA Commands section
Reset	Resets the PFA. Resetting the PFA includes reauthenticating (if necessary), checking whether the Internet Agent is running, reloading the clock, and forwarding any downloaded messages.	Available	PFA Commands section
Resume	Resumes mail downloads after they have been stopped with the Suspend command. Downloads resume according to the current schedule.	Available	PFA Commands section
Rush	Checks for mail for all mail accounts at the ISP immediately. This command ignores (or overrides) the current schedule. Rush organization_name: Check for mail only for the domain. Rush username: Check for mail only for the specified user.	Available	List POP Accounts link
Tasks	Lists the PFA tasks that are waiting to be run. You should not see any tasks unless all the threads are busy.	Available	PFA Diagnostics link
Threads	Lists the PFA worker threads. You should not see any tasks unless all the threads are busy. The threads are idle most of the time. HINT:  You can use the Rush command to generate threads.	Available	PFA Diagnostics link

Viewing or Changing the PFA Schedule

The following table explains the functions of the color, field, and buttons on the PFA schedule interface.

Color/Field/Button	Function
Light green color	Indicates the PFA is on and polling for e-mail according to the mail download interval.
Dark green color	Indicates the PFA is off and dormant.
Mail Download Interval in Minutes field	Indicates how often within the hour the PFA will check to download mail from the ISP.
PFA Always On button	Turns all cells light green (on).
PFA Always Off button	Turns all cells dark green (off).
Reset Schedule button	Resets the schedule to the last schedule that was saved.
Save Schedule button	Saves the current schedule displayed on the screen.

Using the default schedule, the PFA checks for e-mail at the ISP every 30 minutes from 6:00 a.m. to 6:59 p.m. each day. You can adjust the PFA polling schedule to meet your specific needs.

You can view or adjust the PFA polling schedule using the PFA text screen console. For information about accessing the schedule from this console, see .

To change the polling schedule:

1. Access the schedule.

2. Click a block of cells to turn the PFA on or off for the hours and days indicated by the block.

   When the PFA is on, it polls for waiting e-mail according to the mail download interval. When the PFA is off, it is dormant and not polling.

3. Enter a value in the Mail Download Interval in Minutes field.

4. Click Save Schedule.

Changing the Common Mailbox for Your Company

Events like changing ISPs or changing your company name can make it necessary to change the information about the common mailbox that the PFA accesses.

1. In ConsoleOne, browse to and right-click the Organization object where your Small Business server is located, then click Properties.

2. Click POP Account.

3. Modify the following fields as needed:

   POP Host: The name of the mail server at your ISP (for example, mail.myisp.com).

   POP User Name: The corporate POP mailbox name at your ISP (for example, ABCorp).

   Password: The password for your company's mailbox at your ISP.

4. Click OK to save the new POP account information.

Follow the instructions in Testing the POP Forwarding Agent to ensure that the new configuration is forwarding e-mail successfully.

Forwarding Personal E-Mail into Your GroupWise System

If users want to receive e-mail from their personal POP accounts in their GroupWise mailboxes, you can configure the PFA to retrieve messages from multiple POP accounts.

1. In ConsoleOne, browse to and right-click a User object, then click Properties.

2. Click POP Account.

3. Fill in the following fields:

   POP Host: The name of the mail server at the user's ISP (for example, mail.myrealbox.com).

   POP User Name: The user's POP username (for example, LTanaka).

   Password: The user's password.

4. Click OK to save the POP account information.

5. If the user has more than one POP account, add the other accounts.

   1. Right-click the User object again, then click Properties.

   2. Click Other.

   3. Select the POP Account attribute, then click Add.

   4. Enter the POP host, POP username, and password, separated by colons (:); for example:

      mail.mailstar.net:SJones:thunder

   5. Click Apply.

   6. Repeat Step 5.c through Step 5.e for each additional POP account.

   7. When you are finished adding accounts, click OK.

Follow the instructions in Testing the POP Forwarding Agent to ensure that the new configuration is forwarding e-mail successfully.

Handling Multiple Domain Names

Typically, you would specify POP account information for only one Organization object in eDirectory, and that Organization object would have only one corporate POP account associated with it. However, you can configure the PFA to handle more complex situations. For example, you might have multiple POP accounts or even multiple ISPs to accommodate multiple domain names in use by your company.

You specified your main Internet domain name when you performed the Set Up GroupWise and Messenger task in iManager. This information was stored in the Foreign ID field of the Internet Agent (GWIA) object. To accommodate different domain names, you must configure both the PFA and the Internet Agent to handle them.

1. On your Small Business server, edit the sys:\system\pfa.ncf file.

2. On the java line, in front of the -classpath information, add the following parameter:

   -Ddomain="domain1,domain2,etc"

   The resulting line would look similar to the following example:

   java ... -Ddomain="novell.com,gw.novell.com,gwia.novell.com" -classpath ...

3. Save the file and exit the text editor.

4. In ConsoleOne, browse to and right-click the Internet Agent (GWIA) object for the domain, then click Properties.

5. Click GroupWise.

6. In the Foreign ID field, add the additional domain names after the main domain name, separating domain names with a space:

   For example:

   novell.com gw.novell.com gwia.novell.com

7. Click OK to save the multiple domain names.

   ConsoleOne then notifies the Internet Agent to restart so that the multiple domain names are accepted by the Internet Agent.

8. Restart the PFA.