Group. Wise 6. 5 Best Practices Guide. Group. Wise 6. 5 Best Practices Guideprepared for Group. Wise Administratorscontents. Download the pdf version of the Group. Wise 6. 5 Best Practices Guide here. Introduction. This guide serves as a set of considerations and guidelines for Novell? Group. Wise? administrators.
![Groupwise 5.5 (50-User English) Groupwise 5.5 (50-User English)](http://s2.dmcdn.net/Nlm1V/280x157-DaS.jpg)
It is not a comprehensive instruction set, and it is not intended to replace product manuals. Administrators using this guide should consult product documentation, technical information documents (TIDs), and online help for further instruction regarding each of the guidelines offered here. It is intended that this will be a ? We recognize that administrators are often restricted in the changes they may make to their Group. Wise Systems. Depending on the state of the existing Novell Group. Wise system, some of the practices outlined in this document may be difficult or cost- ineffective to implement.
OnDemand Services 1.5''''' (128 bit)' (50 user)''''' 1.5 ' ' NDS AS: 3.0 ' '. Novell Small Business Suite 5.1 ENGLISH / SPANISH: 5.1: GroupWise for Small Bis: 14 '. Subscriptions Forum. News (NNTP) Interface; Web (HTML).
- Buy Novell's GroupWise 5.5 User's Handbook on Amazon.com FREE SHIPPING on qualified orders.
- Novel Groupwise 6 5. Novell GroupWise 6.5 User's. Working with Folders on page 44 Undeleting Items in the Trash on page 50 Using Proxy to Manage Other Mailboxes on page 50 Using GroupWise Libraries on.
Novell GroupWise 5.5 Administration Part 3 - System Maintenance from Serebra Learning Corporation in Vancouver BC novell groupwise 55 administration Training. Create a GroupWise nickname for a user using NetWare Administrator. Approximately 15 MB for English plus one other language. GroupWise 6.5 system. there is no way to control the size of the GroupWise databases or the user's mailbox. Upgrading Clients to GroupWise 6 in a NetWare Environment. Novell is now a part of Micro. Products. Collaboration + Open Workgroup Suite. GroupWise; Micro FocusĀ® Vibe; Endpoint Management + ZENworks Suite. Service Desk. Recently graduated English majors who have spent their last four years immersed in works of. The user enters their GroupWise username and password. With the recent release of the GroupWise 5.5 Enhancement Pack.
Use these guidelines wherever possible in expanding systems or creating new systems, but temper their application with your experience and knowledge of your organization's unique computing environment. Please also refer to the Novell Group. Wise 6. 5 Documentation.
You may also refer to our partners for more information, tools, and services. System Requirements. Group. Wise NLM Agent Recommended Requirements.
For optimal performance, each Net. Ware? server on which you run the Group. Wise NLM agents must meet or exceed the following recommended system requirements: Requirements. Description. Operating System. Novell Net. Ware 6. Support Pack for your version of Net.
Ware. Available Disk Space for Agent files. MB for all language files. Approximately 1. 5 MB for English plus one other language. Available Memory 1. GB or more. Available Disk Space. Post office and Domain - - No less than 2.
Free Disk Space/Total Disk Space (Free Disk Space/Total Disk Space). Auto purge must be set on Novell Group. Wise Post office and Domain volumes. The required disk space accommodates both Group. Wise agents because both are installed together automatically. The required memory would be adequate for the most basic configuration of a single NLM agent on the server.
Additional free memory can significantly increase agent performance. Multiple agents on the same server require additional memory. Estimating NLM POA Memory Requirements The amount of memory required for the NLM POA is influenced by many factors, including the following: Number of client/server connections being supported Number of active client connections vs. Number of TCP handler threads ? Number of message handler threads Number of database maintenance threads. Estimating NLM MTA Memory Requirements The amount of memory required for the NLM MTA is influenced by many factors, including the following: Number of post offices and domains. Volume of message traffic between post offices and domains Volume of large messages (for example, large attachments, remote updates, and so on) TCP/IP or mapped/UNC links between MTAs.
Group. Wise NT/2. Agent Recommended Requirements. For optimal performance, each Windows NT? Windows 2. 00. 0? Group. Wise NT/2. Requirements. Description. Operating System.
Windows 2. 00. 0 or higher plus the latest Service Pack for your version of Windows. Available Disk Space For Agent Files. MB for all language files. Approximately 1. 5 MB for English plus one other language. Available Memory 1. GB or more. Available Disk Space. Post office and Domain?
No less than 2. 5% Free Disk Space/Total Disk Space (Free Disk Space/Total Disk Space). Auto purge must be set on Novell Group.
Wise Post office and Domain volumes. The required disk space accommodates both Group. Wise agents because both are installed together automatically. The required memory would be adequate for the most basic configuration of a single agent. Additional free memory can significantly increase agent performance. Multiple agents on the same machine require additional memory.
Estimating NLM POA Memory Requirements The amount of memory required for the NLM POA is influenced by many factors, including the following: Number of client/server connections being supported Number of active client connections vs. Number of TCP handler threads Number of message handler threads Number of database maintenance threads.
Estimating NLM MTA Memory Requirements The amount of memory required for the NLM MTA is influenced by many factors, including the following: Number of post offices and domains. Volume of message traffic between post offices and domains Volume of large messages (for example, large attachments, remote updates, and so on) TCP/IP or mapped/UNC links between MTAs. Group. Wise Client Recommended Requirements. For optimal performance, the workstation to which you install the Group.
Wise client for Windows must meet or exceed the following recommended requirements: Requirements. Description. Operating System. Windows 2. 00. 0 or higher. CPUPentium? III or higher.
RAM 2. 56 MB or higher. Disk Space. 60 MB for a standard installation (installed to local drive) for client files only. MB for Attachment Viewing Temp files. For Caching Mode you will need more than the master mailbox size. GWIA System Requirements.
Network Server Recommended Requirements. For optimal performance, the network server to which you install the Internet Agent should meet or exceed the following recommended requirements: Requirements. Description. Processor. Same as the recommended processor for the operating system. Operating system Net. Ware 4. 2 or higher with latest Support Pack.
Windows NT with latest Service Pack. Windows 2. 00. 0 with Service Pack 2 or higher. Disk space. 17 MB for the Internet Agent program files.
MB minimum for message file processing. The actual amount will be determined the by number and size of message files being processed at one time by the Internet Agent. RAM 1. 2 MB. This is the amount of memory the Internet Agent needs to operate. It does not include memory for the operating system or for TCP/IP connectivity.
This amount can increase depending on message size and complexity. Web. Access System Requirements. Network Server Recommended Requirements.
For optimal performance, verify that the machines you've selected to run the Web. Access components meet or exceed the following recommended requirements: Requirements. Description. Web. Access Agent Platform Group. Wise 6. 5 system: The Group. Wise 6. 5 Web. Access Agent can only access Group. Wise 6. 5 post offices and libraries.
Server: Net. Ware 4. Windows NT; Windows 2. With Net. Ware 5. Web. Access Agent can run on multi- processor servers and clustered servers. With Windows NT and 2. Web. Access Agent can run as either a Windows application or a Windows service.
Web Server and Java? Servlet Engine The Web. Access and Web. Publisher Applications require one of the following Web server and Java servlet engine configurations. Net. Ware 4. 2/5. Net. Ware Enterprise Web Server and Novell Servlet Gateway Net. Ware 6: Net. Ware Enterprise Web Server and Tomcat servlet engine; Apache Web Server and Tomcat servlet engine Windows NT: Netscape Enterprise Server?
Novell Servlet Gateway; Microsoft? Internet Information Server 4.
Windows NT must have Service Pack 3 or higher) and Novell Servlet Gateway Windows 2. Microsoft Internet Information Server 5 or higher and Novell Servlet Gateway UNIX?
Solaris?: Apache Web Server 1. Tomcat servlet engine The Novell Servlet Gateway is included and can be installed during Web. Access installation. The Tomcat servlet engine or other JSDK 2. Web. Access. Although Web. Access may run on other configurations, only the above configurations have been tested by Novell. To use a non- tested configuration, see the Web.
Access Readme file. Java Virtual Machine?
The Web. Access and Web. Publisher Applications require JVM?, version 1. B or higher. Please be aware of the following. Net. Ware servers can run only one JVM. On Net. Ware, Web.
Access requires JVM 1. B dated 1. 2/1. 2/2.
This version is included with Web. Access. During installation, you will be prompted to replace your current version with the Web. Access version; you should do so unless the server's current version is newer.
Windows NT/2. 00. JVMs at the same time. To ensure compatibility with Web. Access, you should install JVM 1. JVM 1. 4. 1 (Java 2 Runtime Environment, Standard Edition Version 1. Web. Access. A JVM is not included for UNIX Solaris.
You will need to separately install JVM 1. B or higher to your UNIX Web server. We recommend the newest version available. Monitor System Requirements.
Monitor Recommended Requirements. For optimal performance, verify that the machines you've selected to run the Monitor components meet the following recommended requirements: Requirements. Description. Monitor Agent Platform The Group. Wise Monitor Agent, which provides the Monitor Agent console, runs on Windows NT and Windows 2. Web Server and Java Servlet Engine The Group. Wise Monitor Application, which enables the Monitor Web console, requires one of the following Web server and Java servlet engine configurations.
Net. Ware 5. 1: Net. Ware Enterprise Web Server and Novell Servlet Gateway. Net. Ware 6: Apache Web Server and Tomcat servlet engine. Windows 2. 00. 0: Microsoft Internet Information Server 5 or higher and Novell Servlet Gateway.
UNIX Solaris/Linux: Apache Web Server 1. Tomcat servlet engine. The Novell Servlet Gateway is included and can be installed during Monitor installation. The Tomcat servlet engine or other JSDK 2.
Monitor. Although Monitor may run on other configurations, only the above configurations have been tested by Novell. To use a non- tested configuration, see the Monitor Readme file. Java Virtual Machine? JVM) The Monitor Application requires JVM, version 1. B or higher. Please be aware of the following. Net. Ware servers can run only one JVM.
On Net. Ware, the Monitor Application requires JVM 1. B dated 1. 2/1. 2/2. This version is included with Monitor.