13.07.2015 Views

[MS-DFSRH]: DFS Replication Helper Protocol Specification

[MS-DFSRH]: DFS Replication Helper Protocol Specification

[MS-DFSRH]: DFS Replication Helper Protocol Specification

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

[in] BSTR distinguishedName,[in] SAFEARRAY(_AdAttributeData)* attributes,[in] BSTR networkNameResourceName);domainControllerName: MUST be the FQDN of the domain controller to which the methodsends the LDAP request.distinguishedName: MUST be the distinguished name of the Active Directory object that isbeing modified. 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 added, modified, or deleted.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 lengthbe no more than 32,767 characters. Otherwise, if this parameter is NULL or an empty string,the server MUST use the machine account to execute the LDAP command.Return Values: The method MUST return:• 0 on success.• For LDAP protocol failures:• If the LDAP error is LDAP_OPERATIONS_ERROR, dfsr<strong>Helper</strong>LdapErrorBase + the serversideerror code.• For all other LDAP errors, dfsr<strong>Helper</strong>LdapErrorBase + the LDAP return code. For moreinformation, see [LDAP-ERR].• For all other failures, an implementation-specific nonzero HRESULT error code, as specifiedin [<strong>MS</strong>-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::ModifyObject (as specified in section 3.1.5.2.3), 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.3.1.5.4 IServerHealthReport InterfaceThe IServerHealthReport interface, as specified in <strong>MS</strong>-DCOM, inherits the IUnknown interface.Method opnum field values start with 3; opnum values 0 through 2 represent theIUnknown_QueryInterface, AddRef, and Release methods, respectively.To receive incoming remote calls for this interface, the server MUST implement a DCOM object usingthe UUID {E65E8028-83E8-491b-9AF7-AAF6BD51A0CE}.Methods in RPC Opnum Order[<strong>MS</strong>-<strong><strong>DFS</strong>RH</strong>] – v20080207<strong>DFS</strong> <strong>Replication</strong> <strong>Helper</strong> <strong>Protocol</strong> <strong>Specification</strong>Copyright © 2008 Microsoft Corporation.Release: Thursday, February 7, 200860 / 81

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!