LDAP-UX Client Services B.05.00 with Microsoft Windows Active Directory Server Administrator's Guide (obsolete beyond B.05.00)

• If multiple domains are selected, how will data be stored in the forest?
LDAP-UX Client Services treats the first domain configured as the local domain, and all other
domains in the forest as remote domains. When retrieving data, the search always starts from
the local domain. Frequently accessed information should be stored in the local domain.
For remote domains, information can be stored in every remote domain or only in some remote
domains. Determine the appropriate structure for your environment.
• If multiple domains are selected, how will data be retrieved?
When multiple domains are selected, LDAP-UX Client Services has search rules for remote
domains. For information about configuring the search sequence, refer to “Active Directory
multiple domains” (page 64).
• How many directory databases are needed?
Each client system binds to an Active Directory Server containing your supported name service
data (such as user and group data). On Active Directory networks, each domain controller
contains a copy of the Active Directory database.
The specific number of domain controllers necessary in your network depends on the network
size and configuration. A minimum of two Active Directory domain controllers are recommended
for each domain. For more information, refer to the Active Directory documentation, or to
http://www.microsoft.com/Windows2003 and http://windowsupdate.microsoft.com.
• Where will you get your name service data when migrating the data to the directory?
You can get the data from:
◦ /etc/passwd and /etc/group
◦ The same source files used to create your NIS maps, if using NIS
◦ The NIS maps
For information about importing information into the directory, refer to Section 2.5.1 (page 52).
For information on migration scripts, refer to the “Command and tool reference” chapter of
the LDAP-UX Client Services Administrator's Guide.
To add an individual user entry or modify an existing user entry in your directory, use the
ldapugadd or ldapugmod commands or other directory administration tools, such as
ldapmodify or the Active Directory Users and Computers interface tool.
NOTE: Keep a small subset of users in /etc/passwd, particularly the root login (any
account with uid number 0). This allows administrative users to log in during installation and
testing. Also, if the directory is unavailable you can still log in to the system.
• Where will name service data be located in your directory?
LDAP-UX Client Services, by default, expect user and group data to use the object classes and
attributes specified by RFC 2307. The migration scripts for Active Directory, by default,
populate the existing Users container. Figure 5 (page 31) shows a base DN of DC=cup,
DC=hp, DC=com.
If you prefer to merge your name service data into an existing directory structure, you can
map the standard RFC 2307 attributes to alternate attributes. Refer to Appendix B (page 146).
• How will user and group data be migrated into your directory?
The migration scripts provided with LDAP-UX Client Services for Active Directory migrate all
user and group data to the "Users" container.
If you merge your data into an existing directory, for example, to share user names and
passwords with other applications, the migration scripts can create LDIF files of your user data,
2.4 Customized installation (setup) 29