This section contains issues that you might encounter while installing eDirectory.
On NetWare 6.5 SP3, if sys:\NI\nis30\bin is added to the search path in autoexec.ncf, installation might fail during the certificate server configuration.
Ensure that this is not added in autoexec.ncf before starting eDirectory 8.8 SP4 installation.
The eDirectory, ConsoleOne, Novell iManager, and eGuide installs use Java* 1.4. 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.
Do not configure IPX while installing and configuring eDirectory 8.8 SP4 on NetWare servers. If you configure IPX, you might get some random issues.
In some cases, schema extensions do not synchronize fast enough to the lower levels of a tree where the first new eDirectory 8.8 SP4 server is being installed, so some features are not completely installed.
This type of problem can be avoided by manually extending the schema in your tree before you install eDirectory 8.8 SP4, using the eDirectory 8.8 SP4 schema files located in the \nw\sys\system\schema directory.
With eDirectory 8.7, enhancements were made to the DSI that added more flexibility in extending the schema. Many of the schema files located in the \nw\sys\system\schema directory, take advantage of this new functionality. If an older version of dsi.nlm or dsisch.nlm (anything older than version 10411.14, dated September 26, 2002) is used by nwconfig.nlm to extend the new schema, the following error will occur:
Error: Parsing the NDS500.sch file while extending schema.
To avoid this error:
Copy nw\sys\system\dsi.nlm and nw\sys\system\dsisch.nlm to the server that will do the schema extension.
IMPORTANT:This should be a server that holds a copy of the Root partition.
Copy the desired schema files to a temporary directory on the NetWare server.
Run nwconfig.nlm and use the Directory Services option to extend the schema.
IMPORTANT:There are some dependencies between the schema files in the nw\sys\system\schema directory. Because of these dependencies, we recommend that the schema files be extended in the order that is listed in the nw\sys\system\schema\schema.cfg file.
Before you upgrade to eDirectory 8.8 SP4, make sure you have the latest eDirectory patches installed on all servers prior to eDirectory 8.8 SP4 in the tree. You can get eDirectory patches from the Novell Support Web site.
If you have eDirectory 8.5.x or 8.6.x, you have to first upgrade to eDirectory 8.7.x and then upgrade to eDirectory 8.8 SP4.
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 was 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.8 SP4 when eDirectory reports corruption errors because of incorrect keys.
To resolve this issue, run dsrepair.nlm 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.
During the upgrade from eDirectory 8.7.x to eDirectory 8.8.4, the location of the IDM files is changed requiring a reinstall of the IDM engine and drivers. Any third party jar files will not automatically be copied to the new location and will need to be manually placed prior to starting the drivers affected. It is recommended that all drivers be set to manual prior to upgrading to eDirectory 8.8 SP4.
Upgrading from eDirectory 8.7.x to eDirectory 8.8 SP4 rebuilds the LDAP Mapping table and re-adds the inetOrgPerson --> User mapping, causing any new objects created via LDAP to be of the User base class instead of the inetOrgPerson base class. This is only an issue if you deleted the mapping for inetOrgPerson --> User and defined a real inetOrgperson Class in your previous version of eDirectory.
To work around this problem, use iManager to remove the mapping from the Class Mappings page of the LDAP Group Object.
When eDirectory server is upgraded from 8.7.3.x and 8.8 versions to eDirectory 8.8 SP1 or later, the disk space check for the DIB upgrade is performed. The free disk space necessary in the file system, where the DIB resides would be equal to that of the DIB size. The messages of the disk space check would be updated in the ndscheck.log located in the instance’s specific log directory. For default instance, sys:\system\dscheck.log.
NOTE:The disk space check is required only during the DIB upgrade process. For more information, refer to Upgrade Requirements of eDirectory 8.8 in the Novell eDirectory 8.8 Installation Guide.
When you install eDirectory 8.8 SP4, it comes with NMAS 3.3.1. However, when you do a post install of NetWare products, NMAS 3.3.1 is selected by default to get installed. Therefore, you need to uncheck NMAS 3.3.1 during post installation of NetWare products.
When eDirectory is upgraded to eDirectory 8.8 SP4, the server is stopped and a DIB upgrade operation is performed before the server is started and the normal upgrade is performed. The time taken for this upgrade depends on the number of objects in the tree.
For more details on the DIB upgrade, refer to Upgrade Requirements of eDirectory 8.8 in the Novell eDirectory 8.8 Installation Guide.
eDirectory 8.8 SP4 does not function properly with Nsure Audit 1.0.x. For full functionality with eDirectory 8.8 SP4, upgrade to Novell Audit 2.0.
Download the following iManager Plugins from the Web.
eDir_88_iMan25_Plugins.npm
eDir_88_iMan26_Plugins.npm
eDir_88_iMan27_Plugins.npm
Install the NPM as mentioned in the iManager 2.5 or iManager 2.6 or iManager 2.7.