Share via

3.1.1.3.3.28 enableOptionalFeature

  • Article

This operation requests that an optional feature (as described in section 3.1.1.9) be enabled for some scope. The requester MUST have the "Manage-Optional-Features" control access right on the object representing the scope.

This operation is triggered by setting the enableOptionalFeature attribute to a value that contains the DN of the object that represents the scope, followed by the ':' character, followed by the GUID of the optional feature to be enabled, expressed as a GUIDString.

If the server does not recognize the GUID as identifying a known feature, the server will return the error operationsError / ERROR_INVALID_PARAMETER.

If the DN represents an existing object but the object does not represent a scope, the server will return the error unwillingToPerform / ERROR_DS_NOT_SUPPORTED. If the DN does not represent an existing object, the server will return the error operationsError / ERROR_INVALID_PARAMETER.

If the feature is not marked as being valid for the specified scope, the server will return the error unwillingToPerform / ERROR_DS_NOT_SUPPORTED.

If the specified scope is forest-wide and this operation is not performed against the DC that holds the Domain Naming Master role, the server will return the error unwillingToPerform / ERROR_DS_NOT_SUPPORTED.

If the specified optional feature is already enabled in the specified scope, the server will return the error attributeOrValueExists / ERROR_DS_ATT_VAL_ALREADY_EXISTS.

The LDAP server returns success when the specified optional feature has been successfully enabled.

An LDIF sample that performs this operation is shown as follows.

 dn:
 changetype: modify
 add: enableOptionalFeature
 enableOptionalFeature: cn=Partitions,cn=Configuration,DC=Contoso,DC=Com:766DDCD8-ACD0-445E-F3B9-A7F9B6744F2A
 -