Export (0) Print
Expand All

3.1.1.3.3.27 disableOptionalFeature

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

This operation is triggered by setting the disableOptionalFeature attribute to a value that contains the DN of the object that represents the scope, followed by the colon (:) character, followed by the GUID of the optional feature to be disabled, 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 feature is not marked as being able to be disabled, the server will return the error unwillingToPerform / ERROR_DS_NOT_SUPPORTED.

If the specified optional feature is not already enabled in the specified scope, the server will return the error noSuchAttribute / ERROR_DS_CANT_REM_MISSING_ATT_VAL.

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

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

dn:
changetype: modify
add: disableOptionalFeature
disableOptionalFeature: cn=Partitions,cn=Configuration,DC=Contoso,DC=Com:766DDCD8-ACD0-445E-F3B9-A7F9B6744F2A
-
 
Show:
© 2015 Microsoft