Subscribe to notifications to be the first to know when there are changes to this guide! The official release of this guide is version 1.0.0 dated March 31, 2014. You will find this version number on the inside cover of the printed guide, or what is page i of the PDF version. Prior to version 1.0.0 there were numerous formatting and typographical changes to the book, but no substantial changes to content.
<h1>Changes since version 1.0.0</h1>
Setting the mode to user should be: ./gwadminutil installcfg -m user -u gwinstall -p mypass
Page 45 – add the following section.
<h2>Verify the location of the domain in ConsoleOne</h2>
If the path to your domain in the wpdomain.db is not generally the same as the details in the startup file, you may run into issues during the upgrade process, and the Administration Service may fail to initialize after the upgrade. Before you proceed with the upgrade, check the path in ConsoleOne on the server where GroupWise is running, and verify that the path shown is the same as the startup file. Since this is an in-place upgrade, you may wonder how you could possibly have the wrong path. It will be more likely on Windows than on Linux, but here are some possibilities:
<li>On Linux, your domain may be in a location such as <strong><em>/grpwise/domain</em></strong>, but you have created a mount point to facilitate ConsoleOne administration from both Linux and Windows. In that case, the path in ConsoleOne when viewed from Linux may look like <strong><em>/mnt/server/grpwise/domain</em></strong>. Make sure that the path in the domain directory is the same as the path in the startup file.</li>
<li>On Windows, you may have an issue if you frequently run ConsoleOne from a workstation and you have placed a mapped location from your workstation in Consoleone. For example g:\domain. On the Windows server, this might instead be d:\domain. Verify that the location in ConsoleOne is the same as the location in the startup file on the Windows server.</li>
At the end of the "Reenabling the GroupWise High Availability Agent section, add the following:
Edit the /etc/opt/novell/groupwise/gwha.allow file and add the user you have defined for your "hauser" user.
The POA Server must be able to access port 8500 of the WebAccess server in order for auto-refresh to occur.