To extend an AD LDS repository to support Enterprise Server configuration objects

Restriction: This topic applies only when the Enterprise Server feature is enabled.

Create an LDIF file containing the required schema extensions by using the mfds -L command. For example, at the command line, enter:
```
mfds -L DC=X 1 mfds_schema.ldf
```
This creates an LDIF file mfds_schema.ldf. The DC=X specifies distinguished name for the schema partition string assigned to each entry in the LDIF file. You could specify the actual destination here, but typically you will want to create a portable file. In this example, we use DC=X and replace it with the appropriate value when we import.
Use the LDIFDE command to import the generated LDF file into AD LDS. For example,
```
ldifde -I -v -k -c "DC=X" CN=Schema,CN=Configuration,
DC=customer_dom,DC=com -f mfds_schema.ldf
```
The -c option replaces the schema partition string specified when creating the LDIF file with the schema partition into which the objects are to be imported. In this example, the container is CN=Schema,CN=Configuration, DC=customer_dom,DC=com but it will vary depending on your particular circumstances. If using AD LDS, the schema partition root can be extracted using the schemaNamingContext RootDSE attribute value e.g.
```
ldifde -i -f mfds-schema.ldf -s -k -v -j . -c "DC=X" #schemaNamingContext
```

Important: You must have sufficient rights to modify the LDAP schema and the schema must be writable.