7 Appendix B: Product Behavior

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Windows NT 3.1 operating system

  • Windows NT 3.5 operating system

  • Windows NT 3.51 operating system

  • Windows NT 4.0 operating system

  • Windows 2000 Server operating system

  • Windows XP operating system

  • Windows Server 2003 operating system

  • Windows Vista operating system

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 1.3: The server end of the Disk Management Remote Protocol is implemented by the Windows DmAdmin service on any machine that exposes storage objects for management. On each Windows machine, the client end of the Disk Management Remote Protocol is implemented by the DmRemote COM server. The DmRemote COM server invokes method calls on the DCOM interface on behalf of a number of components, including the Windows Logical Disk Manager (LDM) user interface (UI) and the Diskpart.exe command-line tool.

<2> Section 1.4:  The Disk Management Remote Protocol is used by the Windows LDM UI and the Diskpart.exe command-line tool.

<3> Section 1.6: Windows 2000 Server, Windows XP, and Windows Server 2003 implement the Disk Management Remote Protocol. The Windows Server 2003 operating system and Windows Vista implement the VDS Remote Protocol, which is used for disk management for these operating systems. The interfaces associated with the Disk Management Remote Protocol are not available on Windows Vista. The Disk Management Remote Protocol is replaced in Windows Vista by the VDS Remote Protocol.

<4> Section 1.7:

  • The IDMNotify and IDMRemoteServer interfaces are available on Windows XP, Windows 2000 Server, and Windows Server 2003.

  • The IVolumeClient and IVolumeClient2 interfaces are to be used for disk management for Windows 2000 Server. These interfaces can be used for disk management for Windows Server 2003 and Windows XP.

  • The IVolumeClient3 interface can be used with Windows XP and Windows Server 2003, but cannot be used with Windows 2000 Server.

  • The IVolumeClient4 interface can be used with Windows Server 2003 but cannot be used with Windows 2000 Server or Windows XP.

<5> Section 2.1: Windows configures the underlying RPC transport with the following flags, as specified in [C706] and [MS-RPCE].

Interface

 Windows 2000 Server

 Windows XP (pre-SP2)

 Windows Server 2003 and Windows XP SP2

IVolumeClient, IVolumeClient2, IVolumeClient3, IVolumeClient4

 RPC_C_AUTHN_LEVEL_CONNECT

 RPC_C__IMP_LEVEL_IDENTIFY

 EOAC_APPID

 RPC_C_AUTHN_LEVEL_CONNECT

 RPC_C__IMP_LEVEL_IMPERSONATE

 EOAC_NONE

 RPC_C_AUTHN_LEVEL_PKT_PRIVACY

 RPC_C__IMP_LEVEL_IDENTIFY

EOAC_SECURE_REFS | EOAC_DISABLE_AAA | EOAC_NO_CUSTOM_MARSHAL

IDMRemoteServer

 RPC_C_AUTHN_LEVEL_NONE

 RPC_C__IMP_LEVEL_IMPERSONATE

 EOAC_NONE

 RPC_C_AUTHN_LEVEL_NONE

 RPC_C__IMP_LEVEL_IMPERSONATE

 EOAC_NONE

 RPC_C_AUTHN_LEVEL_NONE

 RPC_C__IMP_LEVEL_IDENTIFY

 EOAC_NO_CUSTOM_MARSHALL

<6> Section 2.1:  The authorization constraints in Windows vary by operating system release. The following table explains the variations. The boxes of the matrix identify a Windows security group that has the required level of access.

Interface

 Windows 2000 Server

 Windows XP

 Windows Server 2003

IVolumeClient, IVolumeClient2, IVolumeClient3, IVolumeClient4 Launch

 Administrators

 Administrators, backup operators

 Administrators, backup operators

 Local_system

IVolumeClient, IVolumeClient2, IVolumeClient3, IVolumeClient4 Access

 Administrators

 Administrators, backup operators

 Administrators, backup operators

 Local_system

IDMRemoteServer Launch

 Administrators

 Administrators

 Administrators

 Local_system

IDMRemoteServer Access

 No restrictions

 No restrictions

 No restrictions

<7> Section 2.3.1.1: Other OEM partition types recognized by Windows NT 3.1, Windows NT 3.5, Windows NT 3.51, and Windows NT 4.0 are as follows.

 Partition type

 Value

 Description

PARTITION_EISA

0x12

Extended Industry Standard Architecture (EISA) partition

PARTITION_HIBERNATION

0x84

Hibernation partition for laptops

PARTITION_DIAGNOSTIC

0xA0

Diagnostic partition on some Hewlett-Packard (HP) notebook PCs

PARTITION_DELL

0xDE

Dell partition

PARTITION_IBM

0xFE

IBM initial microprogram load (IML) partition

<8> Section 2.5.1.2: Disk signatures are guaranteed to be unique among disks on a single machine.

<9> Section 2.5.1.2: GUIDs generated are guaranteed to be globally unique.

<10> Section 2.5.1.3: Windows 2000 Server and Windows XP servers do not define any partition flags and always initialize this field to 0.

<11> Section 2.5.1.3: Hidden volumes are not accessible by opening a handle to the file system on the volume using the Win32 API. The volume may be accessed only by opening a handle to the volume device.

<12> Section 3.1.4:  Gaps in the opnum numbering sequence apply to Windows as shown in the following table.

 Opnum

Description

IVolumeClient Opnum 0

Default DCOM method QueryInterface

IVolumeClient Opnum 1

Default DCOM method AddRef

IVolumeClient Opnum 2

Default DCOM method Release

IVolumeClient Opnum 12

Used only locally by Windows, never remotely

IVolumeClient Opnum 27

Not implemented

IVolumeClient Opnum 42

Not implemented

IVolumeClient Opnum 49

Not implemented

IVolumeClient Opnum 50

Not implemented

IVolumeClient Opnum 60

Used only locally by Windows, never remotely

IVolumeClient Opnum 61

Used only locally by Windows, never remotely

IVolumeClient Opnum 62

Used only locally by Windows, never remotely

IVolumeClient Opnum 63

Used only locally by Windows, never remotely

IVolumeClient Opnum 64

Used only locally by Windows, never remotely

IVolumeClient Opnum 65

Used only locally by Windows, never remotely

IVolumeClient Opnum 66

Used only locally by Windows, never remotely

IVolumeClient2 Opnum 0

Default DCOM method QueryInterface

IVolumeClient2 Opnum 1

Default DCOM method AddRef

IVolumeClient2 Opnum 2

Default DCOM method Release

IVolumeClient3 Opnum 0

Default DCOM method QueryInterface

IVolumeClient3 Opnum 1

Default DCOM method AddRef

IVolumeClient3 Opnum 2

Default DCOM method Release

IVolumeClient3 Opnum 12

Used only locally by Windows, never remotely

IVolumeClient3 Opnum 56

Used only locally by Windows, never remotely

IVolumeClient3 Opnum 57

Used only locally by Windows, never remotely

IVolumeClient3 Opnum 58

Used only locally by Windows, never remotely

IVolumeClient3 Opnum 59

Used only locally by Windows, never remotely

IVolumeClient3 Opnum 60

Used only locally by Windows, never remotely

IVolumeClient3 Opnum 61

Used only locally by Windows, never remotely.

IVolumeClient3 Opnum 62

Used only locally by Windows, never remotely

IVolumeClient3 Opnum 63

Used only locally by Windows, never remotely

IVolumeClient4 Opnum 0

Default DCOM method QueryInterface

IVolumeClient4 Opnum 1

Default DCOM method AddRef

IVolumeClient4 Opnum 2

Default DCOM method Release

IDMRemoteServer Opnum 0

Default DCOM method QueryInterface

IDMRemoteServer Opnum 1

Default DCOM method AddRef

IDMRemoteServer Opnum 2

Default DCOM method Release

IDMNotify Opnum 0

Default DCOM method QueryInterface

IDMNotify Opnum 1

Default DCOM method AddRef

IDMNotify Opnum 2

Default DCOM method Release

<13> Section 3.1.4.1.4: Call sequencing is determined by the invoking application; whether or not this is done is application-specific.

<14> Section 3.1.4.3:  The Disk Management UI client updates the graphical user interface (GUI) display based on these notifications.

<15> Section 3.2.1.1: In Windows, the unique identifier (UID) of the disk object changes when it is converted from basic disk to dynamic disk or from dynamic disk to basic disk.

<16> Section 3.2.4: Windows servers enforce authorization checks. For more information on the authorization requirements for the various methods, see section 2.1.

<17> Section 3.2.4.3: In Windows, all the methods listed that can be implemented asynchronously are implemented as asynchronous methods.

<18> Section 3.2.4.3: For example, in Windows, the call to the file system to format will call back to the server with notifications based on the percentage of the format completed. In Windows, the server sends notifications based on 10-percent increments; for example, notifications are sent at 0 percent finished, 10 percent finished, or 20 percent finished.

<19> Section 3.2.4.4.1.3: A partition cannot be created at the offset zero if the disk is partitioned with either MBR or GPT disk partitioning formats.

<20> Section 3.2.4.4.1.3: MUST be set to zero when sent and MUST be ignored on receipt.

<21> Section 3.2.4.4.1.3: MUST be set to zero when sent and MUST be ignored on receipt.

<22> Section 3.2.4.4.1.3: MUST be set to zero when sent and MUST be ignored on receipt.

<23> Section 3.2.4.4.1.3:  A drive letter can be assigned to the partition automatically by the Windows mount point manager depending on several factors, including whether or not NoAutoMount is enabled, whether or not the partition type is recognized by Windows, or whether or not the GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER or GPT_BASIC_DATA_ATTRIBUTE_HIDDEN flags is set.

<24> Section 3.2.4.4.1.3: Windows uses the PARTITION_INFORMATION_EX structure to create and format partitions. For more information about this structure, see [MSDN-PARTITIONINFO].

<25> Section 3.2.4.4.1.4: In Windows, the server does not check the letterLastKnownState parameter. Even if the specified drive letter is not present in the list of storage objects, the CreatePartitionAssignAndFormat method creates the partition.

<26> Section 3.2.4.4.1.4: In Windows, if specifies that a drive letter be assigned, the field tinfo.storageId is set to 0 even if the partition is created successfully.

<27> Section 3.2.4.4.1.4: MUST be set to zero when sent and MUST be ignored on receipt.

<28> Section 3.2.4.4.1.4: MUST be set to zero when sent and MUST be ignored on receipt.

<29> Section 3.2.4.4.1.4: MUST be set to zero when sent and MUST be ignored on receipt.

<30> Section 3.2.4.4.1.4:  The formatting is handled as an asynchronous task.

<31> Section 3.2.4.4.1.6: In Windows, the server does not verify whether partitionSpec.LastKnownState matches the LastKnownState field of the object.

<32> Section 3.2.4.4.1.6: MUST be set to zero when sent and MUST be ignored on receipt.

<33> Section 3.2.4.4.1.6: MUST be set to zero when sent and MUST be ignored on receipt.

<34> Section 3.2.4.4.1.6: MUST be set to zero when sent and MUST be ignored on receipt.

<35> Section 3.2.4.4.1.6: If the force parameter is not set, the call will fail with LDM_E_VOLUME_IN_USE if the volume cannot be locked.

<36> Section 3.2.4.4.1.7: MUST be set to zero when sent and MUST be ignored on receipt.

<37> Section 3.2.4.4.1.7: MUST be set to zero when sent and MUST be ignored on receipt.

<38> Section 3.2.4.4.1.7: MUST be set to zero when sent and MUST be ignored on receipt.

<39> Section 3.2.4.4.1.8: MUST be set to zero when sent and MUST be ignored on receipt.

<40> Section 3.2.4.4.1.8: MUST be set to zero when sent and MUST be ignored on receipt.

<41> Section 3.2.4.4.1.8: MUST be set to zero when sent and MUST be ignored on receipt.

<42> Section 3.2.4.4.1.9: MUST be set to zero when sent and MUST be ignored on receipt.

<43> Section 3.2.4.4.1.9: MUST be set to zero when sent and MUST be ignored on receipt.

<44> Section 3.2.4.4.1.9: MUST be set to zero when sent and MUST be ignored on receipt.

<45> Section 3.2.4.4.1.9: In a Windows implementation, the server always returns the status of the operation as REQ_FAILED.

<46> Section 3.2.4.4.1.10: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<47> Section 3.2.4.4.1.11: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<48> Section 3.2.4.4.1.12: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<49> Section 3.2.4.4.1.12: If the force parameter is not set, the call will fail with LDM_E_VOLUME_IN_USE if the volume cannot be locked.

<50> Section 3.2.4.4.1.12: MUST be set to zero when sent and MUST be ignored on receipt.

<51> Section 3.2.4.4.1.12: MUST be set to zero when sent and MUST be ignored on receipt.

<52> Section 3.2.4.4.1.12: MUST be set to zero when sent and MUST be ignored on receipt.

<53> Section 3.2.4.4.1.13: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<54> Section 3.2.4.4.1.13: If the bForce parameter is not set, the call will fail with LDM_E_VOLUME_IN_USE if the volume cannot be locked when removing the drive letter associated with the volume.

<55> Section 3.2.4.4.1.13: MUST be set to zero when sent and MUST be ignored on receipt.

<56> Section 3.2.4.4.1.13: MUST be set to zero when sent and MUST be ignored on receipt.

<57> Section 3.2.4.4.1.13: MUST be set to zero when sent and MUST be ignored on receipt.

<58> Section 3.2.4.4.1.13: Note that the new volume that results when breaking a single volume into two separate partitions might automatically get a new drive letter assigned by the operating system.

<59> Section 3.2.4.4.1.14: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<60> Section 3.2.4.4.1.14: MUST be set to zero when sent and MUST be ignored on receipt.

<61> Section 3.2.4.4.1.14: MUST be set to zero when sent and MUST be ignored on receipt.

<62> Section 3.2.4.4.1.14: MUST be set to zero when sent and MUST be ignored on receipt.

<63> Section 3.2.4.4.1.15: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<64> Section 3.2.4.4.1.15: MUST be set to zero when sent and MUST be ignored on receipt.

<65> Section 3.2.4.4.1.15: MUST be set to zero when sent and MUST be ignored on receipt.

<66> Section 3.2.4.4.1.15: MUST be set to zero when sent and MUST be ignored on receipt.

<67> Section 3.2.4.4.1.16: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<68> Section 3.2.4.4.1.16: MUST be set to zero when sent and MUST be ignored on receipt.

<69> Section 3.2.4.4.1.16: MUST be set to zero when sent and MUST be ignored on receipt.

<70> Section 3.2.4.4.1.16: MUST be set to zero when sent and MUST be ignored on receipt.

<71> Section 3.2.4.4.1.17: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<72> Section 3.2.4.4.1.17: MUST be set to zero when sent and MUST be ignored on receipt.

<73> Section 3.2.4.4.1.17: MUST be set to zero when sent and MUST be ignored on receipt.

<74> Section 3.2.4.4.1.17: MUST be set to zero when sent and MUST be ignored on receipt.

<75> Section 3.2.4.4.1.18: In Windows, the enumeration of drive letter objects excludes the objects with drive letters 'A' and 'B'.

<76> Section 3.2.4.4.1.19: MUST be set to zero when sent and MUST be ignored on receipt.

<77> Section 3.2.4.4.1.19: MUST be set to zero when sent and MUST be ignored on receipt.

<78> Section 3.2.4.4.1.19: MUST be set to zero when sent and MUST be ignored on receipt.

<79> Section 3.2.4.4.1.20: If the forceOption parameter is not set, the call will fail with LDM_E_VOLUME_IN_USE if the volume cannot be locked.

<80> Section 3.2.4.4.1.20: MUST be set to zero when sent and MUST be ignored on receipt.

<81> Section 3.2.4.4.1.20: MUST be set to zero when sent and MUST be ignored on receipt.

<82> Section 3.2.4.4.1.20: MUST be set to zero when sent and MUST be ignored on receipt.

<83> Section 3.2.4.4.1.21: In Windows, the server returns file system structure without file system information for partitions on a dynamic disk.

<84> Section 3.2.4.4.1.23: The FILE_SYSTEM_INFO::id parameter is not used in this case.

<85> Section 3.2.4.4.1.23:  If the force parameter is not set, the call will fail with LDM_E_VOLUME_IN_USE if the volume cannot be locked.

<86> Section 3.2.4.4.1.23: MUST be set to zero when sent and MUST be ignored on receipt.

<87> Section 3.2.4.4.1.23: MUST be set to zero when sent and MUST be ignored on receipt.

<88> Section 3.2.4.4.1.23: MUST be set to zero when sent and MUST be ignored on receipt.

<89> Section 3.2.4.4.1.23:  The formatting is handled as an asynchronous task.

<90> Section 3.2.4.4.1.25: This method enumerates the volume extents, not the volume members. A volume member is a volume plex for a mirrored volume, or a volume's column\member for a RAID-5 volume.

<91> Section 3.2.4.4.1.25: In Windows, the server returns S_FALSE if the method is successful.

<92> Section 3.2.4.4.1.26: In Windows, if the size of the volume requested is greater than the size of the volume that can be created on the specified disks, the HRESULT returned is S_OK, TASK_INFO::error is set to S_OK, and TASK_INFO::storageId is set to 0 to indicate that the volume was not created.

<93> Section 3.2.4.4.1.26: Note that in Windows the bNeedContiguous field in the DISK_SPEC structure is ignored if more than one DISK_SPEC structure is passed in.

<94> Section 3.2.4.4.1.26: MUST be set to zero when sent and MUST be ignored on receipt.

<95> Section 3.2.4.4.1.26: MUST be set to zero when sent and MUST be ignored on receipt.

<96> Section 3.2.4.4.1.26: MUST be set to zero when sent and MUST be ignored on receipt.

<97> Section 3.2.4.4.1.26: In Windows, the status returned is REQ_STARTED even if the operation has finished successfully.

<98> Section 3.2.4.4.1.26: Windows sends the region-deleted and region-created notification when a region is deleted and created during this operation in MBR disks. Windows does not send the region-deleted and region-created notification when a region is deleted and created during this operation in GPT disks.

<99> Section 3.2.4.4.1.27: In Windows, the server does not check the letterLastKnownState parameter. Even if the specified drive letter is not present in the list of storage objects, the CreateVolumeAssignAndFormat method creates the volume.

<100> Section 3.2.4.4.1.27: In a Windows implementation, the field tinfo.storageId is set to zero even if the partition is created successfully.

<101> Section 3.2.4.4.1.27: MUST be set to zero when sent and MUST be ignored on receipt.

<102> Section 3.2.4.4.1.27: MUST be set to zero when sent and MUST be ignored on receipt.

<103> Section 3.2.4.4.1.27: MUST be set to zero when sent and MUST be ignored on receipt.

<104> Section 3.2.4.4.1.27:  In Windows, the formatting is handled as an asynchronous task.

<105> Section 3.2.4.4.1.30: In Windows, the method returns 0 without growing the volume, if the length specified in diskList.length is greater than the available free space on that disk.

<106> Section 3.2.4.4.1.30: MUST be set to zero when sent and MUST be ignored on receipt.

<107> Section 3.2.4.4.1.30: MUST be set to zero when sent and MUST be ignored on receipt.

<108> Section 3.2.4.4.1.30: MUST be set to zero when sent and MUST be ignored on receipt.

<109> Section 3.2.4.4.1.30:  If the force parameter is not set, the call will fail with LDM_E_VOLUME_IN_USE if the volume cannot be locked.

<110> Section 3.2.4.4.1.31: MUST be set to zero when sent and MUST be ignored on receipt.

<111> Section 3.2.4.4.1.31: MUST be set to zero when sent and MUST be ignored on receipt.

<112> Section 3.2.4.4.1.31: MUST be set to zero when sent and MUST be ignored on receipt.

<113> Section 3.2.4.4.1.31: Windows sends the region-deleted and OID-created notification when a region is deleted and created during this operation on MBR disks. Windows does not send the region-deleted and region-created notification when a region is deleted and created during this operation on GPT disks.

<114> Section 3.2.4.4.1.31: If the force parameter is not set, the call will fail with LDM_E_VOLUME_IN_USE if the volume cannot be locked.

<115> Section 3.2.4.4.1.32: In Windows, the status returned is REQ_STARTED even if the operation has completed successfully.

<116> Section 3.2.4.4.1.32: MUST be set to zero when sent and MUST be ignored on receipt.

<117> Section 3.2.4.4.1.32: MUST be set to zero when sent and MUST be ignored on receipt.

<118> Section 3.2.4.4.1.32: MUST be set to zero when sent and MUST be ignored on receipt.

<119> Section 3.2.4.4.1.32: In Windows, the server sends a multiple-task completion notification if the operation succeeds.

<120> Section 3.2.4.4.1.33: MUST be set to zero when sent and MUST be ignored on receipt.

<121> Section 3.2.4.4.1.33: MUST be set to zero when sent and MUST be ignored on receipt.

<122> Section 3.2.4.4.1.33: MUST be set to zero when sent and MUST be ignored on receipt.

<123> Section 3.2.4.4.1.34: In Windows, the server does not check the letterLastKnownState parameter. Even if the specified drive letter is not present in the list of storage objects, the SplitMirror method splits the volume.

<124> Section 3.2.4.4.1.34: MUST be set to zero when sent and MUST be ignored on receipt.

<125> Section 3.2.4.4.1.34: MUST be set to zero when sent and MUST be ignored on receipt.

<126> Section 3.2.4.4.1.34: MUST be set to zero when sent and MUST be ignored on receipt.

<127> Section 3.2.4.4.1.34: The call fails with LDM_E_VOLUME_IN_USE if the volume cannot be locked.

<128> Section 3.2.4.4.1.35: MUST be set to zero when sent and MUST be ignored on receipt.

<129> Section 3.2.4.4.1.35: MUST be set to zero when sent and MUST be ignored on receipt.

<130> Section 3.2.4.4.1.35: MUST be set to zero when sent and MUST be ignored on receipt.

<131> Section 3.2.4.4.1.35: In Windows implementations, the server does not send the region deletion notification.

<132> Section 3.2.4.4.1.36: In Windows, the server does not verify that the disk is empty when the method is called. Instead, the method sends an asynchronous task notification indicating the task failure if the disk specified is not empty.

<133> Section 3.2.4.4.1.36: MUST be set to zero when sent and MUST be ignored on receipt.

<134> Section 3.2.4.4.1.36: MUST be set to zero when sent and MUST be ignored on receipt.

<135> Section 3.2.4.4.1.36: MUST be set to zero when sent and MUST be ignored on receipt.

<136> Section 3.2.4.4.1.36: The disk conversion is handled as an asynchronous task.

<137> Section 3.2.4.4.1.36: In Windows implementations, the server does not send the region deletion notification.

<138> Section 3.2.4.4.1.37: MUST be set to zero when sent and MUST be ignored on receipt.

<139> Section 3.2.4.4.1.37: MUST be set to zero when sent and MUST be ignored on receipt.

<140> Section 3.2.4.4.1.37: MUST be set to zero when sent and MUST be ignored on receipt.

<141> Section 3.2.4.4.1.37: The disk reactivation operation is handled as an asynchronous task.

<142> Section 3.2.4.4.1.38: MUST be set to zero when sent and MUST be ignored on receipt.

<143> Section 3.2.4.4.1.38: MUST be set to zero when sent and MUST be ignored on receipt.

<144> Section 3.2.4.4.1.38: MUST be set to zero when sent and MUST be ignored on receipt.

<145> Section 3.2.4.4.1.38: The disk import operation is handled as an asynchronous task.

<146> Section 3.2.4.4.1.39: In a Windows implementation, the field status is set to REQ_STARTED even if the operation finished successfully.

<147> Section 3.2.4.4.1.39: Handling of the DSKMERGE_IN_NO_UNRELATED flag is not implemented in Windows.

<148> Section 3.2.4.4.1.40: In a Windows implementation, the field status is set to REQ_STARTED even if the operation finished successfully.

<149> Section 3.2.4.4.1.40: MUST be set to zero when sent and MUST be ignored on receipt.

<150> Section 3.2.4.4.1.40: MUST be set to zero when sent and MUST be ignored on receipt.

<151> Section 3.2.4.4.1.40: MUST be set to zero when sent and MUST be ignored on receipt.

<152> Section 3.2.4.4.1.41: Windows does not implement this method.

<153> Section 3.2.4.4.1.41: MUST be set to zero when sent and MUST be ignored on receipt.

<154> Section 3.2.4.4.1.41: MUST be set to zero when sent and MUST be ignored on receipt.

<155> Section 3.2.4.4.1.41: MUST be set to zero when sent and MUST be ignored on receipt.

<156> Section 3.2.4.4.1.42: MUST be set to zero when sent and MUST be ignored on receipt.

<157> Section 3.2.4.4.1.42: MUST be set to zero when sent and MUST be ignored on receipt.

<158> Section 3.2.4.4.1.42: MUST be set to zero when sent and MUST be ignored on receipt.

<159> Section 3.2.4.4.1.43: MUST be set to zero when sent and MUST be ignored on receipt.

<160> Section 3.2.4.4.1.43: MUST be set to zero when sent and MUST be ignored on receipt.

<161> Section 3.2.4.4.1.43: MUST be set to zero when sent and MUST be ignored on receipt.

<162> Section 3.2.4.4.1.43: In Windows, the status returned is REQ_STARTED even if the operation has been finished successfully.

<163> Section 3.2.4.4.1.44: A notification that a task has been modified is sent for failure cases. A task-modified notification is not usually sent when a task fails, but parameter-validation failure is an exception.

<164> Section 3.2.4.4.1.44: MUST be set to zero when sent and MUST be ignored on receipt.

<165> Section 3.2.4.4.1.44: MUST be set to zero when sent and MUST be ignored on receipt.

<166> Section 3.2.4.4.1.44: MUST be set to zero when sent and MUST be ignored on receipt.

<167> Section 3.2.4.4.1.45: MUST be set to zero when sent and MUST be ignored on receipt.

<168> Section 3.2.4.4.1.45: MUST be set to zero when sent and MUST be ignored on receipt.

<169> Section 3.2.4.4.1.45: This tinfo::Status field is returned as REQ_STARTED rather than REQ_COMPLETED.

<170> Section 3.2.4.4.1.45: In a Windows implementation, the server does not send task completion notification.

<171> Section 3.2.4.4.1.45: In a Windows implementation, the server does not send notifications for deletion of region objects of the old basic disks.

<172> Section 3.2.4.4.1.45: This information is used to update the boot.ini file's arcpath for the boot volume. Windows stores these values in the registry under "HKLM\SYSTEM\CurrentControlSet\Services\dmio\Partition Info" as DWORD values "OldPartitionNumber" and "NewPartitionNumber." After the server has updated the boot settings as necessary, it deletes the registry entries for "OldPartitionNumber" and "NewPartitionNumber".

<173> Section 3.2.4.4.1.47: Windows stores the boot partition change information in the registry under "HKLM\SYSTEM\CurrentControlSet\Services\dmio\Partition Info" as DWORD values "OldPartitionNumber" and "NewPartitionNumber."

<174> Section 3.2.4.4.1.48:  The SetDontShow method sets a Boolean value that indicates whether to show a disk initialization tool. For more information about this Boolean value, see GetDontShow.

<175> Section 3.2.4.4.1.49:  The GetDontShow method retrieves a Boolean value that indicates whether to show a disk initialization tool. The New Disk Wizard is part of the UI implementation for Disk Management for Windows. If it is enabled, the wizard appears when the UI is started and uninitialized or empty basic disks are available. Windows servers check a registry value and enable or disable the New Disk Wizard accordingly. The SetDontShow method sets the current state of the Boolean value in the registry.

<176> Section 3.2.4.4.1.50: In Windows, this method is not implemented and returns E_FAIL.

<177> Section 3.2.4.4.1.53: Windows always returns S_FALSE.

<178> Section 3.2.4.4.1.53: No flags are defined or returned.

<179> Section 3.2.4.4.1.53: Windows does not return this information from the server. Windows clients on Windows 2000 operating system and Windows XP make this call but do not depend on it. If the call is not implemented, these clients will print the error information based on the HRESULT, using strings they retrieve from the binary.

<180> Section 3.2.4.4.1.54: In Windows, the LDM UI client checks the value of ulIDLVersion to be equal to the version of the IDL file with which the client was built and will disconnect from the server if the ulIDLVersion is not the same.

<181> Section 3.2.4.4.1.54: This flag is never set by the 32-bit version of Windows 2000 Server, Windows Server 2003, or Windows XP. This flag is set by the 64-bit version of Windows XP and Windows Server 2003.

<182> Section 3.2.4.4.1.54: This flag is never set by Windows 2000 Server, Windows Server 2003, or Windows XP.

<183> Section 3.2.4.4.1.54: This flag is set only by Windows 2000 Server.

<184> Section 3.2.4.4.1.54: In Windows, the server responds to all client messages even if the Initialize method has not been called by the client, with the limitation that the client cannot receive any notifications from the server until the Initialize method has been called.

<185> Section 3.2.4.4.1.54: In Windows XP operating system Service Pack 2 (SP2) and Windows Server 2003 operating system with Service Pack 1 (SP1), if cRemote parameter is nonzero, the server uses server machine account authentication to make calls to the IDMNotify interface that is specified by notificationInterface.

<186> Section 3.2.4.4.1.55: In Windows, the server responds to all client messages — even after the Uninitialize method has been called by the client. However, after the Uninitialize method has been called by the client, the client cannot receive any further notifications from the server.

<187> Section 3.2.4.4.1.59: There is no operating system support for this method, so it is not used by Windows.

<188> Section 3.2.4.4.2.1: In Windows, if the diskId is not in the list of storage objects, the server causes the method to succeed without setting the maxAdjustedFreeSpace parameter.

<189> Section 3.2.4.4.3: IVolumeClient3 methods are not implemented in Windows 2000 Server.

<190> Section 3.2.4.4.3.3: Windows uses the PARTITION_INFORMATION_EX structure to create and format partitions. For more information about this structure, see [MSDN-PARTITIONINFO].

<191> Section 3.2.4.4.3.7: MUST be set to zero when sent and MUST be ignored on receipt.

<192> Section 3.2.4.4.3.7: MUST be set to zero when sent and MUST be ignored on receipt.

<193> Section 3.2.4.4.3.7: MUST be set to zero when sent and MUST be ignored on receipt.

<194> Section 3.2.4.4.3.10: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<195> Section 3.2.4.4.3.11: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<196> Section 3.2.4.4.3.12: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<197> Section 3.2.4.4.3.13: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<198> Section 3.2.4.4.3.14: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<199> Section 3.2.4.4.3.15: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<200> Section 3.2.4.4.3.16: In Windows, FT volumes on basic disks can only be created in Windows NT 4.0.

<201> Section 3.2.4.4.3.20: In Windows, the server returns file system structure without file system information for partitions on a dynamic disks.

<202> Section 3.2.4.4.3.32: MUST be set to zero when sent and MUST be ignored on receipt.

<203> Section 3.2.4.4.3.32: MUST be set to zero when sent and MUST be ignored on receipt.

<204> Section 3.2.4.4.3.32: MUST be set to zero when sent and MUST be ignored on receipt.

<205> Section 3.2.4.4.3.32: In a Windows implementation, the server does not send the task completion notification.

<206> Section 3.2.4.4.3.32: In Windows, the lastKnownState of the disk object does not change, even though the disk object is modified.

<207> Section 3.2.4.4.3.33: MUST be set to zero when sent and MUST be ignored on receipt.

<208> Section 3.2.4.4.3.33: MUST be set to zero when sent and MUST be ignored on receipt.

<209> Section 3.2.4.4.3.33: MUST be set to zero when sent and MUST be ignored on receipt.

<210> Section 3.2.4.4.3.33: In a Windows implementation, the server does not send the task completion notification.

<211> Section 3.2.4.4.3.38: MUST be set to zero when sent and MUST be ignored on receipt.

<212> Section 3.2.4.4.3.38: MUST be set to zero when sent and MUST be ignored on receipt.

<213> Section 3.2.4.4.3.38: MUST be set to zero when sent and MUST be ignored on receipt.

<214> Section 3.2.4.4.3.38: In Windows implementations, the server does not send the region deletion notification.

<215> Section 3.2.4.4.3.44: Windows does not implement this method.

<216> Section 3.2.4.4.3.48: MUST be set to zero when sent and MUST be ignored on receipt.

<217> Section 3.2.4.4.3.48: MUST be set to zero when sent and MUST be ignored on receipt.

<218> Section 3.2.4.4.3.48: MUST be set to zero when sent and MUST be ignored on receipt.

<219> Section 3.2.4.4.3.48: In a Windows implementation, the server does not send task completion notification.

<220> Section 3.2.4.4.3.48: In a Windows implementation, the server does not send notifications for deletion of region objects of the old basic disks.

<221> Section 3.2.4.4.3.51: The SetDontShow method sets a Boolean value that indicates whether or not to show a disk initialization tool. For more information on this Boolean value, see GetDontShow (section 3.2.4.4.3.52).

<222> Section 3.2.4.4.3.52:  The GetDontShow method retrieves a value that indicates whether to show a disk initialization tool. The New Disk Wizard is part of the UI implementation for Disk Management for Windows. If enabled, the wizard appears when the UI is started and uninitialized or empty basic disks are available. Windows servers check a registry value and enable or disable the New Disk Wizard accordingly. The SetDontShow method sets the current state of the Boolean value in the registry.

<223> Section 3.2.4.4.3.56: No flags are defined, and this parameter is always initialized to 0.

<224> Section 3.2.4.4.3.57: This flag is never set by the 32-bit version of Windows 2000 Server, Windows Server 2003, or Windows XP. This flag is set by the 64-bit version of Windows XP and Windows Server 2003.

<225> Section 3.2.4.4.3.57: This flag is never set by Windows 2000 Server, Windows Server 2003, or Windows XP.

<226> Section 3.2.4.4.3.57: This flag is set only by Windows 2000 Server.

<227> Section 3.2.4.4.4: IVolumeClient4 methods are not implemented in Windows 2000 Server or Windows XP.

<228> Section 3.2.4.4.4.1: The Windows volume manager keeps track of the dynamic disks present on a system and displays disks that are no longer present as missing.

<229> Section 3.2.6: Windows servers do register for such notifications.

<230> Section 5: For Windows-specific default security configuration please see [MSDN-DefAccPerms] and [MSDN-AccPerms].

Show: