Functionality enhancements in GroupWise 2012 require the GroupWise domain and post office databases to be updated with new records and fields, similar to the schema extensions that are sometimes required for eDirectory. Each domain is updated when you install and start the GroupWise 2012 MTA. Each post office is updated when you install an start the GroupWise 2012 POA.
The following diagram illustrates the required update sequence.
Update the primary domain first, so that correct replication of GroupWise 2012 information can take place as you update secondary domains and post offices.
Update the post offices in the primary domain.
Update secondary domains.
Update the post offices in the updated secondary domains.
The first time you run the GroupWise 2012 MTA against a domain, the MTA rebuilds the domain database (wpdomain.db), so that the database includes the records required for new GroupWise 2012 information. The MTA uses a new domain dictionary file (gwdom.dc) to rebuild the database for use with GroupWise 2012.
Likewise, the first time you run the GroupWise 2012 POA against the post office, the POA rebuilds the post office database (wphost.db), so that the database includes the new records required for GroupWise 2012 information. The POA uses a new post office dictionary file (gwpo.dc), which it requests from the MTA in the updated owning domain, to rebuild the database for use with GroupWise 2012. A user cannot run GroupWise 2012 Windows client until his or her post office has been updated.