LDAP-UX Client Services B.04.10 with Microsoft Windows Active Directory Server Administrator's Guide

For information about importing information into the directory, refer to “Importing Name
Service Data into Your Directory” (page 35). For information on migration scripts, refer to
“Command, Tool, Schema Extension Utility, and Migration Script Reference” (page 145).
CAUTION: If a root login is placed in the Active Directory, that user and password will be
able to log in as root to any client using LDAP-UX Client Services. It is recommended that
you keep the root user in /etc/passwd on each client system so the root user can be
managed locally, and to allow local access to the system. It is not recommended to put the
same users both in /etc/passwd and in the directory, as this could cause conflicts and
unexpected behavior.
• How many profiles do you need?
If you use ADS multiple domains, refer to “Active Directory Multiple Domains” (page 57)
for more information about configuring remote domains.
If ADS multiple domains are not used, refer to the following information.
A configuration profile is a directory entry that contains configuration information shared
by a group of clients. The profile contains the information clients need to access user and
group data in the directory. For example, this information includes:
— Your directory server hosts.
— Where your supported name service data is in the directory.
— Other configuration parameters such as search time limits.
If these parameters are the same for all your clients, you need only one profile. You will
need at least one profile per Active Directory Domain Controller. In general, it is a good
idea to have as few profiles as necessary to simplify maintenance. Refer to “LDAP-UX Client
Services Object Classes” (page 141) to decide how many different profiles you need.
If you are familiar with NIS, one example is to create a separate profile for each NIS domain.
• Where will you put your profile in your directory?
The profile contains directory access information, specifying how and where clients can find
user and group data in the directory. You can put the profile with your user data, or in a
separate configuration area. Clients must have access to the profile and the user, as well as
the group data. The following example shows a configuration profile DN of CN=profile1,
CN=Configuration, DC=cup, DC=hp, DC=com.
Figure 2-1 Example Directory Structure for a Single Domain
DC=cup, DC=hp, DC=com
CN=Configuration
CN=Users
profile
data
group
data
user
data
26 Installing LDAP-UX Client Services