1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 GATEWAY FOR MICROSOFT EXCHANGE - INSTALLATION AND...
  6. Installation and administration manual

Novell GROUPWISE 7 GATEWAY FOR MICROSOFT EXCHANGE - INSTALLATION AND ADMINISTRATION Installation And Administration Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Novell
GroupWise
Microsoft* Exchange
7
M a y 8 , 2 0 0 7
Gateway for
®
I N S T A L L A T I O N A N D
A D M I N I S T R A T I O N G U I D E
w w w . n o v e l l . c o m

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GROUPWISE 7 GATEWAY FOR MICROSOFT EXCHANGE - INSTALLATION AND ADMINISTRATION and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell GROUPWISE 7 GATEWAY FOR MICROSOFT EXCHANGE - INSTALLATION AND ADMINISTRATION

Summary of Contents for Novell GROUPWISE 7 GATEWAY FOR MICROSOFT EXCHANGE - INSTALLATION AND ADMINISTRATION

  • Page 1 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide Novell GroupWise Gateway for ® Microsoft* Exchange w w w . n o v e l l . c o m I N S T A L L A T I O N A N D...

  • Page 2: Legal Notices

    Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
  • Page 3 Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/ trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners.

  • Page 5: Table Of Contents

    Contents About This Guide 1 What Is the GroupWise Gateway for Microsoft Exchange? What’s New in This Release ..........11 2 Exchange Gateway System Requirements 3 Planning the Exchange Gateway Installation Gathering GroupWise System Information .
  • Page 6 7.1.1 Starting the Exchange Gateway As a Windows Application ....55 7.1.2 Starting the Exchange Gateway As a Windows Service ..... . 56 Acquainting E-Mail Users with the Exchange Gateway .
  • Page 7 10.2 Adjusting the Number of Sender and Receiver Threads ......105 10.3 Automating Network Reattachment ..........105 10.4 Reducing Network Traffic .
  • Page 8 January 24, 2007 (Support Pack 1) ..........143 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 9: About This Guide

    We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comment feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.

  • Page 10: Documentation Conventions

    Administration Guide, visit the GroupWise Gateway Documentation Web site (http:// www.novell.com/documentation/gwgateways). Documentation Conventions In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. ® A trademark symbol ( , etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.

  • Page 11: What Is The Groupwise Gateway For Microsoft Exchange

    What Is the GroupWise Gateway for Microsoft Exchange? ® The GroupWise 7 Gateway for Microsoft Exchange connects a GroupWise system and an Exchange system by creating a link between a GroupWise domain and an Exchange server, as shown in the following diagram. The GroupWise 7 version of the Exchange Gateway provides the following capabilities: Message exchange between users of GroupWise 5.x, 6.x, and 7.x and users of Exchange 5.5, 2000, and 2003.
  • Page 12 SNMP is supported, so that the Exchange Gateway can be monitored from SNMP management and monitoring programs. A Web console is provided, so that the Exchange Gateway can be monitored from any location where you have access to a Web browser and the Internet. GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 13: Exchange Gateway System Requirements

    Windows Server 2003 with Active Directory Updated with Updated with Service Pack 1 or later and the NNTP Service (for use with Service Pack 1 Microsoft Exchange 2003) ® Novell Client™ Any version Latest version ® ConsoleOne 1.3.6 Latest version...
  • Page 14 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 15: Planning The Exchange Gateway Installation

    EXCHANGE GATEWAY INSTALLATION WORKSHEET ® Under Item 4: eDirectory Information, list the Novell eDirectory™ tree and context where the Domain object is located. Under Item 5: GroupWise Domain Information, list the domain name and domain directory. If you want to use a separate domain for the Exchange Gateway, create the new domain now.

  • Page 16: Choosing A Gateway Name

    If you install the Exchange Gateway on a different server from where the domain is located, you must provide a username and password for the gateway to use when logging in to the server where the domain is located. The gateway requires Read, Write, Create, Erase, Modify, and File Scan rights in the domain directory.

  • Page 17: Deciding How To Monitor The Exchange Gateway

    Exchange Gateway Web console. 3.5.2 Using an SNMP Monitoring Program If desired, you can monitor the Exchange Gateway from Novell ZENworks® for Servers or any other SNMP management and monitoring program. When properly configured, the Exchange Gateway sends SNMP traps to network management consoles for display along with other SNMP monitored programs.

  • Page 18: Gathering Exchange System Information

    You must enable SNMP during gateway installation. You cannot add this functionality after installation. In order for the option to be offered during installation, the Windows server where you install the gateway must have the SNMP service installed. The SNMP service is usually not included during the initial Windows operating system installation. To add or configure the SNMP service on the server where you plan to install and run the Exchange Gateway, you must be logged in as a member of the Administrator group.

  • Page 19: Determining Connections Between Systems

    3.7 Determining Connections between Systems To facilitate addressing of messages between systems, you must set up a representation of the Exchange system in your GroupWise system and a connector to your GroupWise system in your Exchange system. In GroupWise, non-GroupWise systems are represented by non-GroupWise domains. When you first start the Exchange Gateway, the non-GroupWise domain for the Exchange system is created automatically.

  • Page 20: Determining Where To Install The Exchange Gateway Administrator Snap-In To Consoleone

    The recommendation is to use Exchange mailbox names as GroupWise user IDs. However, if this is not possible for some reason, the following variables can be used to specify the information you want to appear in the GroupWise user IDs: Variable Description Mailbox name (default)

  • Page 21: Exchange Gateway Installation Worksheet

    3.10 Exchange Gateway Installation Worksheet Item Explanation 1) Exchange Gateway Location: Mark whether you want to install the Exchange Gateway on the same server with the GroupWise domain it belongs to, or on a Domain server remote server. Remote server For access to a remote server, provide a username and password Username to facilitate logging in with the required rights.
  • Page 22 Item Explanation 7) Monitoring Options: Mark how you want to monitor the Exchange Gateway. “Deciding How to Monitor the Exchange Gateway” on page Exchange Gateway Web console SNMP monitoring program 8) Gateway Installation Method: Mark whether you want to install the Exchange Gateway as a Windows application or a Windows service.
  • Page 23 Item Explanation 14) Exchange User Address Mark whether you want to use the Exchange mailbox name as the Format GroupWise user ID for each Exchange user. Section 3.8, “Selecting User Address Type and Format,” on Exchange mailbox name page (default) Custom Planning the Exchange Gateway Installation...
  • Page 24 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 25: Installing The Exchange Gateway

    Chapter 2, “Exchange Gateway System Requirements,” on page 1 Make sure that the Novell Client™ is installed. The Installation program creates a Gateway object in eDirectory. The Novell Client is required to access eDirectory. If necessary, you can download the Novell Client from the...

  • Page 26: Adding The Exchange Library Directory To The Path Variable

    Software. 4.3 Installing the Exchange Gateway Software 1 Download the GroupWise Gateway for Microsoft* Exchange from the Novell Product Downloads site (http://download.novell.com) into an empty directory on the server where you want to install it (worksheet item The server where you install the Exchange Gateway must be an Exchange server.

  • Page 27: Installing The Exchange Gateway Addressing Components

    If the Installation program does not start automatically, run install.exe in the directory where you extracted the Exchange Gateway files. 4 Click Next to view the license agreement, then click Accept to accept the license agreement. 5 Select Install Gateway and Addressing Components, then click Next. 6 Follow the prompts, using the information from items 2 through 9 on the...
  • Page 28 3 At each Exchange server, run setupexch700.exe to start the Installation program. If the Installation program does not start it automatically, run install.exe in the directory where you extracted the Exchange Gateway files. 4 Click Next to view the license agreement, then click Accept to accept the license agreement. 5 Select Install Addressing Components.

  • Page 29: Installing The Exchange Gateway Administrator Snap-In To Consoleone

    4.5 Installing the Exchange Gateway Administrator Snap-In to ConsoleOne After you have installed the Exchange Gateway, you can install the Exchange Gateway Administrator snap-in to Console One to additional Exchange servers as needed. The Gateway Administrator snap-in cannot be installed on a workstation. 1 Make sure that no one is running ConsoleOne from the Exchange server where you want to install the Gateway Administrator snap-in.
  • Page 30 4 Select Install Gateway Administrator Snap-Ins for ConsoleOne Only. 5 Click Next to continue with the installation. GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 31: Configuring The Exchange Side Of The Exchange Gateway

    Configuring the Exchange Side of the Exchange Gateway After you install the Exchange Gateway software but before you start the Exchange Gateway for the ® first time, you must prepare your Exchange system to link to your GroupWise system: Section 5.1, “Configuring Exchange 5.5,” on page 31 Section 5.2, “Configuring Exchange 2000/2003,”...
  • Page 32 3 Double-click the Exchange Gateway object (worksheet item 6), then click Export Containers. 4 Select the Recipient containers that contain users whose Address Book information you want to export into the GroupWise system, then click Add. 5 In the Trust Level field, select a trust level number that is larger than the trust level numbers of the users you want to export.

  • Page 33: Customizing Addressing For Exchange 5.5

    Skip to Chapter 6, “Configuring the GroupWise Side of the Exchange Gateway,” on page 51 5.1.1 Customizing Addressing for Exchange 5.5 1 In Exchange Administrator, expand the Site container, then select the Configuration container. 2 Double-click the Site Addressing object, then click the Site Addressing tab. If no GroupWise-specific address type appears in the list, then the addressing components have not been installed on the server.

  • Page 34: Configuring Exchange 2000/2003

    3 Select GWISE (or your custom address type for GroupWise), then click Edit. 4 To change the name of the non-GroupWise domain that you want to represent your Exchange system, replace the Exchange organization with the domain name you want to use (worksheet item 12).

  • Page 35: Performing Basic Configuration For Exchange 2000/2003

    5.2.1 Performing Basic Configuration for Exchange 2000/2003 1 Start Exchange System Manager. TIP: If you do not see the Administrative Groups object, right-click the Organization object, then click Properties. Select Display Administrative Groups and Display Routing Groups, then click OK. 2 Expand Administrative Groups, then expand First Administrative Group (or whatever your system’s administrative group is).
  • Page 36 4 Expand Connectors, right-click the Gateway object, then click Properties. 5 Click Modify, specify the administrator username and password, then click OK. 6 Click Export Containers. 7 Click Add, select the container that contains Exchange users whose addresses and information you want to export to the GroupWise system (for example, the Users container), then click OK to add the export container to the list.
  • Page 37 useimportcontainer gateway startup switch to place the users into the import container specified under Administrative Groups > First Administrative Group > Routing Group > First Routing Group > Connectors > Exchange Gateway Connector. 8 Click OK again to return to the main Exchange System Manager window. 9 Expand Servers, then expand the Server object for your server.
  • Page 38 11 Right-click Mailbox Store, click Properties, then click Security. 12 Add the user to log in to the Exchange services and the Windows server (if the user has not been added already). 13 Scroll to the bottom of the Permissions list, grant the user Send As and Receive As permissions, then click OK.

  • Page 39: Setting Up Bidirectional Busy Search For Exchange 2000/2003

    If you want to customize the name of the non-GroupWise domain that represents the Exchange system, the external post office that represents the Exchange administrative group, or the format of GroupWise-type usernames for Exchange users, skip to Section 5.2.3, “Customizing Addressing for Exchange 2000/2003,”...
  • Page 40 Configuring the Calendar Connector on Exchange 2000 1 In Exchange System Manager, expand Administrative Groups > First Administrative Group > Routing Groups > First Routing Group > Connectors. 2 Right-click the Calendar Connector, then click Properties. 3 Under Connector used to import users into Active Directory, click Modify. GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...
  • Page 41 ® 9 If there is not a Novell GroupWise type already listed, click New, select Novell GroupWise, then click OK to display the GroupWise Calendar Connection dialog box. 10 In the GroupWise API Gateway field, specify domain.exchange_gateway, then click OK.
  • Page 42 Setting Up the Microsoft Calendar Connector on Exchange 2003 “Installing the Calendar Connector on Exchange 2003” on page 42 “Deactivating the Microsoft Connector for Novell GroupWise” on page 44 “Configuring the Calendar Connector on Exchange 2003” on page 45 Installing the Calendar Connector on Exchange 2003 1 Insert the Microsoft Exchange 2003 CD into the CD drive on the Exchange server.
  • Page 43 6 Click the check mark in the Action column for Microsoft Exchange Messaging and Collaboration Services, then select Change from the drop-down list. 7 Click in the Action column for Microsoft Exchange Connector for Novell GroupWise, then select Install. 8 Click in the Action column for Microsoft Exchange Calendar Connector, then select Install.
  • Page 44 Deactivating the Microsoft Connector for Novell GroupWise The Exchange Gateway does not use the Connector for Novell GroupWise provided by Microsoft. 1 In Exchange System Manager, expand Administrative Groups > First Administrative Group > Routing Groups > First Routing Group > Connectors.
  • Page 45 The bidirectional configuration for Busy Search does not use the GWISE address space that is set up when you install the Exchange Gateway. 7 Continue with Configuring the Calendar Connector on Exchange 2003. Configuring the Calendar Connector on Exchange 2003 1 In the Connectors list, right-click Calendar Connector, then click Properties.
  • Page 46 7 Click Apply to save your settings. 8 Click Calendar Connections. 9 If there is not a Novell GroupWise type already listed, click New, select Novell GroupWise, then click OK to display the GroupWise Calendar Connection dialog box. 10 In the GroupWise API Gateway field, specify domain.exchange_gateway, then click OK.
  • Page 47 7b In the Startup Type field, select Automatic. 7c Click Start, then click OK. 8 In the list of services, make sure that the Microsoft Exchange Router for Novell GroupWise is running. If it is not: 8a Right-click Microsoft Exchange Router for Novell GroupWise, then click Properties.
  • Page 48 3a Browse to and right-click the Exchange Gateway object, then click Properties. 3b Click GroupWise > Optional Gateway Settings. 3c Make sure that Directory Sync/Exchange is set to Both. 4 Start the Exchange Gateway, as described in Section 7.1, “Starting the Exchange Gateway,” on page A fresh user synchronization automatically takes places between the two systems and bidirectional Busy Search is now available.

  • Page 49: Customizing Addressing For Exchange 2000/2003

    5.2.3 Customizing Addressing for Exchange 2000/2003 1 In Exchange System Manager, expand the Recipients container, then select the Recipient Policies container. 2 Right-click the Default Policy object, click Properties, then click the E-Mail Addresses (Policy) tab. If no GroupWise-specific address type appears in the list, then the addressing components have not been installed on the server.
  • Page 50 3 Select GWISE (or your custom address type for GroupWise), then click Edit. In the Address field, the three parts of a GroupWise address (domain, post office, and username) are separated by periods. The displayed default is Exchange_organization.Exchange_administrative_group.address_format_variable. 4 To change the name of the non-GroupWise domain that you want to represent your Exchange system, replace the Exchange organization with the domain name you want to use worksheet item...

  • Page 51: Configuring The Groupwise Side Of The Exchange Gateway

    Configuring the GroupWise Side of the Exchange Gateway ® After you have configured the Exchange side of the gateway, you must configure the GroupWise ® side of the gateway by configuring the Exchange Gateway object in ConsoleOne Section 6.1, “Providing Foreign System Configuration Information,” on page 51 Section 6.2, “Providing Gateway Information,”...
  • Page 52 The defaults are typically acceptable, but you can change the information if needed. Address: Specify the name of the Exchange address type (worksheet item 11) that you want the gateway to create in the Exchange system. The default is GWise. Administrator: Specify the name and e-mail address of the administrator of the Exchange system.

  • Page 53: Providing Gateway Information

    6.2 Providing Gateway Information 1 On the Exchange Gateway object, click GroupWise > Identification. 2 Fill in the following fields on the Identification page: Description: This field is optional. If desired, provide any descriptive information about the gateway. Subdirectory: Displays the name of the Exchange Gateway root directory specified during installation.
  • Page 54 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 55: Running The Exchange Gateway

    Running the Exchange Gateway After you have installed the Exchange Gateway software and configured both sides of the gateway, you are ready to start the gateway. Section 7.1, “Starting the Exchange Gateway,” on page 55 Section 7.2, “Acquainting E-Mail Users with the Exchange Gateway,” on page 57 Section 7.3, “Stopping the Exchange Gateway,”...

  • Page 56: Starting The Exchange Gateway As A Windows Service

    2 Click GroupWise Exchange Gateway > Exchange > GroupWise Exchange Gateway. When running as an application, the Exchange Gateway server console appears on the server while it is running. For instructions on interpreting the information displayed on the Exchange Gateway server console, and for information about other monitoring alternatives, see Chapter 9, “Monitoring the Exchange Gateway,”...

  • Page 57: Acquainting E-Mail Users With The Exchange Gateway

    7.2 Acquainting E-Mail Users with the Exchange Gateway After you have started the Exchange Gateway, GroupWise users and Exchange users need only the following information in order to start using the gateway immediately: Section 7.2.1, “Addressing Messages,” on page 57 Section 7.2.2, “Understanding What GroupWise Send Options Are Available through the Gateway,”...

  • Page 58: Stopping The Exchange Gateway

    The following GroupWise send options are not supported: Expiration Date (after x days) Auto-Delete (when the last recipient has deleted the message) Conceal Subject Require Password to Complete Routed Item Sign Digitally Encrypt for Recipients 7.3 Stopping the Exchange Gateway Occasionally, it might be necessary to stop the gateway to perform maintenance on the Windows server or for some other purpose.

  • Page 59: Uninstalling The Exchange Gateway As An Application

    Section 7.4.2, “Uninstalling the Exchange Gateway As a Service,” on page 59 7.4.1 Uninstalling the Exchange Gateway As an Application 1 At the Windows server where you installed the Exchange Gateway, click Start > Programs > GroupWise Exchange Gateway > Exchange > Uninstall. 2 If a message informs you that some files could not be deleted, delete the directory.
  • Page 60 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 61: Configuring The Exchange Gateway

    Configuring the Exchange Gateway ® After the Exchange Gateway is up and running between the GroupWise system and the Exchange system, there are a variety of ways to refine its configuration to meet the specific needs of your e- mail users. Section 8.1, “Enabling Directory Synchronization and Exchange of Address Books,”...
  • Page 62 ® 3 In ConsoleOne , browse to and select the domain where you installed the Exchange Gateway, right-click the Exchange Gateway object, then click Properties to display the gateway Identification page. 4 Click GroupWise > Optional Gateway Settings to display the Optional Gateway Settings page. 5 In the Directory Sync/Exchange field, select Both, then click OK.
  • Page 63 GroupWise users appear in the Exchange Address Book because the Exchange Gateway creates recipient addresses based on the GroupWise address type, as described in Section 3.8, “Selecting User Address Type and Format,” on page When you first turn on directory synchronization and exchange, e-mail addresses from the Exchange system come into the GroupWise Address Book in the format username.administrative_group.exchange_organization.

  • Page 64: Configuring Addressing Instead Of Using Directory Synchronization And Exchange

    users and Exchange users can select each other out of their familiar Address Books. Addressing is not an issue under these circumstances. If you do not want to enable directory synchronization and exchange, you must use other addressing alternatives: Section 8.2.1, “Adding Individual Exchange Users to the GroupWise Address Book,” on page 64 Section 8.2.2, “Adding Individual Exchange Users to Personal Address Books,”...
  • Page 65 4 Right-click the new External User object, then click Properties. 5 Fill in fields as needed to provide information about Exchange the user that you want to appear in the GroupWise Address Book. 6 Click Apply to save the user information. 7 Click GroupWise >...

  • Page 66: Adding Individual Exchange Users To Personal Address Books

    8 Click Add to display the Create Alias dialog box. 9 Fill in the following fields: Gateway Alias Type: From the list, select the Exchange Gateway. The gateway alias type was defined during configuration of the gateway. If there is no gateway alias type listed for the gateway, you can define one now.

  • Page 67: Adding Individual Groupwise Users To The Exchange Address Book

    3 Click New > Contact > OK. 4 Fill in the following fields: First: Specify the user’s first name. Last: Specify the user’s last name. E-mail Address: Specify the explicit address required to route a message to the Exchange user. For syntax and examples, see “Addressing Messages”...
  • Page 68 Adding GroupWise Users in Exchange 5.5 1 Start Exchange Administrator. 2 Expand the Recipients container. 3 Select an existing container. Create a new container for GroupWise recipients. 3a Click File > New Other > Recipients Container. 3b Specify a name for the new container; for example, GroupWise Recipients. 3c Specify a directory for the new container.
  • Page 69 5 Select GWISE Address, then click OK. 6 In the Display Name field, specify the full name of the GroupWise user. 7 In the Address field, specify the GroupWise user’s address in the following format: domain.post_office.user_ID where domain is the name of the GroupWise domain, post_office is the name of the GroupWise post office, and user_ID is the user’s GroupWise ID.
  • Page 70 2 Expand the Users container, select the container in which you want to create a Contact, then click Action > New > Contact. 3 Specify the information about the GroupWise user that you want to be available in the Exchange Address Book, then click Next. 4 In the E-mail Address field, click Modify.

  • Page 71: Using Explicit Addressing

    5 Select Novell GroupWise Address, then click OK. 6 In the Address field, specify the GroupWise user’s address in the following format: domain.post_office.user_ID where domain is the name of the GroupWise domain, post_office is the name of the GroupWise post office, and user_ID is the user’s GroupWise ID.

  • Page 72: Changing The Link Protocol Between The Exchange Gateway And The Mta

    <firstname> <lastname> <firstinitial> <lastinitial> Each tag is replaced with the corresponding user-specific information. Additional text can be added to the address format as well. Examples: /addressrule-<firstname>_<lastname>@<domain> /addressrule-<firstname>.<lastname>@<domain> /addressrule-<username>@exchange.<domain> These address rules would result in the following addresses for a user named Sophie Jones at Corporate.com: Sophie_Jones@Corporate.com Sophie.Jones@Corporate.com...

  • Page 73: Controlling Gateway Access

    2 Click GroupWise > Network Address. 3 In the TCP/IP Address field, click Edit, specify the IP address or DNS hostname of the server where the Exchange Gateway is running (which is not necessarily the server where the Exchange Gateway software is installed), then click OK to return to the Network Address page. 4 In the Message Transfer Port field, specify a unique port number;...

  • Page 74: Using The Access.cfg File In The Gateway Directory

    In the examples provided in the access.cfg file, the string gwaddresstext represents the address of an Exchange user. For example, you could replace gwaddresstext with Novell.Sales.Glen if that is the appropriate address format, as explained in Section 3.8, “Selecting User Address Type and Format,” on page...
  • Page 75 Section Headers Section headers establish groups of users to which access control settings are applied. “[Default:In|Out]” on page 75 “[groupwise_domain:In|Out]” on page 75 “[groupwise_domain.post_office:In|Out]” on page 75 “[AccessGroup:group_name]” on page 76 [Default:In|Out] This section lists the access control settings for users who are not covered by access control settings for a particular GroupWise domain, post office, or access group.
  • Page 76 Syntax: [groupwise_domain.post_office:In] [groupwise_domain.post_office:Out] Examples: [Corporate.Temps:In] Allow NetTech MaxSize=10000 [Corporate.Temps:Out] Allow NetTech MaxSize=10000 AllowRuleGenerated=No This example allows users in the Temps post office to exchange messages with users in the Exchange NetTech system only. It restricts incoming and outgoing messages to 10 KB. It prevents rule-generated messages.
  • Page 77 AllAccess This keyword provides unrestricted access to the Exchange Gateway for those GroupWise users specified by the section header. Users can send messages to or receive messages from Exchange users, depending on the direction specified by the header. Examples: [Corporate.Executives:In] AllAccess[ [Corporate.Executives:Out] AllAccess...
  • Page 78 Block CN=Sophie Jones/O=Sales@XYZCorp The first example prevents GroupWise users in the Temps post office from exchanging messages with users in the Exchange XYZCorp system. The second example prevents GroupWise users in the Executives post office from receiving messages from a specific Exchange user. Providing the username in both formats is required to totally block a user.

  • Page 79: Using The Gateway Access Field On Individual User Objects

    This example prevents GroupWise users in the Temps post office from receiving messages larger than 1 MB and from sending messages larger than 5 MB. AllowRuleGenerated This keyword determines whether or not rule-generated messages are allowed through the Exchange Gateway. It applies only to outbound messages from GroupWise to Exchange. You could use this keyword to control rule-generated messages such as “On Vacation”...
  • Page 80 3 Click GroupWise > Account to display the Account page. 4 Fill in the Gateway Access field. If you created an access control group in the access.cfg file in Step 1, specify the name of the access control group that you want this user to be associated with. If you have not created an access control group, you can put access control information unique to this user in the Gateway Access field.

  • Page 81: Setting Up Accounting

    8.5 Setting Up Accounting Every day at midnight, the Exchange Gateway creates an accounting file (acct) in the directory. The acct file is an ASCII-delimited text file domain\wpgate\exchange\000.prc that records the source, priority, message type, destination, and size of each item passing through the gateway.

  • Page 82: Defining An Accountant

    8.5.2 Defining an Accountant 1 On the Exchange Gateway object, click GroupWise > Gateway Administrators to display the Gateway Administrators page. The Gateway Administrators page lets you select a GroupWise user to be the Accountant for the Exchange Gateway. Each night at midnight, the gateway mails the accounting file (acct) to the Accountant.
  • Page 83 which is updated daily at midnight, is located in the domain\wpgate\exchange\000.prc directory. If no Accountant is defined to receive the file, the file is deleted each day. A sample line from an accounting file is shown below: O,05/18/05, 20:42:55,, Mail,3,Corporate,Temps,LTanaka,,Reminder,Connector,Exchange,, Mail,SJones@Provo,1,0,2593 Each item sent through the gateway is recorded on a separate line, with the fields separated by commas.

  • Page 84: Establishing Gateway Administrators

    8.6 Establishing Gateway Administrators A gateway administrator is any GroupWise user you assign to receive information and error messages from the Exchange Gateway. The gateway does not require an administrator, but if you want to define one, the administrator must either be a user who is associated with GroupWise or with a GroupWise distribution list.

  • Page 85: Enabling Message Status For Sent Items

    4 Click OK to return to the Gateway Administrators page and add the user to the Gateway Administrators list. 5 In the Administrator Role box, select the type of administrator you want the user to be. Operator Accountant Postmaster Foreign Operator 6 Click OK to save the Exchange Gateway administrator list.

  • Page 86: Binding The Exchange Gateway To A Specific Ip Address

    Outbound Status Level: Outbound status refers to the status information returned to GroupWise users for messages they send to Exchange users. Select Undelivered, Delivered, Open, or Full (which is equivalent to selecting Undelivered, Delivered, and Open). Correlation Enabled: Select Yes. Message correlation is used to map Exchange delivery, non- delivery, and receipt reports to GroupWise status messages, and GroupWise status messages to Exchange delivery, non-delivery, and receipt reports.
  • Page 87 2 Click GroupWise > Network Address to display the Network Address page. 3 Select Bind Exclusively to TCP/IP Address, then click OK to save your change. Corresponding Startup Switches You can also use the startup switch in the Exchange Gateway startup file to establish an exclusive bind to the specified IP address.
  • Page 88 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 89: Monitoring The Exchange Gateway

    Monitoring the Exchange Gateway By monitoring the Exchange Gateway, you can determine whether or not its current configuration is meeting the needs of the users it services. You have a variety of tools to help you monitor the operation of the Exchange Gateway: Section 9.1, “Using the Exchange Gateway Server Console,”...

  • Page 90: Information Box

    Section 9.1.5, “Menu Summary,” on page 91 9.1.1 Information Box The top portion of the console provides the following information about the gateway. Domain.Gateway: The domain where the gateway is installed and the name of the gateway. UpTime: The length of time the gateway has been running. Description: The description you added when you configured the gateway, as described in Section 6.2, “Providing Gateway Information,”...

  • Page 91: Log Message Box

    Stop the Exchange Gateway. Configuration Gateway Display the gateway configuration settings from the Settings Exchange Gateway object in Novell® eDirectory™. For more information, see Chapter 6, “Configuring the GroupWise Side of the Exchange Gateway,” on page 51 and various sections in Chapter 7, “Running the Exchange...

  • Page 92: Using The Exchange Gateway Web Console

    9.2 Using the Exchange Gateway Web Console The Exchange Gateway Web console enables you to monitor and control the Exchange Gateway from any location where you have access to a Web browser and the Internet. This provides substantially more flexible access than the Exchange Gateway server console, which can be accessed only from the Windows server where the Exchange Gateway is running.

  • Page 93: Accessing The Exchange Gateway Web Console

    6 Click GroupWise > Optional Gateway Settings. 7 In the HTTP Settings box: 7a In the HTTP User Name field, specify a unique username. 7b Click Set Password. 7c Type the password twice for verification. 7d Click Set Password. Do not use an eDirectory username and password because the information passes over the non-secure connection between your Web browser and the Exchange Gateway.

  • Page 94: Monitoring The Exchange Gateway From The Web Console

    Syntax: http://IP_address_or_hostname:HTTP_port Examples: http://172.16.5.18:7176http://exchserver1:7176 9.2.3 Monitoring the Exchange Gateway from the Web Console The Exchange Gateway Web console provides several pages of information to help you monitor the performance of the Exchange Gateway. The bar at the top of the Exchange Gateway Web console displays the name of the Exchange Gateway and its post office.
  • Page 95 To change the log settings for the current gateway session, click Event Log Settings. All other settings listed on the Configuration page must be changed in ConsoleOne. Checking the Operating System Environment On the Exchange Gateway Web console menu, click Environment to display information about the operating system where the Exchange Gateway is running.
  • Page 96 Click Event Log Settings to change the log settings for the current Exchange Gateway session. For information about Exchange Gateway log files, see Section 9.3, “Using Exchange Gateway Log Files,” on page Checking and Changing Gateway Time Settings On the Exchange Gateway Web console menu, click Time Settings to display the settings listed on the Time Settings page in ConsoleOne.

  • Page 97: Using Exchange Gateway Log Files

    Modify the settings as needed, then click Submit to change them for the current Exchange Gateway session. For information about the optional gateway settings, see the following topics: Section 8.1, “Enabling Directory Synchronization and Exchange of Address Books,” on page 61 Section 8.5, “Setting Up Accounting,”...
  • Page 98 If you have any problems that require assistance from Novell Support (http://www.novell.com/support), it is likely that the technician who helps you will request a copy of this file. Log files are stored in the gateway’s 000.prc directory (domain\wpgate\exchange\000.prc) and can be viewed from the Gateway server console...

  • Page 99: Using Snmp Monitoring Programs

    “Menu Summary” on page 9.4 Using SNMP Monitoring Programs ® You can monitor the Exchange Gateway from Novell ZENworks for Servers or any other SNMP management and monitoring program. When properly configured, the Exchange Gateway sends SNMP traps to network management consoles for display along with other SNMP monitored programs.

  • Page 100: Copying And Compiling The Exchange Gateway Mib File

    To set up SNMP services for the Windows server, complete the following tasks: Section 9.4.1, “Copying and Compiling the Exchange Gateway MIB File,” on page 100 Section 9.4.2, “Configuring the Exchange Gateway for SNMP Monitoring,” on page 100 9.4.1 Copying and Compiling the Exchange Gateway MIB File An SNMP-enabled Exchange Gateway returns information contained in a Management Information Base (MIB).
  • Page 101 2 Click GroupWise > Network Address to display the Network Address page. 3 Click the pencil icon to provide the TCP/IP address or hostname of the server where the Exchange Gateway runs, then click Apply. The Exchange Gateway does not currently support SSL. 4 Click GroupWise >...

  • Page 102: Notifying The Exchange Gateway Administrator About Bad Messages

    ConsoleOne then notifies the Exchange Gateway to restart so the new settings can be put into effect. The Exchange Gateway should now be visible to your SNMP monitoring program. 9.5 Notifying the Exchange Gateway Administrator about Bad Messages Occasionally, the Exchange Gateway encounters a message that it cannot process, either because the message file has been damaged or because the recipient is not a user that is recognized by the gateway.

  • Page 103: Optimizing The Exchange Gateway

    Optimizing the Exchange Gateway You can adjust how the Exchange Gateway functions in order to optimize its performance. Before attempting optimization, you should run the Exchange Gateway long enough to observe its efficiency and its impact on other network applications running on the same server. See Chapter 9, “Monitoring the Exchange Gateway,”...
  • Page 104 2 Click GroupWise > Gateway Time Settings to display the Gateway Time Settings page. 3 Fill in the following fields: Send/Receive Cycle: Specify the maximum amount of time you want the gateway to spend sending and receiving messages during one cycle. The default cycle is 120 seconds, which causes the gateway to send messages for a maximum of 60 seconds and to receive messages for 60 seconds.

  • Page 105: Adjusting The Number Of Sender And Receiver Threads

    10.2 Adjusting the Number of Sender and Receiver Threads The Exchange Gateway can be configured to start from varying numbers of sender and receiver threads, depending on the amount of traffic passing through the gateway. The heavier the traffic, the more threads you should configure the gateway to start.

  • Page 106: Reducing Network Traffic

    Failed Recovery Wait: If the gateway cannot reconnect to the network after the number of times specified in Retry Count, it stops attempting to reconnect. Specify the amount of time you want the gateway to wait until it starts the reconnect process again. The default value is 3600 seconds (1 hour).

  • Page 107: Using Exchange Gateway Startup Switches

    Using Exchange Gateway Startup Switches Startup switches let you set various operational parameters for the gateway. Some startup switches ® override configuration information, such as logging level, that you can set in ConsoleOne . Other switches provide configuration options not available anywhere else. To use a startup switch, you can include it on the command line immediately following the executable command.

  • Page 108: Addressrule

    Startup Switch ConsoleOne Setting TCP/IP Address /log Log File Path /logdays Maximum Log File Age /loglevel Log Level /logmax Maximum Log File Size /nohtml /noreadreceipt /recv /send /single /useimportcontainer /work 11.1 /addressrule Establishes the format of user addresses when sending a busy search request to the Exchange system.

  • Page 109: Badmsg

    Syntax: /allowdom-domain /allowdom-"list_of_domains" Examples: /allowdom-domain1 /allowdom-"domain1, domain2, domain3" See also /blockdom. IMPORTANT: Do not use the /allowdom and /blockdom switches together. If both are specified, only the /allowdom switch takes effect. 11.3 /badmsg Indicates what the gateway should do with bad message files (undeliverable or damaged). See Section 9.5, “Notifying the Exchange Gateway Administrator about Bad Messages,”...

  • Page 110: Corr

    See also /allowdom. IMPORTANT: Do not use the /allowdom and /blockdom switches together. If both are specified, only the /allowdom switch takes effect. 11.5 /corr Specifies the path where the correlation database (gwcorr.db) used for message status tracking is to be redirected. By default, the correlation database is located in the directory.

  • Page 111: Help

    Specifies the password for the Exchange Gateway to prompt for before allowing gateway status ® information to be displayed in your Web browser. Do not use an existing Novell eDirectory password because the information passes over the non-secure connection between your Web browser and the Exchange Gateway.

  • Page 112: Httprefresh

    Example: httpport-7175 See also /httpuser, /httppassword, and /httprefresh. 11.13 /httprefresh Specifies the rate at which the Exchange Gateway refreshes the status information in your Web browser. The default is 60 seconds. See Section 9.2, “Using the Exchange Gateway Web Console,” on page Syntax: /httprefresh-seconds...

  • Page 113: Log

    Section 8.8, “Binding the Exchange Gateway to a Specific IP Address,” on page Syntax: /ip-network_address Example: /ip-172.16.5.18 /ip-exchsvr.provo.novell.com 11.17 /log Redirects the log files to the specified directory. By default, the log files are created in the domain\wpgate\exchange\000.prc directory. See Section 9.3, “Using Exchange Gateway Log Files,”...

  • Page 114: Logmax

    Example: /loglevel-verbose See also /log, /logdays, and /logmax. 11.20 /logmax Overrides the maximum log file disk space specified in ConsoleOne. If the maximum disk space limit is reached, the oldest log file is deleted to make room for a new one. Specify the number of kilobytes you want to use.

  • Page 115: Send

    11.24 /rt Specifies the number of receiver threads that the Exchange Gateway should start. The default it 4. There is no limit to the number of threads you can start, but nothing is gained by starting threads that are always idle. See Section 10.2, “Adjusting the Number of Sender and Receiver Threads,”...

  • Page 116: Useimportcontainer

    11.28 /useimportcontainer Causes the Exchange Gateway to synchronize GroupWise users into the import container specified in the object properties of the Exchange Gateway’s connector object. For more information, see Section 5.1, “Configuring Exchange 5.5,” on page 31 Section 5.2.1, “Performing Basic Configuration for Exchange 2000/2003,”...

  • Page 117: A Error And Informational Messages

    Additional sources of troubleshooting assistance include: ® Novell Support Knowledgebase (http://www.novell.com/support/supportcentral) ® GroupWise Product Support Forums (http://support.novell.com/forums/2gw.html) GroupWise Support Community (http://support.novell.com/products/groupwise) GroupWise Cool Solutions (http://www.novell.com/coolsolutions/gwmag/index.html) A.1 Error Messages “Access to a recipient in the message has been denied while processing inbound message” on page 119 “Configuration database not found”...
  • Page 118 “Ignoring recipient (No FirstName/LastName) (Bad GroupWise proxy)” on page 122 “MAPI initialization failed while initializing the gateway” on page 123 “Memory allocation failed while performing an inbound directory operation” on page 123 “Memory allocation failed while performing an outbound directory operation” on page 123 “Message server directories do not exist”...

  • Page 119: Access To A Recipient In The Message Has Been Denied While Processing Inbound Message

    “Unable to open the configuration file from the MAPI session” on page 131 “Unable to open the event log while initializing the gateway” on page 131 “Unable to send Non-Delivery Report while processing inbound message” on page 131 “Unable to set Microsoft Exchange message property while processing outbound message” on page 131 “Undeliverable message while processing inbound message”...

  • Page 120: Conversion Initialization Error While Processing Outbound Message

    Explanation: The gateway is unable to find the configuration parameters for gwin.dll under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\MAPI Conversions. Action: Verify that this registry entry exists. If not, reinstall the gateway after uninstalling the previous instance of the gateway. See Section 7.4, “Uninstalling the Exchange Gateway,”...

  • Page 121: Error Converting Addresses Between Microsoft Exchange And Groupwise Formats While Processing Inbound Or Outbound Message

    Error converting addresses between Microsoft Exchange and GroupWise formats while processing inbound or outbound message Source: GroupWise Exchange Gateway. Explanation: The gateway is unable to locate the Exchange address table to map addresses between Exchange and GroupWise formats. Action: Verify that the GWISE address type is installed. See Chapter 5, “Configuring the Exchange Side of the Exchange Gateway,”...

  • Page 122: Foreign User Information Not Available While Performing An Inbound Directory Operation

    Foreign user information not available while performing an inbound directory operation Source: GroupWise Exchange Gateway. Explanation: The user information is not available for the object being processed. Possible Cause: The object does not have a GroupWise-type address or the address is invalid. Action: Install the addressing components on the server.

  • Page 123: Mapi Initialization Failed While Initializing The Gateway

    Action: View the application event log (Start > Programs > Administrative Tools > Event Viewer) for reasons as to why the address was not created. Reasons could include invalid characters, absence of vital components such as the mailbox name, and so forth. Explanation: A GroupWise-type address for the recipient object exists but the address has a domain name that is the same as that of the GroupWise primary domain name.

  • Page 124: No Active Recipients While Processing Inbound Message

    Action: Start the MTA for the domain that the gateway belongs to. See the appropriate section of the GroupWise 7 Installation Guide for the platform of your MTA: “Starting the NetWare GroupWise Agents” “Starting the Windows GroupWise Agents” ® Action: Check the GroupWise configuration in ConsoleOne to ensure that the gateway object exists and is correctly configured.

  • Page 125: Unable To Commit Correlation Record While Processing Inbound Message

    Possible Cause: There might not be enough disk space to perform the operation. Action: Verify that there is enough free disk space to update the correlation database with new records. Action: Make sure that the gateway server meets the disk space requirements listed in Chapter 2, “Exchange Gateway System Requirements,”...

  • Page 126: Unable To Convert Attachment While Processing Inbound Message

    Unable to convert attachment while processing inbound message Source: GroupWise Exchange Gateway. Explanation: The gateway failed to convert an attachment. Possible Cause: The attachment might be damaged. Action: Resend the message and attachment. Possible Cause: There might not be enough disk space to perform the operation. Action: Verify that there is enough free disk space to convert the attachment.

  • Page 127: Unable To Create Correlation Record While Processing Inbound Message

    Unable to create correlation record while processing inbound message Source: GroupWise Exchange Gateway. Explanation: The gateway cannot write to the correlation database (gwcorr.db). Possible Cause: There might not be enough disk space to perform the operation. Action: Verify that there is enough free disk space to update the correlation database. Action: Make sure that the gateway server meets the disk space requirements listed in Chapter 2, “Exchange Gateway System Requirements,”...

  • Page 128: Unable To Find Inbound Dll While Initializing The Gateway

    Unable to find inbound DLL while initializing the gateway Source: GroupWise Exchange Gateway. Explanation: The gateway requires gwin.dll but is unable to find it. Action: Add the directory to the path variable on the domain\wpgate\exchange server where the Gateway runs. At the gateway server: 1 Right-click My Computer, then click Properties.

  • Page 129: Unable To Generate Status Message While Processing Inbound Message

    Action: Stop some applications or move them to a different server. Possible Cause: The gateway server might not meet the system memory requirements listed in Chapter 2, “Exchange Gateway System Requirements,” on page Action: Install additional memory. Unable to generate status message while processing inbound message Source: GroupWise Exchange Gateway.

  • Page 130: Unable To Get Configuration Information From The Mapi Session While Initializing The Gateway

    Unable to get configuration information from the MAPI Session while initializing the gateway Source: GroupWise Exchange Gateway. Explanation: The gateway is unable to find the gateway’s Message Store in Microsoft Exchange during initialization. Possible Cause: The Exchange server services might not be running. Action: Verify that all Exchange server services are running.

  • Page 131: Unable To Obtain Directory Handle While Initializing Directory Operations

    Possible Cause: The gateway server might not meet the system memory requirements listed in Chapter 2, “Exchange Gateway System Requirements,” on page Action: Install additional memory. Unable to obtain directory handle while initializing directory operations Source: GroupWise Exchange Gateway. Explanation: The gateway was unable to obtain a DAPI session. Action: Check the application event log (Start >...

  • Page 132: Informational Messages

    Action: Verify that the Exchange server services are running. See Chapter 5, “Configuring the Exchange Side of the Exchange Gateway,” on page Possible Cause: Insufficient memory to perform the operation. Possible Cause: The gateway server might have too many applications running. Action: Stop some applications or move them to a different server.
  • Page 133 Processing <first name last name> Source: GroupWise Exchange Gateway. Explanation: The first name and last name of the object currently being processed during inbound directory exchange. Processed XXX Exchange recipients Source: GroupWise Exchange Gateway. Explanation: Status message that is displayed for every 50 Exchange recipients processed when the logging is set to Verbose mode.
  • Page 134 Explanation: The total number of records or objects obtained and processed during the current directory exchange operation. Some GroupWise records have not been written to the Exchange directory Source: GroupWise Exchange Gateway. Explanation: During the outbound directory operation, errors might have occurred which prevented all records obtained from being exchanged.

  • Page 135: B Exchange Gateway Directory Structure

    Exchange Gateway Directory Structure The following directory structure diagrams help you understand the Exchange Gateway: Section B.1, “Exchange Server Directory Structure,” on page 135 Section B.2, “Exchange Gateway Directory Structure under the Domain,” on page 136 B.1 Exchange Server Directory Structure When you run the Exchange Gateway, it adds a file to the Exchange installation directory.

  • Page 136: Exchange Gateway Directory Structure Under The Domain

    B.2 Exchange Gateway Directory Structure under the Domain The Exchange Gateway is installed in a subdirectory of the domain it belongs to. Exchange Gateway root directory domain\wpgate\exchange Directory for message processing 000.prc Not used in the current version of the Exchange Gateway Working directory for processing messages gwwork Exchange Gateway log files...

  • Page 137: Domain\Wpgate\Exchange Directory

    Supporting Windows DLL programs *.dll B.2.1 domain\wpgate\exchange directory The Exchange Gateway root directory is the default location for all Exchange Gateway files. During installation, you choose the domain where you want to install the Exchange Gateway and you choose the name of the root directory. The default directory name is exchange. To improve performance if you installed the Exchange Gateway on a Windows server remote from the domain directory (for example, if the domain directory is located on a NetWare®...
  • Page 138 gwdx file file indicates that directory exchange has taken place. If you delete the gwdx file and gwdx restart the gateway, the gateway performs directory exchange immediately and then recreates the file. uninstexchange directory directory contains the Exchange Gateway uninstallation program and uninstexchange supporting files.
  • Page 139 Section 5.2.2, “Setting Up Bidirectional Busy Search for Exchange 2000/2003,” on page readmeen.txt file file lists sources of documentation for the GroupWise 7 Gateway for readmeen.txt Microsoft Exchange on the GroupWise Gateways Documentation Web site (http://www.novell.com/ documentation/gwgateways). Exchange Gateway Directory Structure 139...
  • Page 140 GroupWise 7 Gateway for readmeen.txt Microsoft Exchange on the GroupWise Gateways Documentation Web site (http://www.novell.com/ documentation/gwgateways). exgate.exe file file is the Exchange Gateway executable file. You run this program to start the exgate.exe...
  • Page 141 novell_ex.hs file file is the JavaHelp helpset file for the Exchange Gateway help available in novell_ex.hs ® ConsoleOne map.jhm file file is the JavaHelp map file that maps contexts to Exchange Gateway help topics in map.jhm ConsoleOne. *.htm files files are the Exchange Gateway help topics that are available in ConsoleOne. *.htm gwstrs.fil file file is the strings resource file used by the Exchange Gateway server console on...
  • Page 142 142 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide...

  • Page 143: C Documentation Updates

    Documentation Updates ® This section lists updates to the GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide that have been made since the initial release of the gateway. The information helps you to keep current on documentation updates and, in some cases, software updates (such as a Support Pack release).
  • Page 144 Location Change Section 9.1.5, “Menu Added Synchronize Directories under F8 on the gateway server Summary,” on page 91 console menu. “/importsubcontainers” on Added a new startup switch. page 112 Section B.2, “Exchange Added the api_in and api_out subdirectories that are used for Gateway Directory Structure bidirectional Busy Search.

Table of Contents