GroupWise System Administration

From CoolSolutionsWiki

6.1 GroupWise Administration Recommended Requirements
Requirements Description
Operating System SUSE Linux 9.x
SUSE Linux Enterprise Server 9
Novell Linux Desktop
Windows 200x, XP Professional
eDirectoryTM 8.7 or later, plus the latest Support Pack
ConsoleOne® 1.3.6 or later
Software Distribution Directories 500 MB for all GroupWise components
Linux Only The X Window System is required by the GUI GroupWise Installation program and ConsoleOne. The Installation Advisor, and Setup Advisor step you through the process of creating a new GroupWise system. A text-based Installation program is also available.
Windows Only Novell ClientTM on any administrator Windows machine where you run ConsoleOne or the GroupWise Installation program.
6.2 ConsoleOne
6.2.1 Use only the current version of ConsoleOne and the GroupWise 7 Snapins. To ensure that only ConsoleOne is only used for administration, disable NWAdmin GroupWise Administration on upgraded systems.
6.2.2 Novell recommends running ConsoleOne on the same server as the GroupWise domain when the domain is on a SLES (not OES) Linux server. This may be accomplished with either local access to the console, or using redirected X.
6.2.3 If Groupwise is running on an OES Linux server, and the database is on a NSS Volume the following steps should be taken to ensure that the Domain database will not get corrupted:
6.2.3.1 Recommended settings for the Novell client:
1. Right-click on red N letter in a right corner of the system tray and select "Novell Client properties ..."
2. Click on Advance settings.
3. Scroll down and find "File Caching" item -> set it to Off.
4. Scroll down and find "File Caching on Exclusively opened files" -> set it to Off.
5. Scroll down and find "File Commit" -> set it to On
6. If asked, reboot the workstation.
6.2.3.2 Settings on the OES Server
1. Turn on locking through ncpcon using one of the following methods:
# ncpcon <enter>
<SERVERNAME>: set cross_protocol_locks = 1
<SERVERNAME>: exit
  • Or turn on locking by modifying /etc/opt/novell/ncpserv.conf
Add "CROSS_PROTOCOL_LOCKS 1" to the file.
2. Following these to steps to enable OES Linux to honor advisory locks across different protocols.
  • Add the option: Inherit_POSIX_Permissions to each volume.
Edit: /etc/opt/novell/ncpserv.conf
VOLUME <ncp volume name> <volume mount point> Inherit_POSIX_Permissions
  • Reboot server to activate these settings.
6.2.4 You may run ConsoleOne from a Windows against a domain on an OES Linux server by taking the following steps:
6.2.4.1 Recommended settings for the Novell client:
1. Right-click on red N letter in a right corner of the system tray and select "Novell Client properties ..."
2. Click on Advance settings.
3. Scroll down and find "File Caching" item -> set it to Off.
4. Scroll down and find "File Caching on Exclusively opened files" -> set it to Off.
5. Scroll down and find "File Commit" -> set it to On
6. If asked, reboot the workstation.
6.2.4.2 Settings on the OES Server
1. Turn on locking through ncpcon using one of the following methods:
# ncpcon <enter>
<SERVERNAME>: set cross_protocol_locks = 1
<SERVERNAME>: exit
  • Or turn on locking by modifying /etc/opt/novell/ncpserv.conf
Add "CROSS_PROTOCOL_LOCKS 1" to the file.
2. Following these to steps to enable OES Linux to honor advisory locks across different protocols.
  • Add the option: Inherit_POSIX_Permissions to each volume.
Edit: /etc/opt/novell/ncpserv.conf
VOLUME <ncp volume name> <volume mount point> Inherit_POSIX_Permissions
  • Reboot server to activate these settings.
3. The Windows workstation must use the Novell Client for Windows to map a drive to the OES server
  • If you are running the MTA as root at the server, the Windows client can have the root privilege. If you are running the MTA as non-root, make sure the windows client has the same privilege or rights.
6.3 Software Installation and Patching
6.3.1 Keep all GroupWise Software current with the most recent patch.
6.3.2 If you need to run a Novell GroupWise Hot Patch in order to resolve a specific issue on a server, you must update all of the components on that specific server. This is important because many GroupWise server components share common files, i.e. the GroupWise Engine. Not updating all GroupWise components on a specific server will cause problems on that server.
6.3.3 Software Distribution Directories
6.3.3.1 Follow these guidelines when dealing with software distribution directories (SDD)s:
  • Create a master SDD containing a fully patched and installable Novell GroupWise CD. No post offices should be assigned to use this SDD. This will allow the system administrator to update this directory without inadvertently triggering the Client Auto-Update procedure.
  • Burn a copy of the master SDD to CD for backup purposes. A fully patched and installable GroupWise 7 CD may prove to be extremely handy, whether for restoring SDDs or for creating new ones at remote sites.
  • Place SDDs on application servers rather than mail servers. This will simplify server licensing, backup procedures, and application delivery. Be sure to grant users sufficient access (read and file scan) to the client subdirectory so they can run setup at will.
6.3.3.2 Follow this procedure when applying service packs to SDDs:
  • Make a backup copy of the SDD.
  • Apply the patch to the backup copy of the SDD.
  • Copy this patched backup copy of your SDD to the production SDD. Either rename or backup the original.
  • Once the local SDD is patched, use this directory to distribute the new software (i.e., administration, agents, client software).
6.4 Installing Service Packs
6.4.1 Importance of Installing Service Packs
In order to keep your Novell GroupWise system healthy and running at efficient and acceptable levels, Novell recommends that GroupWise Administrators apply Support Packs as soon as feasible in their environment (given corporate policies, testing requirements, etc)
In the event that you need to contact Novell Technical Services to resolve a problem that you suspect is a bug, you should verify that the problem still occurs with the most current released patch since patches provide numerous bug fixes and Novell will add new fixes only to current code. Installing the latest SP prior to opening a Service Request will save you time during troubleshooting with Novell, and in some cases will resolve the issue.
6.4.2 Procedures to Installing Service Packs
  • Download and Apply Service Pack to a test copy of your GroupWise Software Distribution Directory
  • Test Administrative (snapins), Server (POA, MTA, WebAccess, GWIA, etc.), and Client software in your lab before deploying patch.
  • Pilot patched software on representative domain and post office for a few days.
  • Rollout patched server software first.
  • Rollout client software soon after patching server.
6.4.2.1 Patching Administrative files (snapins)
  • Apply administration upgrades and patches to every workstation where Novell GroupWise administration is run. This ensures that only the latest GroupWise Administrator ConsoleOne snap-ins are used.
  • Enable the "Lock Out Older GroupWise Administration Snap-Ins" option (Tools > GroupWise System Operations > System Preferences > Admin Lockout Settings) to prevent administrators from using older GroupWise ConsoleOne snap-ins for accessing GroupWise objects in eDirectory.
6.4.2.2 Patching GroupWise Server Files
Two options are available for patching GroupWise Server Components
  • ZENworks for Servers (recommended)
  • Individual server installation wizards
6.4.2.3 Patching GroupWise Client Files
The following is a list of available GroupWise Client update options in order of preference
  • ZENworks for Desktops
  • GroupWise Auto Update