[MS-VDS]: Virtual Disk Service (VDS) Protocol Specification

1.4 Relationship to Other ProtocolsThe Virtual Disk Service Remote Protocol relies on DCOM [MS-DCOM], which uses remoteprocedure call (RPC) as its transport.The Virtual Disk Service Remote Protocol was designed to replace the Disk Management RemoteProtocol [MS-DMRP] for storage management tasks.1.5 Prerequisites and PreconditionsThe Virtual Disk Service Remote Protocol is implemented over DCOM (as specified in [MS-DCOM])and RPC; as a result, it has DCOM prerequisites, as specified in [MS-DCOM] and [MS-RPCE], asbeing common to DCOM and RPC interfaces.The Virtual Disk Service Remote Protocol assumes that a client has obtained the name of a serverthat supports this protocol suite before the protocol is invoked. The protocol also assumes that theclient has sufficient security privileges to configure disks and volumes on the server.An operating system on which an implementation of the Virtual Disk Service Remote Protocol is torun must be able to dynamically requery the list of storage devices and mount points that areavailable during run time. For more information on these requirements, see sections 3.4.5.2.4.10and 3.4.5.2.4.11.1.6 Applicability StatementThe Virtual Disk Service Remote Protocol applies when an application needs to remotely configuredisks, volumes, and iSCSI initiators.Applications may also use DMRP, as specified in [MS-DMRP], to perform logical functions that aresimilar to those that the Virtual Disk Service Remote Protocol performs.1.7 Versioning and Capability NegotiationSupported Transports: The Virtual Disk Service Remote Protocol uses the DCOM Remote Protocol (asspecified in [MS-DCOM]), which in turn uses RPC over TCP as its only transport. For moreinformation about transport, see section 2.1.Protocol Version: The Virtual Disk Service Remote Protocol comprises a set of DCOM interfaces,which are all version 0.0.Functionality Negotiation: The client negotiates for a specified set of server functionality byspecifying the UUID that corresponds to the necessary RPC interface by means of COMIUnknown::QueryInterface when binding to the server. Certain interfaces are implemented by onlyparticular objects on the server. For more information on storage management objects, see section3.4.1.2.Security and Authentication Methods: For more information, see DCOM, as specified in [MS-DCOM],and RPC, as specified in [MS-RPCE].1.8 Vendor-Extensible FieldsThe Virtual Disk Service Remote Protocol does not define any vendor-extensible fields.Unless otherwise specified, all methods MUST return zero or a non-error HRESULT (as specified in[MS-ERREF]) to indicate success or return an implementation-specific nonzero error code to indicate[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 201122 / 360