See the following sections for some important administrative procedures that you might need to perform, depending on the GroupWise version that you are updating from:
GroupWise 8 included functionality that required you to extend the schema of any Novell eDirectory trees where you have GroupWise objects. The GroupWise 2012 Installation program does not extend the eDirectory schema for you. Use GroupWise 2012 ConsoleOne to extend the eDirectory schema before installing other GroupWise 2012 components.
Install the GroupWise 2012 snap-ins to ConsoleOne.
In ConsoleOne, select an eDirectory tree that contains GroupWise objects.
If the schema is not current, this utility extends the schema for you.
Repeat this procedure for each eDirectory tree that contains GroupWise objects.
Before GroupWise 8 Support Pack 1, trusted application keys needed to be created by the third-party program developer, using the GroupWise Trusted Application API at the Novell Developer Kit Web site.
Starting with GroupWise 8 Support Pack 1, you can create a trusted application and its associated key in ConsoleOne for use with both Linux and Windows trusted applications, as described in GroupWise 2012 Administration Guide.
Before GroupWise 7 SP1, GWIA configuration information was stored both in eDirectory, as properties of the GWIA object, and in the GWIA configuration file (gwia.cfg). Starting in GroupWise 7 SP1, all primary configuration settings have been consolidated into the properties of the GWIA object. Secondary settings are still available only through the startup file.
When you update a GroupWise 7 GWIA to a later version of GroupWise and access the GWIA object in ConsoleOne, all primary configuration settings are moved from the startup file into eDirectory. ConsoleOne no longer writes configuration settings to the startup file. Switches in the startup file can be used to override the settings in ConsoleOne.