GroupWise 6.5 provides substantial improvements over GroupWise 6 in five key areas:
Expanded Client Features: The GroupWise client has an updated look and feel. The new Contacts folder provides access to the Frequent Contacts address book or any personal address book of your choice. From the Contacts folder, you can view, create, and modify contacts, resources, organizations, and groups. The new Checklist folder provides an area to create a personal task list. You can move any items to this folder, arrange them in the order you want, and check them off as you complete them. In addition, you can view any folder as a Checklist, allowing you to reorder messages and other mailbox items into a task list. You can assign color-coded categories to messages, appointment, contacts, and so on, and edit the displayed subject of any item, allowing you to more efficiently manage your mailbox.
Improved Security: Secure Sockets Layer (SSL) connections can now be required by the administrator for all client access to GroupWise mailboxes. In addition, the Internet Agent and the WebAccess Agent can connect to post offices using SSL connections.
Spam Handling: The GroupWise 6.5 client has a new Junk Mail Handling feature that lets users quickly control unwanted Internet e-mail messages (spam) with block lists and by using a Junk Mail folder to automatically file all messages from senders that are not in your personal address books (including Frequent Contacts). In addition, the Internet Agent can be configured to reject messages from known open relay hosts and spam hosts. Combined, these features protect users from seeing unwanted messages in their GroupWise mailboxes.
Virus Scanning: By integrating third-party software into GroupWise as trusted applications, you can scan messages and attachments for viruses and prevent virus damage to your system.
Instant Messaging: Novell GroupWise Messenger is a corporate-based, secure instant messaging solution that supports instant messaging, presence, and archiving of conversations. (GroupWise Messenger will be available shortly after the release of GroupWise 6.5).
To install GroupWise 6.5:
Run setup.exe at the root of the GroupWise 6.5 Administrator CD.
The Installation program lets you view the Readme, the Quick Start, and the Installation guide before you start installing GroupWise. The Quick Start and the Installation guide are in PDF format. You must have Adobe Acrobat Reader version 4 or higher in order to view these files. If necessary, you can download a free version from the Adobe Acrobat Reader page:
http://www.adobe.com/products/acrobat/readstep2.html
Click Create or Update a GroupWise System.
Follow the on-screen instructions.
For detailed installation and update instructions, as well as a complete list of new features, see the GroupWise 6.5 Installation guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 6.5 Administrator CD.
Novell GroupWise Messenger is not included with the initial GroupWise 6.5 release, but will be available soon. Check the GroupWise product page for availability.
If you are using the DirXML driver for GroupWise, you need to obtain an updated version for use with GroupWise 6.5. It is not part of the GroupWise 6.5 release.
The DirXML Driver 2.0 for GroupWise will release shortly after GroupWise 6.5. It will operate with GroupWise 5.5, 5.5 Enhancement Pack, 6.0, and 6.5. Check the Novell Downloads page for availability.
In previous versions of GroupWise, all language versions of the setupip.fil file, used when running SetupIP (also called AutoUpdate over an IP connection), were not included on the CD and had to be downloaded from the Novell Downloads page.
In GroupWise 6.5, the following language version of this file is included on the GroupWise 6.5 Administrator CD in the \admin\utility\setupip directory:
The following language versions are available from the Novell Downloads page:
Copy the language version of setupip.fil you want to the HTTP Web server that you will be using for SetupIP. Rename the file to setupip.fil.
For more information about SetupIP, see the Client section of the GroupWise 6.5 Administration guide at the Novell Documentation Web site.
In ConsoleOne, when you create a Novell eDirectory user synchronization event for the MTA, do no use the Interval setting. It does not schedule the event correctly for the specified interval. You can create multiple events by using the Daily trigger and specifying several different times of day to achieve the same results. This problem will be resolved in Support Pack 1.
To install the GroupWise 6.5 agents:
Run setup.exe at the root of the GroupWise 6.5 Administrator CD, then click Install Products > GroupWise Agents > Install GroupWise Agents.
or
Run install.exe from the \agents subdirectory on the GroupWise 6.5 Administrator CD or in your software distribution directory if you have updated it with GroupWise 6.5 software.
Follow the on-screen instructions.
For detailed installation instructions, see Installing GroupWise Agents in the GroupWise 6.5 Installation guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 6.5 Administrator CD.
When you install the agents on a Windows 2000 machine, you might receive a warning message referring you to the Readme. For the original release of GroupWise 6 and for subsequent Support Packs, either Microsoft HotFix Q266066 or Windows 2000 Service Pack 2 was required. This continues to apply for the GroupWise 6.5 agents.
The GroupWise agents are not supported on Windows XP. Windows XP is not a server platform.
In order to run the GroupWise agents on NetWare 4.2, you must load clibaux.nlm before loading the agent NLM programs. Add the following line to the grpwise.ncf file:
load clibaux
Add it before the lines that load the agents.
If Remote client users connect to their mailboxes through MTAs, rather than through the POAs for their post offices, SSL is not used for the live remote connections, even when the agents are configured for SSL.
As an alternative to live remote connections from outside your firewall, you could set up proxy servers for the POAs, so that Remote client users connect to their mailboxes through the proxy servers rather than through MTAs. Full SSL security is provided through the proxy servers.
The official localized interface languages for the GroupWise 6.5 agent are French, German, Portuguese, and Spanish. These represent the official GroupWise administration languages, which are available for selection during installation.
Additional languages that have been available in earlier GroupWise releases (and are also provided for the client) are still available by manually setting the /language startup switch in the agent startup file. The agents have been localized into these additional non-administration languages to support localized messages generated by the agents that might appear in the client.
To install the GroupWise 6.5 client:
Run setup.exe at the root of the GroupWise 6.5 Client CD.
or
Run setup.exe from the client\win32 subdirectory on the GroupWise 6.5 Client CD.
Follow the on-screen instructions.
For detailed installation instructions, see the GroupWise 6.5 Installation guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 6.5 Administrator CD.
Novell GroupWise Messenger is not available with the initial GroupWise 6.5 release, but will be made available at a later time.
You can only move items from a shared folder to the Checklist folder (or mark items from a shared folder to show in the Checklist folder) if you are the creator of the shared folder.
If you are using a Toshiba Tecra 9100 with Windows 2000 and a True Color (32 bit) display setting, running GroupWise 6.5 will cause a blue screen crash unless you update your Toshiba display drivers.
Download the latest display drivers from the Toshiba Web site.
For detailed installation and update instructions, see the GroupWise 6.5 Installation guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 6.5 Administrator CD.
To install GroupWise 6.5 Internet Agent:
Run setup.exe at the root of the GroupWise 6.5 Administrator CD, click Install Products, click GroupWise Internet Agent, then click Install GroupWise Internet Agent
or
Run setup.exe from the internet\gwia subdirectory on the GroupWise 6.5 Administrator CD or in your software distribution directory if you have updated it with GroupWise 6.5 software.
Follow the on-screen instructions.
When you install the Internet Agent on a Windows 2000 machine, you might receive a warning message referring you to the Readme. For the GroupWise 6 and GroupWise 6 Support Pack 1 releases, either Microsoft HotFix Q266066 or Windows 2000 Service Pack 2 was required. This still applies to the GroupWise 6.5 agents.
The Internet Agent is not supported on Windows XP. Windows XP is not a server platform.
In order to run the Internet Agent on NetWare 4.2, you must load clibaux.nlm before loading the agent NLM programs. Add the following line to the gwia.ncf file:
load clibaux
Add it before the line that loads the Internet Agent.
Before you load the Internet Agent in protected memory on a NetWare server, you should delete or rename the sccfilt.bin and sccopt.bin files if they exist. This causes the files to be re-created and ensures that they contain the current configuration information. If you do not delete these files and they do not contain the current configuration information, the Internet Agent may abend.
To delete the files:
Verify that no scc*.nlm programs are loaded in memory. If these files are still in memory, the sccfilt.bin and sccopt.bin files will not be re-created correctly.
Delete the sccfilt.bin and sccopt.bin files. They reside in the same directory as gwia.nlm (by default, the sys:\system directory).
Start and then exit from the Internet Agent in regular memory.
Start the Internet Agent in protected memory.
This applies only if you are updating from a previous version of the Internet Agent and you modified the status.xml (located in the domain\wpgate\gwia directory) file to customize your status messages (undeliverable, deleted, opened, and so forth).
The format of the status.xml file has changed. The file format change will cause the Internet Agent to not load properly. Because of this, the Internet Agent installation program renames the status.xml file to status.old and copies new statusxx.xml files to the domain\wpgate\gwia directory, where xx is a language code that represents a language included on your GroupWise CD.
As a result of the status.xml file being renamed to status.old, the Internet Agent will revert to using its internal status messages. To implement customized status messages using the new statusxx.xml files:
Open the appropriate statusxx.xml file for the language you want.
Modify any of the desired status messages.
Save the modified file as status.xml.
IMPORTANT: Make sure to remove the two-letter language code. The Internet Agent will only recognize the file if it is named status.xml.
Restart the Internet Agent.
For detailed installation and update instructions, see the GroupWise 6.5 Installation guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 6.5 Administrator CD.
To install GroupWise 6.5 WebAccess:
Run setup.exe at the root of the GroupWise 6.5 Administrator CD, click Install Products, click GroupWise WebAccess, then click Install GroupWise WebAccess
or
Run setup.exe from the internet\webacces subdirectory on the GroupWise 6.5 Administrator CD or in your software distribution directory if you have updated it with GroupWise 6.5 software.
Follow the on-screen instructions.
The GroupWise WebAccess Installation program installs the WebAccess and WebPublisher Applications to the Web servers listed below. These are the Web servers that have been tested by Novell.
If necessary, you can run the WebAccess and WebPublisher Applications on another Web server as long as the Web server supports a Java servlet engine that is JSDK 2.0 compatible. However, the Installation program will not install the applications to other Web servers, which means you must manually install and configure them.
IMPORTANT: Manually installing WebAccess and WebPublisher to a Web server is not a trivial effort. The following steps are generic; you will need to be able to apply them to your Web server environment. To be successful, you need to have a thorough understanding of your Web server and Java servlet engine and how the two work together.
When you run the Installation program, deselect the options to install the WebAccess Application and WebPublisher Application, install the WebAccess Agent, then complete the remaining steps to install the applications.
Unzip webaccess.zip to the root of the Web server's volume. This will create a \novell directory on the volume root.
The webaccess.zip file and the other .zip files referred to in the remaining steps are in the internet\webacces\other directory on the GroupWise 6.5 Administrator CD.
Unzip webaccessdocs.zip to the Web server's document root directory.
Unzip webaccessservlets.zip to the servlet root directory.
Unzip webaccessjars.zip to a library or jar file directory on the Web server (for example, you may want to create a \novell\lib directory), then add the jar files to the class path.
Modify your Java engine's servlet properties file to include the settings shown in the sample WebAccess servlets.properties file.
The WebAccess servlet.properties file is located in the internet\webacces\other directory on the GroupWise 6.5 Administrator CD.
Modify the Templates.path setting in the webacc.cfg and webpub.cfg files to replace java/servlets with the path to the servlet root directory.
The webacc.cfg file is located in the novell\webaccess directory and the webpub.cfg file is in the novell\webpublisher directory on the root of the Web server's volume.
If you created the \novell directory structure in the location specified in step 2 (the root of the Web server's volume), the paths for the following settings in the webacc.cfg and webpub.cfg should already be correct. If not, you need to modify the paths to make them correct from the perspective of the Web server.
File.Upload.path
Log.path
Security.Timeout.path
Provider.GWAP.Config.file
Provider.LDAP.Config.file (webacc.cfg only)
Copy the index.html file to the Web server's document root directory. You can replace your Web server's current default home page with this file, or you can rename the file and link to it from your current default home page.
Copy the commgr.cfg file, located in the WebAccess gateway home directory (domain\wpgate\webac65a), to the novell\webaccess directory and the novell\webpublisher directory.
If you use a Java servlet engine other than the Novell Servlet Gateway or the Tomcat servlet engine, the servlet engine needs to be JSDK 2.0 compatible.
After you've installed WebAccess, complete the following tasks to configure WebAccess to work with the Java servlet engine:
Modify the Java servlet engine's servlet properties file to include the settings shown in the sample WebAccess servlets.properties file.
The servlets.properties file is located in the internet\webacces\other directory on the GroupWise 6.5 Administrator CD.
Modify the Templates.path setting in the webacc.cfg and webpub.cfg files to replace java/servlets with the path to the servlet root directory.
The webacc.cfg file is located in the novell\webaccess directory and the webpub.cfg file is in the novell\webpublisher directory on the root of the Web server's volume.
Add the WebAccess jar files to the class path. On a NetWare server, the jar files are located in the java\lib directory. On a Windows NT/2000 server, the files are located in the novell\java\lib directory.
When you install the WebAccess Agent on a Windows 2000 machine, you might receive a warning message referring you to the Readme. For the GroupWise 6 and GroupWise 6 Support Pack 1 releases, either Microsoft HotFix Q266066 or Windows 2000 Service Pack 2 was required. This still applies to the GroupWise 6.5 agents.
The WebAccess Agent, WebAccess Application, and WebPublisher Application are not supported on Windows XP. Windows XP is not a server platform.
In order to run the WebAccess Agent on NetWare 4.2, you must load clibaux.nlm before loading the agent NLM programs. Add the following line to the strtweb.ncf file:
load clibaux
Add it before the line that loads the WebAccess Agent.
The WebAccess configuration file (webacc.cfg) contains two new settings not available in ConsoleOne, and the WebPublisher configuration file (webpub.cfg) contains one new setting.
Security.HtmlDocument.disableScripts=false
Security.HtmlAttachment.disableScripts=false
The webacc.cfg file is located in the Web server's novell\webaccess directory. The webpub.cfg file is located in the novell\webpublisher directory.
To install GroupWise 6.5 Monitor:
Run setup.exe at the root of the GroupWise 6.5 Administrator CD, then click Install Products > GroupWise Monitor > Install GroupWise Monitor.
or
Run setup.exe from the \admin\monitor subdirectory on the GroupWise 6.5 Administrator CD or in your software distribution directory if you have updated it with GroupWise 6.5 software.
Follow the on-screen instructions.
For detailed installation instructions, see the GroupWise 6.5 Installation guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory on the GroupWise 6.5 Administrator CD.
The GroupWise Monitor Installation program installs the Monitor Application to the Web servers listed below. These are the Web servers that have been tested by Novell.
If necessary, you can run the Monitor Application on another Web server as long as the Web server supports a Java servlet engine that is JSDK 2.0 compatible. However, the Installation program will not install the applications to other Web servers, which means you must manually install and configure them.
IMPORTANT: Manually installing the Monitor Application to a Web server is not a trivial effort. The following steps are generic; you will need to be able to apply them to your Web server environment. To be successful, you need to have a thorough understanding of your Web server and Java servlet engine and how the two work together.
When you run the Installation program, deselect the option to install the Monitor Application, install the Monitor Agent, then complete the remaining steps to install the application.
Unzip gwmonitor.zip to the root of the Web server's drive or volume. This creates a \novell directory at the root of the drive or volume.
The gwmonitor.zip file and the other .zip files referred to in the remaining steps are in the admin\monitor\other directory on the GroupWise 6.5 Administrator CD.
Unzip gwmonitordocs.zip to the Web server's document root directory.
Unzip gwmonitorservlets.zip to the servlet root directory.
Unzip gwmonitorjars.zip to a library or jar file directory on the Web server (for example, you might want to create a \novell\lib directory), then add the jar files to the class path.
Modify your Java engine's servlet properties file to include the settings shown in the sample Monitor servlets.properties file.
The Monitor servlet.properties file is located in the admin\monitor\other directory on the GroupWise 6.5 Administrator CD.
Modify the Templates.path setting in the gwmonitor.cfg file to replace java/servlets with the path to the servlet root directory.
The gwmonitor.cfg file is located in the \novell\gwmonitor directory at the root of the Web server's drive or volume.
If you created the \novell directory structure in the location specified in Step 2 (the root of the Web server's drive or volume), the paths for the following settings in the gwmonitor.cfg file should already be correct. If not, you need to modify the paths to make them correct from the perspective of the Web server.
File.Upload.path
Log.path
Security.Timeout.path
Provider.GWAP.Config.file
Provider.LDAP.Config.file
Copy the index.html file to the Web server's document root directory. You can replace your Web server's current default home page with this file, or you can rename the file and link to it from your current default home page.
If you use a Java servlet engine other than the Novell Servlet Gateway or the Tomcat servlet engine, the servlet engine needs to be JSDK 2.0 compatible.
After you've installed Monitor, complete the following tasks to configure the Monitor Application to work with the Java servlet engine:
Modify the Java servlet engine's servlet properties file to include the settings shown in the sample Monitor servlets.properties file.
The servlets.properties file is located in the admin\monitor\other directory on the GroupWise 6.5 Administrator CD.
Modify the Templates.path setting in the gwmonitor.cfg file to replace java/servlets with the path to the servlet root directory.
The gwmonitor.cfg file is located in the \novell\gwmonitor directory on the root of the Web server's drive or volume.
Add the Monitor jar files to the class path. On a NetWare server, the jar files are located in the java\lib directory. On a Windows NT/2000 server, the files are located in the \novell\java\lib directory.
The Monitor Agent and the Monitor Application are not supported on Windows XP. Windows XP is not a server platform.
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 (®, TM, 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.
You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
U.S. Patent Nos. 4,555,775; 4,580,218; 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; 6,216,123; D393,457 and U.S. Patents Pending.
Copyright © 2003 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, DirXML, and GroupWise are registered trademarks of Novell, Inc. in the United States and other countries.
eDirectory is a trademark of Novell, Inc.
All third-party products are the property of their respective owners.