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

virtual disk: A disk that does not have a physical mechanical counterpart to it, and is notexposed as a hardware array LUN. It is a disk that uses a file to store its data. When this fileis exposed to the operating system as a disk device, the exposed disk device emulates and,for all intents and purposes, behaves like a physical disk.virtual disk file: The file that is the backing store for a virtual disk. This file may be exposedto an operating system as a disk device. The exposed disk device is referred to as a virtualdisk.virtual disk provider: A VDS object that allows query and management of virtual disks on asystem.Virtual Disk Service (VDS): If the term is used as a noun, VDS refers to the servicecomponent that runs on the server. If VDS is used as an adjective, it refers to the protocolthat is specified in this document (which the service uses to communicate with clients).virtual hard disk: Same as a virtual disk.VDS object: An instance of a class that exposes one or more DCOM interfaces to query orconfigure the VDS service, the operating system device (such as a disk or volume), or theconcept (such as a software provider) that the object represents. Each object has anassociated type that indicates the type of device or concept that it represents. Unlessotherwise indicated, the term "object" refers to a VDS object.volume plex member: A RAID construct for organizing disks and volumes. Also called aRAID column.Windows Event log: An audit trail created by Windows instrumentation manifest to monitor thehealth of the operating system and to help troubleshoot issues when they arise. The eventlogs can be browsed and managed by Windows Event Viewer.Windows Preinstallation Environment (Windows PE): A minimal Windows systemenvironment that provides limited services based on the Windows XP, Windows Server 2003,or Windows Vista kernels. It provides the minimum set of features that are required to run theoperating system setup, perform system recovery, access and install operating systems fromthe network, script basic repetitive tasks, and validate hardware.MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used asdescribed in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, orSHOULD NOT.1.2 ReferencesReferences to Microsoft Open Specification documents do not include a publishing year because linksare to the latest version of the documents, which are updated frequently. References to otherdocuments include a publishing year when one is available.1.2.1 Normative ReferencesWe conduct frequent surveys of the normative references to assure their continued availability. Ifyou have any issue with finding a normative reference, please contact dochelp@microsoft.com. Wewill assist you in finding the relevant information. Please check the archive site,http://msdn2.microsoft.com/en-us/library/E4BD6494-06AD-4aed-9823-445E921C9624, as anadditional source.[MS-VDS] — v20110610Virtual Disk Service (VDS) Protocol SpecificationCopyright © 2011 Microsoft Corporation.Release: Friday, June 10, 201118 / 360