April 16, 2013
GroupWise 2012 Support Pack 2 provides enhancements for both administrators and end users.
Windows Server 2012 is now supported.
The GroupWise/Exchange coexistence solution integrates GroupWise and Exchange to provide users of both email systems with unified address book lookups and free/busy calendar searching. For setup instructions, see the GroupWise/Exchange Coexistence Guide.
The new role resource type represents a position in an organization that can be reassigned from one owner to the next. As owners change, the role resource mailbox retains all information associated with the role. Unlike general resources and place resources, role resources are included in a Reply to All.
Windows 8 and Internet Explorer 10 are now supported.
GroupWise 2012 SP2 includes all bug fixes that are available in GroupWise 2012 SP1 and HP1. For a list of the bugs that have been fixed in GroupWise 2012 SP2, see the GroupWise 2012 SP2 Bug Fix List.
For information about the documentation updates that have been made since GroupWise 2012 SP1, see Section 17.0, GroupWise Documentation.
GroupWise 2012 system requirements are listed in GroupWise System Requirements
in GroupWise Product Overview
in the GroupWise 2012 Installation 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 SP2 software.
Download the GroupWise 2012 SP2 Administration compressed tar file to a temporary directory on your Linux server:
gw12.0.2_full_linux_en.tar.gz gw12.0.2_full_linux_multi.tar.gz
In a terminal window at your Linux server, change to the temporary directory, then use the following command to uncompress and untar the downloaded file:
tar -xvzf file_name.tar.gz
The files are extracted to the root of the directory.
Become root by entering su - and the root password.
In the directory where you extracted the GroupWise 2012 SP2 files, use the following command to start the GroupWise Installation program:
./install
Click .
Follow the on-screen instructions to install the GroupWise 2012 SP2 software.
When you install a Support Pack, you can streamline the update process by using the option to install the updated RPM for each agent. Typically, you do not need to use the option after installing updated agent software, if the agent configuration has not changed since the previous installation. If you encounter a problem starting the updated agent, use the option to update the configuration information for the agent.
Update the primary domain first. Start the MTA in the primary domain. Then update secondary domains, followed by the post offices in each domain. Start each MTA and POA for each domain and post office. Then update the other GroupWise agents.
For additional installation instructions, see the GroupWise 2012 Installation Guide.
The GroupWise Windows client is included in the GroupWise 2012 SP2 Linux software image.
To install the Windows client from the Linux image:
On the Linux server where the GroupWise 2012 SP2 image is located, create a Samba share of the software distribution directory (/opt/novell/groupwise/software).
On the Windows workstation where you want to install the GroupWise client, map a drive to the Samba share.
Run setup.exe in the \\linux_server\samba_share\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 SP2 software.
Download the Windows GroupWise 2012 SP2 compressed executable file to a temporary directory on your Windows server:
gw12.0.2_full_win_en.zip gw12.0.2_full_win_multi.zip
Extract the .zip file into a directory at the root of your local drive or to a network server drive that can handle long path names
The compressed file contains directory paths that could exceed DOS limits.
In Windows Explorer, browse to the directory where you extracted the GroupWise 2012 SP2 file.
Double-click setup.exe to run the GroupWise Installation program.
Click .
Follow the on-screen instructions to install the GroupWise 2012 SP2 software.
When you install a Support Pack, you can streamline the update process by copying the updated agent software files but not configuring the agents again. In the Installation program, select on the Installation Path page when you install the POA, the MTA, and the GWIA.
Update the primary domain first. Start the MTA in the primary domain. Then update secondary domains, followed by the post offices in each domain. Start each MTA and POA for each domain and post office. Then update the other GroupWise agents.
For additional instructions, refer to the GroupWise 2012 Installation Guide on the GroupWise 2012 Documentation Web site.
Download the GroupWise 2012 SP2 Windows Client compressed executable file to a temporary directory on your workstation:
gw12.0.2_client_win_en.exe gw12.0.2_client_win_multi.exe
In Windows Explorer, browse to the directory where you downloaded the GroupWise 2012 SP2 Client compressed executable file.
Double-click the downloaded file to extract the GroupWise client software and start the GroupWise client Setup program.
Follow the on-screen instructions to install the GroupWise 2012 SP2 client software on your workstation.
The GroupWise Setup Progress dialog box displays a green bar during the installation process. Occasionally, long pauses might occur. You can also check the activity of the GroupWise client Setup program by viewing the tab of the Windows Task Manager to observe CPU usage.
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.
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. There are two workarounds:
Configure the virtual machine with at least 4 GB of memory to avoid the problem.
In ConsoleOne, delete the POA object that was created during GroupWise system creation, then create a new POA object. Install and configure the agents independent from creating the GroupWise system.
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.
GroupWise 2012 SP2 supports Windows Server 2012, but Novell eDirectory is not yet supported on Windows Server 2012. The updated eDirectory version is expected to release in mid-2013.
In the meantime, the GroupWise 2012 SP2 agents can run on Windows Server 2012, but your eDirectory installation must remain on an earlier version of Windows or on Linux.
The GroupWise Windows client is a 32-bit application. Microsoft indicates that it is not advisable to run 64-bit Office applications that use 64-bit MAPI in the same environment with 32-bit applications that use 32-bit MAPI. For background information, refer to Building MAPI Applications on 32-Bit and 64-Bit Platforms.
If you need to run the GroupWise client in the same environment with Microsoft Office, the 32-bit version of Office is recommended. If you prefer the 64-bit version of Office, GroupWise and Office do coexist successfully in the majority of environments.
Very occasionally, you might encounter the following errors when you start the GroupWise client when 64-bit Office is also installed:
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. Please run GroupWise Setup, or contact your system administrator.
To enable the GroupWise client to function correctly in these situations, use either of the following workarounds:
Run the GroupWise client Setup program a second time, selecting .
or
Uninstall the GroupWise client, then reinstall it.
Similarly, you might very occasionally encounter the following errors if you start 64-bit Outlook:
Either there is no default mail client or the current mail client cannot fulfill the messages request. Please run Microsoft Outlook and set it as the default mail client.
Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. An unexpected error has occurred. MAPI was unable to load the information service gwmsp1.dll. Be sure the service is correctly installed and configured.
To enable Outlook to start correctly, do not select the Novell GroupWise Profile that is installed with the GroupWise Windows client. Instead, create a new profile as you start Outlook, so that the profile is compatible with 64-bit Outlook.
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.
Starting in GroupWise 2012 SP1, you cannot launch the GroupWise client directly from the client Setup program. You must exit the client Setup program, then launch the GroupWise client.
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.
In earlier versions of GroupWise, the GroupWise Generate CSR Utility (GWCSRGEN) created a certification signing request (CSR) that returned an MD5 certificate. The MD5 algorithm is now considered compromised and should not be used.
Starting in GroupWise 2012 SP1, GWCSRGEN creates a CSR that returns an SHA-1 certificate. The SHA-1 algorithm is more secure than MD5, but also has some potential weaknesses.
For the most stringent security needs, GWCSRGEN should no longer be used for generating CSRs. For suggested alternatives, see Generating a Certificate Signing Request
in Security Administration
in the GroupWise 2012 Administration Guide.
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 must configure it so that it does not scan GroupWise directory structures such as domains and post offices. Running antivirus software on GroupWise directory structures creates file locking conflicts with the GroupWise agents, which prevents email and administration messages from being delivered.
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.
However, on Open Enterprise Server (OES), when you create an NSS volume, the volume name automatically appears in all uppercase in the path name. Because the use of lowercase letters in directory names is recommended for convenience, but is not required by any GroupWise program, this behavior on OES does not present any problems for GroupWise. You simply need to remember to type the uppercase letters when you specify the path name on OES.
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 the GWIA receives an incoming message from the Internet, it creates a MIME version of the message that includes the message and any attached files. This doubles the size of the message.
You can restrict message size at the GWIA, the MTA, and the POA. The message size that you set at the GWIA determines the maximum size of messages that are allowed into your GroupWise system. However, because of the way that the GWIA creates the MIME version of incoming messages, message size limits at the MTA and POA must be two to three times the size set at the GWIA. Otherwise, some messages can successfully enter your GroupWise system at the GWIA, but they cannot be delivered because of the size limits set at the MTA or the POA.
When such a delivery failure occurs, no undeliverable message is sent, so no one is notified of the problem.
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
GroupWise 2012 SP1 included a fix for the problem where the Windows POA terminates unexpectedly and repeatedly when GroupWise Windows client users connect from outside of the firewall on the external client/server port. If you continue to see the problem after installing Support Pack 1 and later versions, add the /udpslap switch to the POA startup file. This switch is designed specifically to alleviate this particular connection issue.
If you run the Document Viewer Agent (DVA) on Windows Server 2008, and if you have not configured it to run as the Administrator user, you must use the /home switch in the gwdva.dva file to specify a directory where the DVA user can write files. You might want to create a c:\novell\groupwise\gwdva directory for this purpose.
The setupip.exe and writeip.exe SetupIP programs are falsely identified as viruses by Norton Internet Security 2010. As a workaround, configure Norton Internet Security 2010 to ignore these files.
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.
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.
The first time you prime a new Caching mailbox, the GroupWise client might terminate at the end of the priming process. However, the Caching mailbox is successfully created. Restart the client to access the new Caching mailbox.
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.
Do not use Filr with your GroupWise mailbox. As with other directory synchronization applications, Filr does not respect the database locking mechanism employed by GroupWise. Creating a copy of a GroupWise database while it is in use can result in a corrupted database. This applies to your Caching mailbox and to your archive.
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 a future GroupWise release.
GroupWise 2012 does not include the Mac/Linux Client. The GroupWise 8 Mac/Linux client is compatible with GroupWise 2012. The GroupWise 8 SP2 HP 4 Mac client includes bug fixes for improved performance with GroupWise 2012.
The new indexable file types of PDF, OpenOffice.org, and Microsoft Office 2007 are not indexed by the Mac client in Caching mode. The module that provides this functionality is not currently available on Mac. If you change to Online mode, the POA handles this indexing, so you can find these documents in Online mode.
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.
In GroupWise 8 WebAccess, you needed to manually set the WebAccess time zone if you wanted WebAccess to use a time zone that was different from the time zone of your post office. In GroupWise 2012, the WebAccess time zone automatically matches the time zone of your workstation. To change the WebAccess time zone, change your workstation time zone.
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: |
/var/opt/novell/tomcat6/webapps/gw |
|
Tomcat on SLES 11: |
/usr/share/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.
In the GroupWise Windows client, you can right-click a Calendar folder, then click to display the Calendar of a proxy user as a sub-calendar in your own Calendar.
In WebAccess, you cannot create a Proxy Calendar, and Proxy Calendars created in the Windows client do not display in WebAccess. In WebAccess, you must proxy to the other user’s mailbox in order to view that user’s Calendar.
Android tablets that run Android 3.2 or later are supported for use with WebAccess Mobile.
Many Android tablets that run Android 4.0 work well with WebAccess Mobile. However, some Android 4.0 tablets have device/OS-specific issues that might cause display, usability, or functionality challenges. Many of these issues have easy workarounds. However, some Android 4.0 tablets simply do not function as expected with WebAccess Mobile. Keeping device firmware updates current can help mitigate some of these challenges while Novell works to fully support Android 4.0.
On a Samsung Galaxy tablet, the Quickoffice HD location for attaching documents and text files might not be available, depending on the specific model of the Galaxy tablet. You can attach files in WebAccess Mobile only from locations that are available on your particular tablet.
PDF files cannot be displayed on ASUS Transformer TF101 and TF102 tablets. These tablets do not currently have a plug-in for displaying PDF files. As a result, the PDF file is downloaded to the tablet rather than being immediately displayed. To display a PDF file after it has been downloaded, use a native application like MyLibrary or Polaris Office to view it.
ASUS tablets have browser display issues in WebAccess Mobile, including:
Pages occasionally do not load.
Pages might be very slow to load.
The browser quits. When it is relaunched, the browser does not display the pages and tabs that were originally displayed when it quit.
Typing text in the browser is very slow.
As a workaround:
Enter the following text in the address bar:
about:debug
In the browser menu, click .
Deselect .
Repeat this procedure each time you restart the tablet.
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.
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.
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.
In Internet Explorer 6 and 7, WebAccess relies on Google Chrome Frame in order to provide a variety of advanced features. If a user’s workstation does not have Google Chrome Frame, the user is prompted to download and install it from the Internet. If your WebAccess users do not have access to the Internet, you can make Google Chrome Frame available locally.
Download the Google Chrome Frame installer from the following Web site:
http://www.google.com/chromeframe
The Google Chrome Frame installer is named GoogleChromeframeStandaloneEnterprise.msi.
Place the .msi file under the document root directory on your Web server.
Test the location by viewing the URL for the file in your Web browser.
Specify the URL for the Google Chrome Frame installer in the WebAccess configuration file:
Edit the webacc.cfg file in an ASCII text editor.
Add the following line at the bottom of the file:
GoogleChromeFrame.url=installer_location
Replace installer_location with the URL that you tested in Step 3.
Save the file and exit the text editor.
Restart Tomcat.
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 issue also pertains to the Calendar Publishing Host:
None.
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 issue also pertains to Monitor:
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.
The GroupWise/Exchange coexistence solution is available starting in GroupWise 2012 SP2.
If you have been using the legacy GroupWise Gateway for Microsoft Exchange or another method for connecting your GroupWise and Exchange systems, you must consider how to handle information that has already been synchronized before you implement the coexistence solution provided in GroupWise 2012 SP2. For a list of considerations, see Appendix A, Preexisting GroupWise/Exchange Synchronization
in the GroupWise/Exchange Coexistence Guide.
When you enable address book synchronization in ConsoleOne, you receive the following notification:
Exchange address book synchronization requires its own license. If you enable Exchange address book synchronization, your GroupWise system might be subject to additional licensing fees. We invite you to contact your Novell representative, reseller, or partner to learn more about this feature or for pricing and licensing information.
Make sure that you understand the licensing fees that might apply before you implement address book synchronization.
After address book synchronization, Exchange objects are organized under an External Domain object, which is located under the GroupWise System object in ConsoleOne. The original Active Directory context of each object is represented by an External Post Office object. The External Post Office object cannot have the same name as the External Domain object.
If you want your GroupWise system and your Exchange system to have the same Internet domain name (for example, novell.com), some specialized configuration is required. For background information, see Configure Exchange 2012 to Route Messages for a Shared Address Space.
Edit the Accepted Domain for the Organization Hub Transport Accepted domain.
Change it to an Internal Relay Domain.
Create a new Send Connector.
Configure it to relay by setting its SMTP Address Space to the GWIA IP address or DNS hostname.
Configure the MX record for the shared Internet domain name to point to the Exchange system, which then forwards non-local addresses to the GWIA in the GroupWise system.
During the synchronization process, GroupWise and Exchange object names become part of email addresses. The space character is not valid in email addresses. As a result, objects with spaces in their names do not synchronize because their email addresses are invalid.
Exchange prevents the creation of invalid email addresses. For GroupWise, you must set up a preferred email ID for each object that would, by default, have an invalid email address. For more information, see Object Naming Consideration
in GroupWise/Exchange Address Book Synchronization
in the GroupWise/Exchange Coexistence Guide.
The current version of the GroupWise Free/Busy service does not provide free/busy information for groups.
If you use the Scheduling Assistant in Outlook, you see free/busy information from GroupWise users in a group only if you expand the group.
In Outlook WebAccess, you cannot expand the group. Therefore, you cannot see free/busy information for GroupWise users in the group, and you might get an error.
The following GroupWise send options were supported by the legacy GroupWise Exchange Gateway but are not supported in the GroupWise/Exchange coexistence solution:
Classification (Normal, Proprietary, Confidential, Secret, Top Secret, For Your Eyes Only)
Reply Requested (When Convenient, With Days)
Delay Delivery
Notify Recipients
If users select these send options in GroupWise, the options have no effect on messages sent to Exchange users.
If the passwords for the Free/Busy service user accounts that access the GroupWise and Exchange systems change for any reason, the Free/Busy service can no longer obtain free/busy information. Ideally, set up these user accounts to be exempt from password expiration rules. If these account passwords need to change for any reason, run the Free/Busy Configurator to provide the current passwords to the Free/Busy service.
In the Outlook Scheduling Assistant, GroupWise users’ schedules are correctly listed as you add attendees to the appointment. However, the Suggested Times box cannot determine the availability of GroupWise users.
GroupWise cannot correctly identify a country code in a phone number when there is no delimiter between the country code and the rest of the phone number. For example, if +49 is the country code, and if you enter a contact phone number as +491234567890, an SMS text message to that contact is undeliverable. If you put a space or a dash between the country code and the phone number, such as +49 1234567890, the SMS text message is successfully delivered.
Sending SMS text messages from GroupWise is free of charge for senders. However, in some European countries, recipients must pay a small charge when they receive SMS text messages.
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 with the user interface provided by the --show switch. However, by default, the grpwise script starts the agents as daemons, without the user interface. To configure the grpwise script to start the agents with the 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 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.
On some tablets, garbage characters display in the WebAccess Mobile Login window instead of readable text. This problem tends to occur on older devices, even when they are running a supported tablet operating system.
On tablets, the process for inputting double-byte characters varies. The Name Completion feature in WebAccess Mobile does not work correctly when recipient names include double-byte characters.
Two workarounds are available:
Click , then browse to the recipient.
Type the first few characters of the user’s email address. Email addresses do not include double-byte characters. Therefore, the Name Completion feature can always complete the email address.
On some tablets, when you select a file with double-byte characters in the file name, the characters display as garbage characters. This is a problem with the device.
In WebAccess, the online help does not display correctly in Arabic. To correct the problem, enable Compatibility View by clicking .
Hebrew was dropped from the list of supported languages in GroupWise 8 SP1.
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.
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.
Starting in Firefox 19, Firefox includes a built-in PDF viewer by default. In earlier versions, Adobe Acrobat has been used with Firefox.
The built-in Firefox PDF viewer does not include the ability to expand and collapse the table of contents bookmarks in the left panel of PDF guides. In a large GroupWise guide, this expand/collapse functionality can be very useful.
To configure Firefox to use Adobe Acrobat as it did in previous versions:
Click .
In field, select , then click .
GroupWise 2012 SP2 includes all bug fixes that are available in GroupWise 2012 SP1 and HP1. For a list of the bugs that have been fixed in GroupWise 2012 SP2, see the GroupWise 2012 SP2 Bug Fix List.
All GroupWise 2012 documentation is available at the GroupWise 2012 Documentation Web site.
Each GroupWise 2012 guide lists the documentation updates that have occurred for Support Pack 2:
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-2013 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.