Automatic Profile Downloading

When you choose the GCS to retrieve data from remote domains, you don't have to explicitly specify which domains you want LDAP-UX to search, but you still need to create a profile for every domain in the forest so that LDAP-UX has the information about where and how to establish the connection with their domain controllers in the forest (set up described below in step 5). However, 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, once the first LDAP-UX client creates 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:

When LDAP-UX client binds to ADS, if the profile doesn't 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, you need to manually create it in each domain using ADSI Edit before you run the setup tool to configure profiles.