LDAP-UX Client Services B.04.00 with Microsoft Windows 2000/2003 Active Directory Administrator's Guide

Active Directory Multiple Domains
Downloading an Automatic Profile
Chapter 364
Downloading an Automatic Profile
When you select the GCS to retrieve data from remote domains, it is not
necessary to specify which domains LDAP-UX is to search. However, you
should create a profile for every domain in the forest so LDAP-UX has
the information about where and how to establish the connection with
their domain controllers in the forest.
Not every LDAP-UX client has to create the profile entry in the directory.
The LDAP-UX configuration profile created by setup and saved in the
directory server (ADS domain controller) is designed to be shared by
many clients. In previous releases, when the first LDAP-UX client
created the profile entry in the directory, other LDAP-UX clients still had
to download it from the server. In the B.03.00 release, LDAP-UX can
automatically download the profile if the following two conditions are
met:
• If the first LDAP-UX creating the profile entry in the directory uses a
standard profile path (for example,
CN=ldapuxprofile,CN=configuration,DC=ca,DC=hp,DC=com)
• If LDAP-UX clients use the same DNS for ADS, which can support
service location resource records (SRV) described in RFC 2052
When an LDAP-UX client binds to ADS, if the profile does not exist
locally, LDAP-UX queries DNS for the server and port information, then
connects to the server to download the profile entry using the standard
path. This feature eliminates administration costs to set up agreements
between domains. As long as the first LDAP-UX client creates the profile
entry using the standard path, the following LDAP-UX clients
automatically download it.
NOTE By default, the cn=configuration,DC=myorg,DC=mycom,DC=com
configuration container only exists in the root domain. To create the
standard profile path for LDAP-UX, manually create it in each domain
using ADSI Edit before running the setup tool to configure profiles.