GroupWise System Administration ® As a GroupWise system administrator, it is your responsibility to keep your GroupWise system running smoothly for your GroupWise users. This GroupWise 7 Administration Guide provides a wealth of information to help you accomplish this task. This System section provides an overview of ®...
IMPORTANT: Because the GroupWise snap-ins to ConsoleOne are required in order to work with GroupWise objects, you cannot use other network management tools, such as Novell iManager, to administer your GroupWise system. Also, you should not use older network management tools, such ®...
When you install ConsoleOne, a ConsoleOne icon is automatically created on your Windows desktop for starting ConsoleOne. Before you start ConsoleOne, turn off file caching in the Novell Client to protect database integrity. 1 Right-click the red N in the notification area, then click Novell Client Properties.
2.3 ConsoleOne in a Multiple-Platform Environment If your GroupWise system includes multiple platforms, you can administer Linux domains from Windows ConsoleOne or to administer NetWare or Windows domains from Linux ConsoleOne. The cross-platform connections required for cross-platform GroupWise administration are described in the following sections of “Migration”...
® ® When administering GroupWise in ConsoleOne , you can use the standard Novell eDirectory View or you can use the GroupWise View. The following sections discuss the GroupWise View and how to use it: Section 3.1, “eDirectory View vs. GroupWise View,” on page 43 Section 3.2, “GroupWise Object Icons,”...
GroupWise View Figure 3-2 In the left pane, all Domain objects are displayed under the GroupWise system, and all Post Office objects are subordinate to the domains where they reside. You can select the GroupWise system, a domain, or a post office in the left pane and then use the drop-down list of GroupWise objects on the toolbar to display associated objects (Users, Resources, Message Transfer Agents, and so on) in the right pane.
Page 11
Icon GroupWise Object Additional Information External Domain Represents a domain from another GroupWise system. Non-GroupWise Domain Represents all or part of a non-GroupWise system. Post Office Represents a collection of user accounts (mailboxes). For additional information, see Part III, “Post Offices,” on page 153.
Represents a method of linking to another e-mail system or transport. For additional information, see the GroupWise gateway guides (http://www.novell.com/documentation/ gwgateways). 3.3 Customizing the GroupWise View You can change the column display, order, and width to customize the GroupWise View.
The Users view allows you to sort by ID, user name, first name, or last name. Each of these is treated as a separate Users view for which you can determine the column display and order. The views for different objects offer different sort options. 3 Click View >...
3.4 Searching in the GroupWise View You can search for a specific entry in a view. The search is performed on the first column. For example, if the Resources view is displayed, you can search for a specific resource based on its object ID.
Page 15
GroupWise Internet Agent and want to simplify addressing for your users by adding the Internet as a non-GroupWise domain, you must perform the task in the GroupWise View. GroupWise View...
By default, ConsoleOne must be connected to a GroupWise domain in order for you to administer your GroupWise system. Being connected to a GroupWise domain ensures that information is ® replicated not only in Novell eDirectory but also in the GroupWise domain and post office databases.
Page 18
ConsoleOne Window Showing the Domain You Are Connected To Figure 4-1 Some administrative tasks require you to be connected to a specific domain but others do not. In general, operations that create new GroupWise container objects or delete GroupWise container objects require you to be connected to the domain where the object resides.
Domain Connection Options Table 4-1 ConsoleOne Domain Platform Connection Options Platform Windows NetWare server Mapped drive ConsoleOne Linux server Samba mount where the path to the domain on the Linux server is prefixed by the Linux server hostname from the point of view of ConsoleOne Windows server Local drive...
1 In ConsoleOne, click Tools > GroupWise System Operations > System Preferences. The GroupWise System Preferences dialog box contains the following tabs: Admin Preferences: Controls how rights are assigned and what network ID format is used when creating new GroupWise users. By default, rights are assigned automatically and the fully distinguished name format is used.
If you are not using the driver, you can disable the option to avoid receiving unnecessary messages. For more information, see “GroupWise DirXML Driver for Novell Identity Manager” in the GroupWise 7 Interoperability Guide.
Default Routing Domain: If a domain’s MTA cannot resolve a message’s address, the message is routed to this default domain’s MTA. The default domain’s MTA can then be configured to handle the undeliverable messages. This might involve routing the message to another GroupWise domain or to an Internet address (by performing a DNS lookup).
4.2.4 Nickname Settings 1 Click the Nickname Settings tab to modify any of the following options: Auto-Create on User Move: A nickname is an alternative address that can be associated with a user. Whenever you move a user, GroupWise can automatically create a nickname with the user’s old name and old post office.
Restrict System Operations to Primary Domain: Enable this option to allow an administrator to perform system operations (Tools > GroupWise System Operations) only when he or she is connected to the primary domain. All operations except Select Domain, Pending Operations, and Restore Area Management are unavailable when connected to a secondary domain.
ConsoleOne installation that is not running the GroupWise Administrator snap-in, the user information is not changed in the GroupWise databases. This is also true if you add or modify user information using Novell iManager or older administration tools such as NetWare Administrator.
To ensure that the user information stored in the GroupWise databases is always synchronized with the user information in eDirectory, you can set up eDirectory user synchronization. For detailed information see Section 41.4.1, “Using eDirectory User Synchronization,” on page 638. 4.4 Admin-Defined Fields eDirectory includes user information that is not associated to GroupWise user fields.
4.6 Addressing Rules You can use the Addressing Rules feature to configure GroupWise so that users can enter shortened forms of e-mail addresses. For more information, see Section 6.8, “Facilitating Addressing through GroupWise Gateways,” on page 100. 4.7 Time Zones When you create a domain or post office, you select the time zone in which it is located.
3 Modify any of the following fields: Time Zone Name: Provide a name for the time zone definition (for example, some of the major cities in the time zone). We suggest you include a reference (+ or -) to GMT, for example (GMT-07:00).
3 Fill in the following fields: Time Zone Name: Provide a name for the time zone definition (for example, some of the major cities in the time zone). We suggest you include a reference (+ or -) to GMT, for example (GMT-07:00).
2 Select the time zone to remove from the list, click Delete, then click Yes to confirm the deletion. 4.8 External System Synchronization The External System Synchronization feature lets you automatically synchronize information between your system and an external GroupWise system connected to your system. For information about connecting GroupWise systems and keeping information synchronized between them, see “Connecting to GroupWise 5.x, 6.x, and 7.x Systems”...
4.9.1 Creating a Software Distribution Directory 1 Make sure the directory you want to use as the software distribution directory exists. All distribution subdirectories (admin, agents, client, and so forth) will be created under this directory. 2 Click Tools > GroupWise System Operations > Software Directory Management to display the Software Distribution Directory Management dialog box.
Page 32
Description: Specify an optional description for the software distribution directory. You might want to use this description to indicate the software version or to give other pertinent information. Location: Specify the location where you want to create the software distribution directory. If you specify a path to a directory that does not exist, ConsoleOne creates the directory for you.
4.9.2 Updating a Software Distribution Directory 1 Click Tools > GroupWise System Operations > Software Directory Management to display the Software Distribution Directory Management dialog box. The Software Distribution Directories list includes all software distribution directories defined in your GroupWise system. 2 Select the software distribution directory to update, then click Update to display the Update Software Distribution Directory dialog box.
update check of the client software version, but the software distribution directory’s files are not updated. To determine the current client software version in ConsoleOne, click Tools > GroupWise Diagnostics > Record Enumerations to display a list of records types in the domain database. From the drop-down list, select Areas by ID, select a software distribution directory, then click Info to list detailed information about the software distribution directory.
For information about creating and installing trusted applications, search for GroupWise Trusted Application API at the Novell Developer Kit Web site (http://developer.novell.com/wiki/index.php/ Category:Novell_Developer_Kit). For security guidelines for managing trusted applications, see Section 81.6, “Protecting Trusted Applications,” on page 1165 Section 4.12.1, “Editing a Trusted Application,”...
Name: This field displays the trusted application’s name. You cannot change the name. Description: Specify a description for the trusted application. Requires SSL: Select this option to require a secure (SSL) connection between the trusted application and POAs and Internet Agents. Provides Message Retention Service: Select this option if the purpose of the trusted application is to retain GroupWise user messages by copying them from GroupWise mailboxes (user databases) into another storage medium.
For information about defining LDAP servers, see “Providing LDAP Server Configuration Information” on page 501. For information about using LDAP for user authentication to GroupWise mailboxes, see “Providing LDAP Authentication for GroupWise Users” on page 501. 4.14 Global Signatures You can build a list of globally available signatures that can be automatically appended to messages sent by GroupWise client users.
GroupWise Utilities ® ® The GroupWise utilities in ConsoleOne are used to perform various maintenance and configuration tasks for your GroupWise system. The following sections provide information about the system utilities included on the Tools menu (Tools > GroupWise System Utilities): Section 5.1, “Mailbox/Library Maintenance,”...
5.2 System Maintenance You can use the System Maintenance utility to check the integrity of and repair domain and post office databases. For detailed information and instructions, see Chapter 26, “Maintaining Domain and Post Office Databases,” on page 377. 5.3 Backup/Restore Mailbox You can use the Backup/Restore Mailbox utility to restore an individual user’s Mailbox items from a backup copy of the post office database.
5.7 Email Address Lookup You can use the Email Address Lookup utility to search for the GroupWise object (User, Resource, Distribution List) that an e-mail address is associated with. You can then view the object’s information. For more information, see Section 14.7.1, “Ensuring Unique E-Mail Addresses,”...
The GroupWise Import utility reads an ASCII-delimited text file created by the GroupWise Export ® utility or by a third-party export, and creates Novell eDirectory and GroupWise objects with attributes from the file. The Import utility supports most eDirectory classes (including extensions) and GroupWise classes.
3 Click Yes to extend the schema for GroupWise so that you can create GroupWise objects in the selected tree. Click No if you decide you do not want to be able to create GroupWise objects in the selected tree. If the schema of the tree has already been extended for GroupWise objects, a message notifies you of this and you can immediately create new GroupWise objects in the selected tree.
5.16.1 Graft GroupWise Objects You can use the Graft GroupWise Objects utility to create GroupWise objects in the eDirectory tree from the information in your GroupWise domain database. The utility creates Domain, Post Office, and Gateway objects as well as User, Resource, and Distribution List objects. When grafting GroupWise user information from the GroupWise database into eDirectory, you can match the GroupWise user information to an existing User object, or you can create a new eDirectory External Entity object and convert it into an eDirectory User object, as described in...
Page 45
You can use the Invalid Associations utility to correct invalid associations between information in the GroupWise domain database and eDirectory. To check for invalid associations: 1 In the eDirectory View in ConsoleOne, select the container whose objects you want to check for invalid associations (for example, an Organization, Organizational Unit, Domain, or Post Office).
5.16.3 Associate Objects You can use the Associate Objects utility to associate GroupWise information with an eDirectory object. For example, if you delete a user’s eDirectory account but not his or her GroupWise account, the user’s GroupWise information is retained as a GroupWise External User object in the GroupWise database and can be viewed in the GroupWise View.
In the eDirectory View, select the eDirectory External Entity object you want. 2 Click Tools > GroupWise Utilities > GW / eDirectory Associations > Associate Objects. 3 If you selected a GroupWise External Entity object in Step 1, select the eDirectory External Entity object you want to associate with it.
5.16.6 Convert User to External Entity You can use the Convert User to External Entity utility to convert a User object to a GroupWise External Entity object. 1 In ConsoleOne, select the User object that you want to convert to an GroupWise External Entity object.
For information about using TSAFSGW, see Section 34.2.2, “GroupWise Target Service Agent for File Systems (TSAFSGW) for NetWare 6.x/OES and Linux,” on page 439. 5.17.4 GroupWise Backup Time Stamp Utility (GWTMSTMP) The GroupWise Backup Time Stamp utility (GWTMSTMP) can be used to place a time stamp on a GroupWise user database to indicate the last time the database was backed up.
GroupWise Address Book ® The GroupWise Address Book plays a central role in a GroupWise user’s experience with addressing messages. The default configuration of the GroupWise Address Book is often sufficient for a typical GroupWise system, but some customization options are available to enable the GroupWise Address Book to meet user needs.
The Address Book Fields list shows all fields that are available for selection in the Address Book in the GroupWise client. The Available Fields list shows additional predefined GroupWise user fields that can be added ® to the Address Book. Novell eDirectory also includes user information that is not associated GroupWise 7 Administration Guide...
to GroupWise user fields. For example, a User object includes Postal Address fields named City, State, and Zip Code. By default, these fields are not included as GroupWise fields. However, you can use the Map Additional Fields button to map eDirectory user fields to GroupWise fields so that they can be displayed in the GroupWise Address Book.
In the Add Property dialog box, all capitalized property names sort ahead of all uncapitalized property names. 3 Select Show All Properties, scroll down to locate the property you want to add to the GroupWise Address Book, select the property (for example, Title), then click OK. 4 With the new property highlighted, select Inheritable, then click OK twice to save the new property settings.
6.1.4 Removing Fields from the Address Book If there are fields in the Address Book that are not used or that you don’t want displayed to users, you can remove them. On the Address Book page of the Domain object: 1 In the Address Book Fields list, select the field you want to remove, then click the right-arrow to move the field to the Available Fields list.
Page 56
Domain: The object is visible only in the Address Book of the post offices located in the object’s domain. Post Office: The object is visible only in the Address Book of the object’s post office. This is the default for distribution lists, groups, and organizational roles. None: The object is not visible in the Address Book of any post offices.
3 In the Available Fields list, select Distinguished Name, then click the left-arrow to move Distinguished Name into the Address Book Fields list. 4 Click OK to save your change. 5 After the Address Book is properly configured, use the Client Options feature to enable or disable Messenger presence on a domain, post office, or user level.
last time it connected. This means that Remote client users always have an up-to-date Address Book to work with. Because the Address Book updates are stored as records in the post office database (wphost.db), this feature causes the post office database to grow in size as time passes. Therefore, in ConsoleOne, you can specify the maximum number of days you want to store the incremental update records.
meaning that a user can use wild card addressing to send to all users on his or her post office only. You can change the default for individual users, post offices, or domains. When using wildcard addressing, the sender only sees whether the item was delivered to a domain, post office, or system (by viewing the item’s properties).
4 In the Wildcard Addressing list, select from the following options: Not Allowed: Select this option to disable wildcard addressing. Limited to Post Office (Default): Select this option to limit wildcard addressing to the user’s post office. The user can use wildcard addressing to send items to users in his or her post office only.
Wildcard Addressing Setting To send an item to... Type in the To field... All users in your post office Limited to Domain All users in your domain All users in another post office in your *.post_office domain All users in your post office Limited to System All users in your domain All users in another post office in your...
6.7.1 Creating a Non-GroupWise Domain to Represent the Internet ® 1 In ConsoleOne , right-click GroupWise System (in the left pane), then click New > Non- GroupWise Domain. 2 Fill in the fields: Domain Name: Specify a name that has not been used for another domain in your system (for example, Internet).
Page 63
2 If the Internet Agent domain is not the currently displayed domain, select it from the list of domains on the toolbar. The non-GroupWise domain should be displayed in the Direct column. In the graphic displayed under step 1, Internet is the non-GroupWise domain. 3 Double-click the non-GroupWise domain to display the Edit Domain Link dialog box.
When creating a post office to represent an Internet host, the post office name cannot be identical to the hostname because the period that separates the hostname components (for example, novell.com) is not a valid character for post office names. GroupWise reserves the period for its addressing syntax of user_ID.post_office.domain.
Page 65
To create a non-GroupWise post office: 1 In ConsoleOne, right-click the non-GroupWise domain that represents the Internet, then click New > External Post Office. 2 Fill in the following fields: Post Office Name: Specify a name to associate the post office with the Internet host. Do not use the fully-qualified hostname.
New > External User. 2 In the User Name field, specify the exact user portion of the user’s Internet address. If the address is jsmith@novell.com, the portion you would specify is jsmith. 3 Click OK to create the external user.
6.8.1 Creating an Addressing Rule 1 In ConsoleOne, click Tools > GroupWise System Operations > Addressing Rules. 2 Click New to display the New Addressing Rule dialog box. 3 Fill in the following fields: Description: Specify a short description for the rule. The description is what appears when the rule is listed in the Addressing Rules dialog box.
4 If desired, you can test the rule on an address. To do so, specify an address in the Test Address dialog box (the address does not have to be real) > click Test to see the results. 5 Click OK to add the rule to the list. The rule is automatically enabled, which means that it is available for use.
Page 69
3 Click the check box in front of an addressing rule to enable it. 4 When you are finished enabling rules, click OK to save your changes. GroupWise Address Book 103...
Multilingual GroupWise Systems ® GroupWise is a multilingual e-mail product that meets the needs of users around the world. The following sections provide guidance if your GroupWise system includes users that speak a variety of languages: Section 7.1, “Client Languages,” on page 105 Section 7.2, “Administration Languages,”...
The online help available in the GroupWise clients is provided in all languages into which the client software is translated. The GroupWise client user guides available from the GroupWise clients and on the GroupWise Documentation Web site are translated only into the administration languages.
7.4 Multi-Language Workstations If GroupWise users receive messages in multiple languages, their workstations need to be configured to handle the character sets used by these languages. On Windows XP: 1 From the Control Panel, double-click Regional and Language Options, then click Languages. 2 If you receive messages in Arabic, Hebrew, or other complex languages, select Install Files for Complex Script and Right-to-Left Languages.
Need help?
Do you have a question about the GROUPWISE 7 - SYSTEM and is the answer not in the manual?
Questions and answers