Most often, you will notice a synchronization problem when a user has trouble sending a message. Symptoms include:
The sender receives a “user is undeliverable” message.
A new user or resource created in ConsoleOne does not appear in the Address Book in some or all post offices.
User or resource information is incorrect in the Address Book but correct in ConsoleOne.
A user or resource is listed in the Address Book as belonging to one post office but actually belongs to another.
To synchronize individual User and/or Resource objects:
In ConsoleOne, connect to the domain that owns the users and/or resources.
Connect to the primary domain.
If you need assistance with this task in a GroupWise system that includes domains on Linux servers, see Section 4.1, Select Domain.
Browse to and right-click one or more User or Resource objects to synchronize, then click.
Make sure the correct information appears on the object’s Identification page, then click.
Select each User or Resource object, then click.
When you are asked whether to proceed, click.
Current, correct information is then replicated throughout your GroupWise system.
If many User or Resource objects are being synchronized, you can check progress by viewing pending operations. See Section 4.5, Pending Operations.
After synchronization is complete, you can verify that it was successful by checking the synchronized objects in Address Books and several post offices in your GroupWise system.
If there are indications that a large number of User or Resource objects need to be synchronized, rebuilding the post office database (wphost.db) can be preferable to synchronizing individual objects. However, this process requires exclusive access to the post office database. See Section 26.3, Rebuilding Domain or Post Office Databases.
Occasionally, GroupWise user information can get out of sync with Novell eDirectory user information. This requires a different type of synchronization process. See Section 42.4.1, Using eDirectory User Synchronization.