To make a long story short, I ran into some major problems while doing an
upgrade on an OES1 SP2 server to OES2. Couldn't get eDirectory
communicating after finishing the upgrade (stopped at 58%). I finally did
successfully get eDirectory 8.8.2 running on the server by
deleting/recreating the tree CA on a different server, copying the nds.conf
file from a working OES2 Linux server, changing the file to include the
correct information for this server and pointing at the original location of
the DIB (/var/nds/dib), and running ndsconfig upgrade. Now all is running
fine as far as eDirectory is concerned.

So now I am running OES2 eDirectory 8.8.2 with the dib in the original
location. It seems that the OES2 upgrade wants to move it to
/var/opt/novell/eDirectory/data/dib. The problem is running the OES
install/configuration options in Yast through the GUI. The first thing it
wants to do is upgrade eDirectory again before I can do any of the other
OES2 component configuration tasks (e.g., LUM, NSS, etc.). How do I
convince the GUI tool that eDirectory is already upgraded? Is there another
..conf file that needs to be adjusted, or what?

Thanks for any input.


Dennis R. Crowther, CNE