Novell eDirectory 8.7 for Windows NT/2000
December 2, 2002

 

TABLE OF CONTENTS

1.0    Installation Issues
         1.1     Prerequisites
         1.2     Distributing Proper Versions of DSREPAIR to All Servers in the Tree
         1.3     Upgrading from a Previous Version
         1.4     Uninstalling eDirectory 8.7
         1.5     NICI Uninstall Issues
         1.6     Video Cards and Driver Settings
         1.7     Using Dotted Container Names in a Server's Context
         1.8     HTTP Server Port Configuration
         1.9     Installing Novell iManager 1.5
         1.10   SNMP Installation Notes
         1.11   IPX Configuration - Network Settings
         1.12   Manually Extending the Schema Before Installation
         1.13   Installing eDirectory on a Window Server That Has a Jaz or Zip Drive
         1.14   Specifying eDirectory Information During the Installation
         1.15   Core DS Component Installation
2.0    Known Issues
         2.1     iMonitor Issues
         2.2     Using the Latest LDAP Features
         2.3     ConsoleOne Issues
         2.4     Security Domain Keys Issues
         2.5     SNMP Issues
         2.6     eDirectory Service Manager Issues
         2.7     Accessing Encrypted Objects and Attributes
         2.8     Roll-Forward Logs Are Turned Off After Restoring eDirectory
         2.9     Certificate Server Issues
         2.10   Increasing the Size of the eDirectory Log Files
         2.11   Upgrading eDirectory on a ZENworks for Desktops 4  Middle Tier Server
         2.12    eMBox Client Commands: Don’t Use “-ns” or “ac”
3.0    Documentation Issues
         3.1     Viewing Documentation on the Product CD
         3.2     Additional Readme Files
         3.3     Additional Readme Information
4.0    Legal Notices
         4.1     Disclaimer, Export Notice, Copyright, and Patents
         4.2     Novell Trademarks
         4.3     Third-Party Trademarks
         4.4     The Novell TLS Library

 

1.0    Installation Issues

1.1    Prerequisites

IMPORTANT: Windows XP is not a supported Novell eDirectory 8.7 platform.

set dstrace = !ne

NOTE: If DS.NLM is unloaded and reloaded without rebooting the server, the above set command must be executed after DS.NLM is loaded.

For more information about this setting, see TID #2963473 in the Knowledgebase at http://support.novell.com.

1.2     Distributing Proper Versions of DSREPAIR to All Servers in the Tree

For information on preparing an existing tree for an eDirectory 8.7 installation, see Updating the eDirectory Schema for NT/2000 in the Novell eDirectory Administration Guide.

1.3     Upgrading from a Previous Version

1.3.1 Prerequisites

Before you upgrade to eDirectory 8.7, make sure you have the latest NDS and eDirectory patches installed on all non-eDirectory 8.7 servers in the tree. You can get NDS and eDirectory patches from the Novell Support Web site.

You should also make sure that the latest Windows NT/2000 Service Packs are installed.

1.3.2 Upgrading to Novell eDirectory 8.7 on a Double-byte System

In previous releases of eDirectory, some index keys were built incorrectly in double-byte language (Japanese, Korean, or Chinese) systems. Because of the incorrect keys, some searches did not work correctly. This issue has been resolved in Novell eDirectory 8.7. However, because existing eDirectory databases on these systems still have these incorrect keys, there might be times even after your upgrade to eDirectory 8.7 when eDirectory will report corruption errors that are due to incorrect keys.

To resolve this issue, run dsrepair.dlm from NDS Services (in the Windows Control Panel, double-click NDS Services > select dsrepair.dlm > click Start) after the upgrade is complete and perform a physical rebuild of the database. This is only necessary if the database is a double-byte language database (Japanese, Korean, or Chinese). It is not necessary to run DSRepair after upgrading if you are not using one of these languages.

1.3.3 Certificate Server 2.0.1

Your CA server must be running Certificate Server 2.0.1 or later before installing a new server into the tree. You can determine which server is the CA by viewing the Certificate Authority object located in the Security container at the root of the tree.

To verify the version of the Certificate Server software, check the module version number on PKI.NLM (NetWare) or pki.dlm (Windows).

If the Certificate Server software version on the CA server is out of date, install eDirectory 8.7 on the CA server first, then proceed to install eDirectory 8.7 on any additional servers.

 1.3.4 X.509 and CertMutual Login Methods

The X.509 and CertMutual login methods that shipped with eDirectory 8.6.x are not compatible with eDirectory 8.7. When you upgrade from 8.6.x to 8.7, you must upgrade the X.509 and CertMutual login methods as well.

1.3.5  Upgrading from a Beta Version of Novell eDirectory 8.7

When upgrading from a beta version of Novell eDirectory 8.7, if the Windows SNMP Service is installed on the server, and the SNMP Service has one or more dependent services, you should manually stop the Windows SNMP Service before starting the eDirectory 8.7 installation.

To stop the Windows SNMP Service:

  1. Click Start > Settings > Control  Panel > Administrative Tools > Services.
  2. Right-click SNMP Service in the Name list, then click Stop.
  3. Click Yes to All.

If you start the eDirectory installation without stopping the SNMP Service, the following error will occur:

IO Error

Error opening destination file xxxxxx\dclient.dll.
The file may be in use. Close any applications on this computer or any other that may be accessing the file. Then hit the Retry button. Would you like to retry copying this group of files, skip this group of files, or cancel this installation?

Retry  Skip  Cancel

Clicking Skip or Cancel will cause the eDirectory installation to fail. Clicking Retry will not work unless you shut down the Windows SNMP Service.

If the installation fails, follow these steps to perform the eDirectory upgrade:

  1. Manually stop the Windows SNMP Service and all its dependencies:
    1. Click Start > Settings > Control  Panel > Administrative Tools > Services.
    2. Right-click SNMP Service in the Name list, then click Stop.
    3. Click Yes to All.
  2. Copy the entire contents of the nt\i386\NDSonNT\ndsnt\nds directory from the previous (beta) eDirectory CD image to the installed eDirectory location (for example, c:\novell\nds). Copy all subdirectories and files.
  3. Copy the entire contents of the nt\i386\NDSonNT\ndsnt\snmp directory from the previous (beta) eDirectory CD image to the installed eDirectory location (for example, c:\novell\nds). Copy all subdirectories and files.
  4. Manually start the NDS Service. This step simply verifies that all the files are in place. You might want to try some things with eDirectory to make sure it is functioning as before.
  5. Restart the eDirectory 8.7 upgrade installation.

1.4     Uninstalling eDirectory 8.7

When uninstalling eDirectory 8.7, you might receive the following error if the installation of eDirectory 8.7 was an upgrade from NDS eDirectory or NDS eDirectory 8.5:

Incompatible JClient/DClient Package
JClient Revision 1.0.19
DClient Revision 1.1.1095

This error occurs only when the previous eDirectory installation was performed on a date later than the dates of the eDirectory 8.7 files located in the \NT\I386\NDSONNT\NI\LIB directory on the Novell eDirectory 8.7 CD. If the previous installation was performed prior to those dates, this error will not occur.

To solve this issue, copy the .JAR files from the \NT\I386\NDSONNT\NI\LIB directory on the Novell eDirectory 8.7 CD to the \PROGRAM FILES\COMMON FILES\NOVELL\NI\LIB directory on the Windows server before performing the eDirectory 8.7 uninstall.

1.5     NICI Uninstall Issues

After uninstalling NICI, if you want to completely remove NICI from your system, delete the "%SYSTEMROOT%\WINNT\SYSTEM32\NOVELL\NICI" subdirectory. You might need to take ownership of some of the files and directories to delete them.

WARNING: Once the NICI subdirectory has been removed, any data or information that was previously encrypted with NICI will be lost.

1.6     Video Cards and Driver Settings

The eDirectory, ConsoleOne, Novell iManager, and eGuide installs use Java 1.3. This means that a minimum color depth of 8 bits (256 colors) is required by your video card and driver setting to run the installations properly. On NetWare, the video card must also be VESA-compliant.

With some video cards, and with some driver versions, you might notice some visual abnormalities in the installation screens. Examples include a pastel color scheme and a strange mottling effect that may look like the resolution is much lower than the actual setting. Some installation screens will not display at all. This makes it appear that the installation is hung up, or that it has aborted. If you see that the installation screens do not appear correctly, download a newer version of the driver for your video card. Otherwise, the installation may not complete successfully.

With some video cards, when 256 colors are set, the installation screen might seem to disappear after the SNMP portion of the installation even though install.exe and launch.exe are still running (as shown in the Windows Task Manager). If this happens, use Task Manager to terminate the launch.exe process, set your display to more than 256 colors, then re-run the installation. This will perform an upgrade installation over the top of the existing installation, and the upgrade should complete successfully.

1.7     Using Dotted Container Names in a Server's Context

The Novell eDirectory 8.7 installation does not support dotted container names in the server's context (for example, OU=Eng.Sales.O=www.acme.com). To avoid errors, you should install new servers into a tree that does not contain dots in the server's context.

Note: You cannot escape the dots (for example, OU=Eng\.Sales.O=www\.acme\.com will not work).

1.8     HTTP Server Port Configuration

You should make sure that the HTTP stack ports you set during the eDirectory installation are different than the HTTP ports you have used or will be using for Novell iManager.

If eDirectory 8.7 is installed before Novell iManager, you might have port conflicts if an exception similar to the following is displayed in the console window when iManager is installed:

java.lang.reflect.InvocationTargetException: org.apache.tomcat.core.TomcatException: Root cause - Address in use: JVM_Bind

If Novell iManager does not load when you click the link in the Getting Started document (gettingstarted.html), check the following file:

<iManager installation path>\tomcat\logs\jvm.stderr

You will see exceptions at the bottom of the file similar to the following:

java.lang.reflect.InvocationTargetException: org.apache.tomcat.core.TomcatException: Root cause - Address in use: JVM_Bind

To resolve this problem, do the following:

  1. In Windows Control Panel for NT and Administrative Tools for 2000, select Services.
  2. Find the jakarta entry, then click Stop.
  3. Start ConsoleOne and log in to your eDirectory 8.7 tree.
  4. In the tree view, select the container where you installed the server object.
  5. Open the properties of the HTTP Server - <servername> object and select the Other tab.
  6. Change the httpDefaultClearPort and httpDefaultTLSPort attributes to port numbers other than your iManager web server (probably 80) and tomcat ports (8080, 8007, 8009). For example, change to 8008 for httpDefaultClearPort and 8009 for httpDefaultTLSPort.
  7. Open NDS Services from the Windows Control Panel and select the Services tab.
  8. Select ds.dlm service and click the Configure button.
  9. In NDS Configuration, select the Triggers tab.
  10. Click Limber to start the Limber process. The new Port assignments should be set.
  11. In Windows Control Panel for NT and Administrative Tools for 2000, select Services.
  12. Find the jakarta entry, then click Start.
  13. Verify that your Web server is running. Test this by opening the Getting Started page (eMFrame\help\en\install\gettingstarted.html) and selecting the iManager link.

1.9     Installing Novell iManager 1.5

After you have installed eDirectory 8.7, make sure that you install Novell iManager 1.5 from the WebApps CD in order to take full advantage of the features and capabilities of eDirectory 8.7. In this release, previous versions of iManager will not work correctly with the new Role Based Services objects delivered in the installation of eDirectory 8.7.

For additional information on Novell iManager 1.5, see \readme\en\imanager_readme.html on the WebApps CD.

1.10   SNMP Installation Notes

Prior to the installation of eDirectory 8.7 on Windows NT/2000, make sure that the native Master Agent is installed.

If you have the Windows SNMP service installed and running on your system, the eDirectory installation will temporarily shut it down while it installs the Novell SNMP sub agent. After the Novell SNMP sub agent is installed, the Windows SNMP service will be restarted.

1.11   IPX Configuration - Network Settings

If your IPX configuration (in Network Settings in the Windows Control Panel) is configured with an Internal Network Number of 0, the eDirectory 8.7 installation might fail if the machine has multiple NICs. The Internal Network Number must be set to something other than 0 in order for the eDirectory installation to complete properly, and for eDirectory to run properly after installation.

If you choose to uninstall IPX, IPX should be completely uninstalled as a protocol, not merely disabled on some or all adapters.

If you use IPX, it must be configured correctly. That is, multiple adapters (LAN or WAN) must have a valid internal IPX net number set.

You cannot install, remove, enable, or disable a protocol on any adapter while eDirectory is running.

1.12   Manually Extending the Schema Before Installation

In some cases, schema extensions do not synchronize fast enough to the lower levels of a tree where the first new eDirectory 8.7 server is being installed for some features to be completed installed properly. One instance of this is the httpServer object schema definition, which might not synchronize to the server where the object instance needs to be created before the install code attempts to create it. In this particular instance, the failure to create the httpServer object schema definition is not fatal, as it only contains optional configuration information.

This type of problem can be avoided by manually extending the schema in your tree before you install eDirectory 8.7. This can be done by manually extending the schema using the eDirectory 8.7 schema files located in the \nt\i386\NDSonNT\ndsnt\nds directory on the eDirectory 8.7 CD.

1.13   Installing eDirectory on a Windows Server That Has a Jaz or Zip Drive

When installing eDirectory on a Windows server that has a Jaz or Zip drive, you might receive the following error:

"There is no disk in the drive. Please insert a disk into <drive_name>."

To resolve this issue, do one of the following:

1.14   Specifying eDirectory Information During the Installation

When specifying the eDirectory information during the installation, if an invalid Server object container type is specified, the installation will not detect the error until later, and the eDirectory installation will fail with a -611 or -634 error.

The valid Server object container types are:

1.15   Core DS Component Installation

On rare occasions, the eDirectory installation will fail during its core DS component installation. If so, an error dialog like the following will be displayed:

"The DS component of eDirectory failed to install correctly. The error received was: '<some error>'. Please view DSInstall.log for more detailed information. The eDirectory installation will now be terminated."

If you receive this error, you should try to reinstall the product, or remove it and then reinstall it. If the reinstallation fails because of a partial installation already being on your system, or for any other reason, please visit the Novell Support Web site for possible solutions.

2.0    Known Issues

2.1     iMonitor Issues

2.1.1 Browser Compatibility

The iMonitor included with this release of eDirectory requires Internet Explorer 5.5 or later or Netscape 6.2 or later.

2.1.2  Browsing for Objects in iMonitor Containing Double-byte Characters

When using iMonitor to browse an eDirectory tree for objects, an object with double-byte characters in the name might not hyperlink to the object properties correctly. This issue will be resolved in a future release of iMonitor.

 2.1.3 Automatic Refresh for Trace Live Doesn't Refresh

After specifying the refresh rate and selecting Refresh On, the Trace window will update only once. To get more data added to the trace window, select the Update button as needed.

2.2    Using the Latest LDAP Features

To use the latest LDAP features such as start TLS, stop TLS, SASL External, SASL Digest MD5, and SASL NMAS Methods, download the September 2002 or later version of the LDAP Libraries for C from the Novell Developer Web site. SDKs are available for NetWare, Windows, Solaris, Linux, and AIX.

The LDAP Libraries for C available at http://developer.novell.com/ndk/cldap.htm is the latest released version of the LDAP libraries.

2.3    ConsoleOne Issues

2.3.1  ConsoleOne Errors on Exporting Certificates

Sometimes during a certificate export using ConsoleOne, the following error message is displayed:

"ConsoleOne.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created."

At other times, there is no error message displayed, and ConsoleOne simply exits unannounced.

This problem occurs because of an incompatibility between NICI 2.01 or 2.02 and the Novell Client version 4.83 (Window NT/2000) or Novell Client version 3.32 (Windows 98). To resolve this problem, do one of the following:

  • Install NICI 2.4.1 on the machine that you run ConsoleOne from. NICI 2.4.1 is available on the eDirectory 8.7 CD in the following location:

    \nt\i386\nici\wcniciu0.exe

  • Run ConsoleOne on a Windows NT/2000 machine that has eDirectory 8.7 installed on it, which will also have NICI 2.4.1 installed.

2.3.2  Installing the DirXML 1.1 Snap-in for ConsoleOne

When installing DirXML 1.1 on this version of eDirectory 8.7 on Windows, a file copy error will occur while installing the DirXML 1.1 snap-in for ConsoleOne. To get around this problem, when installing DirXML 1.1 for Windows, don't select the option to install the DirXML snap-in for ConsoleOne. Instead, install this snap-in separately using the standalone install available from the ConsoleOne Snap-ins section of the Novell Download Web site.

2.3.3  Using ConsoleOne to Manage NetWare 4.x Servers

In order to use ConsoleOne to manage a tree containing NetWare 4.x servers (DS v 6.17), IPX must be installed on the management client. Even if ConsoleOne is run from a NetWare box via a mapped drive on the client, the client machine on which ConsoleOne is running must be able to connect natively via IPX.

2.3.4  New ConsoleOne Switch

Using the -forceMaster switch when starting ConsoleOne will cause ConsoleOne to always talk to the master replica for the objects being accessed.

We don't recommend this switch during normal use of ConsoleOne. Use this switch under direction from Novell Technical Support personnel.

2.4     Security Domain Keys Issues

Each eDirectory server is normally installed with one or more Security Domain (SD) keys. SD keys are used to manage sensitive information shared between servers within a given tree. SD keys are normally setup automatically during the eDirectory installation process.

Problems can surface when SD keys are out of sync between the servers, such as an inability to create user certificates or the inability to set user passwords. Usually the error that is reported in these cases is -1460. There are three ways in which the SD keys can be out of sync:

  1. The W0 object is pointing to a server that is not installed with an SD key.
  2. Various servers have SD keys not shared with other servers.
  3. The W0 object does not contain a server entry.

Note: The W0 object is located in the KAP.Security container. Use ConsoleOne to view the W0 object.

To resolve problem 1:

To resolve problem 2:

To resolve problem 3:

If you are unable to locate a server containing a copy of the SD key, delete the W0 object and restart the eDirectory installation. The next server you install will become the SD key server.

2.5     SNMP Issues

2.5.1  eDir.mib

The eDirectory MIB file (<eDirectoryInstallRootDir>\snmp\edir.mib) on Windows, compiles with a few errors and warnings on HP-OpenView. Please ignore these errors.

2.5.2  SNMP Log Files

If you have problems bringing up SNMP services, check the following log files, located in the C:\novell\nds\snmp\ directory by default, to get more information on possible errors:

  • ndssnmpsa.log
  • ndssnmpsrv.log

2.5.3  SNMP Configuration File

If LDAP is not configured to run in clear text mode, the name of the trusted root certificate file needs to be given in the SNMP configuration file (for example, SSLKEY sys:\etc\trust.der) before bringing up dssnmpsa.

ndssnmp.cfg can be found in <eDirectoryInstallRootDir>\snmp\ on Windows.

2.5.4  Sub Agent Login Screen

On Windows 2000, the SNMP Sub Agent login screen sometimes appears after a considerable delay.

2.5.5  Using SNMP After a New Tree Installation

When installing eDirectory 8.7 for the first time (creating a new tree), if the Windows SNMP Service is installed on the server, and the SNMP Service has one or more dependent services, eDirectory will not be able to shut down the SNMP Service. In this case, SNMP will not be ready to use after the eDirectory installation.

To use SNMP, follow these steps to restart the SNMP service:

  1. Click Start > Settings > Control  Panel > Administrative Tools > Services.
  2. Right-click SNMP Service in the Name list, then click Stop.
  3. Click Yes to All.
  4. Right-click SNMP Service in the Name list, then click Start.

2.5.6  Uninstalling eDirectory

If the Windows SNMP Service is installed on a server, and the SNMP Service has one or more dependent services, the eDirectory uninstall will not delete all the SNMP files in the \novell\nds directory. However, the other uninstallation processes will complete successfully, including the deletion of the SNMP registry entries, and the deconfiguration process that the Novell SNMP agent does with DS and the SNMP Service.

Follow these steps to complete the uninstallation:

  1. Click Start > Settings > Control  Panel > Administrative Tools > Services.
  2. Right-click SNMP Service in the Name list, then click Stop.
  3. Click Yes to All.
  4. Right-click SNMP Service in the Name list, then click Start.
  5. Manually delete the remaining SNMP files in the \novell\nds directory.

2.6     eDirectory Service Manager Issues

If you use the eDirectory Service Manager in Novell iManager to stop eDirectory, restarting it through Service Manager is not possible. Use the NDSCons utility (c:\novell\NDS\NDSCons.exe) on the eDirectory server to restart eDirectory.

2.7     Accessing Encrypted Objects and Attributes

If you cannot access your Certificates, KMO objects, NMAS attributes, CA, or other encrypted objects and attributes hosted by a server after you have completed upgrading eDirectory from a version prior to 8.6, this might be due to NICI not fully migrating. This problem might be reported as error -1460 by the service.

To resolve this issue:

  1. Shut down eDirectory.
  2. Back up all folders in winnt\system32\nici, then delete these folders.

    Important: Delete only the sub-folders, DO NOT DELETE the NICI folder or other files in the NICI folder.

  3. Restart eDirectory.

2.8     Roll-Forward Logs Are Turned Off After Restoring eDirectory

As part of the process of restoring the eDirectory database, roll-forward logging on the server is always reset to the default settings. This means that after a restore, roll-forward logging is reset to Off, and the location of the roll-forward logs is reset to the default location.

If you have been using roll-forward logging on a server, and you want to continue to use it on that server after a restore, you must do the following:

  1. After a restore, re-create your configuration for roll-forward logging to make sure it is on and the logs are being saved in a fault-tolerant location.
  2. After turning on the roll-forward logs, do a new full backup.

The new full backup is necessary so that you are prepared for any failures that might occur before the next unattended full backup is scheduled to occur.

For more information on the roll-forward logs and how to choose a fault-tolerant location, see "Using Roll-Forward Logs" in the "Backing Up and Restoring eDirectory" chapter in the eDirectory 8.7 Administration Guide.

2.9    Certificate Server Issues

2.9.1  Extractable Keys Support

When creating the Organizational CA object or Server Certificate objects (also known as KMOs), extractable keys are supported only if the server you selected for the key pair generation is running eDirectory 8.6 or later on NetWare and NT platforms, or if running eDirectory 8.7 or later for Unix platforms. If you are attempting to make the keys extractable on an unsupported platform, you will receive a -1222 error.

2.9.2  Importing CRL Data Onto a CRL Object

Importing CRL data onto a CRL object is not supported through iManager. You must use ConsoleOne for this feature.

2.10   Increasing the Size of the eDirectory Log Files

You can use Novell iManager to increase the maximum size of the eDirectory log files (in iManager, click eDirectory Maintenance Utilities > Log File > specify which server will perform the log file operation > authenticate to the server > Log File Options > enter a new maximum file size) to a large value (such as several meg).

However, the size of the log files can become a problem and might cause eDirectory to stop responding on Windows NT. To solve this problem, increase the heap size allocated to the JVM for iManager by using an environment variable of the following form:

TOMCAT_OPTS=-Xmx512m

This increases the JVM heap size from the default of 64MB to 512MB.

2.11   Upgrading eDirectory on a ZENworks for Desktops 4 Middle Tier Server

When the ZENworks for Desktops 4 Middle Tier Server and ZENworks for Desktops "Back-end" Server exist on the same Windows 2000 server, and the server is upgraded to eDirectory 8.7, you should reinstall the ZENworks for Desktops Middle Tier portion on the server. Symptoms include the following:

If the Windows 2000 server is hosting only the ZENworks for Desktops Middle Tier Server and not the ZENworks for Desktops "Back-end" Server, and the server is upgraded to eDirectory 8.7, the reinstallation of the ZENworks for Desktops Middle Tier Server is NOT required.

2.12   eMBox Client Commands: Don’t Use “-ns” or “ac”

When running the eMBox Client at the command line or in a batch file, do not use the –ns or ac options on Windows NT/2000. The eMBox Client will return an error if you do.

The –ns and ac options are used only for the NetWare platform (sometimes shown together in the documentation as “-nsac”).

In the documentation, the general example of a batch file command included the –ns option, which is misleading. Also, the example of a Windows batch file command mistakenly included the –ns option. The incorrect Windows example using –ns appears in "Doing Unattended Backups, Using a Batch File with the eMBox Client" in the "Backing Up and Restoring eDirectory" chapter in the eDirectory 8.7 Administration Guide.

Here is the corrected Windows example, with “–ns” no longer included after “java”:

Example Batch File for Windows

java -cp c:\novell\nds\embox\eMBoxClient.jar embox
-s myserver -p 8008 -u admin.myorg -w mypassword -n
-t backup.backup -b -f c:\backup\backup.bak
-u c:\backup\includes\includefile.txt
-l c:\backup\backup.log
-e -t -w

3.0 Documentation Issues

3.1     Viewing Documentation on the Product CD

This product CD contains documentation for the following products:

\DOCUMENTATION\ENGLISH\EDIR87\EDIR87.PDF
\DOCUMENTATION\ENGLISH\EDIR87\QSEDIR87.PDF

\DOCUMENTATION\ENGLISH\NOCLIENU\NOCLIENU.PDF

\DOCUMENTATION\ENGLISH\CERTSERV\CERTSERV_ADMIN.PDF

\DOCUMENTATION\ENGLISH\CONSOL13\C1_ENU.PDF

\DOCUMENTATION\ENGLISH\NMAS\DOC\NMAS_ADMIN.PDF

3.2     Additional Readme Files

For additional information on the contents of this release, see the following sources on the Novell eDirectory 8.7 CD:

\NW\INSTALL\NLS\4\NWREADME.TXT

\NT\I386\SERVERNICI\NI\HELP\EN\README.HTML

\NT\I386\README.TXT

For additional information on Novell iManager 1.5 and Novell eGuide 2.1, see the following sources on the Web Application CD:

\README\EN\IMANAGER_README.HTML

\README\EN\EGUIDE_README.HTML

3.3    Additional Readme Information

For information on additional eDirectory issues for this release, refer to Solution #10073723, titled "Novell eDirectory 8.7.x Readme Addendum," in the Novell Knowledge Base.

4.0     Legal Notices

4.1     Disclaimer, Export Notice, Copyright, and Patents

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.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

Copyright (C) 2002 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.

U.S. Patent No. 5,608,903; 5,671,414; 5,677,851; 5,758,344; 5,784,560; 5,794,232; 5,818,936; 5,832,275; 5,832,483; 5,832,487; 5,870,739; 5,873,079; 5,878,415; 5,884,304; 5,913,025; 5,919,257; 5,933,826. U.S and Foreign Patents Pending.

4.2     Novell Trademarks

Novell, NetWare, NDS, and ConsoleOne are registered trademarks of Novell, Inc. in the United States and other countries.

eDirectory, Novell Client, Novell Certificate Server, Novell Modular Authentication Services, and NMAS are trademarks of Novell, Inc.

4.3     Third-Party Trademarks

All third-party trademarks are the property of their respective owners.

4.4     The Novell TLS Library

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.

Please refer to \documentation\english\license\license.txt on the eDirectory CD for additional information and license terms.