This section teaches you how to ensure that the GroupWise client can get the necessary login parameters through Novell Directory Services or the DNS. This section also discusses Registry entries to "push" to workstations, should you happen to be using a tool such as Novell ZENworks. Configuring eDirectoryAll users of a GroupWise post office should have browse, read, and compare rights to the post office object itself, as well as to the POA associated with that post office. (However, if you are using LDAP authentication, your users do not need these rights.) For simplicity, assign the rights to the post office object, and the POA object to the OU or OUs in which the users for the post office reside. The following steps provide you with the tools to verify access modes and IP addresses when configuring eDirectory:
In these eight steps, you have accomplished two tasks:
Tip You can easily display the IP address and port for each POA object in the system by adding these columns to the POA view. Simply highlight a POA object, and then go to Tools, Edit Columns. From there, you can add columns that apply to the POA object. Select the IP address and port, and you will see every IP address and port for all your POA objects in the GroupWise system. You can also do the same thing for the UNC path. You must have the post office object highlighted when adding columns for the UNC path. Configuring DNSNow you need to choose a POA, preferably one that is centrally located on the LAN, to serve as the NGWNAMESERVER agent. On very large systems, it might be advisable to create a dummy post office (no users) with a POA dedicated to NGWNAMESERVER redirection. This is accomplished by following these steps:
In these four steps, you have ensured that any GroupWise client that looks for NGWNAMESERVER on your system will find a POA at the IP address specified. That POA will then redirect the client to the correct POA for connection to the user's mailbox. |