Several of the steps in this process use the Microsoft
ldifde utility, a relatively complex command-line utility with many options. You may want to read the documentation for
ldifde that comes with ADAM.
Here are some tips for using
ldifde:
- The
ldifde command reads an LDIF file (with a
.ldf extension) and updates AD with the objects listed in the file. LDIF files are text files and can be edited in editors such as Notepad.
- Many of the
ldifde command lines shown below use the
-c option, which takes two strings as parameters, and changes the first string to the second wherever it appears in the input. For example, the parameter
-c DC=X DC=mydom,DC=com changes
DC=X in the
.ldf file to
DC=mydom,DC=com. You would use this to customize the information in the default
.ldf files for your installation.
- You can copy the
.ldf files to your AD server and run
ldifde there, or you can run it on a system with
Enterprise Developer installed, and then update AD remotely with the modified
.ldf files.
- ldifde has to bind (log on to) AD in order to make changes to the directory. If you are not logged on as an authorized AD user, you can add
-b username
domain
password to the
ldifde command line to specify the authorization to use.
- In the
ldifde command lines below, the
-s servername option tells
ldifde the hostname of the AD server. If you are running on the AD server, or if your AD server is the domain controller for the domain that you are running in, you can omit the
-s servername option.
- Each time you run
ldifde (with the
-j . option), it creates an
ldif.log file in the current directory. If there are errors or warnings, it creates an
ldif.err file as well. If the files already exist, they will be overwritten. We recommend you rename the log file after each
ldifde run (eg to ldif-1.log,
ldif-2.log, etc) so you can send them to
SupportLine if you have problems. If an
ldifde command fails, you can check the log and error files for more information.
A typical ldifldifdede command has these parts:
| Ldifde
|
Command name
|
| -i
|
Command type: import data into AD
|
| -f filename.ldf
|
Specify LDIF file to import from
|
| -s servername
|
Hostname of AD server
|
| -k
|
Keep going even if some entries can't be processed
|
| -j .
|
Create log files in current directory
|
| -c from-string to-string
|
Change from-string in data to to-string. This lets you customize a generic LDIF file for your installation. For example, from-string might be the placeholder DC=X, and to-string might be your domain DN.
|