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

Active Directory Multiple Domains

Changing Multiple Domain Conﬁgurations

Chapter 370

Re-ordering the Remote Domain Search Sequence

The search sequence is the sequence in which you conﬁgured the remote

domains during setup. This sequence is also shown in

/etc/opt/ldapux/ldapux_client.conf. To re-order the remote domain

search sequence, either run setup to re-conﬁgure the remote domains, or

manually edit the /etc/opt/ldapux/ldapux_client.conf ﬁle to

re-arrange the order. Restart the client daemon for the change to take

effect.

Adding the GCS into the Search Scope

The only way that you can add the GCS into the search scope is to run

setup and add the GCS as your multiple domain support. Restart the

client daemon for the change to take effect.

Removing the GCS from the Search Scope

To remove the GCS from the search scope, either run setup to

re-conﬁgure, or manually edit /etc/opt/ldapux/ldapux_client.conf

to remove the gc section, its corresponding proﬁles

(/etc/opt/ldapux/domain_profiles/ldapux_profile.bin.gc and

ldapux_profile.ldif.gc), and all entries to the end of the ﬁle. Restart

the client daemon for the change to take effect.

Adding POSIX Attributes to the Global Catalog

If you select GCS to support LDAP-UX integration with ADS multiple

domains, you should add POSIX attributes into the global catalog. The

needed attributes are those used by getXbyY() APIs to return data. For

LDAP-UX B.03.00, only passwd and group are supported in multiple

domains. Therefore, the following POSIX attributes must be added into

the global catalog:

• If your SFU version is 2.0:

msSFUName - used by getpwnam() and getgrnam()

uidNumber - used by getpwuid()

gidNumber - used by getgrgid()

• If your SFU version is 3.0 or 3.5:

msSFU30Name - used by getpwnam() and getgrnam()

msSFU30uidNumber - used by getpwuid()

msSFU30gidNumber - used by getgrgid()