[MS-DFSRH]: DFS Replication Helper Protocol Specification

[in] BSTR distinguishedName,[in] SAFEARRAY(_AdAttributeData)* attributes,[in] BSTR verifyNameDomainControllerName,[in] BSTR networkNameResourceName);domainControllerName: MUST be the FQDN of the domain controller to which the methodsends the LDAP request. The format of the distinguished name MUST be as specified in[RFC2251] section 4.1.3.distinguishedName: MUST be the distinguished name of the Active Directory object that isbeing created. The distinguished name of any object in Active Directory MAY be used. Theformat of the distinguished name is specified in [RFC2251] section 4.1.3.attributes: MUST be the safe array of attributes that are to be created for the new object.verifyNameDomainControllerName: If the attributes of the object refer to an object inanother domain, the client MUST specify the domain controller in that domain that will be usedto verify the reference. The LDAP_SERVER_VERIFY_NAME_OID control MUST be added to theLDAP command. The LDAP_SERVER_VERIFY_NAME_OID control is specified in [MS-ADTS]section 3.1.1.3.4.1.16. If this parameter does not specify a domain controller that can becontacted to validate these references, the method MUST fail and return an LDAP protocolfailure.networkNameResourceName: MUST be the name of the cluster resource (the resource typeMUST be "Network Name"). If this parameter is a non-empty string, the server MUST executethe LDAP command under the account that corresponds to this network name. There are noconstraints regarding the format of the network name except the requirement that its lengthMUST NOT be longer than 32,767 characters. Otherwise, if this parameter is NULL or anempty string, the server MUST use the machine account to execute the LDAP command.Return Values: Return Values: The method MUST return:• 0 on success.• For LDAP protocol failures:• If the LDAP error is LDAP_OPERATIONS_ERROR, dfsrHelperLdapErrorBase + the serversideerror code.• For all other LDAP errors, dfsrHelperLdapErrorBase + the LDAP return code. For moreinformation, see [LDAP-ERR].• For all other failures, an implementation-specific nonzero HRESULT error code, as specifiedin [MS-ERREF] section 2.1, between 0x80000000 and 0xFFFFFFFF. For protocol purposes,all nonzero values MUST be treated as equivalent failures.The server MUST handle this message by using the same sequence of steps as forIADProxy::CreateObject (as specified in section 3.1.5.2.1), with the following additional step:• The server MUST execute the LDAP command under the credentials that correspond to thenetwork resource name that is supplied in the networkNameResourceName parameter.[MS-DFSRH] – v20080207DFS Replication Helper Protocol SpecificationCopyright © 2008 Microsoft Corporation.Release: Thursday, February 7, 200858 / 81