January 24, 2012
The main emphasis of GroupWise 2012 is the enhancement of the GroupWise Windows client and WebAccess interfaces and functionality. Agent and administration enhancements are also included.
Windows Client Enhancements: Substantial functionality has been added to the GroupWise Windows client to bring new convenience to frequently used features and to add new functionality. When you modify existing appointments by changing the subject, body text, attachments, and so on, changes display automatically in recipients’ Calendars. However, when you modify the date, time, or place, recipients have the opportunity to re-accept the appointment. Appointment modifications also carry through to delegated appointments. The Multi-User Calendar now includes week, month, and year views, with adjustable columns. Scheduling recurring appointments is much easier, as is editing attached documents. Those who share folders can enjoy sharing an entire folder tree in a single operation. Name completion remembers who you selected last time and displays the most relevant users first. Integrations have been added for Skype and the Windows 7 taskbar. Speller technology has been upgraded to provide higher quality for all supported languages.
WebAccess Enhancements: Substantial functionality has been added to GroupWise WebAccess to bring it closer to the functionality available in the GroupWise Windows client. The Messages list can be sorted by any column, in ascending or descending order. Addressing messages is easier with the new Address Selector, rather than going into the Address Book. Photos can be added to contacts in your personal address books. Managing personal groups is easier. You can schedule recurring appointments. You can create HTML and plain text signatures, and the same signatures are available in WebAccess and in the Windows client. The Busy Search interface has been substantially improved.
WebAccess Mobile (New): GroupWise 2012 includes a new WebAccess interface designed for use on the Apple iPad. It enables you to access your GroupWise mailbox from your iPad with the standard iPad look and feel. You can compose, retract, read, reply to, and forward email messages, as well as check the status of sent items. You can schedule appointments for yourself and others, as well as accept, decline, and delegate appointments. You can create tasks for yourself and others, and view the Tasklist folder. Robust search capabilities are available.
Agent Enhancements: To simplify WebAccess administration, the WebAccess Agent has been eliminated. The WebAccess Application now communicates directly with the Post Office Agent. The Document Viewer Agent that was previously part of WebAccess is now an independent agent, so that its HTML conversion capabilities can be used by the Post Office Agent as well as by WebAccess. In addition, you can set up multiple Document Viewer Agents to provide improved responsiveness for WebAccess users. The Internet Agent handles undeliverable messages in a more convenient way for GroupWise users. The Calendar Publishing Host has configurable settings for an auto-refresh rate and a default published calendar view.
Administration Enhancements: The GroupWise Windows client software has been added to the downloaded Linux software image to simplify distribution of the Windows client. You can configure external users in external email systems so that they appear in GroupWise Busy Searches. You can lock the reply format options that are available to GroupWise Windows client users. You can disable the download of GroupWise Address Book updates to reduce growth of the post office database where the updates are stored. The WebAccess Application and GroupWise Monitor are no longer configured in ConsoleOne, but are configured solely through their configuration files.
IMPORTANT:If you are updating from a version of GroupWise earlier than GroupWise 8, review the latest GroupWise 8 Readme as well as this GroupWise 2012 Readme. The GroupWise 8 Readme lists GroupWise 8 enhancements compared with earlier GroupWise versions, as well as issues between GroupWise 8 and earlier GroupWise versions that are not issues between GroupWise 8 and GroupWise 2012. The GroupWise 2012 Readme does not include issues between GroupWise 2012 and GroupWise versions earlier than GroupWise 8. Such legacy issues are covered in the GroupWise 8 Readme and as TIDs in the Novell Support Knowledgebase.
GroupWise 2012 system requirements are listed in the GroupWise System Requirements
in the GroupWise 2012 Installation Guide. Ensure that the server where you plan to install GroupWise 2012 meets the system requirements.
IMPORTANT:If you are installing the GroupWise software in a cluster, refer to the GroupWise 2012 Interoperability Guide for cluster-specific installation instructions before starting to install the GroupWise 2012 software.
Make sure that ConsoleOne is installed on the Linux server where you want to install GroupWise.
In a terminal window, become root by entering su - and the root password.
Run the GroupWise Installation program at the root of the downloaded GroupWise 2012 software image:
./install
Select the language in which you want to run the GroupWise Installation program, then click .
The GroupWise Installation program lets you view the Readme, the Administrator Quick Start, and the Installation Guide before you start installing GroupWise.
On Linux, all available languages are included in the GroupWise RPMs, so all languages are always installed.
Click .
Follow the on-screen instructions to install the GroupWise 2012 software.
For detailed system installation and update instructions, and a complete list of new features, see the GroupWise 2012 Installation Guide.
The GroupWise 2012 Windows client is now included in the GroupWise 2012 Linux software image.
To install the Windows client from the Linux image:
On the Linux server where the GroupWise 2012 image is located, create a Samba share of the software distribution directory.
On the Windows workstation where you want to install the GroupWise client, map a drive to the Samba share.
Run setup.exe in the /opt/novell/groupwise/software/client directory, as described in Installing the GroupWise Clients
in the GroupWise 2012 Installation Guide.
For automated distribution of the GroupWise Windows client, SetupIP is also included in the Linux software image. For usage instructions, see Using GroupWise AutoUpdate and SetupIP to Distribute the GroupWise Windows Client
in Client
in the GroupWise 2012 Administration Guide.
IMPORTANT:If you are installing the GroupWise software in a cluster, refer to the GroupWise 2012 Interoperability Guide for cluster-specific installation instructions before starting to install the GroupWise 2012 software.
On the Windows server where you want to install GroupWise 2012, log in as an Admin equivalent to the eDirectory tree in which you are creating your GroupWise system.
Run setup.exe at the root of the downloaded GroupWise 2012 software image.
The GroupWise Installation program lets you view the Readme, the Administrator Quick Start, and the Installation Guide before you start installing GroupWise.
(Conditional) If prompted, select the language in which you want to run the GroupWise Installation program, then click .
The Windows GroupWise 2012 software image can be downloaded in a multilanguage version or an English-only version. When you install from the multilanguage version, all languages are always installed, regardless of the specific language that you select for running the Installation program.
Log in as an Admin equivalent to the eDirectory tree in which you are creating your GroupWise system.
Click , click to accept the License Agreement, then click to begin a standard installation.
The option is selected by default.
Click , then follow the on-screen instructions to set up your basic GroupWise system.
For detailed system installation and update instructions, and a complete list of new features, see the GroupWise 2012 Installation Guide.
At a Windows workstation that meets the GroupWise Windows client system requirements, run setup.exe from the root of the downloaded GroupWise 2012 software image.
or
If you have already copied the Windows client software to a Windows software distribution directory, run setup.exe from the root of the software distribution directory.
(Conditional) If prompted, select the language in which you want to run the GroupWise Installation program, then click .
The Windows GroupWise 2012 software image can be downloaded in a multilanguage version or an English-only version. When you install from the multilanguage version, you can select which languages you want to install for the GroupWise Windows client, regardless of the specific language that you select for running the Installation program.
Click to start the client Setup program.
(Conditional) If prompted, select the language in which you want to run the client Setup program, then click .
Follow the on-screen instructions to install the GroupWise 2012 Windows client software on your workstation.
Installation issues for individual GroupWise components are located under the heading for each component.
Platform-specific installation issues are listed in separate sections below. Installation issues for individual GroupWise components are located under the heading for each component.
If you install GroupWise on multiple platforms, or if you run multiple versions (for example, GroupWise 7 or 8 and GroupWise 2012 in the same GroupWise system), refer to GroupWise Version Compatibility
in the GroupWise 2012 Installation Guide to make sure that the combinations you are using are supported.
For example, you cannot run a GroupWise 2012 client against a GroupWise 8 or earlier post office. Earlier POAs cannot support later GroupWise clients. However, you can run a GroupWise 8 or earlier client against a GroupWise 2012 POA.
Also, you should not run the GroupWise 8 or earlier snap-ins to ConsoleOne to access GroupWise 2012 databases or eDirectory objects. You can use under to specify the required version of the ConsoleOne snap-ins for each domain as needed.
The WebAccess Application, Calendar Publishing Host 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.
When you install a Linux operating system for use with GroupWise, do not deselect the 32-bit runtime libraries. GroupWise requires the 32-bit runtime libraries.
When you install SUSE Linux Enterprise Server (SLES) for use with GroupWise, select the option. If you select the option, the GroupWise Installation program prompts you to install additional packages to meet GroupWise dependencies. Although you can manually install the additional packages after installing SLES, it is simpler to install SLES so that all GroupWise dependencies are automatically met.
When you run the Linux GroupWise Installation program and create a new GroupWise system in a virtual machine on SLES 11, the system creation process might crash with a Java exception. Configure the virtual machine with at least 4 GB of memory to avoid the problem.
When you install GroupWise on SLES 10 to a Xen guest, you might receive the following error message:
The current window is not large enough to run install. Please resize the window and run install again.
At present, the SLES 10 Xen console window does not report its dimensions properly. To work around this:
Make sure that SSH is enabled on the Xen guest.
Open an X terminal window on the SLES 10 Xen host, using the following command:
ssh -X root@guest_ip_address
Run the GroupWise Installation program from the Xen host.
If you need to uninstall and reinstall eDirectory on Open Enterprise Server for Linux, your GroupWise system is affected, because the GroupWise objects in eDirectory are lost when eDirectory is uninstalled. Therefore, you need to re-create the GroupWise objects in the new eDirectory tree.
(Conditional) If ConsoleOne has been uninstalled and reinstalled along with eDirectory, reinstall the GroupWise snap-ins to ConsoleOne, as described in Installing the GroupWise Administrator Snap-Ins to Linux ConsoleOne
in System
in the GroupWise 2012 Administration Guide.
In ConsoleOne, extend the eDirectory schema for GroupWise objects, as described in Check eDirectory Schema
in System
in the GroupWise 2012 Administration Guide.
Graft the GroupWise objects into the new eDirectory tree:
Access the primary GroupWise domain directory, as described in Select Domain
in System
in the GroupWise 2012 Administration Guide.
Graft your GroupWise domains and post offices into the new eDirectory tree, as described in Graft GroupWise Objects
in System
in the GroupWise 2012 Administration Guide.
For additional assistance, see TID 7004121, How to Graft GroupWise Objects,
in the Novell Support Knowledgebase.
Graft in GroupWise users and other GroupWise objects that belong to post offices.
Start all the GroupWise agents.
The GroupWise 2012 Windows client does not install successfully in a 64-bit environment when the following situations exist on the workstation:
An earlier GroupWise version is installed, then the 64-bit version of Office 2010 is installed, then GroupWise is updated to 2012.
The 32-bit version of Office 2007 or 2010 is installed, then an earlier GroupWise version is installed, then Office is updated to the 64-bit version of Office 2010, then GroupWise is updated to 2012.
To enable the GroupWise 2012 Windows client to function correctly in these situations, use either of the following workarounds:
Run the GroupWise Windows client Setup program a second time, selecting .
or
Uninstall the GroupWise Windows client, then reinstall it.
If you do not repair or reinstall the GroupWise Windows client in these situations, you encounter the following errors:
Either there is no default mail client or the current mail client cannot fulfill the messages request.
The ‘MAPI Session Handle’ of the Novell GroupWise ‘Object Request Broker’ could not be accessed. The address book cannot run.
GroupWise is not properly installed. The Address Book component could not be initialized.
If the GroupWise Windows client is originally installed by the Windows Administrator user, the Administrator user must also perform software updates. When the client is installed by the Administrator, the GroupWise client software cannot be updated by a regular user or a Windows Power User.
Windows Server 2003 is available only in a 32-bit version. Windows Server 2003 R3 is available in both 32-bit and 64-bit versions. The 32-bit version of Windows Server R2 is supported for use with GroupWise but the 64-bit version is not.
This is because the Novell Client, which is required in order to run the GroupWise Installation program, is not supported on the 64-bit version. See TID 3882364, Novell Client Support
in the Novell Support Knowledgebase.
Older versions of Norton Internet Security 2010 incorrectly identify GroupWise SetupIP as a virus and automatically remove it while it is trying to install the GroupWise Windows client on a workstation. Symantec indicates that this problem is resolved by running LiveUpdate to obtain the latest version of Norton Internet Security 2010. If you still encounter the problem, you must disable Norton Internet Security 2010 before SetupIP can successfully run on a workstation.
When filling in a field in ConsoleOne, you must specify the server name. You cannot use an IP address or DNS hostname.
Do not run a DirXML or Identity Manager driver earlier than version 3.5.2 against a GroupWise 2012 system. Older drivers are not compatible. You can download the latest version of the GroupWise Identity Manager driver from Novell Downloads.
For more information, see TID 7002222: “How is the GroupWise Driver Configured for Identity Manager?” in the Novell Support Knowledgebase.
The GroupWise 2012 product is comprised of many 32-bit services and applications. These pieces all run successfully on 64-bit hardware and operating systems.
The Identity Manager driver for GroupWise is also a 32-bit application. It requires either a 32-bit version of the Identity Manager engine, or a 32-bit version of the Identity Manager Remote Loader. For most installations, we recommend deploying the 64-bit version of the Identity Manager engine on a 64-bit system, and then deploying the 32-bit Identity Manager Remote Loader along with the Identity Manager driver for GroupWise on a 32-bit system as described here.
Set up a 32-bit server for use by the Identity Manager driver for GroupWise.
Install and configure the Identity Manager Remote Loader on the 32-bit server.
Follow the setup instructions for your version of Identity Manager:
Install and configure the Identity Manager driver for GroupWise on the same 32-bit server as the Identity Manager Remote Loader.
Follow the setup instructions for your version of the Identity Manager driver for GroupWise:
In this configuration, the Identity Manager Remote Loader on the 32-bit server communicates successfully with the Identity Manager engine and with the GroupWise agents that are both running on 64-bit servers.
If you run server-based antivirus 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.
Because of long-standing file lock issues with NFS, 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. In addition, you cannot use an NFS mount between Linux servers, for example when a POA needs access to a remote restore area or a remote document storage area.
Use a Samba mount if you want to use Windows ConsoleOne to access a domain located on a Linux server. For access between Linux servers, use a Samba mount or an NCP (Novell Core Protocol) mount. For instructions to set up a Samba mount or an NCP mount, see ConsoleOne Administration Tool
in System
in the GroupWise 2012 Administration Guide.
All GroupWise agents can be monitored through an SNMP management console. However, 64-bit Linux operating systems do not include the 32-bit components required for communication with the 32-bit GroupWise engine. Therefore, SNMP monitoring of GroupWise agents is not currently available on 64-bit Linux operating systems.
GroupWise 2012 does not include GWTSAFS. The supported versions of Novell Open Enterprise Server (OES) provide TSAFS, which is the preferred backup approach moving forward. For more information, see GroupWise Backup
in the Storage Management Services Administration Guide for your version of OES.
All directory names in paths to GroupWise domains and post offices should consist of lowercase letters. File names should also consist of lowercase letters. There are no length restrictions.
GroupWise 2012 administration on Linux does not include the following features that are available in GroupWise 2012 on Windows:
Import/Export utility in ConsoleOne
Document Properties Management feature in ConsoleOne
Versions of Novell eDirectory earlier than 8.8.4 are not supported on Windows Server 2008.
If you create a DSfW static group and then convert it to a GroupWise distribution list by assigning it to a post office, email messages addressed to the group are not delivered to GroupWise users. To correct the problem, synchronize the post office that owns the distribution list. In ConsoleOne, select the post office, then click .
If you use NSS volumes with quotas turned on, you must turn on quotas on all GroupWise directories. Otherwise, you receive No Disk Space errors.
The GroupWise 2012 WebAccess Application communicates directly with the POA through SOAP. Therefore, the POA that the WebAccess Application is configured to communicate with must have SOAP enabled in order for WebAccess to function. For appropriate security, SSL should be enabled on the SOAP connection.
For setup instructions, see the following sections in the GroupWise 2012 Administration Guide:
When you update the POA software to GroupWise 2012, updated view files are copied to the software distribution directory, but not to post offices. This maintains any customizations you might have made in the view files in post offices.
However, when each GroupWise 2012 POA starts for the first time, it copies the new view files from the software distribution directory to its post office. Therefore, if you have created custom view files with the same names as standard view files, you must create backup copies before starting the GroupWise 2012 POA, so that your customized view files are not lost when the post office view files are updated. After you start the GroupWise 2012 POA, restore your custom view files.
Occasionally, the POA is unable to copy the updated view files from the software distribution directory to its post office. When this happens, users receive a message that their view files are out of date. To resolve this, use the option under > > in ConsoleOne to update the post office view files from the software distribution directory. After you refresh the views, you must restore your customized view files to the post office.
Whenever the POA runs an audit report, it causes the MTA for the domain to restart. In a domain with a large number of post offices, these MTA restarts might become noticeable. This is working as designed, although improved functionality has been requested.
On Novell Open Enterprise Server and SUSE Linux Enterprise Server, services such as IMAP and IMAP SSL, which require port numbers below 1025, cannot be initiated or restarted after the GroupWise agents are running as a non-root user. To initiate or restart those services, you must manually stop the services and then restart the GroupWise agents.
By default, the maximum number of open files on a Linux server is 1024. This default might not be sufficient for a busy POA. Therefore, the POA initializes the maximum number of open files to 200000.
The default number of open files is typically acceptable for the other GroupWise agents.
If you run the Document Viewer Agent (DVA) as a user that is not running the X Window system, WebAccess 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 the DVA is running the X Window System and has a DISPLAY environment variable set so that the DVA can write to the local display. One way to accomplish this is to use the sux command to become root before you start the DVA.
The third-party viewer software used by the DVA 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
None.
The GroupWise 2012 Windows client uses a new speller engine technology named Hunspell. You should not notice any difference in the “spell-as-you-type” mode. However, there are a few features available in the old Spell Checker dialog box that are no longer available.
When the Spell Checker dialog box opens, it immediately begins spell checking.
You can no longer check spelling in a paragraph, sentence, or by word.
You can no longer add or manage multiple personal word lists from the Spell Checker dialog box. There is only one personal word list.
You must be in Online mode in order to change the settings under . If you change them in Caching mode, the modified settings are gone when you start GroupWise again.
You must be in Online mode in order to publish your main GroupWise Calendar. However, all personal calendars can be successfully published in Caching mode.
The URL for your main GroupWise Calendar that is generated in Caching mode is not recognizable to the Calendar Publishing Host. Therefore, if you publish your main GroupWise Calendar in Caching mode, it is not accessible to Internet users.
The recommended location for a Windows client user’s archive is on his or her local workstation.
Creating an archive on a network drive is supported in the following two configurations:
The Novell Map Network Drive feature of the Novell Client is used to map a network drive from the user’s workstation to a Novell Open Enterprise (OES) Linux server or a NetWare server where the archive is located.
The OES Linux server must use NSS volumes, and you must use NCP access with cross-protocol locks enabled in order to ensure safe client access to the archive. The setup for Windows client access to an OES Linux server is the same as for Windows ConsoleOne access to an OES server. For setup instructions, see Configuring the OES Linux Server for NCP Access from Windows
in ConsoleOne Administration Tool
in the GroupWise 2012 Administration Guide.
The Windows Map Network Drive feature is used to map a network drive from the user’s workstation to an OES Linux server using Novell CIFS access.
Other configurations, including Samba on a SUSE Linux Enterprise Server (SLES) server, are not currently supported.
GroupWise 8 Windows client users in Caching mode might see duplicate appointments from GroupWise 2012 users. The duplicate appointments occur if the GroupWise 2012 user modifies a recurring appointment. In Caching mode, the GroupWise 8 Windows client does not completely remove the original appointment from the Caching mailbox when the GroupWise 8 user accepts the modified appointment. As a result, both the original appointment and the modified appointment display in the GroupWise 8 Calendar.
This issue is resolved in GroupWise 8 Support Pack 3. You can also resolve it by updating GroupWise 8 users to GroupWise 2012.
If you use Novell Vibe with GroupWise, Vibe 3 or later is required for GroupWise 2012 integration.
Do not use iFolder with your GroupWise mailbox. For more information, see GroupWise Files Become Corrupted in an iFolder
in Troubleshooting
in the Novell iFolder Cross-Platform User Guide.
The issues involved with trying to use iFolder with GroupWise apply to using GroupWise with other directory synchronization applications such as Microsoft Offline Files. Do not use any of these applications with GroupWise.
If you are a member of the Power Users group when you install the GroupWise Windows client, you cannot immediately uninstall the GroupWise Windows client in the Control Panel. You must follow these steps to uninstall:
Remove yourself from the Power Users group.
Log out of Windows.
Log back in to Windows.
Uninstall the GroupWise Windows client.
If you install Outlook, then install GroupWise, then uninstall Outlook, you must reinstall GroupWise in order to restore MAPI, which is uninstalled along with Outlook. To avoid this problem, uninstall Outlook before you install GroupWise.
The GroupWise Windows client allows you to use Microsoft Word or OpenOffice.org as the text editor for composing messages. Microsoft Word 2010 is not currently supported, although earlier versions of Word are fully supported. Microsoft Word 2010 will be supported in a future GroupWise release.
Users of the JAWS screen reader can install the JAWS script available for GroupWise. Follow the instructions in the \client\jaws\gw_jaws_readme.txt file to install the JAWS script and other files on your workstation.
If you encounter Section 508 accessibility issues in the GroupWise 2012 Windows client, continue to use the GroupWise 8 Windows client. Section 508 accessibility issues will be addressed in the next major GroupWise release.
Novell is currently formulating a long-term GroupWise Mac/Linux client strategy. In the interim, the GroupWise 8 Mac/Linux client has been included in GroupWise 2012. Although no enhancements have been made to this client, it is completely compatible with a post office that has been updated to GroupWise 2012.
To improve the performance of the GroupWise Mac client:
Edit the following file:
GroupWise.app\Contents\Info.plist
Locate the following line:
<string>-Xms64m -Xmx256m</string>
Increase the default memory settings to:
<string>-Xms128m -Xmx512m</string>
Save the file, then restart the Mac client.
Attachments are not indexed by the Mac client in Caching mode. Therefore, in Caching mode, the Find feature does not locate words in attachments.
The module that provides attachment indexing is not currently available on the Mac. If you change to Online mode, the POA handles this indexing, so in Online mode, the Find feature can locate words in attachments.
The Mac/Linux client currently requires exclusive access to the sound device in your workstation. As a result, if Notify is turned on and configured to play a sound for notifications or alarms, other programs cannot use the sound device as long as Notify is running. Novell is awaiting a Sun Java fix in order to resolve this problem.
Depending on the Linux version on your workstation, you might need to install the following packages to resolve dependencies for the GroupWise Linux client:
Open Motif 2.2 or later
The GIMP Toolkit (GTK) 2 or later
libstdc++33 or later
Typically, these packages are part of your base Linux operating system.
In the GroupWise Linux client, if you display a Web page that includes Flash content, and if you have Adobe Flash Player 9 installed in your Web browser, the GroupWise Linux client might crash. Install the latest Service Pack for SUSE Linux Enterprise Desktop to resolve the problem. This Service Pack includes an updated version of Flash Player 9, where the problem no longer occurs.
By default, KDE applications like Konqueror do not launch the Linux GroupWise client when a mailto link is selected. To configure KDE applications to work with the GroupWise Linux client, see TID 7001213, Configuring KDE Applications to Launch GroupWise
in the Novell Support Knowledgebase.
If you run the Linux client in Caching mode as root, 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 are 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 required location for a Mac/Linux client user’s archive is on his or her local workstation. Creating an archive on a network drive is not currently supported.
When you are prompted to rebuild your mailbox, there is no progress indicator displayed during the rebuild process.
Occasionally, after you update the WebAccess software, the WebAccess URL displays a gray page instead of the WebAccess Login window. The problem occurs when you install multiple GroupWise Web applications in quick succession. It is possible for one Web application installation to be incomplete when the next one starts, which results in an unusable installation.
To prevent the problem, display each Web application in your Web browser before you install the next application:
http://web_server_address/gw/webacc http://web_server_address/gwcal/admin http://web_server_address/gwmon/gwmonitor
To resolve the problem after it has occurred:
Stop Tomcat.
|
OES 2 and SLES 10 |
rctomcat5 stop |
|
OES 11 and SLES 11 |
rctomcat6 stop |
|
Windows |
|
Remove the gw directory from the Tomcat installation.
|
Tomcat on OES 2: |
/var/opt/novell/tomcat5/webapps/gw |
|
Tomcat on SLES 10: |
/srv/www/tomcat5/base/webapps/gw |
|
Tomcat on OES 11 and SLES 11: |
/srv/tomcat6/webapps/gw |
|
Tomcat on Windows |
c:\Novell\tomcat6\webapps\gw |
Restart Tomcat.
|
OES 2 and SLES 10 |
rctomcat5 start |
|
OES 11 and SLES 11 |
rctomcat6 start |
|
Windows |
|
This re-creates the gw directory structure, which ensures that all files are correctly extracted from the gw.war file.
Starting with GroupWise 2012, you can share folder trees. In the GroupWise Windows client, the shared folder notification for the folder tree arrives as a single notification. In WebAccess, you receive a shared folder notification for each folder in the shared folder tree. In a large folder tree, this could result in a large number of shared folder notifications.
Multiple shared folder notifications for folder trees shared in GroupWise 2012 occur in GroupWise 8 in both the Windows client and in WebAccess.
If your mailbox is located in a post office where LDAP authentication is enabled, WebAccess seems to allow you to change your password, but your password is not actually changed. LDAP authentication uses your network password to access your GroupWise mailbox, rather than a GroupWise password. WebAccess cannot change your network password. You must change your network password outside of WebAccess.
In WebAccess, if you delete recipients from the , , or fields of an item after the item has been manually saved or auto-saved, and then send the item before the item is saved again, the deleted recipients still display in the properties of the sent item. However, the item is not actually sent to the deleted recipients.
WebPublisher is not part of GroupWise 2012. To continue using WebPublisher, you must maintain a GroupWise 8 domain with GroupWise 8 WebAccess to support your WebPublisher needs until comparable functionality becomes available in the future.
In GroupWise 8, you could customize the WebAccess interface. As a result of the substantial rearchitecting that took place for GroupWise 2012 WebAccess, this functionality is not currently available. It will be reinstated in a future release.
Starting in GroupWise 2012, the WebAccess Application communicates directly with the POA, and the WebAccess Agent is no longer needed. As a result, WebAccess cannot be monitored by GroupWise Monitor, because Monitor communicates with agents, not with Web applications.
If your Web server is configured to allow directory browsing, a user can 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.
During installation, the Linux WebAccess Installation program requires access to eDirectory by way of LDAP authentication. The LDAP Group object includes an option named , 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 WebAccess.
Unless you already have SSL set up, an easier alternative is to disable 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 and restart eDirectory again.
If you update an existing WebAccess installation to GroupWise 2012, you must use both the and options in the GroupWise Installation program in order for the GroupWise 2012 version of the WebAccess Application to be installed and configured correctly. If you do not run the option, you continue to run the old WebAccess Application, not the GroupWise 2012 version.
On Windows, WebAccess requires ISAPI support. ISAPI support is no longer installed by default when you install Windows Server 2008 and Internet Information Services (IIS). Ideally, you should select ISAPI support during the installation of IIS. However, if you are installing WebAccess on Windows Server 2008 and ISAPI support is not yet installed, you can add it after the fact.
In Windows Server Manager, expand , then right-click .
In the section, click .
Select , select and , then click .
(Conditional) If you installed the GroupWise WebAccess Application before you installed ISAPI support, reinstall the GroupWise WebAccess Application.
The WebAccess Installation program restarts Tomcat and IIS to put the ISAPI changes into effect.
Do not install WebAccess and Novell iManager on the same Windows 2003/2008 server. Because WebAccess installs and configures its own Tomcat and Jakarta connector, it must be installed on a server where Tomcat is not already in use by another program. If they are installed on the same server, either WebAccess or iManager does not work.
The --msstu switch replaces spaces with underscores (_) in the email address of the sender, but not in the addresses of recipients. This is working as designed.
During installation, the Linux Internet Agent Installation program requires access to eDirectory by way of LDAP authentication. The LDAP Group object includes an option named , 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 , 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 and restart eDirectory again.
None.
The Calendar Publishing Host Installation program prompts for the name of the Calendar Publishing Host. If you are updating an existing Calendar Publishing Host installation, the Calendar Publishing Host name must match the name provided in ConsoleOne under . The name must be specified identically in both places, including spacing and capitalization. If the names do not match, the Calendar Publishing Host cannot function.
If calendar items include attachments, the attachments are not published to the Web, but the calendar items themselves are still successfully published.
The Calendar Publishing Host and WebAccess share a substantial amount of functionality. The following WebAccess issues also pertain to the Calendar Publishing Host:
None.
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 want to enable SSL by using the Monitor Agent /httpssl and /httpcertfile switches, the certificate file must be in PEM format. This differs from the other GroupWise agents, which take a .b64 public certificate file and a .key private key file. The PEM format combines the certificate and key in a single file.
None.
Monitor and WebAccess share a substantial amount of functionality. The following WebAccess issues also pertain to Monitor:
Do not use double-byte characters in directory names and file names.
Do not use double-byte characters in user 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 you start an individual GroupWise agent in a language other than English with a command like the following:
./gwmta --show @provo.mta
you must turn off UTF-8 in order for the agent server console to display properly.
To turn off UTF-8 for the Linux server:
In YaST, click .
Deselect , then click .
Click to save the new setting, then reboot the Linux server.
If you do not want to turn off UTF-8 for the server, you can use the grpwise script to start the agents, because it turns off UTF-8 automatically when it starts the agents. However, by default, the grpwise script starts the agents as daemons, without the user interface provided by the --show switch. To configure the grpwise script to start the agents with a user interface, see Starting the Linux Agents as Daemons
in Installing GroupWise Agents
in the GroupWise 2012 Installation Guide.
On Windows, Mozilla-based browsers such as Firefox do not save extended character file names correctly, even though the file name displays correctly in the Save As dialog box. This is a browser problem, not a GroupWise problem. There is no workaround.
In Safari on Macintosh, extended character file names are not interpreted correctly. As a workaround, use Firefox instead of Safari if you receive attachments with extended character file names. This is a browser problem, not a GroupWise problem.
On Windows, Mozilla-based browsers such as Firefox do not handle extended character file names correctly for published calendars. This is a browser problem, not a GroupWise problem. There is no workaround.
In Safari on Macintosh, extended character file names are not interpreted correctly. As a workaround, use Firefox instead of Safari to display published calendars. This is a browser problem, not a GroupWise problem.
In the Windows client, you can select Turkish as your interface language, but the online help still displays in English. In the Mac/Linux client, Turkish is not available. Turkish will be fully supported in a future release.
Hebrew was dropped from the list of supported languages in GroupWise 8 Support Pack 1.
If you run the Linux client on SUSE Linux Enterprise Desktop (SLED) 11, Chinese, Japanese, and Korean characters display incorrectly. You must meet the Linux client system requirements and install SLED 11 Service Pack 1 in order for double-byte characters to display correctly.
If you run the Linux GroupWise agents with an agent console interface in languages other than English, the 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 , then double-click .
Select the language you are running the agents in, then click .
Deselect , then click .
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 usually 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 Mac/Linux 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.
|
Language |
Character Set Code |
|---|---|
|
French |
fr_FR |
|
German |
de_DE |
|
Portuguese |
pt_BR |
|
Spanish |
es_ES |
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.
When you update WebAccess, the Calendar Publishing Host, or Monitor, if you install the multilanguage version over the English-only version or vice versa, you receive the following message:
The feature you are trying to use is on a network resource that is unavailable.
Click OK to try again, or enter an alternate path to a folder containing the installation package ‘component.msi’ in the box below.
Simply click . This is an automatic InstallShield message. The GroupWise Installation program correctly handles the situation without your assistance.
Setting ShowDialogs=No in the setup.cfg file does not suppress the interface language dialog box that appears when you install the GroupWise Windows client from the multilanguage GroupWise software image. The interface language dialog box is displayed by InstallShield to ask what language the GroupWise Client Setup program should run in. It does not affect which client languages are installed by the Client Setup program.
To suppress the interface language dialog box:
Edit the following file in a text editor:
software_distribution_directory\client\win32\setup.ini
Locate the following line:
EnableLangDia=Y
Change Y to N.
Save the setup.ini file, then exit the text editor.
The QuickCorrect feature in the GroupWise Windows client does not currently work for double-byte languages (Arabic, Chinese, Japanese, and Korean).
Files with certain extended and double-byte characters in their file names cannot be dragged into Novell Vibe folders. The problem is resolved in Novell Vibe 3.3.
On a Windows server running the Spanish version of Windows, the GWCSRGEN utility does not start successfully. Use the English version of GWCSRGEN instead. GWCSRGEN runs successfully on other language versions of Windows.
None.
When you start the Linux POA, the Linux MTA, and the Linux Internet Agent by using the ‑‑show switch to display a GUI user interface, if the agents are running as a non-root user, clicking 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.
None.
All GroupWise 2012 documentation is available at the GroupWise 2012 Documentation Web site:
In addition to the GroupWise product documentation, the following resources provide additional information about GroupWise 2012:
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 the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2012 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.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.