[MS-DFSRH]: DFS Replication Helper Protocol Specification

3 Protocol Details3.1 Server Role Details3.1.1 Abstract Data ModelNo abstract data model is required.3.1.2 TimersNo timers are required.3.1.3 InitializationThe server MUST be considered to be initialized after a successful activation of one of the threeinterfaces that are registered with the Distributed Component Object Model (DCOM) RemoteProtocol infrastructure, as specified in [MS-DCOM] section 1.3.6.3.1.4 Higher-Layer Triggered EventsAll method invocations are triggered by higher-layer events, such as commands issued withinadministrative and diagnostic applications. The details of method invocations are provided in thefollowing sections.3.1.5 Message Processing Events and Sequencing Rules3.1.5.1 Methods with PrerequisitesThe methods of the IServerHealthReport, IADProxy, and IADProxy2 interfaces require noprerequisite calls against the server.3.1.5.2 IADProxy InterfaceThe IADProxy interface, as specified in MS-DCOM, inherits the IUnknown interface. Method opnumfield values start with 3; opnum values 0 through 2 represent the IUnknown_QueryInterface,AddRef, and Release methods, respectively.To receive incoming remote calls for this interface, the server MUST implement a DCOM object usingthe UUID {4BB8AB1D-9EF9-4100-8EB6-DD4B4E418B72}.In these methods, the DFS-R Helper Protocol calls several Windows APIs and returns the error codesreturned by these APIs. In the following sections, these codes are referred to as nonzeroimplementation-specific error codes.Methods in RPC Opnum OrderMethodCreateObjectDeleteObjectDescriptionCreate an Active Directory object with the specified distinguished name and attributes.Opnum: 3Delete an Active Directory object with the specified distinguished name.Opnum: 452 / 81[MS-DFSRH] – v20080207DFS Replication Helper Protocol SpecificationCopyright © 2008 Microsoft Corporation.Release: Thursday, February 7, 2008