Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - User Guide

About the Coexistence Manager for GroupWise documentation suite Introduction Coexistence Manager for GroupWise Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Running and stopping the Directory Connector service
Coexistence Manager for GroupWise Mail Connector Coexistence Manager for GroupWise Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C:Configuring Coexistence Manager for GroupWise logging

G-to-E: Exchange Target Information

Enter the information needed to identify and access the Exchange target server:

Domain or Server (the field name depends on the radio-button selection for Domain Controller vs. Domain vs. Forest): The name of the target server (in a form sufficiently qualified that it can be identified from the Coexistence Manager for GroupWise Directory Connector server) or Active Directory domain. For example: Mustang or mustang.engineering. A set of three radio buttons to the right of this field lets you further characterize the source:
Username: The username by whose authority the Directory Connector will access the target server. This must be a domain administrator account with sufficient rights/permissions to access the source server.
Password: The password associated with the above Username.
Port: The port number that the target (AD) server will use to communicate with Coexistence Manager for GroupWise’s Directory Connector. Quest recommends you leave this value set to its default, unless the host AD system is not using the default ports.

When these fields are filled with the correct information, click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).

G-to-E: Target Location Information

Enter this information to characterize data destination(s) in the target server:

Target Domain: The name of the Active Directory server. Coexistence Manager for GroupWise prefills this field with the same value you entered for it on the Exchange Target Information screen.
Target OU: In the adjacent container tree, select (click) the container in the target directory that you want to contain the Coexistence Manager for GroupWise target container (cn=cmg)—into which this connector will copy objects from the Novell source. Coexistence Manager for GroupWise names its AD target container cn=cmg as a subcontainer within the OU you select here. (Coexistence Manager for GroupWise will create cn=cmg if it doesn't already exist in this Target OU.)
NOTE: Remember: Coexistence Manager for GroupWise’s DC connectors can be configured to facilitate destructive directory updates—that is, after a connector’s first run, a subsequent run can be told to remove an object from the target if the corresponding object no longer exists in the source. For this reason, no two G-to-E connectors can share the same destination container. (If two such connectors were directed to the same container, each connector run would remove the contacts for users who were copied in the last run of the other connector, but who are not part of the source population for the current connector.) For two or more G-to-E connectors, you can name their Target OUs ou=users1, ou=users2, ou=users3, etc.
Target Search Base Dn: An OU subtree root that defines the scope of the connector’s searches for target objects. Use the Browse button (at right) to open a pop-up list of available target base DNs, with checkboxes, so you can select one or more. If you want to include users in the sync process, to check for existing objects in multiple target domains, each target base DN must be explicitly selected to be included in the comparisons. Selecting a higher-level OU does not include all of its lower-level OUs. You can improve search performance by excluding OUs that do not contain any objects relevant to these searches. The OU selected here must contain the Target OU specified in the preceding field.
[  ] Enable Internal Routing Domain (only if using subdomains for mail routing): Mark this checkbox and enter the target’s subdomain name (for example, sub1.xyzcorp.com) into the associated text box. This is the subdomain portion of the addresses (after the @ symbol) that will route mail from the target environment back to the source.
Legacy Exchange Dn: Base Dn for the Legacy Exchange Dn (_________/CN=Recipients/CN=[UserValue]). Use the Load from AD button (see below) or type the value into the text box.
Address Books Container Dn: Base Dn for the Address Books Container Dn. Use the Load from AD button (see below) or type the value into the text box.
Global Address List Dn: Base Dn for the Global Address List Dn. Use the Load from AD button (see below) or type the value into the box.
Load from AD button (to the right of the three Dn text boxes listed above): Tells Coexistence Manager for GroupWise to search Active Directory for these values, show them to you (in a pop-up dialog box), and then let you choose which value(s) you want to insert into the Target Location Information screen. To use this feature: Click Load from AD, review the values as Coexistence Manager for GroupWise finds them in AD, mark the checkbox of each value you want to insert into Target Location Information, and then click OK.

When these fields are filled with the correct information, click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).

G-to-E: Connector Order Management

This screen provides a table of all previously defined connectors, with a checkbox corresponding to each connector in the list. Mark the checkbox for each connector that must complete its run before the current connector will be permitted to start.

Then click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).

G-to-E: Connector Scheduling

This screen lets you schedule this connector’s runs in much the same way that you define a recurring meeting in GroupWise or Exchange. You can define more than one recurrence pattern for any single connector; if you do, the scheduled runs will be the sum of all such recurrence patterns defined here. That is, if more than one recurrence pattern appears in the table (bottom half of this screen), the connector will run for all of the scheduled patterns that appear in the table.

2
Click the Add button.
Simply Delete it from the table, and then Add a new recurrence pattern to replace it.

Note that it is possible to define a connector without scheduling it for automatic recurring runs. Some admins, for example, like to have one or more unscheduled connectors defined that can be run as-needed, by the Run Connector Now feature in the Management Console.

When the table appears as you want it, click Next to complete the Wizard and create (or edit) the connector, or click Back to revisit an earlier screen.

Remember: For a GroupWise 7-to-Exchange connector, you must also define an object filter to exclude the GroupWise Post Office to which you synched the Exchange user. This is accomplished in the Connector Advanced Settings tab: object filtering features (described later in this chapter).

Be sure to see Other options you can set per connector, to see if any of the feature options described there may be useful or necessary to your coexistence scenario.

Related Documents