LDAP-UX Client Services B.05.01 Administrator Guide for HP directory servers and Windows ADS

add the unixAccount attributes to your existing entries under CN=Users and add their HP-UX
information there.
• Ensure that the user and group numbers to be imported or migrated do not collide with those
already on the HP-UX host (see Section 3.5.1.1 (page 152)).
3.5.1.1 Prevent user and group number collisions with those already on the HP-UX host
Before you import users into Windows ADS, make sure no users or groups to be managed in the
directory server collide with users or groups managed in the /etc/passwd and /etc/group
files on the HP-UX hosts being managed in the domain. To avoid UID number or GID number
collisions, a best practice is to establish separate UID and GID number ranges used on the HP-UX
host from those that will be used for directory entries. For example, all UID numbers less than 1000
could be reserved for entries in the /etc/passwd and /etc/group files.
3.5.1.2 Steps for importing name service data
To import your user, group, and other services data into your directory, complete the following
steps, modifying them as necessary.
1. Decide which migration method and scripts you will use.
Migration scripts are provided to ease the task of importing your existing name service data
into your Active directory. For a complete description of the scripts, what they do, and how
to use them, see Section 9.6 (page 383). Modify the migration scripts, if needed.
2. Back up your directory.
3. Run the migration scripts.
4. If the migration method that you used did not already import your data, use ldapmodify to
import the LDIF file into your directory.
3.5.2 Verifying LDAP-UX Client Services for Single Domain
For simple ways to verify the installation and configuration of your LDAP-UX Client Services, see
Section 2.5.2 (page 91). You might need to do more elaborate and detailed testing, especially if
you have a large environment.
3.5.3 Enabling AutoFS support
AutoFS is a client-side service that automatically mounts appropriate file systems when users request
access to them. If an automounted file system has been idle for a period of time, AutoFS unmounts
it. AutoFS uses name services such as files or NIS to store and manage AutoFS maps.
LDAP-UX Client Services B.04.10 and later supports the automount service under the AutoFS
subsystem. This feature enables users to store AutoFS maps in an Windows 2003 R2 or 2008
Active Directory Server (ADS).
3.5.3.1 Automount schema
This section describes the automount schema based on RFC 2307-bis.
This schema defines automountMap and automount structures to represent AutoFS maps and
their entries in the directory server. AutoFS maps are stored in the directory server using structures
defined by this schema.
This automount schema is not loaded in the Windows 2003 R2 or 2008 Active Directory Server.
If you are installing LDAP-UX B.04.10 or later on your client system, the setup program will import
the automount schema into your Active Directory Server. If you previously configured LDAP-UX
B.04.00 or a previous version, and are now updating the product to version B.04.10 or later, you
must rerun the setup program to import the automount schema into the directory server. The
subsequent client systems do not need to rerun the setup program.
The following shows the automount schema based on RFC 2307-bis in the LDIF format:
152 Installing and configuring LDAP-UX Client Services for a Windows ADS environment