LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

optionally the port), and the bind DN and password of a user who has sufficient privileges to
add the local HP-UX host to the LDAP-UX domain. When you specify a remote host where the
existing directory server is located, the guided installation cannot validate the identity of the
directory server unless a valid domain (CA certificate) or server certificate exists on the local
host. If one does not exist, you are given the option of having the guided installation download
and install the CA or server certificate (without trust) or, if the server was created by
autosetup, you can download (from the server to your host) a certificate depot that installs
the CA certificate for the LDAP-UX domain.
For information about installing LDAP-UX for the first time in an existing directory server
environment, see Section 2.3.5 (page 52).
• Installing LDAP-UX into an existing LDAP-UX domain (Existing LDAP-UX Domain Installation
mode): In this scenario, LDAP-UX has already been configured in the environment. You can
then use the guided installation to join the HP-UX host to an existing LDAP-UX domain (or to
a Windows ADS domain). The guided installation simply downloads the existing domain
configuration (LDAP-UX configuration profile) and registers the host in the domain.
In this scenario, the guided installation prompts you for similar input as does the preceding
scenario, and if you have not preinstalled the CA certificate, you are also asked if you want
to trust the directory server.
For information about installing LDAP-UX into an existing LDAP-UX domain, see Section 2.3.6
(page 55).
NOTE: You can install LDAP-UX into an existing LDAP B.04.xx environment; however, the
hosts search descriptor serviceSearchDescriptor in the LDAP-UX configuration profile
will likely define an incorrect location for host entries (it should be ou=hosts). Host tools
expect the correct location for host entries to be defined in the configuration profile. If the
location is incorrect, the ldaphostmgr tool will add hosts to an incorrect location in the
directory tree.
The guided installation (with LDAP-UX B.05.00 or later) configures the profile with the correct
location for host entries. If you are installing LDAP-UX into an LDAP-UX environment that has
not been set up by the guided installation, ensure that the correct location is specified in the
profile (normally, that is ou=hosts). To determine the location configured for hosts in the
LDAP-UX configuration profile, you can use the following command:
/opt/ldapux/bin/ldapcfinfo -t hosts -b
If you need to modify the configuration profile, you can modify the
serviceSearchDescriptor attribute for the hosts service. For information about how
to modify the LDAP-UX configuration profile, see Section 7.10.2 (page 245).
In these autosetup scenarios, you configure LDAP-UX on the local host for the first time. When
installing LDAP-UX to create a new directory server, autosetup introduces the LDAP-UX domain
to your organization, creates a directory server and a new LDAP-UX configuration profile, configures
your local HP-UX host, and joins the host to the LDAP-UX domain. When installing LDAP-UX into
an existing directory server environment, autosetup introduces the LDAP-UX domain to your
organization using an existing directory server, creates a new LDAP-UX configuration profile,
configures your local HP-UX host, and joins the host to the LDAP-UX domain. When installing
LDAP-UX into an existing LDAP-UX domain, autosetup configures your local HP-UX host based
on an existing directory server LDAP-UX configuration profile, and joins the host to the existing
LDAP-UX domain.
If no valid directory server software is installed on the local system, the guided installation prompts
you for the name of an existing remote directory server. If the specified directory server not found,
the guided installation aborts.
2.3 Guided installation (autosetup) for an HP directory server environment 29