This section contains important information for the following scenarios:
You should install one server at a time into a tree, waiting for the installation program to complete before installing an additional server into the same tree.
If you are installing the first OES Linux server into an existing NDS/eDirectory tree, run Deployment Manager first to prepare the tree so it is compatible with the new version of eDirectory that comes with OES.
To run the Deployment Manager, follow the steps outlined in Prepare the Network with Deployment Manager
in the OES NetWare Installation Guide. This procedure is for NetWare® OES servers, but it also applies to OES Linux servers.
IMPORTANT:If you are installing into an eDirectory tree that is using a NetWare server to supply LDAP, upgrade the LDAP server that the OES Linux installation will communicate with to the NetWare 6.5 SP3 or later software; otherwise, the server (running NetWare 6.5 SP2 or earlier) will most likely abend.
To ensure a successful OES Linux installation, do the following before installing your first OES Linux server in an existing NetWare tree:
Extend the schema using the Schema Update
in Deployment Manager.
Schema Update is a new tool in the OES SP1 version of Deployment Manager. It extends the schema for Linux and NetWare trees. For more information, see Schema Update
in the OES NetWare Installation Guide.
Ensure the schema is synchronized throughout the tree from [ROOT] by doing the following:
Verify that schema is synchronizing out from [ROOT] by entering the following commands at the System Console prompt of the server with the Master of [ROOT]:
Toggle to the Directory Services screen and look for the message: All Processed = YES
On each server that holds a Master of a partition, enter the following commands at the System Console prompt:
Toggle to the Directory Services screen and look for the message: All Processed = YES
Before installing an OES Linux server into an existing tree that is running NetWare 5.1 server only, do the following:
Run Deployment Manager first to prepare the tree so it is compatible with the new version of eDirectory that comes with OES.
IMPORTANT:If you install the OES Linux server into an existing tree with servers with versions earlier than NetWare 5.1 SP7 and eDirectory 8.6.x, you first need to run Deployment Manager to prepare the network. See eDirectory Rights Required to Install OES Linux. If all the servers in the tree are running NetWare 5.1 SP7 or later with eDirectory 8.6.x or later, you do not need to run Deployment Manager.
Deployment Manager is on the OES NetWare 6.5 Operating System CD 1. To run the Deployment Manager, follow the steps outlined in Prepare for New eDirectory
in the OES NetWare Installation Guide. This procedure is for NetWare OES servers, but it also applies to OES Linux servers.
Deployment Manager runs from a Windows* workstation and requires a NetWare server that holds a root replica of the tree.
Update the OES schema in the tree by using the Schema Update Wizard in Deployment Manager.
For more information, see Schema Update
in the OES NetWare Installation Guide.
Ensure that all NetWare 5.1 servers in the tree are running NetWare 5.1 SP7 or later.
Apply a new sas.nlm file to each NetWare 5.1 server in the tree. For more information, see TID 2970116 “NetWare 5.1 SP8 SAS.NLM for OES Install”.
Ensure that all OES services (components) are pointing to the OES Linux server that you are installing and that they are not pointing to the NetWare 5.1 server.