The primary domain controller must be the first Advanced Server/9000
or Windows NT server that is installed in a domain. There can be
only one primary domain controller in a domain. If you configure
a server as a primary domain controller in a domain that already
exists, the result will be two domains with the same name, neither
of which will operate properly.
If the primary and backup domain controllers are on different
subnets and you have a Windows NT Server, you can use WINS to locate
systems easily on remote networks.When using WINS, you will need
to configure NetBIOS so that it can contact a WINS server-- refer
to the Advanced Server/9000 Administrator's Guide
for details. If you don't have a Windows NT WINS server,
and the primary and backup domain controllers are on different subnets,
you will need to use nbutil to load the NetBIOS
name-to-IP address mappings as described in the Advanced
Server/9000 Administrator's Guide.
During the installation of a primary domain controller, you
are prompted for the server name, server role, domain name, and
administrative account password. For information about these items,
see the section titled "Data Needed during Installation"
earlier in this chapter.
When running asu_inst, it will first ask the type of setup
you wish to perform: Express Setup or
Custom Setup:
Express Setup - the installation scripts use default
settings so installation is quick and easy. You may
change these settings after installation completes.
The server is installed as a primary domain controller
in its own domain. |
Custom Setup - this mode allows you to specify the
settings at the beginning of installation. If you
select this mode, you must specify the server's name,
the domain it will participate in, and the role in
that domain. |
 |
Selecting the Express Setup will set up the server using the
defaults. The system name will be used for the server name, the
server role will be a Primary Domain Controller, the domain name
will be the system name appended with _dom, and administrative account
password will be password. Express setup
does not require any user interaction to complete. Selecting Custom
Setup will prompt for the server name, server role, domain name,
and administrative account password. User interaction is required
for Custom Setup. At the prompt, select 'y' to use Express Setup,
'n' to use Custom Setup. After asu_inst has completed, you can use
the joindomain, setservername,
and setdomainname commands to change the server
configuration. See the Advanced Server/9000 Administrators
Guide for more information on these commands.
To install the Advanced Server/9000 as a primary domain controller:
Run the utility to configure Advance Server/9000: /opt/asu/lanman/bin/asu_inst
The system begins the installation process which
includes incorporating and updating the saved files and adding the
server to the protocol stack.
The system displays the following message:
Advanced Server for UNIX provides a NETLOGON service which simplifies the administration of multiple servers. A single user accounts database can be shared by multiple servers grouped together into an administrative collection called a domain. Within a domain, each server has a designated role. A single server, called the primary domain controller, manages all changes to the user accounts database and automatically distributed those changes to other servers, called backup domain controllers, within the same domain. You may now supply a server name (the name which this server will be known on the network), the role that this server will perform in that domain (primary or backup), and a domain name. Enter the name of the server or press Enter to select 'uname': |
Enter the name of the server or press ENTER to accept
the default name. See the section titled "Data Needed during
Installation" earlier in this chapter for information about
the server name.
The system displays the following message:
Each server must be given a role in a domain. The possible
roles are:
primary domain controller:
Administration server. Distributes user accounts information
to backup domain controllers. Validates network logon
requests. There can be only one primary domain controller per
domain.
backup domain controller:
Receives user account information from the primary domain
controller. Validates network logon requests and can be
promoted to primary if the primary domain controller is not
accessible.
Enter role (primary or backup): |
Type primary and press ENTER.
The system prompts you for the name of the domain.
Enter the name of a domain or press ENTER to accept
the default (uname_dom).
The system displays the following message and prompt:
This server will be the primary controller for the domain.
An administrative account Administrator will now be created
for you to manage the domain. |
Enter the password for Administrator: |
Enter a password for the Administrator account.
It can be up to 14 characters in length. Re-enter it when prompted.
It is recommended you change the Administrator password at
this time. Record this password for future reference.
If you do not enter an Administrator password, the Administrator
will not have a password--allowing anyone administrative ability
on the server!
The system will ask you to confirm your choices.
Confirm or make changes when prompted. The system continues the
installation process which includes creating a user accounts database,
a new access control list database, and a new share list file.
The asu_inst script
starts the Advanced Server/9000 and sends mail to root which contains
a listing of the available resources. If the Advanced Server/9000
does not start, check the error messages and follow the instructions
in the section titled "Troubleshooting Installation problems."
When you see the following message, installation of the primary
domain controller is complete.
* The Advanced Server for UNIX
Systems is now operational. |
Printable version
