Most organizations test new products in a lab setting prior to making them available for general use.
This guide is designed to help you set up Novell® Open Enterprise Server (OES) in a lab environment using a specific and simplified configuration. The configuration is limited in scope and is meant only to acquaint you with OES and provide exposure to the Novell products it contains.
The instructions in this guide will help you do the following:
Install an OES NetWare® server into an eDirectory™ tree named EXAMPLE_TREE
If you are installing the OES NetWare server first, you will create the tree during the installation process. If you already installed OES for Linux, you will install this server into the tree you created during that installation.
Install select OES components on the server
Perform simple tasks to get acquainted with basic OES services
The sections in this guide are designed to be accessed sequentially, and they guide you through the following main tasks:
Installing an OES NetWare server.
Setting up the eDirectory infrastructure—user objects, group objects, passwords, etc.
Reviewing the services featured in the guide and performing all additional setup tasks required for test driving and exploring the features.
Test driving and exploring the features.
If you want to install additional OES servers or create a different tree structure than the one specified in this guide, you can still use these instructions as a basic guide for setting up OES services in a lab environment. However, you will probably also want to refer to the information found in the following guides:
We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation.
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items within a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
When a single pathname can be written with a backslash for some platforms, or a forward slash for other platforms, the pathname is presented with a forward slash to reflect the Linux* convention. Users of platforms that require a backslash, such as NetWare, should use backslashes as required by the software.