August 15, 2005
Updated October 5, 2007, with upgrade instructions for Open Enterprise Server 2 and SUSE® Linux Enterprise Server 10.
Novell® GroupWise® 7 provides substantial improvements over GroupWise 6. x in six areas:
Windows Client Enhancements: The Windows(thrdmrk) client has a new look and feel that includes the Navigation Bar, Panels, Home Folder, color schemes, and new icons. In addition to the new look and feel, you can now create and view multiple calendars, create all day events, spell check as you type, perform Quick Filters, see the Messenger presence information for users, create HTML signatures, and control inline quotations.
Cross-Platform Client Enhancements: The Cross-Platform client has added many features including spell checking, rules, junk mail handling, cleanup tools for your mailbox, backup and restore, and the ability to set your default views, create all day events, and control inline quotations.
WebAccess Client Enhancements: The WebAccess client has a new look and feel that brings it closer to the look and feel of the Windows client. Some of the new features include the ability to drag and drop items, right-click items to display menus, easier tabbed navigation, and name completion from your Frequent Contacts address book.
Administration Enhancements: GroupWise administrators have additional control over users' working environments, including granting rights to users to edit distribution lists, appending global signatures to users' messages, and controlling the appearance of the GroupWise Windows client interface.
Agent Enhancements: The POA now supports SOAP, so that SOAP clients such as Evolution™ can connect to GroupWise. The Internet Agent can fail over to an alternate Internet Agent to provide redundancy for outbound Internet mail. The GroupWise Linux(thrdmrk) agents can now run as a non-root user and the new High Availability service automatically restarts the Linux agents if they go down unexpectedly. The Linux and Windows agents support IPV6.
GroupWise Connector for Outlook: The GroupWise Connector for Outlook(thrdmrk) allows you to use Microsoft(thrdmrk) Outlook to connect to your GroupWise System. The GroupWise Connector for Outlook includes support for e-mail, meeting requests and appointments, recurring appointments, scheduling, tasks, contacts, shared folders, delegates, and proxy.
For a complete list of new features in GroupWise 7, see What's New in Update in the GroupWise 7 Installation Guide .
To install GroupWise 7 on NetWare® or Windows:
Run setup.exe at the root of the GroupWise 7 Administrator (NetWare/Windows) CD.
The GroupWise Installation program lets you view the Readme, the Quick Start, and the Installation Guide before you start installing GroupWise.
Click Create or Update a GroupWise System.
Follow the on-screen instructions.
For detailed system requirements, installation and update instructions, and a complete list of new features, see the GroupWise 7 Installation Guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 7 Administrator (NetWare/Windows) CD or on the GroupWise 7 Documentation Web site.
For ease of installation, make sure that ConsoleOne® is installed on the Linux server where you want to create your GroupWise system.
ConsoleOne is located in /usr/ConsoleOne/bin.
If necessary, you can download ConsoleOne from the Novell Downloads Web site.
At the server where you want to create your GroupWise system, open a new terminal window, then become root by entering sux and the root password.
When creating your GroupWise system, you must run the GroupWise Installation program in an environment where The X Window System(thrdmrk) is running.
Change to the root of the GroupWise 7 Administrator (Linux) CD.
Start the GroupWise Installation program:
./install
Click Create or Update a GroupWise System.
Follow the on-screen instructions.
For detailed system requirements, installation and update instructions, and a complete list of new features, see the GroupWise 7 Installation Guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 7 Administrator (NetWare/Windows) CD of the GroupWise 7 Documentation Web site GroupWise 7 Documentation Web site.
If you are updating your version of Linux as well as updating GroupWise, perform the Linux operating system upgrade first. In addition, when you upgrade on a server where GroupWise WebAccess or Monitor is installed, you need to run a script that reconfigures the WebAccess Application or the Monitor Application for the new Apache and Tomcat configuration and directory structure.
When you upgrade from Open Enterprise Server (OES) 1 to OES 2 with GroupWise installed on your OES server, you encounter package conflicts that must be resolved. A pop-up message appears immediately before the Installation Settings screen that informs you that the Delete Unmaintained Packages option is selected under Update Options. OES 2 considers GroupWise an “unmaintained package.” This means that, by default, your GroupWise software will be deleted as part of the upgrade process, unless you follow the instructions below.
Read the pop-up warning carefully, then click OK to close the pop-up.
The pop-up describes three possible actions you can take to resolve the GroupWise status as an unmaintained package. This procedure steps you through the second of the three possible actions. This alternative works most efficiently for preserving your GroupWise installation.
When ConsoleOne® is installed on the server:
The following message displays below the Packages link on the Installation Settings screen:
Cannot solve all conflicts. Manual intervention is required.
Click the Packages link.
The upgrade process checks for package conflicts, then displays the following message:
NOVLc1-1.3.6-1.i386 is locked and cannot be uninstalled.
Select Keep NOVLc1, then click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1 and displays one or more package-related warnings, providing you with alternatives for how to handle each conflict. The specific warnings you receive depend on the packages installed on the server you are upgrading. Therefore, warnings vary. Here are some examples:
NOVLc1-1.3.6-1.i386 cannot be installed due to missing dependencies.
novell-eguide-2.1.32.noarch cannot be installed due to missing dependencies.
The messages fall into two categories of problems:
Missing dependencies for ConsoleOne (the NOVLc1 package)
Missing dependencies for some other product package besides ConsoleOne (for example, eGuide)
The following steps help you decide which action to take for each type of message.
If the message indicates missing dependencies for ConsoleOne (NOVLc1), select Ignore This Requirement Just Here.
If the message indicates missing dependencies for some other product package besides ConsoleOne, and you are sure that you do not want that product package, select Delete package_name.
WARNING:ConsoleOne is dependent on a variety of packages. Delete packages only when you are certain that they are not required by ConsoleOne. If in doubt, select Keep package_name.
When you have selected an action for each conflict message, click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1. Additional messages might be displayed for you to select actions to resolve the conflicts. This cycle repeats until all conflicts have been resolved, then you successfully reach the Packages page.
On the Packages page, select Search in the Filter field.
Search for the GroupWise packages that are installed on the server by typing the following in the Search field:
novell-groupwise
Click Search.
Depending on what GroupWise components are installed on the server, the search results include some of the following packages:
novell-groupwise-admin novell-groupwise-agents novell-groupwise-dbcopy novell-groupwise-gwcheck novell-groupwise-gwha novell-groupwise-gwia novell-groupwise-gwinter novell-groupwise-gwmon novell-groupwise-monitor novell-groupwise-webaccess
Right-click the first GroupWise package in the list, then click All in This List > Keep.
This changes the status of each GroupWise package from Delete to Keep.
Search for the NOVLc1 package.
The NOVLc1 and NOVLc1Linuxjre packages should be listed and marked as locked. This means that they will not be deleted.
If these packages are marked with a Delete status, change their status to Keep.
Click Accept on the Packages page.
If you are presented with a font License Agreement, click Accept.
Click Continue to return to the Install Settings page.
Verify that the package conflict message is now gone from under the Packages link, then continue with the upgrade process.
After you have finished the upgrade, reinstall the NDSbase RPM that was originally installed with ConsoleOne.
The upgrade process removed it, but it is still needed by ConsoleOne.
In a Linux terminal window, log in as root, then change to the directory where you originally extracted the ConsoleOne files.
Change to the Linux subdirectory.
Use the following command to reinstall the NDSbase RPM:
rpm -ivh NDSbase-8.7.3.7-38.i386.rpm
If you encounter problems with GroupWise after you have upgraded from OES 1 to OES 2, see TID 3570778 in the Novell Knowledgebase for assistance.
When you upgrade from SLES 9 to SLES 10 with GroupWise installed on your SLES server, you encounter package conflicts that must be resolved.
When ConsoleOne is installed on the server:
The following message displays below the Packages link on the Installation Settings screen:
Cannot solve all conflicts. Manual intervention is required.
Click the Packages link.
The upgrade process checks for package conflicts, then displays the following message:
NOVLc1-1.3.6-1.i386 is locked and cannot be uninstalled.
Select Keep NOVLc1, then click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1 and displays one or more package-related warnings, providing you with alternatives for how to handle each conflict. The specific warnings you receive depend on the packages installed on the server you are upgrading. Therefore, warnings vary. Here are some examples:
NOVLpkia-2.7.0-6.i386 is locked and cannot be uninstalled.
NOVLc1-1.3.6-1.i386 cannot be installed due to missing dependencies.
The messages fall into two categories of problems:
A locked package
Missing dependencies for ConsoleOne (the NOVLc1 package)
The following steps help you decide which action to take for each type of message.
If the message indicates a locked package, select Keep package_name.
If the message indicates missing dependencies for ConsoleOne (NOVLc1), select Ignore This Requirement Just Here.
When you have selected an action for each conflict message, click OK - Try Again.
The upgrade process checks again for conflicts for NOVLc1. Additional messages are displayed for you to select actions to resolve the conflicts. This cycle repeats until all conflicts have been resolved (approximately nine times), then you successfully reach the Packages page.
On the Packages page, select Search in the Filter field.
Search for the GroupWise packages that are installed on the server by typing the following in the Search field:
novell-groupwise
Click Search.
Depending on what GroupWise components are installed on the server, the search results include some of the following packages:
novell-groupwise-admin novell-groupwise-agents novell-groupwise-dbcopy novell-groupwise-gwcheck novell-groupwise-gwha novell-groupwise-gwia novell-groupwise-gwinter novell-groupwise-gwmon novell-groupwise-monitor novell-groupwise-webaccess
Right-click the first GroupWise package in the list, then click All in This List > Keep.
This changes the status of each GroupWise package from Delete to Keep.
Search for the NOVLc1 package.
The NOVLc1 and NOVLc1Linuxjre packages should be listed and marked as locked. This means that they will not be deleted.
If these packages are marked with a Delete status, change their status to Keep.
Click Accept on the Packages page.
If you are presented with a font License Agreement, click Accept.
Click Continue to return to the Install Settings page.
Verify that the package conflict message is now gone from under the Packages link, then continue with the upgrade process.
After you have finished the upgrade, reinstall the NICI RPM and the NDSbase RPM that were originally installed with ConsoleOne.
The upgrade process removed them, but they are still needed by ConsoleOne.
In a Linux terminal window, log in as root, then change to the directory where you originally extracted the ConsoleOne files.
Change to the Linux subdirectory.
Use the following commands to reinstall the RPMs:
rpm -ivh nici-version-i386 rpm -ivh NDSbase-version.i386.rpm
If you encounter problems with GroupWise after you have upgraded from SLES 9 to SLES 10, see TID 3570778 in the Novell Knowledgebase for assistance.
When you upgrade your Linux operating system, OES 2 installs new versions of Apache and Tomcat by default. SLES does not; you must install them manually by following the procedure in this section. In addition, the GroupWise 7 installations of the WebAccess Application and the Monitor Application must be modified to accommodate changes made in Apache and Tomcat. The WebAccess/Monitor Update script takes care of this process for you. This script is available with TID 3624780 in the Support Knowledgebase.
If you have upgraded to SLES 10, use YaST to install Apache and Tomcat if they were not already installed on SLES 9:
Start YaST, then provide the root password.
Click Software Management.
In the Search field, type Apache, click Search, then select apache2 from the list.
In the Search field, type Tomcat, click Search, then select tomcat5 from the list.
Apache 2 was part of your SLES 9 installation, so it should have been automatically upgraded. Tomcat changed from Tomcat 4 to Tomcat 5, so unless Tomcat 5 was installed on SLES 9, Tomcat 5 needs to be installed.
Click Accept.
Follow the prompts to install the needed packages to your SLES 10 server.
Exit YaST.
Download the WebAccess/Monitor Update script from TID 3624780 in the Novell Support Knowledgebase to a convenient location on your Linux server.
Change to the directory where you downloaded the script file.
Give the script file execute permissions:
chmod +x fixgwweb.sh
Run the script.
The script makes some slight reconfigurations of GroupWise files and directories that were originally set up when the WebAccess Application and the Monitor Application were installed on your previous version of Linux.
Apache 2: On OES 1 and SLES 9, Apache 2 used the mod_jk connector to facilitate communication between Apache and Tomcat. On OES 2 and SLES 10, Apache 2 uses the mod_proxy module instead. The WebAccess/Monitor Update script modifies the gw.conf file with this change. On SLES 10, the script also creates a symbolic link from /etc/opt/novell/gw/gw.conf to the new Apache 2 location of /etc/apache2/conf.d/gw.conf.
Tomcat 5: On OES 1 and SLES 9, the WebAccess /var/opt/novell/gw directory was linked to /var/opt/novell/tomcat4/webapps/gw. The script changes this link to /var/opt/novell/tomcat5/webapps/gw. For Monitor, the /var/opt/novell/gwmon directory now links to /var/opt/novell/tomcat5/webapps/gwmon.
Start or restart Tomcat.
Start or restart Apache.
If you are upgrading to OES 2:
You might receive the following message when starting Apache 2:
Module "Jk" is not installed, ignoring.
You can safely ignore this message, but if you want to eliminate it:
Start YaST, then provide the root password.
Click NetWork Services > HTTP Server.
On the Server Modules tab, select the jk module in the list of services, then toggle the status to Off.
Click Finish to save your change.
Exit YaST.
You should now be able to run WebAccess and Monitor successfully on your upgraded Linux operating system.
For detailed installation instructions, see the GroupWise 7 Installation guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 7 Administrator CD.
Run setup.exe at the root of the GroupWise 7 Client (Windows) CD.
or
Run setup.exe from the client\win32 subdirectory on the GroupWise 7 Client (Windows) CD.
Follow the on-screen instructions.
From a terminal window, change to the \linux directory of the GroupWise 7 Client (Linux/Macintosh) CD.
Run the GroupWise Setup Advisor to install the GroupWise Cross-Platform client software:
./install
To start the Cross-Platform client after installation, click the GroupWise icon on your Linux desktop.
Browse to the \mac directory of the GroupWise 7 Client (Linux/Macintosh) CD.
Double-click the GroupWise.dmg file to install the GroupWise Macintosh(thrdmrk) client.
To start the Cross-Platform client after installation, click the GroupWise icon on your Macintosh desktop.
For instructions on how to install and for additional information about the GroupWise Connector for Outlook, see the GroupWise Connector for Outlook Readme. The GroupWise Connector for Outlook Readme is available in the \client\doc\us\ directory of the GroupWise 7 Client (Windows) CD.
If you install GroupWise on multiple platforms, or if you run multiple versions (for example, GroupWise 6.5 and GroupWise 7 in the same GroupWise system), refer to the GroupWise Version Compatibility appendix in the GroupWise 7 Installation Guide to make sure that the combinations you are using are supported. For example, you cannot run a GroupWise 7 client against a GroupWise 6.5 or earlier post office. Earlier POAs cannot support later GroupWise clients. However, you can run a GroupWise 6.5 or earlier client against a GroupWise 7 POA.
If you install GroupWise 7 components from a software distribution directory located on your local drive or a network drive and then try to update those components by installing from a CD, the installation fails by erroneously prompting for a disk:
Please insert the disk: 1
Uninstall the existing software, then install from the CD.
The WebAccess Application, WebPublisher Application, and Monitor Application share a common library. If you are updating from an earlier GroupWise version and if you run these applications on the same Web server, you must update all three before any of them can work properly.
Palm OS(thrdmrk) devices are no longer supported in GroupWise 7. However, the Installation program still offers the opportunity to configure this feature. If you have been using a PQA in an earlier version of GroupWise, you can continue to do so, but it is no longer a supported feature.
Platform-specific installation issues are listed in separate sections below. Installation issues for individual GroupWise components are located under the heading for each component.
When you create a new system and are prompted for software to copy to the software distribution directory, select at least the agent and client software. The GroupWise Installation program launches the Agent Installation program and the Client Installation program. It currently must run those programs from the software distribution directory.
When installing any GroupWise agent (Post Office Agent, Message Transfer Agent, Internet Agent, WebAccess Agent, Monitor Agent) to a NetWare server from a Windows XP machine where Service Pack 2 has been installed, you must have the Novell Client™ 4.90 SP2 or later installed on the Windows machine. If you have an earlier Novell Client, the GroupWise Installation program claims that it cannot find some of the directories to which you want to install software.
If you still have GroupWise 4.1 domains or post offices in your GroupWise system, you must update them to at least GroupWise 5.2 before updating your primary domain to GroupWise 7. If you try to update a 4.1 domain or post office to 7 after the primary domain has already been updated to 7, you need to rebuild each 4.1 secondary domain database using the GroupWise 7 or later snap-ins to ConsoleOne, and you also need to have each rebuilt secondary domain database manually edited by Novell Support before it can function correctly with the 7 primary domain.
When you upgrade any GroupWise component to GroupWise 7, all GroupWise components on a server must be updated at the same time. A message prompts you to update all components. However, you must still run the Configure option for each component so that the software that was automatically installed is also configured. If you do not run Configure, the new GroupWise High Availability service is not properly configured for the agents.
Because all GroupWise components on a server must be updated at the same time, if you are installing GroupWise 7 from a software distribution directory that does not contain RPMs for all the components installed on the server, you receive the following error:
Install failed for an unknown reason (7)
The GroupWise 7 component cannot be updated because its RPM is not present in the software distribution directory. You can use the GroupWise 7 Administrator (Linux) CD to update the server, then use Configure Administration to create a complete software distribution directory.
The Update section of the GroupWise 7 Installation Guide provides instructions for moving from NetWare or Windows to Linux. If you are moving post offices and domains belonging to a GroupWise 4.1 system, you might need to manually rename the domain database (wpdomain.db) from uppercase to lowercase, along with all .dc files. In addition, subdirectories in post office and domain directories might need to be renamed to lowercase.
You might encounter a problem including an image file in a global signature if the path to the image is too long. This is a Java(thrdmrk) problem. The easiest workaround is to move the image to a location with a shorter path. Another solution on Windows is to set the TMP environment variable to c:\temp before starting ConsoleOne.
If you enable global signatures, it disables flat forwarding through the Internet Agent because the signature is appended to each message. As an administrator, you must choose which is more important in your GroupWise system, global signatures or flat forwarding.
After a domain has been updated to GroupWise 7, do not administer that domain with earlier versions of the GroupWise snap-ins to ConsoleOne. Doing so could result in the unintentional creation of duplicate e-mail IDs.
The e-mail ID indexing scheme has been changed to allow the same e-mail ID to be used in different Internet domains within the same GroupWise system. This was prevented by the previous indexing scheme. Because the check for uniqueness works differently now, you must use the GroupWise 7 version of the ConsoleOne snap-ins when administering a GroupWise 7 domain to prevent the possibility of duplication.
When filling in a UNC Path field in ConsoleOne, you must specify the server name. You cannot use an IP address or DNS hostname.
Do not run an existing DirXML® or Identity Manager driver dated earlier than July, 2005, against a GroupWise 7 system.
GroupWise 7 requires the latest version of the GroupWise Identity Manager driver. Older drivers are not compatible. You can download the required version of the GroupWise driver from the Novell Identity Manager Patches Web site.
If you run server-based anti-virus software, you should configure it so that it does not scan GroupWise directory structures such as domains and post offices where file locking conflicts can create problems for the GroupWise agents. If you need virus scanning on GroupWise data, check the GroupWise Partner Products page for compatible products.
All directory names in paths to GroupWise domains and post offices can consist of up to 8 characters.
Filenames can also consist of up to 8 characters, with extensions of up to 3 characters. Do not use long filenames for any files used by any GroupWise components. This requirement applies even to files that are not specific to GroupWise (such as SSL certificates and key files).
If you will run ConsoleOne on Windows NT(thrdmrk) 4, you must install NT 4 Service Pack 6 before you install ConsoleOne.
The GroupWise Target Service Agent (GWTSA) handles situations where the same directory names are used on different volumes to back up by numbering the instances. For example:
GroupWise System/[Dom]Provo2: GroupWise System/[Dom]Provo2:
GroupWise System/1[DOM]Provo2: GroupWise System/2[DOM]Provo2:
Each instance is numbered and DOM is in all uppercase letters. After updating GWTSA with GroupWise 6.5 Support Pack 1 or later, you must re-create your backup jobs because the path has changed.
The NetWare version of the GroupWise Time Stamp Utility (GWTMSTMP) currently requires startup switches to use a dash (for example, -u), rather than the standard NetWare switch format (for example, /u).
If you use NSS volumes with quotas turned on, then you must turn on quotas on all GroupWise directories. Otherwise, you will receive No Disk Space errors.
If you see E811 errors on the POA or the GroupWise client, a possible cause is that TurboFat is corrupting GroupWise database pointers. The solution is to turn off TurboFat.
To turn off TurboFat on NetWare 5. x servers, use turbodis.nlm.
To turn off TurboFat on NetWare 6. x servers, use tdis600.nlm.
These NLM™ programs disable TurboFat at startup.
Because of long-standing file lock issues with NFS(thrdmrk), you cannot use an NFS mount to mount a server file system where your GroupWise system is located to a workstation where you are running ConsoleOne. We recommend using an SMB mount instead.
All directory names in paths to GroupWise domains and post offices should consist of lowercase letters. Filenames should also consist of lowercase letters. There are no length restrictions.
However, if you update a GroupWise 4.1 system and move it to Linux, you might see uppercase letters in database names. This is not a problem. The Database Copy (DBCopy) utility that you use to move domains and post office to Linux handles any uppercase/lowercase issues that might arise, so you should not manually rename any databases that have been copied to Linux using DBCopy.
If you run ConsoleOne on SUSE® LINUX 9 with Ximian® Desktop 2 installed, the label text on the property tabs does not display. As a workaround, click the tab to select it, then use the Up-arrow and Down-arrow keys to display each property page until you reach the one you want.
GroupWise 7 administration on Linux does not include the following features that are available in GroupWise 7 on NetWare and Windows:
Import/Export utility in ConsoleOne
Document Properties Management feature in ConsoleOne
None.
By default, the POA uses 1026 for its CAP (Calendar Access Protocol) port. On some Windows 2000 servers, port 1026 is already used by the Windows Task Scheduler or other Windows service. If this occurs, configure the POA to use a different CAP port using the /capport switch in the POA startup file.
If you try to start the POA or MTA using the --show switch on a server where The X Window System and Open Motif(thrdmrk) are not running, you receive the following error:
libXm.so.3: cannot open shared object file no such file or directory
To resolve the error, start The X Window System and Open Motif before starting the POA or MTA with the --show switch. If you start the POA or MTA without the --show switch, you can use the agent's Web console to monitor the agent from your Web browser.
Currently there is no way to set one computer as a primary archive. This can result in multiple archives if you use GroupWise on different computers.
If you install the GroupWise Windows client with Outlook XP already installed, an error message appears reading, “Either there is no default mail client or the current mail client cannot fulfil the messaging request. Please run Microsoft Outlook and set it as the default mail client”. In addition, if you open the Address Book, the GroupWise client crashes.
To fix the problem run win32\wms\nt\us\wms.exe from the install directory, then restart the client.
Installing Windows XP Service Pack 2 enables the Windows Firewall by default. The default Windows Firewall configuration blocks UDP (User Datagram Protocol). GroupWise is dependent on UDP for several key features such as listing new messages in your Mailbox, displaying notifications, and performing Busy Searches. To reconfigure the Windows Firewall so that it does not interfere with GroupWise functionality, follow the instructions in TID 10094089 in the Novell Support Knowledgebase.
Users of the JAWS(thrdmrk) screen reader should install the new JAWS script available in GroupWise 7. Copy the groupwise.jsb file from the \client\jaws directory of the GroupWise 7 Client (Windows) CD to the \jaws510\settings\enu directory on your workstation. This JAWS script includes Section 508 accessibility defect fixes that have occurred since the script was updated for GroupWise 6.5 Support Pack 3.
If you use ClearType to smooth the edges of screen fonts and have an LCD display, your screen might flicker when scrolling in a text message.
If you are using Microsoft's Anti-Spyware software, and you try to switch modes, GroupWise does not close. You must manually close GroupWise to switch modes.
The address books do not display in GroupWise if you install GroupWise for the first time after you have installed Outlook 2003. To resolve the problem, uninstall Outlook 2003 before you install GroupWise for the first time.
After your account has been moved from one post office to another, your Notify alarms disappear for appointments. To get your Notify alarms back, you need to re-create all the alarms manually. For information on setting alarms for appointments, see the help.
If you have spyware detection software installed on your Windows computer, the GroupWise client for Windows might not install properly. Disable the spyware detection software before you install the GroupWise client for Windows.
If you receive an item that was forwarded from the GroupWise Connector for Outlook, the item does not open in the Macintosh version of the Cross-Platform client.
If you run the Cross-Platform client in Caching mode as root on Linux, you might encounter synchronization problems with your master mailbox when you next run as a regular user. If pending requests from the root session remain when you log in as a regular user, regular user requests get backed up behind the root requests, which cannot be processed while you are logged in as a regular user. To resolve any problems, run the client as root again so that all messages are synchronized, then run as a regular user thereafter to prevent further problems.
The Cross-Platform client does not recognize the mailbox size limits set in ConsoleOne (Tools > GroupWise Utilities > Client Options > Send > Disk Space Management).
If you have installed Microsoft Office or Internet Explorer on your Macintosh, new messages might not display as bold in your mailbox. To resolve the problem, disable your user fonts, which are typically duplicates of your system fonts, or update to JVM(thrdmrk) 1.4.2 Update 1 or later.
Archiving with the Cross-Platform client can only be done to your local computer hard drive.
When prompted to rebuild your database, there is no progress indicator displayed during the rebuild process.
When you click Reply on Macintosh, you cannot just type the message. You must move the mouse cursor to the message body window of the reply message before you can start typing.
If you try to browse to the GWCheck program and run it by double-clicking the icon, you receive an error stating that there is no associated program. You must run GWCheck from a terminal window on Macintosh.
If you're using an Asian language for the client and external recipients are seeing corrupt characters in their received messages, then compose your message in HTML instead of text.
If you have more than one WebAccess Agent in your GroupWise system, you do not need to update all of them to GroupWise 7 at the same time. The GroupWise 7 WebAccess Application is compatible with older versions of the WebAccess Agent. However, users in post offices with a older default WebAccess Agent do not have all of the features available to users in post offices with a default GroupWise 7 WebAccess Agent. For more information, see Taking Advantage of Some of the New GroupWise 7 WebAccess Features While Still Running GroupWise 6.5.
If you access the WebAccess client through Virtual Office 1.5 or earlier, you might see the old WebAccess client interface rather than the new one. To resolve this problem, see TID 10098412 in the Novell Knowledgebase.
Before GroupWise 7, WebAccess stored its default user interface files in the following directory on the Web server:
tomcat_root/webapps/gw/WEB-INF/classes/com/novell/webaccess/templates/frames
In GroupWise 7, the user interface files are stored in the css subdirectory of templates rather than the frames subdirectory.
If you have exteNd™ portlets configured to use WebAccess, you must copy some of the exteNd template files from the frames directory into the css directory. Refer to the Novell exteNd documentation to determine which exteNd template files you should copy to the css directory. Do not copy the entire contents of the frames directory into the css directory; this would damage the new GroupWise 7 WebAccess user interface.
In addition, modify the WebAccess URL in the exteNd Portal Preferences from:
http:// Web_server_address/servlet/webacc
to:
http:// Web_server_address/gw/webacc
If you use the WebAccess client in the Safari(thrdmrk) Web browser on Macintosh, name completion is disabled because of lack of support for certain browser capabilities in Safari. Name completion is supported in the Mozilla(thrdmrk) Firefox(thrdmrk) Web browser on Macintosh.
If the WebAccess login page appears in one or more of the frames (for example, the Folder list or the Item list) after a WebAccess user has successfully logged in, the user is probably accessing WebAccess through one or more proxy servers.
To prevent this problem:
In ConsoleOne, right-click the WebAccess Application object (GroupWiseWebAccess), then click Properties.
Click Application > Security, then deselect the Use Client IP in Securing Sessions option.
For information about this option, click Help on the Environment page.
Click OK to save the change.
If you are using the Tomcat servlet engine with GroupWise WebAccess, the maximum memory allocation (heap size) for Tomcat should be at least 128 MB. The maximum memory allocation is set by using the -Xmx parameter when starting Tomcat (for example, -Xmx128m).
This error indicates a browser setup issue. You would encounter the same problem on any Web site that uses Java in frames. Depending on your browser, check mozilla.org, sun.com, or other browser supplier for more information.
If your Web server is configured to allow directory browsing, it is possible for a user to access the /com directory of your Web server and browse downward from there. There is no confidential information located in any of the directories that are accessible in this manner.
However, if you want to prevent access, you can change the configuration of your Web server. For example, if you are using Apache, you can modify the httpd.conf file to remove the access that is provided by default. Locate the section that provides directory options for the htdocs directory. Either remove the Indexes option from the Options directive or place a minus (-) in front of it. Restart Apache to put the change into effect.
Under certain very specific circumstances, it is possible for a user to view WebAccess template files from a Web browser without logging in to WebAccess. There is no confidential information located in any of the template files that are accessible in this manner.
Starting with GroupWise 6.5 Support Pack 4, a line was added to the webacc.cfg file to prevent such access:
Templates.requireAuthentication=true
With this setting, unauthenticated users have no access to any WebAccess template files except for the Login page. If you have customized WebAccess templates for your own specialized use, this setting causes your templates to be inaccessible, even if GroupWise authentication was not previously required. You can turn off the authentication requirement by changing the line in the webacc.cfg file to:
Templates.requireAuthentication=false
If you have created your own customized versions of the WebAccess send.inc and msgitem.htt templates, you need to make the following changes to these files in order for them to be compatible with GroupWise 7:
Do not use the Url.Item.Reply.to and Url.Item.Reply.cc variables to pass and post names in a reply message's To and CC fields. Instead, use Item.toFullID and Item.ccFullID (or Item.toName or Item.ccName).
When issuing an Item.Read action for a reply, set the Item.Reply parameter to either “sender” (to reply only to the sender) or “all” (to reply to all).
The cache created by the Document Viewer Agent is not compatible with the cache previously used with WebPublisher. Old WebPublisher cache directories should be removed from servers where the Viewer Agent is installed.
The Document Viewer Agent startup file (gwdva.dva) lists a /template startup switch that is not yet implemented.
If you receive an error during installation indicating that the nvweb.dll file cannot be found, update the workstation to the latest Novell Client. The Novell Client is available for download from the Novell Downloads Web site.
If you install the WebAccess Agent as a Windows service, reboot the server, and then do a workstation login as an Administrator, the WebAccess Agent service might fail to start. If this occurs, update to the latest Novell Client. The Novell Client is available for download from the Novell Downloads Web site.
If WebAccess and Novell iManager are installed on the same Windows 2000/2003 server, iManager might stop working. Because WebAccess installs and configures its own Tomcat and Jakarta connector, it is preferable to install it on a server where Tomcat is not already in use.
If the GroupWise 6.5 WebAccess Application is running on the server where you plan to install GroupWise 7 WebAccess, you should manually stop WebAccess, the Web server, and Tomcat before starting the GroupWise 7 installation. Under certain circumstances, the WebAccess Installation program cannot stop them for you.
Existing users of WebAccess are accustomed to accessing the following URLs on NetWare and Windows Web servers:
Default index.html file of the Web server
http:// web_server_address/servlet/webacc
http:// web_server_address/servlet/webpub
The WebAccess URLs on NetWare and Windows Web servers are now the same as the URLs used on Linux:
http:// web_server_address/gw/index.html
http:// web_server_address/gw/webacc
http:// web_server_address/gw/webpub
To keep users' browser bookmarks from being broken, you should redirect the old URLs to the new URLs. Follow the instructions below for your Web server.
Change to the conf subdirectory of the Apache root directory (for example, \apache2\conf.
Edit the Apache configuration file for GroupWise.
On NetWare 6, the Apache configuration file is gwapache.conf. On NetWare 6.5, the Apache configuration file is gwapache2.conf.
Add the following line:
redirect permanent /servlet/webacc http:// web_server_address/gw/webacc
If you use WebPublisher, add the following additional line:
redirect permanent /servlet/webpub http:// web_server_address/gw/webpub
Save the file, then exit the editor.
Restart Apache to put the redirections into effect.
Change to the inetpub\wwwroot subdirectory of the IIS root directory (for example, c:\inetpub\wwwroot
Create a subdirectory named servlet.
Under the servlet subdirectory, create subdirectory named webacc.
If you use WebPublisher, create a second subdirectory named webpub.
In IIS Manager, expand the tree in the left pane to display Default Web Site under Web Sites.
Under Default Web Sites, you should see the servlet subdirectory you created in Step 2.
Expand the servlet subdirectory to display the webacc subdirectory (and optionally, the webpub subdirectory) that you created in Step 3.
Right-click the webacc subdirectory, then click Properties.
Click Directory, select A Redirection to a URL, then type /gw/webacc in the associated field.
Select A Permanent Redirection for This Resource, then click OK to save your changes.
If you use WebPublisher, repeat Step 7 through Step 9, using webpub in place of webacc.
Restart the IIS Web server to put the redirections into effect.
For redirection instructions, search the Novell Support Web site.
As part of the change from /servlet/webacc to /gw/webacc, the WebAccess Installation program installs the WebAccess Application files into the servlet container (gw) but it does not remove old servlet and htdoc files located under the ROOT container of the servlet and the Web server. Therefore, you might want to manually delete the following directories and files:
sys:\apache2\htdocs\com sys:\apache2\htdocs\index.html (if customized for GroupWise) sys:\apache2\htdocs\novell.html (if index.html was not customized) sys:\tomcat\4\webapps\ROOT\WEB-INF\classes\com sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\ldapfilt.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\ldapjdk.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\njgwap.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\njweb.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\lib\SpellServlet.jar sys:\tomcat\4\webapps\ROOT\WEB-INF\web.xml
The one file you should definitely delete is web.xml, because might cause the WebAccess, WebPublisher, and Monitor Applications to run in both the old and new locations. Also, if you have customized the GroupWise template files, you should copy the contents of the template subdirectories under:
sys:\tomcat\4\webapps\ROOT\WEB-INF\classes\com\novell
to the corresponding templates subdirectories under:
sys:\tomcat\4\webapps\gw\WEB-INF\classes\com\novell
Under certain circumstances, stopping the WebAccess Agent by unloading it at the NetWare server command line:
unload gwinter
might cause the following error:
"Module GWDVA.NLM in Address Space GWDVAWRKRX did not unload yet.[lnbrk] Killing the address space is the only way to remove the module. [lnbrk]Should the address space be Killed ? n"
Regardless of whether you respond with “n” or “y”, the server might hang and need to be restarted. If you encounter this problem on your NetWare server, use one of the following methods to stop the WebAccess Agent, rather than using the unload command.
At the WebAccess Agent server console, press F7 or Esc, then select Yes to stop the WebAccess Agent.
At the NetWare server console, enter stopweb to stop the WebAccess Agent.
On NetWare, the Viewer Agent requires at least 1 GB of memory for running about 5 worker processes. By default, 5 processes are started.
On NetWare, you must install the latest Support Pack for your version of NetWare in order to have the correct version of clib.nlm.
On NetWare, Memory Protection Fault Cleanup must be set to On in order for the Viewer Agent worker processes to recover successfully when a document fails HTML conversion.
On NetWare, when a document fails HTML conversion and its worker process dies, NetWare creates a small file named core*.dmp in the server's root directory. You should periodically delete these files.
When using Internet Explorer 5.0 to view messages through WebAccess, URLs to messages become part of the History cache and can be read by other users who have access to the same workstation. For solutions to this problem, see TID 10056452 in the Novell Knowledgebase.
GroupWise 7 on Linux includes a Novell distribution of Apache and Tomcat that you can install along with the WebAccess Application if you do not already have Apache and Tomcat running on that server. The Novell distribution is installed in the following directories:
/var/opt/novell/http and /etc/opt/novell/http
/var/opt/novell/tomcat4 and /etc/opt/novell/tomcat4
and is started using the following customized commands:
/etc/init.d/novell-tomcat4 start
/etc/init.d/novell-httpd start
The WebAccess Installation program lets you choose whether you want to install the Novell distribution. During installation, select Install WebAccess Application with Apache and Tomcat if you want to install the Novell distribution. Select Install WebAccess Application if you do not want to install the Novell distribution of Apache and Tomcat because you have an existing Apache and Tomcat installation that you want to use with WebAccess.
NOTE:If you are installing on Novell Open Enterprise Server (OES), the option to install with Apache and Tomcat is not available.
If you install the Novell distribution on a server where a standard distribution of Apache and Tomcat is already installed and running, you will encounter a port conflict on port 80. You can resolve the port conflict by choosing to run one distribution or the other, or you can reconfigure one distribution or the other.
To reconfigure the Novell distribution to use a different port number, edit the httpd.conf file in the /etc/opt/novell/httpd/conf directory. Locate the following line:
Listen 80
Change the port number to a something that is not already being used on the server, then save and exit the file.
On slower machines, if you select Install WebAccess Application with Apache and Tomcat, your machine might appear to hang on the “Please Wait” message. Apache and Tomcat are being installed while the “Please Wait” message is displayed, before the WebAccess Application installation begins.
During installation, the WebAccess Installation program requires access to eDirectory™ by way of LDAP authentication. The LDAP Group object includes an option named Require TLS for Simple Binds with Password, which is enabled by default. With this option enabled, you must provide the LDAP server's Trusted Root Certificate, which must be exported from the LDAP server, in order for LDAP authentication to take place (typically on port 636) during installation of the WebAccess.
Unless you already have SSL set up, an easier alternative is to disable Require TLS for Simple Binds with Passwords in ConsoleOne, which allows LDAP authentication to take place using clear text (typically on port 389), during installation of WebAccess. After disabling the option, restart eDirectory, install WebAccess, then re-enable Require TLS for Simple Binds with Password and restart eDirectory again.
If you install WebAccess in an eDirectory context where the WebAccess objects already exist, a message informs you that you can “use the existing objects.” In actuality, the objects are deleted and re-created, so if you have customized the properties of the existing objects, you must customize the objects again after installing WebAccess on Linux.
The WebAccess Agent currently does not run on Novell Cluster Services™ on Linux.
On Linux, if you run the Viewer Agent as a user that is not running The X Window system, then WebAccess client users cannot view embedded vector-based graphics in attachments. To enable users to view embedded vector-based graphics, make sure that the user that starts WebAccess (and hence, the Viewer Agent) is running The X Window System and has a DISPLAY environment variable set so that the Viewer Agent can write to the local display. One way to accomplish this is to use the sux command to become root before you start the WebAccess Agent.
On Linux, the third-party viewer software used by the Viewer Agent has a dependency on libXm.so.1, which might not be included with your Linux package. To resolve this, create a symbolic link in the agents lib directory to the version of the libXm modules that is available on your Linux server. For example:
ln -s /usr/X11R6/lib/libXm.so.3.0.1 /opt/novell/groupwise/agents/lib/libXm.so.1
The WebAccess Installation program does not configure WebPublisher for you. Some manual configuration is required. For instructions, see the GroupWise 7 Installation Guide (/docs/us/GroupWiseInstallationGuide.pdf).
Changes to the settings on the Templates page of the GroupWiseWebPublisher object in ConsoleOne are not saved to the webpub.cfg file. To work around this, after making changes on the Templates page, select a different property page on the GroupWiseWebPublisher object, then click OK or Apply to save the template settings correctly.
If you have commented out any lines in the Linux WebAccess configuration file (webacc.cfg) or the WebPublisher configuration file (webpub.cfg), you should back up those files before installing GroupWise 7. If you use the Configure WebAccess Application option in the Installation program, those commented lines become uncommented and the settings return to their defaults. However, any other changes you have made to the configuration files are retained. You must comment out the lines again and edit the settings as needed, using the backup copies for reference.
In GroupWise 6 and its Support Packs, there was a problem with the address format used for sending to distribution lists and resources if you set Internet Addressing to one of the following formats (which are not appropriate for distribution lists and resources):
first_name. last_name@ Internet_domain
last_name. first_name@ Internet_domain
Messages to distribution lists and resources were initially undeliverable and were sent to the Internet Agent. The Internet Agent then successfully resolved the addresses and sent the messages back into the GroupWise system. Users did not notice the problem, but some administrators noticed unnecessary traffic through the Internet Agent.
In GroupWise 6.5, the address format problem for sending to distribution lists and resources was corrected. However, users who originally used GroupWise 6 have the erroneous address format for distribution lists and resources in their Frequent Contacts address books. If you are updating from GroupWise 6 to GroupWise 7 and unnecessary traffic through the Internet Agent is a continuing problem, have users delete distribution lists and resources from their Frequent Contacts address books so that the correct address format is used for name completion in the future.
If you run the NetWare Internet Agent on the same server and in the same address space with the NetWare WebAccess Agent, and if you unload and then reload the Internet Agent, the server abends.
To work around this problem, unload both agents, then reload both agents, or run each agent in its own separate address space.
GroupWise 6.5 included the /etc/init.d/grpwise-ia script for starting and stopping the Internet Agent. In GroupWise 7, the Internet Agent is started along with the POA and the MTA, using the grpwise script. Therefore, you should delete the obsolete grpwise-ia script from /etc/init.d so that it is not used by accident.
During installation, the Internet Agent Installation program requires access to eDirectory by way of LDAP authentication. The LDAP Group object includes an option named Require TLS for Simple Binds with Password, which is enabled by default. With this option enabled, you must provide the LDAP server's Trusted Root Certificate, which must be exported from the LDAP server, in order for LDAP authentication to take place (typically on port 636) during installation of the Internet Agent.
Unless you already have SSL set up, an easier alternative is to disable Require TLS for Simple Binds with Passwords in ConsoleOne, which allows LDAP authentication to take place using clear text (typically on port 389), during installation of the Internet Agent. After disabling the option, restart eDirectory, install the Internet Agent, then re-enable Require TLS for Simple Binds with Password and restart eDirectory again.
If you try to start the Internet Agent using the --show switch on a server where The X Window System and Open Motif are not running, you receive the following error:
libXm.so.3: cannot open shared object file no such file or directory
To resolve the error, start The X Window System and Open Motif before starting the Internet Agent with the --show switch. If you start the Internet Agent without the --show switch, you can use the Internet Agent Web console to monitor the Internet Agent from your Web browser.
Monitor settings are stored in the monitor.xml file in the Monitor installation directory. Agent groups are also stored in this file. If you reinstall the Monitor software, the monitor.xml file is backed up as monitor.001. To restore previous Monitor settings and agent groups, remove the newly installed monitor.xml file and rename monitor.001 to monitor.xml.
If you've used Monitor on a NetWare or Windows Web server, you are accustomed to accessing the following URLs:
Default index.html file of Web server
http:// web_server_address/servlet/gwmonitor
Starting in GroupWise 7, use the following URLs on NetWare and Windows Web servers:
http:// web_server_address/gw/index.html
http:// web_server_address/gw/gwmonitor
To keep users' browser bookmarks from being broken, you should redirect the old URLs to the new URLs. Follow the instructions in New NetWare and Windows WebAccess URLs, substituting /gw/gwmonitor for /gw/webacc as needed in the instructions.
Monitor and WebAccess share a substantial amount of functionality. The following WebAccess issues also pertain to Monitor:
For installation instructions and known issues relating to the GroupWise Connector for Microsoft Outlook, see the readmeolus.txt file in the \client\docs\us directory of the GroupWise 7 Client (Windows) CD.
Do not use double-byte characters in directory names and filenames.
Do not use double-byte character in users' passwords.
The Change GroupWise Password dialog box in ConsoleOne currently allows entry of double-byte characters. However, the GroupWise client login does not allow entry of double-byte characters in passwords, so a user who was assigned a password with double-byte characters in ConsoleOne cannot type the double-byte characters when attempting to log in to GroupWise.
If a WebAccess client user receives a message, task, or appointment with a Euro character in the Subject field, it might display as an upside-down question mark when viewed in the Java version of the Calendar. The issue resides with the user's browser.
Netscape users need to upgrade to Netscape Communicator(thrdmrk) 6.
Internet Explorer users should be using at least version 3309 of the JVM. The latest JVM can be downloaded from the Microsoft Web site and installed on the user's workstation. This JVM enables Internet Explorer 4. x and later to correctly display the Euro character.
Auto-detection of character encoding for the WebAccess/WebPublisher index.html page does not work for some Web browsers. If you do not see the localized languages in the drop-down menu on the Web services page (index.html), set your Web browser's character encoding to UTF-8. In some browsers, you can click View > Encoding to set the Web browser's encoding.
You might also encounter character encoding problems when reading HTML-formatted messages. In this case, set your Web browser's character encoding for the new message window to UTF-8. You can do this by right-clicking in the new message window and then setting the encoding, or by clicking View > Encoding.
When Russian characters are used, they are displaying in the Spell Checker as corrupt characters.
On the Monitor Web console, you might see incorrect display of some characters, particularly accented characters.
The GroupWise client Print Calendar feature always prints calendars in the language specified in Regional Options or Regional Settings in the Control Panel, even if the client is installed in a different language. For example, if French (Switzerland) or French (Swiss) is specified in the Control Panel and the client is installed in German, calendars print in French.
If you use RichWin in combination with GroupWise 7, be sure to run RichWin first, then run GroupWise.
If you run the agents with an agent console interface in languages other than English, the display of logging information might not display correctly. The problem occurs if your language encoding is set to UTF-8.
To determine your current language encoding, use the following command in a terminal window:
locale
You can change your language encoding in YaST:
Start YaST, click System, then double-click Choose Language.
Select the language you are running the agents in, then click Details.
Deselect Use UTF-8 Encoding, then click OK.
Stop and then restart the agents to put the new setting into effect.
When you use a Russian keyboard, the Linux environment variables that provide language and locale information are typically set to ru_RU. Typically, this setting implies the Russian character set ISO-8859-5. However, on some distributions of Linux, the ISO-8859-5 character set must be set explicitly in order for your Russian keyboard to work with the GroupWise Cross-Platform client. Use the following command to specify the character set along with the language and locale information:
export LANG=ru_RU.ISO-8859-5
In most cases, setting the LANG environment variable also sets all LC_* environment variables and resolves all Russian keyboard problems. If you set the LANG environment variable and your Russian keyboard still does not work, use the following command to view the current settings for the LANG and LC_* environment variables:
locale
If any of the LC_* environment variables have not inherited the ISO-8859-5 specification, export them individually.
Keyboard mnemonics for menu items work for characters a-z and A-Z, but not for other characters.
The Linux GroupWise agent user interfaces display correctly if the Linux environment is using the ISO-8859-1 character set, which is the default for the GroupWise administration languages and locales.
If the Linux environment is using a different character set encoding such as UTF-8 (for example, fr_FR.UTF-8), the localized agent user interfaces do not display correctly.
Languages that display right-to-left display right-justified rather than left-justified.
None.
To support accessibility requirements within GroupWise Help, the Help for the GroupWise Windows client uses Microsoft HTML Help. In order for Microsoft HTML Help to display on a Windows workstation, the workstation must have Internet Explorer 4. x or later installed.
When you start the POA, the MTA, and the Internet Agent using the --show switch to display a GUI user interface, if the agents are running as a non-root user, clicking Help does not display the agent help file. Help is displayed in a browser window and the agents currently launch the browser as root. Giving the user access to the browser window as root would be a security risk.This is working as designed.
If you display help from an agent Web console on a server where Novell iChain® is installed, and if iChain is configured to use the Path-Based Multihoming option, the image at the top of the help topic does not display.
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2005 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and in other countries.
ConsoleOne, DirXML, GroupWise, iChain, NetWare, Novell, and Ximian are registered trademarks of Novell, Inc. in the United States and other countries.
SUSE is a registered trademark of SUSE AG, a Novell business.
eDirectory, Evolution, exteNd, NLM, Novell Client, and Novell Cluster Services are trademarks of Novell, Inc.
All third-party trademarks are the property of their respective owners.