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

Section 3.1.7.1: This interface is only supported in Windows Server 2003 R2, Windows Vista,Windows Server 2008, Windows 7, and Windows Server 2008 R2. If a client attempts to get theinterface on a previous version of Windows by calling IUnknown::QueryInterface, E_NOINTERFACE(0x80004002) is returned. Attempting to call these methods with opnums 5 or 6 may result in NDRraising an RPC_X_BAD_STUB_DATA exception. For more information, see [MS-DCOM]. Section 3.1.7.1: Gaps in the opnum numbering sequence apply to Windows as follows.OpnumDescription05 Only used locally by Windows, never used remotely.06 Only used locally by Windows, never used remotely. Section 3.1.8.1: This interface is only supported in Windows Server 2003 R2, Windows Vista,and Windows Server 2008, Windows 7, and Windows Server 2008 R2. If a client attempts to get theinterface on a previous version of Windows by calling IUnknown::QueryInterface, E_NOINTERFACE(0x80004002) is returned. Attempting to call methods with opnums 5, 6, or 7 may result in NDRraising an RPC_X_BAD_STUB_DATA exception. For more information, see [MS-DCOM]. Section 3.1.8.1: Gaps in the opnum numbering sequence apply to Windows as follows.OpnumDescription05 Only used locally by Windows, never used remotely.06 Only used locally by Windows, never used remotely.07 Only used locally by Windows, never used remotely. Section 3.1.11.1: Attempting to call a method with opnum 10 may result in NDR raising anRPC_X_BAD_STUB_DATA exception. For more information, see [MS-DCOM]. Section 3.1.11.1: Gaps in the opnum numbering sequence apply to Windows as follows.OpnumDescription10 Only used locally by Windows, never used remotely. Section 3.1.12.4: This method is not implemented for removable disks in WindowsServer 2003. Section 3.3.6: When the sequence shown in the following event log entry is executedrepeatedly in a program (say, 200 times) on Windows Server 2008, the client will occasionallyencounter the error "0x800706BE". This error mainly comes at AddDisk and sometimes on Wait. Inthis circumstance, the following entry is recorded in the event log on the server:"====Faultingapplication vds.exe, version 6.0.6001.18000, time stamp 0x479198cb, faulting module ntdll.dll,version 6.0.6001.18000, time stamp 0x4791adec, exception code 0xc0000005, fault offset0x000000000001f7fa, process id 0xda4, application start time 0x01c967e37ddea470.====-QueryUnallocatedDisks- CreatePack- AddDisk- Clean- Wait (for clean to complete)" Section 3.4.1.1: See the product behavior note in section 1.7, which specifies which interfacesare included in the various versions of Windows. Note that the set of VDS interfaces is accumulative;interfaces are never removed. For example, IVdsService and IVdsServiceInitialization shippedwith Windows Server 2003, and therefore are present in Windows Server 2003 R2, Windows Vista,[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011342 / 360