Ability to create a preinstallation check-list.


 
 
 
Try This:

Make sure you can login as root or Administrator on your target system. 



The preinstallation procedures covered in this module apply to both Solaris and NT systems.



See Chapter 1 of the Installation Guide.

Preinstallation Planning

In the instructions that follow, the term "target system" refers to the system you're going to install the Server software on. 

Three Big Steps

The installation process occurs in 3 big steps:

1.  Copying the installation software from a CD-ROM or the network onto a staging directory on 
     the target system.

2.  Using the command-line installation script to install the Server software into its final destination on
     the target system.

3.  Using the GUI installation application to perform initial configuration.
 

Things To Consider Before Proceeding

  • Solaris systems:
    • What's the root password for the target system?
    • What version of Solaris is on the target system?
    • What port number should the Server use to communicate with client applications?

    •  
  • NT systems:
    • What's the Administrative password for this system?

    •  
  • Both Solaris and NT:
    • Where are the installation source files?
    • Where will you put the installation software on the target system?
    • Where will you put the actual Server software on the target system?
    • Who will be the primary administrator for the Server?
    • What other users and groups will be given administration privileges?
    • What level of security is appropriate for the information on this Server?
    Most of these issues will be covered in the following sections.

Define Your Root DN

The root DN is the special entry to which access control does not apply.  You can think of the root DN as your directory's superuser account. 

When prompted for a root DN during the installation process, you'll enter a common name value.  For example, if you want the root DN to be named Directory Superuser,  you'll enter the following string in the field for unrestricted user: 

cn=Directory Superuser
If you don't want an unrestricted user configured with your server, leave this field blank.  However, if you don't create an unrestricted user account, you could be locked out of your directory.  This is because, by default, no access is allowed to the directory except to the unrestricted user.  If you don't create an unrestricted user, then create your directory from LDIF files and provide the appropriate access control information at that time.

We'll cover access control in much more detail in the Security module.

Copyright © 2000
Sun-Netscape Alliance