Virtual Disk Service is transitioning to Windows Storage Management API
- Clients – Windows 8
- Servers – Windows Server 2012
Beginning with Windows 8 and Windows Server 2012, the Virtual Disk Service COM interface is superseded by the Storage Management API, a WMI-based programming interface. For managing storage subsystems, (Windows) disks, partitions, and volumes, we strongly recommend using the Storage Management API. For more info, see Windows Storage Management API.
For all usages except mirror boot volumes (using a mirror volume to host the operating system), dynamic disks are deprecated. For data that requires resiliency against drive failure, use Storage Spaces, a resilient storage virtualization solution. For more info, see Storage Spaces Technical Preview.
You can continue to use DiskPart, DiskRAID, and Disk Management during the deprecation period, but these tools will not work with Storage Spaces or with any other new Windows Management Instrumentation (WMI)-based Windows Storage Management APIs or in-box storage management utilities or clients.
|VDS||WMI||DiskPart||DiskRAID||Disk Mgmt GUI||PowerShell||Storage Spaces Control Panel|
The result of this transition will be increased storage resiliency, availability, and scalability; a unified scripting and programming language, reduced storage management costs, and easier remote storage management.
The DiskPart and DiskRAID utilities used in the VDS environment do not support the new Storage Spaces. Similarly, the new Storage PowerShell utility does not support the deprecated Dynamic Disks
Microsoft strongly recommends that you base any new storage management apps on the Windows Storage Management API, and that you plan to transition existing apps that are based on the VDS infrastructure to the Windows Storage Management API during your standard updating cycles.
- Windows Storage Management API
- Storage Cmdlets in Windows PowerShell
- Windows Management Instrumentation
- Windows PowerShell