You can use the Microsoft LDIFDE command to import configuration data from an LDIF configuration file into a standard or replica View Connection Server instance.

About this task

In View releases earlier than View 4.5, you must use the Microsoft LDIFDE command to import configuration data from an LDIF configuration file. The vdmimport command is not supported in View releases earlier than View 4.5.

If you have View 4.5 or later, use the vdmimport command rather than the LDIFDE command. The vdmimport command does not display the large number of error messages that are produced by running the LDIFDE command. For more information, see Use the vdmimport Command to Import LDAP Configuration Data.

Because the LDIFDE command does not update, create, or delete any LDAP records that are not defined in the LDIF configuration file, it enables you to customize an LDIF configuration file so that only selected records are affected when you import the file. For complete information about using the LDIFDE command, go to http://support.microsoft.com/kb/237677.

Prerequisites

Export LDAP configuration data to an LDIF configuration file. See Export LDAP Configuration Data.

Procedure

  1. Log in to a View Connection server instance.

    Option

    Action

    View 3.1 or earlier

    Log in as an administrator and be a member of the Local Administrators user group.

    View 4.5 or later

    Log in as a user in the Administrators role.

    Note:

    You must be logged in as a user in the Administrators role to import configuration data into the View configuration repository.

  2. At the command prompt, type the LDIFDE command and use the -f option to specify an existing LDIF configuration file.

    For example: LDIFDE -i -f myexport.LDF -s 127.0.0.1 -z

Results

After the LDIFDE command runs, the configuration of your View Connection Server instance is updated with the data from the file, and the number of records that are successfully updated is displayed.

Error messages appear whenever an existing entry in the repository is overwritten. You can ignore these error messages. Error messages also appear if a record cannot be updated because your role has insufficient privileges.