Importing LDIF files during setup
Applies To: Windows Server 2003 R2
On the Import LDIF Files page, you can specify that the optional ms-InetOrgPerson.ldf, ms-User.ldf, ms-UserProxy.ldf, and MS-AZMan.ldf LDAP Data Interchange Format (LDIF) files be imported. Together, these files contain several user class schema definitions, along with objects for use with Windows Authorization Manager, that can be imported into the schema of the new ADAM instance that is currently being installed.
To import LDIF files during setup
On the Import LDIF Files page, do one of the following, and then click Next:
If you do not want to import or use the optional user class schema definitions, click Do not import LDIF files for this instance of ADAM.
If you want to use the optional user class schema definitions or Windows Authorization Manager with your ADAM instance, click Import the selected LDIF files for this instance of ADAM; in Available files, click one or more of the LDAP Data Interchange Format (LDIF) files to import; and then click Add.
The following table describes each of the optional .ldf files.
.ldf file User classes Import this file if ...
You want to create user objects in the ADAM directory, but you do not want to create users of the InetOrgPerson class (as defined in RFC 2798).
You want to create user objects in the ADAM directory, and you want to create users of the InetOrgPerson class (as defined in RFC 2798).
You want to create proxy objects in ADAM for use in bind redirection. For more information about proxy objects and bind redirection, see Understanding ADAM bind redirection.
- Not applicable
You want to use Windows Authorization Manager with ADAM. For information about role-based authorization in Windows Server 2003, see "Dynamic Groups in Windows Server 2003 Authorization Manager" at the Microsoft MSDN Web site.
If you choose not to import these LDIF files during setup, you can import them at a later time, using the ldifde command-line tool. For more information, see Related Topics.
This wizard page appears only during the installation of a unique ADAM instance and not during the installation of a replica ADAM instance.
You must be logged on as an account that is specified as the ADAM administrator to import these schema class definitions into the ADAM schema.
Import the user classes supplied with ADAM
Administering users and groups
Understanding ADAM users and groups