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

Interfaces that are used when querying HBA and iSCSI initiator information.The following table lists, by operating system version, the interfaces that are used when queryingHBA and iSCSI initiator information.Supported operating system versionInterfaceWindowsServer 2003WindowsServer 2003R2Windows VistaWindowsServer 2008IVdsServiceHba X X XIVdsServiceIscsi X X XIVdsHbaPort X X XIVdsIscsiInitiatorAdapter X X XIVdsIscsiInitiatorPortal X X X Section 2.1: Windows configures the underlying RPC transport by using the following flags. Formore information on the meaning of these flags, see [C706] and [MS-RPCE].•RPC_C_AUTHN_LEVEL_PKT_PRIVACY•RPC_C_IMP_LEVEL_IDENTIFY•EOAC_SECURE_REFS | EOAC_NO_CUSTOM_MARSHAL Section 2.1: The authorization constraints in Windows do not vary by operating systemrelease. All interfaces that are described in this document require an access level that correspondsto any of the following Windows security groups:•Administrators•Backup Operators•SYSTEM•The VDS Remote Protocol works only when the client and the server are on the same domain,or in domains that have a trust relationship with one another.•The VDS Remote Protocol does NOT work when client and server are on a workgroup; serverthrows ACCESS_DENIED error. Section 2.2.1.2.2: Windows does not currently send this notification under any circumstance,but may do so in future releases. Section 2.2.1.2.12: This enumeration type is used only in Windows Vista and WindowsServer 2008. Section 2.2.1.2.22: No Win32 API path names are created. Win32 APIs such asFindFirstVolume and FindNextVolume do not enumerate this volume. Section 2.2.1.2.23: The flag is set by default for dynamic disk and basic GPT disk volumes.VDS_VF_HIDDEN, VDF_VF_READ_ONLY, VDS_VF_SHADOW_COPY andVDS_VF_NO_DEFAULT_DRIVE_LETTER are set as follows:[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 2011337 / 360