If you set up a new GroupWise system by manually creating GroupWise users in the GroupWise Admin console, you can later associate those GroupWise users with users in an LDAP directory. The directory then becomes the primary location for user information. User synchronization updates the user information in GroupWise based on the information in the LDAP directory. It can also publish users’ email addresses to the LDAP directory.
In the GroupWise Admin console, configure your GroupWise system to communicate with the LDAP directory.
For instructions, see Section 6.1, Setting Up an LDAP Directory.
Click System > Directory Associations.
(Conditional) If you have multiple LDAP directories, select the one where you want to associated the GroupWise users.
(Conditional) If the context of the User objects is under the Base DN, browse to and select the LDAP context where User objects are located.
(Optional) Specify an LDAP filter and select additional options as needed.
Click Preview to list the users who will be associated with LDAP directory objects.
(Conditional) As needed, adjust the filter and options, then click Update Preview until you are satisfied with the list.
When you are satisfied with the list, click Associate.
The GroupWise users are associated with their LDAP directory counterparts.
The process of migrating from NetIQ eDirectory to Microsoft Active Directory is straightforward. Before you start the migration, ensure that both directories are stable.
The Active Directory object in your GroupWise system must be properly configured to support the migration process.
In the GroupWise Admin console, click System > LDAP Servers.
Click the name of the Active Directory object.
Verify that the Base DN field displays the location where you plan to create the Active Directory User objects for the GroupWise users. Update it if necessary.
Verify that the Sync Domain field displays the domain where the users’ post office and GroupWise mailboxes are located.
Verify that Enable Synchronization is selected.
On the Email Publishing tab, verify that Publish Email Addresses to This Directory is selected.
Click OK, then click Close.
Continue with Creating the Directory Associations.
Create a User object in Active Directory for each GroupWise user.
IMPORTANT:Ensure that, on each new Active Directory User object, the User logon name (pre-Windows 2000) field (the sAMAccountName property in Active Directory) exactly matches the GroupWise user name (the uniqueID property in eDirectory). Any user for whom these names do not match must be manually migrated.
In the GroupWise Admin console, click System > Directory Associations.
Select the LDAP directory that you verified in Preparing for the Migration.
(Conditional) If the context of the User objects is under the Base DN, browse to and select the LDAP context where User objects are located.
Select Override Existing Association.
By default, existing users retain their existing associations. The migration process requires that eDirectory associations be replaced with Active Directory associations.
(Optional) Specify an LDAP filter and select additional options as needed.
Click Preview to list the users who will be migrated from eDirectory to Active Directory.
(Conditional) As needed, adjust the filter and options, then click Update Preview until you are satisfied with the list.
HINT:Initially, migrate only a small number of users to ensure that the migration process is working as expected.
Click Associate.
Continue with Verifying the Directory Associations.
When the associations between GroupWise and Active Directory are properly set up, GroupWise data synchronizes reliably between the two systems.
In Active Directory, verify that the user’s GroupWise information has synchronized to Active Directory:
On the General tab of a GroupWise User object, verify that the Email Address field displays the user’s GroupWise email address.
To provide a test of user synchronization from Active Directory to GroupWise, modify the user’s phone number.
In the GroupWise Admin console, ensure that the MTA console is password protected so that you can control the MTA in your web browser:
Browse to and click the MTA that synchronizes GroupWise data with Active Directory.
Click the Agent Settings tab, then verify that the HTTP section shows that the MTA is configured with an HTTP user name and password.
(Conditional) If necessary, provide a user name and password.
Click Save, then click Close to return to the main Admin console window.
In the MTA console, perform user synchronization between GroupWise and Active Directory:
When prompted, provide the user name and password that are required for controlling the MTA in the MTA console.
On the Configuration tab, click Directory User Synchronization.
Select Perform GroupWise Directory Synchronization Now, then click Submit.
Click the Log Files tab, then view the most recent log file to look for lines similar to the follow example:
In the GroupWise Admin console, verify that the user’s information in Active Directory has synchronized to GroupWise:
Click Users, then click the name of the user whose phone number you modified in Active Directory in Step 1.b.
On the General tab, verify that the user’s phone number matches what is in Active Directory.
Change the user’s phone number back, then click Save.
Continue with Verifying Successful Authentication.
When the associations are correctly set up, GroupWise users can log in to their mailboxes by using LDAP authentication.
In the GroupWise Admin console, verify that the post office of the migrated users is configured for LDAP authentication:
Browse to and click the name of the post office.
On the Security tab, verify that LDAP Authentication is selected.
Start the GroupWise client for a user that has been migrated to Active Directory.
Verify that the user credentials provided by Active Directory result in a successful login into the GroupWise mailbox.
Continue with Verifying a Complete User Migration.
After you have used the Directory Associations tool to migrate all of your users from eDirectory to Active Directory, you can verify that, in fact, no more users remain in eDirectory.
In the GroupWise Admin console, click Users to list all of your GroupWise users.
Use the Search User Name field to check for users that might have been missed:
Use the following filter to search for users who are not currently associated with any LDAP directory:
directory = null
Use the following filter to search for users who are not associated with Active Directory:
directory != active_directory_name
(Conditional) If your searches revealed orphan users that no longer need GroupWise accounts, plan to disable their accounts at an appropriate time.
For instructions, see Section 53.10, Disabling and Enabling GroupWise Accounts.
(Conditional) If your searches revealed users whose Active Directory logon name did not match their GroupWise user name, you can associate them manually:
After searching for the unassociated users, click a user name.
Click More > Associate.
Select the LDAP directory where you want to associate the user.
Browse to and select the user in the LDAP directory.
Click OK.
When you are sure that you no longer need the User objects in eDirectory, you can delete them.
Using an SSL connection between GroupWise and Active Directory is strongly recommended. The process for establishing an SSL connection is beyond the scope of the GroupWise product documentation.
In the GroupWise Admin console, browse to and click the name of the User that you want to dissociate from the LDAP directory.
Click More > Dissociate.
Verify that the right user information is displayed, then click OK.
The user is still a GroupWise user, but the user is no longer associated with a User object in an LDAP directory.