Windows 10 DLL File Information

Windows 10 DLL File Information - storagewmi.dll

The following DLL report was generated by automatic DLL script that scanned and loaded all DLL files in the system32 directory of Windows 10, extracted the information from them, and then saved it into HTML reports. If you want to view a report of another DLL, go to the main page of this Web site.

General Information

File Description:	WMI Provider for Storage Management
File Version:	10.0.10130.0 (fbl_impressive.150522-2224)
Company:	Microsoft Corporation
Product Name:	Microsoft® Windows® Operating System
DLL popularity	Very Low - There is no any other DLL in system32 directory that is statically linked to this file.
File Size:	1,979 KB
Total Number of Exported Functions:	7
Total Number of Exported Functions With Names:	7

Section Headers

Name	Virtual Address	Raw Data Size	% of File	Characteristics	Section Contains...
.text	0x00001000	1,785,344 Bytes	88.1%	Read, Execute	Code
.data	0x001b5000	60,928 Bytes	3.0%	Write, Read	Initialized Data
.idata	0x001c5000	10,240 Bytes	0.5%	Read	Initialized Data
.didat	0x001c8000	512 Bytes	0.0%	Write, Read	Initialized Data
.rsrc	0x001c9000	4,608 Bytes	0.2%	Read	Initialized Data
.reloc	0x001cb000	163,840 Bytes	8.1%	Read, Discardable	Initialized Data

Static Linking

This means that when storagewmi.dll is loaded, the above files are automatically loaded too. If one of these files is corrupted or missing, storagewmi.dll won't be loaded.

General Resources Information

Resource Type	Number of Items	Total Size	% of File
Icons	0	0 Bytes	0.0%
Animated Icons	0	0 Bytes	0.0%
Cursors	0	0 Bytes	0.0%
Animated Cursors	0	0 Bytes	0.0%
Bitmaps	0	0 Bytes	0.0%
AVI Files	0	0 Bytes	0.0%
Dialog-Boxes	0	0 Bytes	0.0%
HTML Related Files	0	0 Bytes	0.0%
Menus	0	0 Bytes	0.0%
Strings	1,912	351,518 Bytes	17.3%
Type Libraries	0	0 Bytes	0.0%
Manifest	0	0 Bytes	0.0%
All Others	4	48,898 Bytes	2.4%
Total	1,916	400,416 Bytes	19.8%

Icons in this file

No icons found in this file

Cursors in this file

No cursors found in this file

Dialog-boxes list (up to 1000 dialogs)

No dialog resources in this file.

String resources in this dll (up to 1000 strings)

String ID	String Text
1	ObjectId is a mandatory property that is used to opaquely and uniquely identify an instance of a class. ObjectIds must be unique within the scope of the management server (which is hosting the provider). The ObjectId is created and maintained for use of the Storage Management Providers and their clients to track instances of objects. If an object is visible through two different paths (for example: there are two separate Storage Management Providers that point to the same storage subsystem) then the same object may appear with two different ObjectIds. For determining if two object instances are the same object, refer to the UniqueId property.
2	UniqueId is a mandatory property that is used to uniquely identify a logical instance of a storage subsystem's object. This value must be the same for an object viewed by two or more provider instances (even if they are running on seperate management servers). UniqueId can be any globally unique, opaque value unless otherwise specified by a derived class.
4	PassThroughServer is the name or address of the computer system hosting the proprietary storage provider classes.
5	PassThroughNamespace is the WBEM namespace that contains the proprietary storage provider classes.
6	PassThroughClass is the WBEM class name of the proprietary storage provider object.
8	Common base class for all Storage Management Provider objects
9	Primary classification of the error. The following values are defined: 2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another. 3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance. 4 - Software Error. Error of this type are principally associated with a software or processing fault. 5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure. 6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations. 7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues. 8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation. 9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource. 10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.
10	Unknown
11	Other
12	Communications Error
13	Quality of Service Error
14	Software Error
15	Hardware Error
16	Environmental Error
17	Security Error
18	Oversubscription Error
19	Unavailable Resource Error
20	Unsupported Operation Error
21	DMTF Reserved
22	A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.
24	An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.
25	The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity.
26	An array containing the dynamic content of the message.
27	An enumerated value that describes the severity of the Indication from the notifier\'s point of view: 0 - the Perceived Severity of the indication is unknown or indeterminate. 1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property. 2 - Information should be used when providing an informative response. 3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 5 - Major should be used to indicate action is needed NOW. 6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action. 2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.
28	Information
29	Degraded/Warning
30	Minor
31	Major
32	Critical
33	Fatal/NonRecoverable
34	An enumerated value that describes the probable cause of the error.
35	Adapter/Card Error
36	Application Subsystem Failure
37	Bandwidth Reduced
38	Connection Establishment Error
39	Communications Protocol Error
40	Communications Subsystem Failure
41	Configuration/Customization Error
42	Congestion
43	Corrupt Data
44	CPU Cycles Limit Exceeded
45	Dataset/Modem Error
46	Degraded Signal
47	DTE-DCE Interface Error
48	Enclosure Door Open
49	Equipment Malfunction
50	Excessive Vibration
51	File Format Error
52	Fire Detected
53	Flood Detected
54	Framing Error
55	HVAC Problem
56	Humidity Unacceptable
57	I/O Device Error
58	Input Device Error
59	LAN Error
60	Non-Toxic Leak Detected
61	Local Node Transmission Error
62	Loss of Frame
63	Loss of Signal
64	Material Supply Exhausted
65	Multiplexer Problem
66	Out of Memory
67	Output Device Error
68	Performance Degraded
69	Power Problem
70	Pressure Unacceptable
71	Processor Problem (Internal Machine Error)
72	Pump Failure
73	Queue Size Exceeded
74	Receive Failure
75	Receiver Failure
76	Remote Node Transmission Error
77	Resource at or Nearing Capacity
78	Response Time Excessive
79	Retransmission Rate Excessive
80	Software Program Abnormally Terminated
81	Software Program Error (Incorrect Results)
82	Storage Capacity Problem
83	Temperature Unacceptable
84	Threshold Crossed
85	Timing Problem
86	Toxic Leak Detected
87	Transmit Failure
88	Transmitter Failure
89	Underlying Resource Unavailable
90	Version Mismatch
91	Previous Alert Cleared
92	Login Attempts Failed
93	Software Virus Detected
94	Hardware Security Breached
95	Denial of Service Detected
96	Security Credential Mismatch
97	Unauthorized Access
98	Alarm Received
99	Loss of Pointer
100	Payload Mismatch
101	Transmission Error
102	Excessive Error Rate
103	Trace Problem
104	Element Unavailable
105	Element Missing
106	Loss of Multi Frame
107	Broadcast Channel Failure
108	Invalid Message Received
109	Routing Failure
110	Backplane Failure
111	Identifier Duplication
112	Protection Path Failure
113	Sync Loss or Mismatch
114	Terminal Problem
115	Real Time Clock Failure
116	Antenna Failure
117	Battery Charging Failure
118	Disk Failure
119	Frequency Hopping Failure
120	Loss of Redundancy
121	Power Supply Failure
122	Signal Quality Problem
123	Battery Discharging
124	Battery Failure
125	Commercial Power Problem
126	Fan Failure
127	Engine Failure
128	Sensor Failure
129	Fuse Failure
130	Generator Failure
131	Low Battery
132	Low Fuel
133	Low Water
134	Explosive Gas
135	High Winds
136	Ice Buildup
137	Smoke
138	Memory Mismatch
139	Out of CPU Cycles
140	Software Environment Problem
141	Software Download Failure
142	Element Reinitialized
143	Timeout
144	Logging Problems
145	Leak Detected
146	Protection Mechanism Failure
147	Protecting Resource Failure
148	Database Inconsistency
149	Authentication Failure
150	Breach of Confidentiality
151	Cable Tamper
152	Delayed Information
153	Duplicate Information
154	Information Missing
155	Information Modification
156	Information Out of Sequence
157	Key Expired
158	Non-Repudiation Failure
159	Out of Hours Activity
160	Out of Service
161	Procedural Error
162	Unexpected Information
163	A free-form string describing the probable cause of the error.
164	A free-form string describing recommended actions to take to resolve the error.
165	The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property.
166	The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as: 0 - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application. 1 - Other. The format is defined by the value of the OtherErrorSourceFormat property.2 - CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.
167	CIMObjectPath
168	A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL.
169	The CIM status code that characterizes this instance. This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation. The following values for CIM status code are defined: 1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code. 2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client. 3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist. 4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid. 5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist. 6 - CIM_ERR_NOT_FOUND. The requested object could not be found. 7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported. 8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances. 9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances. 10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist. 11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists. 12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist. 13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type. 14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported. 15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language. 16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed. 17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist. 18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected. 19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid. 20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty. 21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid. 22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty. 23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty. 24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed. 25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported. 26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported. 27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...). 28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down. 29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.
170	CIM_ERR_FAILED
171	CIM_ERR_ACCESS_DENIED
172	CIM_ERR_INVALID_NAMESPACE
173	CIM_ERR_INVALID_PARAMETER
174	CIM_ERR_INVALID_CLASS
175	CIM_ERR_NOT_FOUND
176	CIM_ERR_NOT_SUPPORTED
177	CIM_ERR_CLASS_HAS_CHILDREN
178	CIM_ERR_CLASS_HAS_INSTANCES
179	CIM_ERR_INVALID_SUPERCLASS
180	CIM_ERR_ALREADY_EXISTS
181	CIM_ERR_NO_SUCH_PROPERTY
182	CIM_ERR_TYPE_MISMATCH
183	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
184	CIM_ERR_INVALID_QUERY
185	CIM_ERR_METHOD_NOT_AVAILABLE
186	CIM_ERR_METHOD_NOT_FOUND
187	CIM_ERR_UNEXPECTED_RESPONSE
188	CIM_ERR_INVALID_RESPONSE_DESTINATION
189	CIM_ERR_NAMESPACE_NOT_EMPTY
190	CIM_ERR_INVALID_ENUMERATION_CONTEXT
191	CIM_ERR_INVALID_OPERATION_TIMEOUT
192	CIM_ERR_PULL_HAS_BEEN_ABANDONED
193	CIM_ERR_PULL_CANNOT_BE_ABANDONED
194	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
195	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
196	CIM_ERR_SERVER_LIMITS_EXCEEDED
197	CIM_ERR_SERVER_IS_SHUTTING_DOWN
198	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
199	A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.
200	2.22.1
201	CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation.
202	Provides extra status information about an extrinsic method's invocation
203	A system defined name for this storage job.
204	The Description property provides a textual description of the storage job operation.
205	The time interval that the job has been executing or the total execution time if the storage job is complete.
206	If the operation that this storage job was tracking has failed, the provider will set this with an error code defined by the method that invoked the operation. If this job tracked a background task, the error code can be set to any valid Storage Management error code as defined in the value map below. If there was no error, this property must be set to 0 - 'Success'. This property should be NULL until the operation has completed.
207	A free-form string that contains the vendor error description.
208	The current execution state of the storage job.
210	Starting
211	Running
212	Suspended
213	Shutting Down
214	Completed
215	Terminated
216	Killed
217	Exception
218	Service
219	Query Pending
220	Microsoft Reserved
221	Vendor Reserved
222	A free-form string that represents the status of the job. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details.
223	This property indicates whether the times represented in the StartTime, TimeOfLastStateChange, and TimeSubmitted properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2 - 'UTC Time'.
224	Local Time
225	UTC Time
226	Indicates the current statuses of the element.
228	Degraded
229	Stressed
230	Predictive Failure
231	Error
232	Non-Recoverable Error
233	Stopping
234	Stopped
235	In Service
236	No Contact
237	Lost Communication
238	Aborted
239	Dormant
240	Supporting Entity in Error
241	Power Mode
242	Relocating
243	Strings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus.
244	The percentage of the job that has completed at the time that this value is requested.
245	Percent
246	The time that the job was actually started.
247	The amount of time that the Job is retained after it has finished executing, regardless of whether it failed during execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property.
248	The date or time when the state of the job last changed. If the state of the job has not changed and this property is populated, it must be set to a 0 interval value. If a state change was requested, but was rejected or not yet processed, the property must not be updated.
249	The time that the job was submitted to execute. A value of all zeroes indicates that the owning element is not capable of reporting a date and time.
250	If TRUE, the storage job will be automatically deleted after a short time interval.
251	If TRUE, this storage job represents an automated background task initiated by the storage subsystem. For all user / management initiated operations, this value should be set to FALSE.
252	Describes the recovery action to be taken for an unsuccessfully run job. The possible values are: 0 - 'Unknown' meaning it is unknown as to what recovery action to take 1 - 'Other' indicating that the recovery action will be specified in the OtherRecoveryAction property 2 - 'Do Not Continue' meaning stop the execution of the job and appropriately update its status 3 - 'Continue With Next Job' meaning continue with the next job in the queue 4 - 'Re-run Job' indicating that the job should be re-run
253	Do Not Continue
254	Continue With Next Job
255	Re-run Job
256	Denotes a vendor-specific recovery action to be taken for an unsuccessfully run job. This value should only be set if RecoveryAction is set to 1 - 'Other'.
257	Requests that the state of the job be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost.
258	Success
259	Not Supported
260	Unspecified Error
261	Failed
262	Invalid Parameter
263	State transition started
264	Invalid state transition
265	Access denied
266	There are not enough resources to complete the operation.
267	Cannot connect to the storage provider.
268	The storage provider cannot connect to the storage subsystem.
269	RequestStateChange changes the state of a job. The possible values are as follows: 2 - 'Start' changes the state to 'Running'. 3 - 'Suspend' stops the job temporarily. The intention is to subsequently restart the job with a second call to RequestStateChange requesting 1 - 'Start'. It might be possible to enter the 'Service' state while suspended. (This is job-specific.) 4 - 'Terminate' stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner. 5 - 'Kill' terminates the job immediately with no requirement to save data or preserve the state. 6 - 'Service' puts the job into a vendor-specific service state. It might be possible to restart the job.
270	Start
271	Suspend
272	Terminate
273	Kill
274	This method retrieves the extended status information for an unsuccessful job.
275	Storage jobs represent long running operations on a storage subsystem. These operations can either be user-initiated through the various management interfaces defined by this MOF, or automatically by intelligent storage subsystems.
276	DeviceId is an address or other identifier that uniquely names the physical disk.
278	This field describes the intended usage of this physical disk within a concrete pool. Storage pools are required to follow the assigned policy for a physical disk. 1 - 'Auto-Select': This physical disk should only be used for data storage. 2 - 'Manual-Select': This physical disk should only be used if manually selected by an administrator at the time of virtual disk creation. A manual-select disk is selected using the PhysicalDisksToUse parameter to CreateVirtualDisk. 3 - 'Hot Spare': This physical disk should be used as a hot spare. 4 - 'Retired': This physical disk should be retired from use. At a minimum, no new allocations should go to this disk. If the virtual disks that reside on this disk are repaired, the data should be moved to another active physical disk.
279	Auto-Select
280	Manual-Select
281	Hot Spare
282	Retired
283	Journal
284	This field describes the supported usages of this physical disk.
289	This field is a string representation of the physical disk's part number or SKU.
290	This field is a string representation of the physical disk's firmware version.
291	This field is a string representation of the physical disk's software version.
293	Failed Media
294	Split
295	Stale Metadata
296	IO Error
297	Unrecognized Metadata
298	Healthy
299	Warning
300	Unhealthy
301	Indicates the total physical storage size of the disk in bytes
302	Bytes
303	This field indicates the sum of used space on this physical disk. This should include usage from all storage pools and other data stored on the disk.
304	SCSI
305	ATAPI
307	1394
309	Fibre Channel
311	RAID
312	iSCSI
314	SATA
317	Virtual
318	File Backed Virtual
319	Storage Spaces
320	This field indicates the physical sector size of the physical disk in bytes. For example: for 4K native and 512 emulated disks, the value should be 4096.
321	This field indicates the logical sector size of the physical disk in bytes. For example: a 4K native disk should report 4096, while a 512 emulated disk should report 512.
323	Indicates whether the physical disk's identification LEDs are active or not. This is typically used in maintenance operations.
325	Indicates the enclosure number in which the disk physically resides
326	Indicates the enclosure slot number in which the disk physically resides
327	Indicates whether this physical disk can be added to a concrete pool or not
328	Indicates the reason why this physical disk cannot be added to a concrete pool
329	In a Pool
330	Not Healthy
331	Removable Media
332	In Use by Cluster
333	Offline
334	Insufficient Capacity
335	Spare Disk
336	Reserved by subsystem
337	If CannotPoolReason contains 1 - 'Other', this field contains the string representing the vendor defined reason why this physical disk cannot be added to a concrete pool. This property must be NULL if CannotPoolReason does not contain 1 - 'Other'.
339	Media type of this physical disk
342	This method allows a user to perform certain maintenance tasks on the physical disk.
343	The storage pool could not complete the operation because its health or operational status does not permit it.
344	The storage pool could not complete the operation because its configuration is read-only.
345	If set to TRUE, this instructs the physical disk to enable its indication LED. The indication LED should remain enabled until a second call to Maintenance is made with this parameter specified as FALSE.
346	ExtendedStatus allows the storage provider to return extended (implementation specific) error information.
347	This method resets the health and operational status of the physical disk. Exact behavior of this method is dependent on whether this physical disk belongs to a concrete pool. If it is a member of a concrete pool, the health and operational statuses should be reset to 1 - 'Healthy', and 1 - 'OK', respectively. If any additional errors are detected after Reset, the health and operational statuses should reflect these new errors. If the physical disk is not a member of a concrete pool, then this method should not only reset the health and operational statuses, but it should return the disk into a state where it is usable as storage for a concrete pool. For example: If a physical disk had become missing and then has reappeared (after it has been replaced) this physical disk is expected to be in the primordial pool only with an operational status indicating its data is either split or unrecognized. Calling Reset should clear the physical disk of any data, remove any remaining ties to its former concrete pool, and return the disk to a healthy, usable state.
348	This method allows the physical disk to be renamed.
349	This method allows the physical disk's description to be changed.
350	This method allows the physical disk's usage to be updated.
351	This method allows the physical disk's attributes to be updated.
352	A subsystem drive or spindle.
354	Media type of this storage tier
355	Unspecified
357	A user settable description of the storage tier
359	This parameter controls the asynchronous behavior the method will follow. If TRUE, this method will make use of the CreatedStorageJob out parameter when the request is taking a long time to service. If a storage job has been created to track the operation, this method will return 4096 - 'Method Parameters Checked - Job Started'. Note, even if RunAsJob is TRUE, the method can still return a result if it has finished in sufficient time. If FALSE or NULL, this method will follow default WMI asynchronous behavior as determined by the client's method for invocation (i.e. synchronous unless requested otherwise).
360	If RunAsJob is set to TRUE and this method takes a while to execute, this parameter returns a reference to the storage job used to track the long running operation.
362	Not enough available capacity
363	This method allows the storage tier to be renamed.
364	This method allows the user to update or set various attributes on the storage tier. Note that not all parameters must be specified, and only those given will be updated.
365	This method allows the storage tier's description to be changed.
366	This method returns the supported sizes for a new storage tier. These sizes can either be returned in an array of all supported sizes, through a min, max, and divisor, or both.
367	Cache out of date
370	This parameter denotes the minimum supported size that a tier created in this pool can be.
371	This parameter denotes the maximum supported size that a tier created in this pool can be.
372	This parameter indicates the interval in which the supported sizes increment. For example: If the minimum supported size is 10 GB, and this parameter is 2 GB, then the supported sizes for this pool would be 10 GB, 12 GB, 14 GB, etc. until the maximum supported size is reached.
373	A storage tier.
375	Name is a semi-unique (scoped to the owning storage subsystem), human-readable string used to identify the virtual disk.
376	VPD83NAA6
377	VPD83NAA5
378	VPD83Type2
379	VPD83Type1
380	VPD83Type0
381	SNVM
382	NodeWWN
384	EUI64
385	T10VID
386	UniqueIdFormat indicates the type of identifier used in the UniqueId field. The identifier used in UniqueId must be the highest available identifier using the following order of preference: 8 (highest), 3, 2, 1, 0 (lowest). For example: if the virtual disk device exposes identifiers of type 0, 1, and 3, UniqueId must be the identifier of type 3, and UniqueIdFormat should be set to 3.
387	Vendor Specific
388	Vendor Id
389	FCPH Name
390	SCSI Name String
391	Certain values for UniqueIdFormat may include various sub-formats. This field is a free-form string used to describe the specific format used in UniqueId.
392	This field indicates the intended usage for this virtual disk.
393	Unrestricted
394	Reserved for ComputerSystem (the block server)
395	Reserved by Replication Services
396	Reserved by Migration Services
397	Local Replica Source
398	Remote Replica Source
399	Local Replica Target
400	Remote Replica Target
401	Local Replica Source or Target
402	Remote Replica Source or Target
403	Delta Replica Target
404	Element Component
405	Reserved as Pool Contributor
406	Composite Volume Member
407	Composite VirtualDisk Member
408	Reserved for Sparing
409	If the virtual disk's Usage field is set to 1 - 'Other', this field must contain a description of the vendor or user defined usage. If Usage is not set to 1 - 'Other', this field must not be set.
410	Denotes the current health status of the virtual disk. Health of a virtual disk is derived from the health of the backing physical disks, and whether or not the virtual disk can maintain the required levels of resiliency. 0 - 'Healthy': All physical disks are present and in a healthy state. 1 - 'Warning': The majority of physical disks are healthy, but one or more may be failing I/O requests. 2 - 'Unhealthy': The majority of physical disks are unhealthy or in a failed state, and the virtual disk no longer has data integrity.
412	Detached
413	Incomplete
414	If OperationalStatus contains 1 - 'Other', this field contains the string representing the vendor defined operational status. This property must be NULL if OperationalStatus does not contain 1 - 'Other'.
415	The name of the resiliency setting used to create this virtual disk.
416	The logical size of the virtual disk measured in bytes
417	The currently allocated size of the virtual disk. If the virtual disk's ProvisioningType is 2 - 'Fixed', this value should equal Size. If the ProvisioningType is 1 - 'Thin', this value is the amount of space actually allocated (i.e. some value less than Size).
418	This field indicates the total storage pool capacity being consumed by this virtual disk. For example: in the case of a 2-way mirrored virtual disk of size 1 GB, the footprint on the pool will be approximately 2 GB.
419	Denotes the provisioning scheme of the virtual disk. 1 - 'Thin' indicates that the virtual disk's capacity is allocated on demand. 2 - 'Fixed' indicates that the virtual disk's capacity is fully allocated upon creation.
420	Thin
421	Fixed
422	This field indicates the number of complete data copies that are being maintained. For example, RAID 5 maintains 1 copy of data, whereas RAID 1 maintains at least 2 copies.
425	Non-rotated Parity
426	Rotated Parity
427	This field indicates the number of underlying physical disks across which data for this virtual disk is striped.
428	This field indicates the number of bytes that will form a strip in common striping-based resiliency settings. The strip is defined as the size of the portion of a stripe that lies on one physical disk. Thus, Interleave * NumberOfColumns will yield the size of one stripe of user data.
429	Indicates whether the virtual disk is available for read and/or write access
430	Readable
431	Writeable
432	Read/Write
433	Write Once
434	Indicates whether this virtual disk is a snapshot of another virtual disk
435	If TRUE, this virtual disk will only be attached to the system if an explicit call is made to the Attach method. Note that this property is specific to Storage Spaces.
436	Determines the current allocation behavior for this virtual disk. Enclosure aware virtual disks will intelligently pick the physical disks to use for their redundancy. If TRUE, the virtual disk will attempt to use physical disks from different enclosures to balance the fault tolerance between two (or more) physical enclosures.
437	Denotes the reason why this virtual disk is detached. This field will only be set when the virtual disk's OperationalStatus includes 0xD002 - 'Detached'. Note that this field is specific to Storage Spaces.
438	None
439	By Policy
440	Majority Disks Unhealthy
442	This method deletes the virtual disk. After this method is called, the space used by the virtual disk will be reclaimed and the user will be unable to reverse the delete operation.
443	Method Parameters Checked - Job Started
444	The virtual disk could not complete the operation because another computer controls its configuration.
445	This method shows a virtual disk to an initiator. This operation is also known as 'exposing' or 'unmasking' a virtual disk.
446	The HostType requested is not supported.
447	The initiator address specified is not valid
448	The target port address specified is not valid.
449	An array of target port addresses from which the virtual disk should be shown
450	The address of the initiator to which the virtual disk should be shown
451	This field indicates the operating system type running on the host of the initiator port.
452	Standard
453	Solaris
454	HPUX
455	OpenVMS
456	Tru64
457	Netware
458	Sequent
460	DGUX
461	Dynix
462	Irix
463	Cisco iSCSI Storage Router
464	Linux
465	Microsoft Windows
466	OS400
467	TRESPASS
468	HI-UX
469	VMware ESXi
470	Microsoft Windows Server 2008
471	Microsoft Windows Server 2003
472	This method hides a virtual disk from an initiator. This operation is also known as 'unexposing' or 'masking' a virtual disk.
473	An array of target port addresses from which the virtual disk should be hidden. Note: this array may contain a subset of the addresses originally given in Show.
474	The address of the initiator to which the virtual disk should be hidden
475	This method creates a point in time snapshot of the virtual disk.
476	This operation is not supported on primordial storage pools.
477	The storage pool is reserved for special usage only.
478	The specified storage pool could not be found.
479	The desired name of the snapshot virtual disk
480	This field indicates which storage pool should be used to hold the created snapshot. If this field is not set, this method will default to using the same storage pool that contains the source virtual disk.
481	This method creates a clone of the virtual disk, resulting in another virtual disk with identical data to the source.
482	The desired name of the virtual disk clone
483	This field indicates which storage pool should be used to hold the created clone. If this field is not set, this method will default to using the same storage pool that contains the source virtual disk.
484	This method allows a virtual disk to be resized. The size specified must be in the range of valid values given by the GetSupportedSize method on the storage pool object.
485	In Use
486	Size Not Supported
487	The virtual disk could not complete the operation because its health or operational status does not permit it.
488	As input, this parameter contains the requested size for the virtual disk to become. As output, this parameter contains the size that was actually achieved after the resize operation.
489	This method initiates a repair of the virtual disk - restoring data and redundancy to different (or new) physical disks within the storage pool.
490	There is not enough redundancy remaining to repair the virtual disk.
491	This method returns the security descriptor that controls access to this specific object instance.
492	A Security Descriptor Definition Language (SDDL) formed string describing the access control list of the object.
493	This method allows a user with sufficient privileges to set the security descriptor that control access to this specific object instance. If the call is not made in the context of a user specified in the security descriptor's access control list, this method will fail with 40001 - 'Access Denied'. If an empty security descriptor is passed to this function, the behavior is left to the specific implementation so long as there is some user context (typically domain administrators) that can access and administer the object.
494	A Security Descriptor Definition Language (SDDL) formed string describing the desired access control list for this object.
495	This method allows the virtual disk to be renamed.
496	This method allows the virtual disk's intended usage to be updated. Not all virtual disks may allow this and will return 1 - 'Not Supported' if this operation cannot be performed.
497	If Usage is set to 1 - 'Other', this parameter takes in the string representation of a vendor defined usage for this virtual disk. This parameter must not be set if Usage is a value other than 1 - 'Other'.
498	This method allows the user to update or set various attributes on the virtual disk. Note that not all parameters must be specified, and only those given will be updated.
500	The value for WriteCacheSize is outside of the supported range of values.
501	Attaches a Storage Spaces based virtual disk to the system. This operation is similar to Show and Hide, however there is no need for target and initiator configuration since everything is done locally. Depending on the system's NewDiskPolicy (formerly SAN policy), a Storage Space may need to be Attached before it can be used.
502	Detaches a Storage Spaces based virtual disk from the system. This operation is similar to Hide, however there is no need for target and initiator configuration since everything is done locally. Detaching a Storage Space will result in it's corresponding disk object to be suprise removed from the system. Note that detaching can happen in response to certain failure and warning conditions (such as failing redundancy, or thin provisioning capacity limits being reached).
503	The virtual disk could not complete the operation because its Manual Attach status does not permit it.
504	This method will add one or more physical disks for manual allocation.
505	One of the physical disks specified is not supported by this operation.
506	One of the physical disks specified is already in use.
507	One of the physical disks specified uses a sector size that is not supported by this storage pool.
508	This method will remove one or more physical disks from manual allocation.
509	One of the physical disks specified could not be removed because it is still in use.
510	A subsystem storage volume.
545	Drive letter assigned to the volume.
546	Guid path of the volume.
548	Scan Needed
549	Spot Fix Needed
550	Full Repair Needed
551	File system on the volume.
552	File system label of the volume.
553	Total size of the volume
554	Available space on the volume
555	Denotes the type of the volume.
556	Invalid Root Path
557	Removable
558	Remote
559	CD-ROM
560	RAM Disk
561	Format
562	This command is not supported on x86 running in x64 environment
563	Access Denied
565	The specified cluster size is invalid
566	The specified file system is not supported
567	The volume cannot be quick formatted
568	The number of clusters exceeds 32 bits
569	The specified UDF version is not supported
570	The cluster size must be a multiple of the disk's physical sector size
571	Cannot perform the requested operation when the drive is read only
572	Repair
573	The repair failed
574	The scan failed
578	Cannot open drive for direct access
579	Cannot determine the file system of the drive
580	Optimize
581	SetFileSystemLabel
582	GetSupportedFileSystems
583	GetSupportedClusterSizes
584	Gets the volume attributes
586	Sets the volume attributes
587	This setting may not be changed due to the group policy setting
588	This setting may not be changed due to the global registry setting
593	Represents a volume on the system.
594	A user-friendly string representing the name of the storage pool. Friendly name can be set using the SetFriendlyName method.
595	Name is a semi-unique (scoped to the owning storage subsystem), human-readable string used to identify a storage pool.
596	Denotes the intended usage of the storage pool.
597	Reserved as a Delta Replica Container
598	Reserved for Migration Services
599	Reserved for Local Replication Services
600	Reserved for Remote Replication Services
601	If Usage is set to 1 - 'Other', this field contains the string representation of the vendor defined usage for the storage pool. This property must be NULL if Usage is not set to 1 - 'Other'.
602	If this field is set to TRUE, the storage pool is primordial. A primordial pool, also known as the 'available storage' pool is where storage capacity is drawn and returned in the creation and deletion of concrete storage pools. Primordial pools cannot be created or deleted. If this field is set to FALSE, the storage pool is a concrete pool. These pools are subject to all of the management operations defined on the storage pool class. This includes creation, deletion, creation of virtual disks, etc.
603	Denotes the current health status of the storage pool. Health of a storage pool is derived from the health of the backing physical disks, and whether or not the storage pool can maintain the required levels of resiliency. 0 - 'Healthy': All physical disks are present and in a healthy state. 1 - 'Warning': The majority of physical disks are healthy, but one or more may be failing I/O requests. 2 - 'Unhealthy': The majority of physical disks are unhealthy or in a failed state, and the pool no longer has data integrity.
604	Indicates the current operating conditions of the storage pool. Unlike HealthStatus, this field indicates the status of hardware, software, and infrastructure issues related to this storage pool, and can contain multiple values. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail. 4 - 'Stressed': indicates that the storage pool is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, and so on. 5 - 'Predictive Failure': indicates that the storage pool is functioning nominally but predicting a failure in the near future. 11 - 'In Service': describes a storage pool being configured, maintained, or otherwise administered. 12 - 'No Contact': indicates that the storage provider has knowledge of this storage pool, but has never been able to establish communications with it. 13 - 'Lost Communication': indicates that the storage pool is known to exist and has been contacted successfully in the past, but is currently unreachable. 10 - 'Stopped' and 14 - 'Aborted' are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the storage pool might need to be updated. 15 - 'Dormant': indicates that the storage pool is inactive. 16 - 'Supporting Entity in Error': indicates that this storage pool might be OK, but that another element, on which it is dependent, is in error.
605	Read-only
606	A string representation of the vendor defined operational status. This field should only be set if the OperationalStatus array contains 1 - 'Other'.
607	Indicates the capacity of the storage pool. If the pool is primordial, this is the sum of all the healthy physical disk sizes. If the pool is concrete, this is the sum of all associated physical disks (except hot-spares, and including failed drives).
608	Indicates the total sum of all the capacity used by this storage pool. If the pool is primordial, this will be the sum of all capacity currently allocated to concrete storage pools. If the pool is concrete, this value should be the sum of all capacity currently allocated to virtual disks and other pool metadata.
609	This field indicates the logical sector size of the storage pool, in bytes. This value is derived from the backing physical disks, as well as the preference specified at the time this storage pool was created.
610	This field indicates the physical sector size of the storage pool, in bytes. This value is derived from the backing physical disks for this storage pool.
612	Denotes the provisioning schemes that this storage pool supports.
613	Indicates the default resiliency setting used for virtual disk creation. This default can be overridden at the time of virtual disk creation. This property's value should correspond to the resiliency setting's Name field.
614	Indicates whether or not the storage pool's configuration is read-only. If TRUE, the storage pool will not allow configuration changes to itself or any of its virtual and physical disks. Note that the data on the virtual disk may still be writable.
616	Indicates whether or not the storage pool is used in a clustered environment.
617	If TRUE, this storage pool supports data deduplication.
618	Percentages at which an alert should be generated
619	Percentage
620	If TRUE, the storage pool should clear (zero out) physical disks that are removed from the pool.
621	This property indicates whether the disks comprising this pool are able to tolerate power loss without data loss, e.g. automatically flush volatile buffers to non-volatile media after external power is disconnected.
622	Determines the default allocation behavior for virtual disks created in this pool. Enclosure aware virtual disks will intelligently pick the physical disks to use for their redundancy. If TRUE, the storage subsystem will use physical disks from different enclosures to balance the fault tolerance between two (or more) physical enclosures.
623	If TRUE, the storage subsystem will automatically retire missing physical disks in this storage pool and replace them with hot-spares or other available physical disks (in the storage pool).
624	Auto
625	Always
626	Never
632	Default size of write cache for virtual disk creation
633	Minimum size of write cache for virtual disk creation
634	Maximum size of write cache for virtual disk creation
636	You must specify a size by using either the Size or the UseMaximumSize parameter. You can specify only one of these parameters at a time.
637	The specified resiliency setting is not supported by this storage pool.
638	There are not enough eligible physical disks in the storage pool to create the specified virtual disk configuration.
639	No resiliency setting with that name exists.
640	The value for NoSinglePointOfFailure is not supported.
641	The value for PhysicalDiskRedundancy is outside of the supported range of values.
642	The value for NumberOfDataCopies is outside of the supported range of values.
643	The value for ParityLayout is outside of the supported range of values.
644	The value for Interleave is outside of the supported range of values.
645	The value for NumberOfColumns is outside of the supported range of values.
646	Not enough physical disks were specified to successfully complete the operation.
647	This parameter allows the user to specify the FriendlyName at the time of the virtual disk creation. FriendlyNames are expected to be descriptive, however they are not required to be unique. Note that some storage subsystems do not allow setting a friendly name during virtual disk creation. If a subsystem doesn't support this, virtual disk creation should still succeed, however the disk may have a different name assigned to it.
648	Indicates the size for the virtual disk. Note that some storage subsystems will round the size up or down to a multiple of its allocation unit size. This parameter cannot be used if UseMaximumSize is set to TRUE.
649	UseMaximumSize instructs the storage array to create the largest possible virtual disk given the available resources of this storage pool. This parameter cannot be used if the Size parameter is set.
650	Denotes the provisioning type of the virtual disk. 1 - 'Thin': The storage for the virtual disk is allocated on-demand. 2 - 'Fixed': The storage for the virtual disk is allocated up front.
651	This parameter specifies the resiliency setting to use as a template for this virtual disk. This property's value should correspond with the particular resiliency setting instance's Name property. Only resiliency settings associated with this storage pool may be used.
652	Denotes the intended usage of the virtual disk
653	Allows a user to set a vendor specific usage for the new virtual disk object. This parameter can only be specified if the Usage parameter is set to 1 - 'Other'.
655	Specifies how many physical disk failures the virtual disk should be able to withstand before data loss occurs. If specified, this value will override the PhysicalDiskRedundancyDefault which would have been inherited from the resiliency setting specified by ResiliencySettingName.
657	If TRUE, this field instructs the storage provider (or subsystem) to automatically pick what it determines to be the best number of columns for the virtual disk. If this field is TRUE, then the NumberOfColumns parameter must be NULL.
659	Determines the allocation behavior for this virtual disk. Enclosure aware virtual disks will intelligently pick the physical disks to use for their redundancy. If TRUE, the virtual disk will attempt to use physical disks from different enclosures to balance the fault tolerance between two (or more) physical enclosures.
660	If specified, allocation of this virtual disk's storage is limited to the physical disks in the list. These physical disks must already be added to this storage pool.
661	Storage tiers on this virtual disk
662	Sizes of each tier
663	Size of write cache on the virtual disk
664	Indicates if provider should pick up the auto write cache size or not
666	This method creates a virtual disk and single volume using the resources of the storage pool.
668	Indicates the size for the virtual disk. Note that some storage subsystems will round the size up or down to a multiple of its allocation unit size. The size of the resulting volume will be the maximum size possible for the resulting virtual disk.
669	Denotes the provisioning type of the volume. 1 - 'Thin': The storage for the volume is allocated on-demand. 2 - 'Fixed': The storage for the volume is allocated up front.
670	This parameter specifies the resiliency setting to use as a template for this volume. This property's value should correspond with the particular resiliency setting instance's Name property. Only resiliency settings associated with this storage pool may be used.
674	FAT16
675	FAT32
683	NTFS
684	ReFS
685	CSVFS_NTFS
686	CSVFS_ReFS
690	Friendly name of the storage tier
691	Media type of the storage tier
692	Description of the storage tier
693	This method deletes an empty storage pool. If the storage pool contains any virtual disks, these virtual disks should be removed first.
694	The storage pool contains virtual disks.
695	This method will upgrade the version of the storage pool.
696	This method will add one or more physical disks from the primordial storage pool to an existing concrete storage pool.
697	This method removes one or more physical disks from the pool and returns all previously allocated space on the disk to the available capacity in the primordial pool.
698	This method returns the supported sizes for a virtual disk created on this storage pool. These sizes can either be returned in an array of all supported sizes, through a min, max, and divisor, or both.
700	This parameter denotes the minimum supported size that a virtual disk created in this pool can be.
701	This parameter denotes the maximum supported size that a virtual disk created in this pool can be.
702	This method allows the storage pool to be renamed.
703	This method allows the storage pool's intended usage to be updated. Not all storage pools may allow this and will return 1 - 'Not Supported' if this operation cannot be performed.
704	Denotes the new intended usage of the storage pool.
705	If Usage is set to 1 - 'Other', this parameter takes in the string representation of a vendor defined usage for this storage pool. This parameter must not be set if Usage is a value other than 1 - 'Other'.
706	This method allows the user to update or set various defaults on the storage pool. Note that not all parameters must be specified, and only those given will be updated.
707	Specifies the new default provisioning type of the storage pool.
708	Specifies the new default resiliency setting that should be used by this storage pool. The resiliency setting specified must already be associated with this storage pool.
709	This parameter indicates the default allocation policy for virtual disks created in an enclosure aware storage pool. For example, an enclosure aware subsystem could balance each data copy of the virtual disk across multiple physical enclosures such that each enclosure contains a full data copy of the virtual disk.
710	New default size of write cache for virtual disk creation
711	This method allows the user to update or set various attributes on the storage pool. Note that not all parameters must be specified, and only those given will be updated.
712	The number of thin provisioning alert thresholds specified exceeds the limit for this storage pool.
713	Represents a logical grouping of physical disks that may be used to create virtual disks. These virtual disks can be created with different characteristics and levels of resiliency based on the number of available physical disks and the capabilities of the storage pool.
714	FriendlyName is a user-friendly name of the masking set. It is specified during the creation of the masking set, and can be changed using the SetFriendlyName method.
715	Name is a user-friendly system defined name for the masking set. Name is unique within the scope of the owning storage subsystem.
716	This field specifies the operating system, version, driver, and other host environment factors that influence the behavior exposed by the storage subsystem.
717	This method adds an initiator to the masking set. All virtual disks in the masking set will be accessible (shown) to these initiators.
718	Only one initiator address is acceptable for this operation.
719	This parameter is an array of initiator addresses. For each address contained in this array, a corresponding initiator ID instance should be created and then associated with this masking set.
720	This method removes one or more initiator ids from the masking set. Note that the initiator id instances themselves should not be deleted from the system.
721	This method adds one or more target ports to the masking set.
722	This method removes one or more target ports from the masking set.
723	This method adds a virtual disk to the masking set, allowing it to be shown to the initiators contained in the set.
724	The specified virtual disk could not be found.
725	The device number specified is not valid.
726	DeviceAccess must be specified for each virtual disk.
727	Read Write
728	Read-Only
729	No Access
730	This method removes a virtual disk from the masking set. Once removed, this virtual disk will no longer be shown to the initiators contained in this masking set.
731	This method deletes the masking set instance.
732	This method allows the FriendlyName to be set.
733	A masking set is a collection of virtual disks, target ports, and initiator ids that are used for bulk Show and Hide operations. When a resource is added to a masking set it is made available for access to all other resources in the masking set. For example, adding a virtual disk object to a masking set will allow all initiator IDs in the masking set to access the virtual disk object.
734	A user settable string representing the name of the storage subsystem. The storage provider or subsystem is expected to supply an initial value for this field.
735	A user settable description of the storage subsystem. This field can be used to store extra free-form information, such as notes or details about the subsystem's intended usage.
736	Name is a globally unique, human-readable string used to identify a storage subsystem.
737	NameFormat describes the format of the Name identifier.
739	Dial
744	ISDN
748	E.164
750	OID/OSI
752	This field is an array of custom identifier for the subsystem. If this field is set, the OtherIdentifyingInfoDescription field must also be set.
753	An array of string description of the format used in the custom identifiers defined in the OtherIdentifyingInfo field. There must be a 1:1 mapping between this array and OtherIdentifyingInfo.
755	Indicates the current statuses of the subsystem. Various operational statuses are defined. Many of the enumeration's values are self-explanatory. However, a few are not and are described here in more detail. 4 - 'Stressed': indicates that the subsystem is functioning, but needs attention. Examples of 'Stressed' states are overload, overheated, and so on. 5 - 'Predictive Failure': indicates that the subsystem is functioning nominally but predicting a failure in the near future. 11 - 'In Service': describes a subsystem being configured, maintained, cleaned, or otherwise administered. 12 - 'No Contact': indicates that the storage provider has knowledge of this subsystem, but has never been able to establish communications with it. 13 - 'Lost Communication': indicates that the subsystem is known to exist and has been contacted successfully in the past, but is currently unreachable. 10 - 'Stopped' and 14 - 'Aborted' are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the subsystem might need to be updated. 15 - 'Dormant': indicates that the subsystem is inactive. 16 - 'Supporting Entity in Error': indicates that this subsystem might be OK, but that another element, on which it is dependent, is in error.
756	This field denotes the cache level that has been discovered. This corresponds to the storage provider's DiscoveryLevel parameter in the Discover method. 0 - 'Level 0': The storage provider and storage subsystem objects have been discovered. 1 - 'Level 1': Storage pools, resiliency settings, target ports, target portals, and initiator ids belonging to this subsystem have been discovered. 2 - 'Level 2': Virtual disks and masking sets belonging to this subsystem have been discovered. 3 - 'Level 3': Physical disks belonging to this subsystem have been discovered.
757	Level 0
758	Level 1
759	Level 2
760	Level 3
761	This field is a string representation of the company responsible for creating the storage subsystem hardware.
762	This field is a string representation of the model number of the subsystem array.
763	This field is a string representation of the serial number of the subsystem array.
764	This field is a string representation of the subsystem's firmware version.
766	Denotes whether this subsystem supports local mirror replication.
767	Denotes whether this subsystem supports remote mirror replication.
768	Denotes whether this subsystem supports local snapshotting. This field must be true if the VirtualDisk::CreateSnapshot method is implemented.
769	Denotes whether this subsystem supports remote snapshotting.
770	Denotes whether this subsystem supports local cloning. This field must be true if the VirtualDisk::CreateClone method is implemented.
771	Denotes whether this subsystem supports remote cloning.
772	Denotes whether a user can create a virtual disk by using the CreateVirtualDisk method on either the storage subsystem or storage pool objects.
773	Denotes whether a user can modify attributes or other properties on a virtual disk by using the various Set* extrinsic methods. (For example: SetFriendlyname ).
774	Denotes whether a user can delete a virtual disk through the use of the DeleteObject extrinsic method on the virtual disk instance.
775	Indicates if the subsystem allows a virtual disk to be grown in size (using the Resize method of the virtual disk instance).
776	Indicates if the subsystem allows a virtual disk to be reduced in size (using the Resize method of the virtual disk instance).
777	Indicates if the subsystem supports explicit repairing of a virtual disk through the Repair method of the virtual disk instance.
779	If TRUE, this subsystem supports the deletion of its storage pools.
780	If TRUE, storage pools on this subsystem support capacity expansion through adding more physical disks.
781	If TRUE, storage pools on this subsystem support the replacement or removal of physical disks by use of the RemovePhysicalDisk method on the storage pool instance.
782	If TRUE, the CreateVirtualDisk method on the storage subsystem is supported.
783	If TRUE, all resiliency settings will be copied from the primordial pool and added to a concrete pool upon its creation. If FALSE, the storage pool should copy the setting specified in the ResiliencySettingNameDefault parameter of CreateStoragePool. If no name was given, the resiliency setting specified by the primordial pool's ResiliencySettingNameDefault property should be used.
785	If TRUE, this subsystem supports the deletion of storage tiers.
786	If TRUE, this subsystem supports the resizing of storage tiers.
788	If TRUE, this subsystem supports the creation of tiered virtual disks.
789	This field is reserved for future releases.
790	If TRUE, the storage subsystem supports showing and hiding (masking) a virtual disk to a host initiator through the Show/Hide methods of the virtual disk and by the use of masking sets.
791	Indicates which address formats can be inferred by the storage provider and subsystem when working with initiator ids.
792	Port WWN
793	Node WWN
794	Host Name
795	iSCSI Name
796	Switch WWN
797	SAS Address
798	If MaskingValidInitiatorIdTypes contains the value 1 - 'Other', this field is used to enumerate the other valid initiator id types for this storage subsystem.
799	Indicates the number of target ports that can be used for masking a virtual disk. This applies to both masking sets and the virtual disk Show method.
800	One TargetPort per view
801	Multiple target ports per view
802	All target ports share the same view
803	If TRUE, the storage provider supports the use of the DeviceNumbers parameter of the CreateMaskingSet and AddVirtualDisk methods.
804	If TRUE, the subsystem will only allow one initiator to be added to a masking set.
805	Indicates the maximum number of masking sets that a particular virtual disk can be added to.
807	Manual
808	Denotes the iSCSI Target Creation Scheme supported by the subsystem. 0 - 'Not Applicable' implies a non-iSCSI subsystem. 1 - 'Not Supported' implies the subsystem does not allow creation of a Target. 2 - 'Manual' implies the subsystem allows manual creation of the Target. 3 - 'Auto' implies the subsystem automatically creates a Target.
809	Not Applicable
810	Denotes the total number of physical disk slots in the subsystem or enclosure.
811	A string representing the name of the management server. This value is only relevant for Storage Management Providers that implement the SMI-S standard.
812	An array representing the supported host types.
813	When the corresponding array entry in SupportedHostType[] is "Other", this entry provides a string describing the manufacturer and OS/Environment. When the corresponding SupportedHostType[] entry is not "Other", this entry allows variations or qualifications of ClientTypes - for example, different versions of Solaris.
814	This method creates a storage pool from available physical disks contained within a common primordial pool. A physical disk is available for storage pool creation if its CanPool property is set to TRUE. Storage pool creation is only available when the SupportsStoragePoolCreation field of the storage subsystem is TRUE.
815	This parameter allows the user to specify the FriendlyName at the time of the storage pool creation. FriendlyNames are expected to be descriptive, however they are not required to be unique. Note that some storage subsystems do not allow setting a friendly name during pool creation. If a subsystem doesn't support this, storage pool creation should still succeed, however the pool may have a different name assigned to it.
816	Allows a user to set a custom usage type for the new storage pool object. This parameter can only be specified if the Usage parameter is set to 1 - 'Other'.
818	This parameter indicates the resiliency setting to be used by default when creating a new virtual disk on this storage pool. If the subsystem's SupportsMultipleResiliencySettingsPerStoragePool property is set to FALSE, this parameter also acts as a hint to the Storage Management Provider on which resiliency setting should be inherited by this storage pool. If no value is given, it is up to the Storage Management Provider to pick the most appropriate resiliency setting.
819	This parameter indicates the provisioning type to be used by default when creating a new virtual disk on this storage pool. If no default is specified, the default is inherited from the primordial pool.
820	This parameter indicates the default logical sector size for the storage pool. This is useful when a storage pool may contain a mix of 512 emulated and either 4K native or 512 native physical disks.
821	This method allows for the creation of virtual disks on a storage subsystem. This method is typically used when either a) the subsystem's storage pools do not allow virtual disk creation directly, or b) the subsystem does not support storage pools. Storage Management Providers may also choose to implement this method to 'intelligently' pick a storage pool for the user. If this method is supported, the subsystem's SupportsAutomaticStoragePoolSelection property should be set to TRUE.
822	No storage pools were found that can support this virtual disk configuration.
823	This parameter allows the user to specify the desired FriendlyName at the time of the virtual disk creation. FriendlyNames are expected to be descriptive, however they are not required to be unique. Note that some storage subsystems do not allow setting a friendly name during virtual disk creation. If a subsystem doesn't support this, virtual disk creation should still succeed, however the disk may have a different name assigned to it.
824	Allows a user to set a custom usage type for the new virtual disk object. This parameter can only be specified if the Usage parameter is set to 1 - 'Other'.
825	Indicates the desired size for the virtual disk. Note that some storage subsystems will round the size up or down to a multiple of its allocation unit size. If this parameter is specified, UseMaximumSize must be NULL or FALSE.
826	Create a virtual disk using the largest supported size. This parameter cannot be used with the Size parameter.
827	Specifies the number of complete data copies to maintain for this virtual disk.
828	Specifies how many physical disk failures the virtual disk should be able to withstand before data loss occurs.
829	Specifies the number of underlying physical disks across which data should be striped.
830	Specifies the number of bytes used to form a strip in common striping-based resiliency settings. The strip is defined as the size of the portion of a stripe that lies on one physical disk. Thus Interleave * NumberOfColumns will yield the total size of one stripe.
832	Denotes the provisioning type of the virtual disk. A value of 1 - 'Thin' means that the storage for the disk is allocated on-demand. A value of 2 - 'Fixed' means that the storage is allocated up front.
833	Creates logical grouping of virtual disks, target ports, and initiators for the purpose of showing virtual disks to host systems.
834	This parameter allows the user to specify the desired FriendlyName for the masking set at the time of its creation. FriendlyNames are expected to be descriptive, however they are not requried to be unique.
835	This parameter specifies the list of virtual disks to show to the initiators in the masking set. The identifier used by this parameter is the virtual disk Name property. This parameter has a 1:1 mapping with the DeviceAccesses parameter (the arrays must be the same length and have the same order).
836	This parameter specifies the level of access the initiator should have to each virtual disk specified by VirtualDiskNames. This parameter has a 1:1 mapping with the VirtualDiskNames parameter (the arrays must be the same length and have the same order).
837	Specifies the order in which the virtual disks should be exposed to the initiator. This capability is only available if the storage subsystem's MaskingClientSelectableDeviceNumbers property is set to TRUE. If specified, this parameter must have a 1:1 mapping with the VirtualDiskNames parameter.
838	This parameter specifies the target ports which should be used when showing the virtual disks to the initiators. The number of target ports that can be specified depends on the subsystem's MaskingPortsPerView property. If MaskingPortsPerView is set to 4 - 'All target ports share the same view', this parameter is essentially ignored as all target ports on the system will be associated with this masking set.
839	This parameter specifies the initiators for which the virtual disks should be shown. If the subsystem's MaskingOneInitiatorIdPerView property is TRUE, only one initiator can be specified for this masking set. The list of valid initiator address formats can be determined through the subsystem's MaskingValidInitiatorIdTypes property.
841	This method allows a user to set the description field of the storage subsystem.
845	SMI-S
846	A user-friendly name of the storage provider.
847	A string indicating the manufacturer of the SMP software.
848	A version string used by the SMP manufacturer to differentiate between software versions.
849	If the SMP is of type 2 - 'SMI-S', this field contains the name of the host running the SMI-S provider software. This field will be NULL otherwise.
850	If the SMP is of type 2 - 'SMI-S', this field contains the protocol, computer host name, and port of the SMI-S server. This field will be NULL otherwise.
851	If the SMP is of type 2 - 'SMI-S', this field contains the protocol, IP address, and port of the SMI-S server. This field will be NULL otherwise.
852	This method is used when a user wants to explicitly discover or re-enumerate objects owned by the storage provider. A call to this method could result in a full or partial cache invalidation and over-the-wire calls to the storage subsystem(s) in order to discover new or updated objects. As this is a time consuming task, it should be used sparingly by the user. The scope of the discovery operation is controlled by the DiscoveryLevel and RootObject parameters. DiscoveryLevel controls the depth of the object discovery. RootObject defines the starting point from which discovery will happen.
853	The storage provider does not support a required profile.
854	The storage provider does not support a required association.
855	This field denotes the level (or depth) of discovery that should be performed. This parameter can only be specified if the root object is a storage provider, storage subsystem, or NULL. When specified, the storage provider will discover objects starting from Level 0 and continuing until the specified level is reached. Associations between objects (within the discovered levels) will also be discovered. The discovery levels are defined as follows: 0 - 'Level 0': The storage provider and storage subsystem objects will be discovered. 1 - 'Level 1': Storage pools, resiliency settings, target ports, target portals, and initiator ids will be discovered. 2 - 'Level 2': Virtual disks and masking sets will be discovered. 3 - 'Level 3': Physical disks will be discovered.
856	If this parameter is set, discovery will begin from this object. When DiscoveryLevel is NULL, well-defined actions will be taken depending on the type of object specified by RootObject: Storage subsystem: All associated objects will be discovered. Storage pool: The pool, along with any associated resiliency settings, virtual disks, and physical disks will be discovered. Masking set: The masking set, along with any associated target ports, initiator ids, and virtual disks will be discovered. For all other objects: Only that object will be discovered / refreshed.
857	This method registers a subsystem to be managed by this provider. Note that the subsystem must be compatible with the provider software.
858	Cannot register/unregister the storage subsystem on local host.
859	This method unregisters a subsystem. The provider will no longer manage this subsystem.
860	The storage subsystem is not registered.
861	This class is a representation of a particular Storage Management Provider (SMP) software package which is used to manage a storage subsystem.
862	In Process
863	Pending
864	Completely on tier
865	Partially on tier
866	Not on tier
869	This class manages file pinning.
871	The operating system's number for the disk that contains this partition. Disk numbers may not necessarily remain the same across reboots.
873	The currently assigned drive letter to the partition. This property is NULL if no drive letter has been assigned.
874	This property is an array of all the various mount points for the partition. This list includes drive letters, as well as mounted folders.
875	Online
876	No Media
878	Total size of the partition, measured in bytes.
879	This property indicates the partition's MBR type. This property is only valid when the disk's PartitionStyle property is set to 1 - 'MBR' and will be NULL for all other partition styles.
880	FAT12
881	Extended
882	Huge
884	This property indicates the partition's GPT type. This property is only valid when the disk's PartitionStyle property is set to 2 - 'GPT' and will be NULL for all other partition styles.
885	System Partition
886	Basic data
887	LDM Metadata
888	LDM Data
889	Microsoft Recovery
890	This property is a string representation of the partition's GPT GUID. This property is only valid if the disk's PartitionStyle property is set to 2 - 'GPT' and will be NULL for all other partition stlyes.
891	Signifies whether or not the partition is active and can be booted. This property is only relevant for MBR disks.
892	If this property is set to TRUE, the partition is not detected by the mount manager. As a result, the partition does not receive a drive letter, does not receive a volume GUID path, does not host volume mount points, and is not enumerated by calls to FindFirstVolume and FindNextVolume. This ensures that applications such as disk defragmenter do not access the partition. The Volume Shadow Copy Service (VSS) uses this attribute on its shadow copies.
893	If this property is set to TRUE, the partition is a shadow copy of another partition. This attribute is used by the Volume Shadow Copy service (VSS). This attribute is an indication for file system filter driver-based software (such as antivirus programs) to avoid attaching to the volume. An application can use this attribute to differentiate a shadow copy partition from a production partition. For example, an application that performs a fast recovery will break a shadow copy virtual disk by clearing the read-only and hidden attributes and this attribute. This attribute is set when the shadow copy is created and cleared when the shadow copy is broken.
894	If this property is set to TRUE, the operating system does not assign a drive letter automatically when the partition is discovered. This is only honored for GPT disks and is assumed to be FALSE for MBR disks. This attribute is useful in storage area network (SAN) environments.
895	Deletes the partition and corresponding volume.
896	In use
897	The partition was deleted, although its access paths were not.
898	The extended partition still contains other partitions.
899	The operation is not allowed on a system or critical partition.
900	This method returns all mount points and drive letters that can be used to access the partition.
902	The requested access path is already in use.
903	Cannot assign access paths to hidden partitions.
904	The access path is not valid.
905	Cannot assign multiple drive letters to a partition.
906	Cannot assign drive letter to this type of partition.
907	This parameter is a string indicating the access path, which is a user-mode path that can be used to open the partition. An access path can be a drive letter (in the form C: or C:\) or a path to an empty directory on an NTFS volume. The access path string does not require a trailing backslash.
908	If this parameter is specified as TRUE, the next available drive letter will be assigned to the partition.
909	This method removes the access path from the partition regardless of whether or not it is in use.
910	Cannot remove a volume GUID path.
911	Cannot remove the drive letter of a boot or paging file partition.
912	This method resizes the partition and any associated filesystem to the size specified by the Size parameter. If the size is outside of the bounds returned by the GetSupportedSize method, then this method will fail with a well defined error code. The resize operation is only supported on NTFS formatted partitions and RAW partitions. If the specified size is smaller than the original size, this method will move files so that they are as close as possible to the beginning of the partition, in order to consolidate free space at the end of the partition. It then truncates the file system volume, reducing its size, and then truncates the partition. In almost all cases, there will be some files that are immovable. For example, file system and storage driver metadata files are likely to be immovable. For this reason, the amount by which a partition can be shrunk is usually less than the total amount of free space on the partition.
913	Cannot shrink a partition containing a volume with errors.
914	Cannot resize a partition containing an unknown file system.
915	This method returns the minimum and maximum sizes that the partition can be resized to using the Resize method. The minimum size is determined by the disk defragmenter and takes into account the location of immovable files. The maximum size is determined by adding the size of any free extents immediately after the current partition.
916	This output parameter contains the minimum size that this partition can become. Note that if this method is run multiple times, this value can change slightly depending on the placement of various temporary files.
917	This output parameter contains the maximum size that this partition can become.
919	This operation is only supported on data partitions.
921	The volume still has access path to it.
922	Sets various attributes and properties of the partition.
923	The disk has not been initialized.
924	The disk is offline.
925	A parameter is not valid for this type of partition.
926	Represents a partition on a disk.
927	Path can be used to open an operating system handle to the disk device.
930	UniqueId of a disk contains the VPD Page 0x83 information that uniquely identifies this disk. The following types are accepted (in order of precedence): 8 - SCSI Name String; 3 - FCPH Name; 2 - EUI64, 1 - Vendor Id, 0 - Vendor Specific. If the disk is an exposed VirtualDisk, UniqueId is used map the association between the two objects.
931	UniqueIdFormat informs the user what VPD Page 0x83 descriptor type was used to populate the UniqueId field.
932	The operating system's number for the disk. Disk 0 is typically the boot device. Disk numbers may not necessarily remain the same across reboots.
933	A string representation of the disk's serial number.
934	A string representation of the disk's firmware version.
935	A string representation of the disk's hardware manufacturer.
936	A string representation of the disk's model.
937	The total size of the disk, measured in bytes.
938	The amount of space currently used on the disk.
939	This field indicates the logical sector size of the disk in bytes. For example: a 4K native disk will report 4096, while a 512 emulated disk will report 512.
940	This field indicates the physical sector size of the disk in bytes. For example: both 4K native disks and 512 emulated disks will report 4096.
941	This field indicates the largest contiguous block of free space on the disk. This is also the largest size of a partition which can be created on the disk.
942	Denotes the provisioning type of the disk device. 1 - 'Thin' means that the storage for the disk is allocated on-demand. 2 - 'Fixed' means that the storage is allocated up front.
943	Not Ready
946	Denotes the I/O bus type used by this disk.
949	The MBR signature of the disk. This property is only valid on MBR disks and will be NULL for all other disk types.
950	The GPT guid of the disk. This property is only valid on GPT disks and will be NULL for all other disk types.
951	If IsOffline is TRUE, this property informs the user of the specific reason for the disk being offline. 1 - 'Policy': The user requested the disk to be offline. 2 - 'Redundant Path': The disk is used for multi-path I/O. 3 - 'Snapshot': The disk is a snapshot disk. 4 - 'Collision': There was a signature or identifier collision with another disk. 5 - 'Resource Exhaustion': There were insufficient resources to bring the disk online. 6 - 'Critical Write Failures': There were critical write failures on the disk. 7 - 'Data Integrity Scan Required': A data integrity scan is required.
952	Policy
953	Redundant Path
954	Snapshot
955	Collision
956	Resource Exhaustion
957	Critical Write Failures
958	Data Integrity Scan Required
959	If IsSystem is TRUE, this disk contains the system partition.
960	If IsClustered is TRUE, this disk is used in a clustered environment.
961	This property indicates that the computer has booted off of this disk.
963	This method will attempt to create a new partition on the disk. By default, it creates a data partition using the largest available free extent. On MBR disks, CreatePartition will automatically create an extended partition when needed.
964	Disk is in use
965	The disk is read only.
966	The disk's partition limit has been reached.
967	The specified partition alignment is not valid. It must be a multiple of the disk's sector size.
968	The specified partition type is not valid.
969	Only the first 2 TB are usable on MBR disks.
970	The specified offset is not valid.
971	There is no media in the device.
972	Operation not supported on a non-empty removable disk.
973	The specified partition layout is invalid.
974	This parameter specifies the desired size (measured in bytes) for the partition. This must be equal to or less than the size specified by the disk's LargestFreeExtent property. This parameter cannot be used with UseMaximumSize.
975	If set to TRUE, the partition will fill the largest free extent on the disk. This parameter cannot be used with the Size parameter.
977	This parameter allows the user to specify a drive letter for the partition at the time of creation. This parameter cannot be used in conjunction with AssignDriveLetter. If both parameters are specified, an Invalid Parameter error will be returned. If the drive letter is not available, the partition will be created, but error '42002' will be returned.
978	If AssignDriveLetter is set to TRUE, the next available drive letter will be assigned to the created partition. If no more drive letters are available, the partition will be created with no drive letter. This parameter cannot be used in conjunction with DriveLetter. If both parameters are specified, an Invalid Parameter error will be returned.
979	Specifies the MBR partition type. MbrType can only be set if the disk's PartitionStyle property is set to 1 - 'MBR', otherwise an error will be returned. If this parameter is not specified, CreatePartition will default to type 6 - 'Huge'.
980	Specifies the GPT partition type. GptType is only valid if the disk's PartitionStyle property is set to 2 - 'GPT', otherwise an error will be returned. If this parameter is not specified, CreatePartition will default to {ebd0a0a2-b9e5-4433-87c0-68b6b72699c7} - 'Basic Data'.
981	If TRUE, the partition will not be able to receive a drive letter assignment, nor will mount manager assign a volume GUID name. The partition will not be enumerated by the FindFirstVolume and FindNextVolume functions. The partition can be opened by its associated volume device name (i.e. \?GLOBALROOT\Device\HarddiskVolumeX).
982	If TRUE, the partition's MBR active bit will be set, and the partition will become bootable. This parameter is only valid for MBR disks.
983	This method initializes a RAW disk with a particular partition style. If no partition style is specified, GPT will be selected by default. If the disk is already initialized, this method will fail with a well defined error code.
984	The disk has already been initialized.
985	The disk is not large enough to support a GPT partition style.
986	Specifies the desired partition style for the disk. If no value is given, Initialize will default to 2 - 'GPT'.
987	This method removes partition information and uninitializes a disk, sending it back into a RAW state. The caller must specify RemoveData, RemoveOEM or both with this method unless they first delete all data partitions, known OEM partitions, and ESP partitions on the disk. This requirement excludes metadata partitions such as the MSR, the LDM metadata partition, and unknown OEM partitions.
988	Cannot clear with OEM partitions present. To clear OEM partitions, use the RemoveOEM flag.
989	Cannot clear with data partitions present. To clear data partitions, use the RemoveData flag.
991	This parameter indicates that it is OK to remove data partitions from the disk. If this parameter is FALSE or NULL, Clear will fail in the presence of a data partition.
992	This parameter indicates that it is OK to remove OEM and other special partitions. If this parameter is FALSE or not specified, Clear will fail in the presence of these types of partitions.
993	If TRUE, this parameter instructs Clear to zero out the entire disk in addition to removing all partition information. If the parameter is FALSE or NULL, only the first and last megabyte of the disk is zeroed.
994	This method converts the partition style of an already initialized disk.
995	Operation not supported on a critical disk.
996	Cannot convert the style of a disk with data or other known partitions on it.
997	Takes the disk offline.
998	Brings the disk online.
999	Sets various attributes and properties of the disk. The disk must be online for most attributes to be set.
1000	If TRUE, the disk will be made read-only. If FALSE, the disk will become writable.
1001	Sets the MBR signature of the disk. This parameter is only valid when the disk's PartitionStyle property is set to 1 - 'MBR'. An error will be returned if the disk is any other partition style.
1002	Sets the GPT guid of the disk. This parameter is only valid when the disk's PartitionStyle property is set to 2 - 'GPT'. An error will be returned if the disk is any other partition style.
1003	This method refreshes the cached disk layout information. This is useful when the backing disk has changed size (if the backing data store is a VHD or a virtual disk).
1004	A disk object models the operating system's concept of a disk device. The disk may be directly attached to the computer system, or a virtual disk exposed to the system through the use of a Storage Management Provider.
1006	A system set description of the capabilities of the resiliency setting, including (but not limited to) when a setting should be used, its strengths and drawbacks, performance information, and any other information that the vendor feels is helpful to the user.
1007	This field reports the minimum number of complete copies of data that will be maintained by the storage pool.
1008	This field reports the maximum number of complete copies of data that can be maintained by the storage pool.
1009	This field is a user-settable preference for the number of complete data copies to maintain. Its value must be within the range defined by NumberofDataCopiesMin and NumberOfDataCopiesMax (inclusive). For new concrete pools, the default should be inherited from the corresponding primordial pool's capability. In the case of the primordial pool, the initial value for this field is left to the Storage Management Provider software.
1010	This field reports the minimum number of tolerable physical disk failures that can occur before data loss would occur.
1011	This field reports the maximum number of tolerable physical disk failures that could occur before data loss would occur.
1012	This field is a user-settable preference for how many physical disk failures a virtual disk should be able to withstand before data loss occurs.
1013	This field describes the minimum number of underlying physical disks across which data can be striped in the common striping-based resiliency settings.
1014	This field describes the maximum number of underlying physical disks across which data can be striped in the common striping-based resiliency settings.
1015	This field is a user-settable preference for the number of underlying physical disks across which data should be striped.
1016	This field describes the minimum number of bytes that can form a strip in common striping-based resiliency settings. The strip is defined as the size of the portion of a stripe that lies on one physical disk.
1017	This field describes the maximum number of bytes that can form a strip in common striping-based resiliency settings. The strip is defined as the size of the portion of a stripe that lies on one physical disk.
1018	This field describes the desired number of bytes that will form a strip in common striping-based resiliency settings. The strip is defined as the size of the portion of a stripe that lies on one physical disk. Thus, Interleave * NumberOfColumns will yield the total size of one stripe.
1019	This field specifies whether a parity-based resiliency setting is using a rotated or non-rotated parity layout. If the resiliency setting is not parity based, this field must be set to NULL
1021	The desired number of full data copies to maintain. This value must be between NumberofDataCopiesMin and NumberofDataCopiesMax.
1022	The desired level of physical disk failure tolerance. This value must be between PhyscialDiskRedundancyMin and PhysicalDiskRedundancyMax.
1023	Specifies the desired number of physical disks to stripe data across. This value must be between NumberOfColumnsMin and NumberofColumnsMax.
1024	If TRUE, this field instructs the storage provider (or subsystem) to automatically pick what it determines to be the best number of columns for this resiliency setting. If this field is TRUE, then the NumberOfColumnsDefault parameter must be NULL.
1025	Specifies the desired size of a data strip on a single physical disk in a striping based resiliency setting. This value must be between InterleaveMin and InterleaveMax.
1026	ResiliencySetting is a detailed description of the resiliency capabilities offered by a storage pool. A storage pool can have one or more of these settings. It specifies a series of properties with a minimum, maximum, and default value. The minimum and maximum values may not reflect the current capabilities of the storage pool, but rather the ideal range of capabilities offered by the subsystem. The default values will be used when creating new virtual disks unless overridden.
1027	FriendlyName is a user-friendly name of the target port.
1028	This field is the node identifier / address. For Fibre Channel networks, this field should be the World-Wide Name (WWN) for the port, formatted as a hexadecimal string (16 characters long), with the most significant byte first. For example, a WWN address of 01:23:45:67:89:AB:CD:EF should be represented as 0123456789ABCDEF. For iSCSI networks, this field should be the IQN.
1029	The identifier of the controller to which this port belongs
1030	Denotes the role of this controller port. For iSCSI, this port must act as either a target or an initiator endpoint. Other transports allow a port to act as both an initiator and a target.
1031	Initiator
1032	Target
1033	Both Initiator and Target
1034	In some circumstances, a target port may be identifiable as a front-end or back-end port. For example: a storage array might have back-end ports to communicate with physical disks, and front-end ports to communicate with hosts. If there is no restriction on the use of the port, then the value should be set to 4 - 'Not restricted'.
1035	Front-end only
1036	Back-end only
1037	Not restricted
1038	Indicates the current operating status of the target port.
1039	Parallel SCSI
1040	IEEE 1394
1041	RDMA
1043	A string representation of the vendor defined connection type. This field should only be set if ConnectionType is set to 1 - 'Other'.
1044	Ethernet
1047	FDDI
1049	Token Ring
1050	Frame Relay
1051	Infrared
1053	Wireless LAN
1054	A string representation of the vendor defined link technology. This field should only be set if LinkTechnology is set to 1 - 'Other'.
1055	The current bandwidth of the port in bits per second. For ports that vary in bandwidth or for those where no accurate estimation can be made, this property should contain the nominal bandwidth for the port.
1056	bits/sec
1057	The maximum bandwidth of the port in bits per second
1058	An array of strings that represent the various network addresses for the target port. The type and format of these addresses depend on the PortType.
1059	Indicates the specific mode currently enabled for the port. If the port is logged in, this will be the negotiated port type. Otherwise, the configured port type will be reported.
1062	F/NL
1069	10BaseT
1070	10-100BaseT
1071	100BaseT
1072	1000BaseT
1073	2500BaseT
1074	10GBaseT
1075	10GBase-CX4
1076	100Base-FX
1077	100Base-SX
1078	1000Base-SX
1079	1000Base-LX
1080	1000Base-CX
1081	10GBase-SR
1082	10GBase-SW
1083	10GBase-LX4
1084	10GBase-LR
1085	10GBase-LW
1086	10GBase-ER
1087	10GBase-EW
1088	A target port represents an instance of an endpoint in a storage subsystem with associated properties for showing and hiding virtual disks. Fibre Channel, Serial Attached SCSI, or iSCSI ports within a storage subsystem controller are all examples of target ports.
1089	The IPv4 address that this portal / endpoint uses.
1090	The IPv6 address that this portal / endpoint uses.
1091	The mask for the IPv4 address of this portal / endpoint, if one is defined.
1092	The port number used by this portal / endpoint
1093	TargetPortal is an endpoint used by IP based storage networks (such as iSCSI). It provides initiators the IP address for which they should discover target ports on.
1094	This field contains the address or unique identifier for the corresponding initiator port.
1095	This field specifies the type of the identifier used for initiator address.
1096	PortWWN
1097	Hostname
1098	SwitchWWN
1099	SASAddress
1100	This field specifies the operating system, version, driver, and other host environment factors that influence the behavior exposed by storage systems.
1101	When the corresponding array entry in HostType[] is "Other", this entry provides a string describing the manufacturer and OS/Environment. When the corresponding HostType[] entry is not "Other", this entry allows variations or qualifications of ClientTypes - for example, different versions of Solaris.
1102	Allows the user to delete an instance of an initiator id
1103	This object represents the storage subsystem's view of an initiator port. This is used in conjunction with target port to establish which initiator port is allowed to access to the subsystem's virtual disks.
1104	Not present
1105	Fabric
1106	Public Loop
1107	FL Port
1108	Fabric Port
1109	Fabric expansion port
1110	Generic Fabric Port
1111	Private Loop
1112	Point to Point
1113	SAS Expander
1114	Operational
1115	User Offline
1116	Bypassed
1117	In diagnostics mode
1118	Link Down
1119	Port Error
1120	Loopback
1121	Allows setting the NodeAddress for an iSCSI initiator port by passing an IQN as the NodeAddress string.
1122	This class represents a Host Bus Adapter (HBA) an initiator port on the host system.
1123	Name is a human-readable string used to identify a storage node.
1124	This field is an array of custom identifier for the node. If this field is set, the OtherIdentifyingInfoDescription field must also be set.
1125	Indicates the current status of the node.
1127	Down
1128	Joining
1129	Paused
1130	Represents a storage node in a cluster.
1131	Association between StorageSubSystem and StorageNode
1132	Association between Disk and Partition
1133	Association between StorageProvider and StorageSubSystem
1134	Association between Partition and Volume
1135	Association between StorageSubSystem and StoragePool
1136	Association between StorageSubSystem and PhysicalDisk. This association should include all physical disks that the subsystem is aware of.
1137	Association between StorageSubSystem and VirtualDisk
1138	Association between StorageNode and StoragePool.
1139	Association between StorageNode and PhysicalDisk.
1140	Association between StorageNode and VirtualDisk.
1142	Association between StoragePool and ResiliencySetting
1143	Association between StoragePool and VirtualDisk. This association should only exist for concrete pools.
1144	Association between VirtualDisk and Disk
1145	Association between StorageSubSystem and TargetPort
1146	Association between MaskingSet and TargetPort
1147	Association between StorageSubSystem and InitiatorId
1148	Association between MaskingSet and InitiatorId
1149	Association between TargetPort and VirtualDisk
1150	Association between StorageSubSystem and MaskingSet
1151	Association between MaskingSet and VirtualDisk
1153	This field indicates the class of the object which caused the indication. For example: if the object causing the indication is a storage pool, this field should be set to MSFT_StoragePool (not the vendor derived class).
1154	This field allows the Storage Management Provider (SMP) to provide a brief description explaining the indication.
1157	Base storage event indication
1158	Storage arrival events are used whenever a storage object is added or created.
1159	Storage departure events are used whenever a storage object is removed or deleted.
1160	Storage modification events are used when the underlying state of an object has changed. Not all properties should be tracked (for example AllocatedSize may change so frequently that sending events would be impractical). At a minimum, an event should be sent any time an objects HealthStatus or OperationalStatus properties change.
1161	This field describes the type of alert being received.
1162	Thin provisioning threshold reached
1163	Storage alert event
1165	Online All
1166	Offline Shared
1167	Offline All
1168	Offline Internal

COM Classes/Interfaces

There is no type library in this file with COM classes/interfaces information

Exported Functions List

The following functions are exported by this dll:

DllCanUnloadNow	DllGetClassObject	DllMain	DllRegisterServer
DllUnregisterServer	GetProviderClassID	MI_Main

Imported Functions List

The following functions are imported by this dll:

msvcrt.dll:

_CxxThrowException

_XcptFilter

__CxxFrameHandler

___lc_codepage_func

___lc_handle_func

___mb_cur_max_func

__crtGetStringTypeW

__crtLCMapStringW

__dllonexit

__mb_cur_max

__pctype_func

__uncaught_exception

_amsg_exit

_callnewh

_errno

_except_handler4_common

_ftol2

_initterm

_lock

_onexit

_purecall

_unlock

_vscwprintf

_vsnwprintf

_wcsicmp

_wcsnicmp

abort

free

iswalpha

localeconv

malloc

mbtowc

memchr

memcmp

memcpy

memcpy_s

memmove

memmove_s

memset

public: __thiscall bad_cast::bad_cast(class bad_cast const &)

public: __thiscall exception::exception(char const * const &)

public: __thiscall exception::exception(class exception const &)

public: __thiscall exception::exception(void)

public: virtual __thiscall bad_cast::~bad_cast(void)

public: virtual __thiscall exception::~exception(void)

public: virtual __thiscall type_info::~type_info(void)

public: virtual char const * __thiscall exception::what(void)const

setlocale

sprintf_s

strcspn

swprintf_s

swscanf_s

toupper

towupper

void __cdecl terminate(void)

wcschr

wcsncmp

wcsrchr

wcsstr

wcstok_s

wcstoul

api-ms-win-eventing-provider-l1-1-0.dll:

ntdll!EtwEventActivityIdControl ntdll!EtwEventRegister ntdll!EtwEventSetInformation
ntdll!EtwEventUnregister ntdll!EtwEventWrite ntdll!EtwEventWriteTransfer
api-ms-win-core-profile-l1-1-0.dll:

ntdll!RtlQueryPerformanceCounter ntdll!RtlQueryPerformanceFrequency
api-ms-win-core-libraryloader-l1-2-0.dll:

KernelBase!DisableThreadLibraryCalls KernelBase!FreeLibrary KernelBase!GetModuleHandleW
KernelBase!GetProcAddress KernelBase!LoadLibraryExW KernelBase!LoadStringW
api-ms-win-core-sysinfo-l1-2-1.dll:

KernelBase!GetComputerNameExW KernelBase!GetSystemDirectoryW KernelBase!GetSystemTimeAsFileTime
KernelBase!GetTickCount KernelBase!GetTickCount64 KernelBase!GetVersionExW
api-ms-win-core-errorhandling-l1-1-1.dll:

KernelBase!GetLastError KernelBase!SetUnhandledExceptionFilter KernelBase!UnhandledExceptionFilter
ntdll!RtlRestoreLastWin32Error

api-ms-win-core-synch-l1-2-0.dll:

KernelBase!CreateEventW	KernelBase!CreateMutexW	KernelBase!ReleaseMutex
KernelBase!ResetEvent	KernelBase!SetEvent	KernelBase!Sleep
KernelBase!WaitForMultipleObjectsEx	KernelBase!WaitForSingleObject	ntdll!RtlAcquireSRWLockExclusive
ntdll!RtlDeleteCriticalSection	ntdll!RtlEnterCriticalSection	ntdll!RtlInitializeConditionVariable
ntdll!RtlInitializeCriticalSection	ntdll!RtlLeaveCriticalSection	ntdll!RtlReleaseSRWLockExclusive

api-ms-win-core-com-l1-1-1.dll:

combase!CLSIDFromString	combase!CoCreateGuid	combase!CoCreateInstance	combase!CoDisconnectObject
combase!CoInitializeEx	combase!CoSetProxyBlanket	combase!CoTaskMemAlloc	combase!CoTaskMemFree
combase!CoUninitialize

api-ms-win-core-processthreads-l1-1-2.dll:

KernelBase!OpenProcessToken	KernelBase!OpenThreadToken	KernelBase!SetThreadToken	kernel32!CreateThread
kernel32!GetCurrentProcess	kernel32!GetCurrentProcessId	kernel32!GetCurrentThread	kernel32!GetCurrentThreadId
kernel32!TerminateProcess	kernel32!TlsAlloc	kernel32!TlsFree	kernel32!TlsGetValue
kernel32!TlsSetValue

OLEAUT32.dll:

SysAllocString SysFreeString VariantClear

api-ms-win-core-file-l1-2-1.dll:

KernelBase!CreateDirectoryW	KernelBase!CreateFileW
KernelBase!DefineDosDeviceW	KernelBase!DeleteFileW
KernelBase!DeleteVolumeMountPointW	KernelBase!FindClose
KernelBase!FindFirstFileW	KernelBase!FindFirstVolumeW
KernelBase!FindNextFileW	KernelBase!FindNextVolumeW
KernelBase!FindVolumeClose	KernelBase!FlushFileBuffers
KernelBase!GetDiskFreeSpaceExW	KernelBase!GetDriveTypeW
KernelBase!GetFileAttributesW	KernelBase!GetFileInformationByHandle
KernelBase!GetFinalPathNameByHandleW	KernelBase!GetVolumeInformationW
KernelBase!GetVolumeNameForVolumeMountPointW	KernelBase!GetVolumePathNameW
KernelBase!GetVolumePathNamesForVolumeNameW	KernelBase!QueryDosDeviceW
KernelBase!ReadFile	KernelBase!SetFileAttributesW
KernelBase!SetFilePointer	KernelBase!SetFilePointerEx
KernelBase!WriteFile

api-ms-win-core-io-l1-1-1.dll:

kernel32!DeviceIoControl
api-ms-win-core-handle-l1-1-0.dll:

KernelBase!CloseHandle
api-ms-win-core-path-l1-1-0.dll:

KernelBase!PathCchAddBackslash KernelBase!PathCchSkipRoot KernelBase!PathCchStripPrefix
KernelBase!PathCchStripToRoot
api-ms-win-core-heap-l2-1-0.dll:

KernelBase!LocalAlloc KernelBase!LocalFree
api-ms-win-core-localization-l1-2-1.dll:

KernelBase!FormatMessageW
api-ms-win-core-registry-l1-1-0.dll:

KernelBase!RegCloseKey KernelBase!RegCreateKeyExW KernelBase!RegGetValueW KernelBase!RegOpenKeyExW
KernelBase!RegQueryValueExW KernelBase!RegSetValueExW
api-ms-win-core-file-l2-1-1.dll:

KernelBase!GetFileInformationByHandleEx KernelBase!MoveFileExW KernelBase!OpenFileById

DEVOBJ.dll:

DevObjCreateDeviceInfoList	DevObjDestroyDeviceInfoList	DevObjEnumDeviceInfo
DevObjEnumDeviceInterfaces	DevObjGetClassDevs	DevObjGetDeviceInstanceId
DevObjGetDeviceInterfaceDetail	DevObjGetDeviceProperty	DevObjGetDeviceRegistryProperty
DevObjOpenDevRegKey	DevObjOpenDeviceInfo	DevObjOpenDeviceInterface

mi.dll:

MI_Application_InitializeV1 mi_clientFT_V1

HBAAPI.dll:

HBA_FreeLibrary	HBA_FreeLibrary	HBA_GetAdapterName
HBA_GetNumberOfAdapters	HBA_OpenAdapter	HBA_RefreshAdapterConfiguration
SMHBA_GetAdapterAttributes	SMHBA_GetAdapterPortAttributes	SMHBA_GetNumberOfPorts

VirtDisk.dll:

AttachVirtualDisk DetachVirtualDisk GetStorageDependencyInformation
GetVirtualDiskInformation GetVirtualDiskPhysicalPath OpenVirtualDisk
SXSHARED.dll:

SxTracerDebuggerBreak SxTracerGetThreadContextRetail SxTracerShouldTrackFailure

ntdll.dll:

EtwTraceMessage	NtPowerInformation
NtQuerySystemInformation	NtQueryVolumeInformationFile
RtlAllocateHeap	RtlCaptureStackBackTrace
RtlDeleteElementGenericTableAvl	RtlEnumerateGenericTableAvl
RtlEnumerateGenericTableWithoutSplayingAvl	RtlFreeHeap
RtlGetLastNtStatus	RtlInitializeGenericTableAvl
RtlInsertElementGenericTableAvl	RtlLookupElementGenericTableAvl
RtlNtStatusToDosError	RtlSetThreadErrorMode

bcd.dll:

BcdCloseObject	BcdCloseStore	BcdDeleteElement	BcdDeleteObject
BcdEnumerateElementTypes	BcdEnumerateObjects	BcdGetElementData	BcdGetElementDataWithFlags
BcdOpenObject	BcdOpenSystemStore	BcdSetElementData

api-ms-win-security-base-l1-2-0.dll:

KernelBase!AdjustTokenPrivileges KernelBase!AllocateAndInitializeSid KernelBase!CheckTokenMembership
KernelBase!DuplicateTokenEx KernelBase!FreeSid
api-ms-win-core-heap-l1-2-0.dll:

KernelBase!GetProcessHeap ntdll!RtlAllocateHeap ntdll!RtlFreeHeap
api-ms-win-core-string-l1-1-0.dll:

KernelBase!MultiByteToWideChar KernelBase!WideCharToMultiByte
api-ms-win-core-wow64-l1-1-0.dll:

KernelBase!IsWow64Process
api-ms-win-service-management-l1-1-0.dll:

sechost!CloseServiceHandle sechost!OpenSCManagerW sechost!OpenServiceW sechost!StartServiceW
api-ms-win-service-management-l2-1-0.dll:

sechost!QueryServiceStatusEx
api-ms-win-security-sddl-l1-1-0.dll:

sechost!ConvertStringSecurityDescriptorToSecurityDescriptorW
api-ms-win-core-interlocked-l1-2-0.dll:

ntdll!RtlInitializeSListHead ntdll!RtlInterlockedPopEntrySList ntdll!RtlInterlockedPushEntrySList
api-ms-win-core-processenvironment-l1-2-0.dll:

KernelBase!ExpandEnvironmentStringsW
api-ms-win-eventing-controller-l1-1-0.dll:

sechost!ControlTraceW sechost!EnableTraceEx2 sechost!StartTraceW
api-ms-win-devices-config-l1-1-1.dll:

cfgmgr32!CM_Get_Device_IDW cfgmgr32!CM_Get_Parent
srvcli.dll:

NetShareAdd NetShareDel NetShareEnum
netutils.dll:

NetApiBufferFree
api-ms-win-core-delayload-l1-1-1.dll:

KernelBase!DelayLoadFailureHook KernelBase!ResolveDelayLoadedAPI
api-ms-win-core-debug-l1-1-1.dll:

KernelBase!OutputDebugStringA
api-ms-win-core-memory-l1-1-2.dll:

KernelBase!VirtualAlloc KernelBase!VirtualFree
api-ms-win-core-rtlsupport-l1-2-0.dll:

ntdll!RtlCompareMemory
api-ms-win-core-kernel32-legacy-l1-1-1.dll:

kernel32!SetVolumeMountPointW
CFGMGR32.dll:

CM_Reenumerate_DevNode_Ex
api-ms-win-core-apiquery-l1-1-0.dll:

ntdll!ApiSetQueryApiSetPresence

ntdll!EtwEventActivityIdControl	ntdll!EtwEventRegister	ntdll!EtwEventSetInformation
ntdll!EtwEventUnregister	ntdll!EtwEventWrite	ntdll!EtwEventWriteTransfer

KernelBase!DisableThreadLibraryCalls	KernelBase!FreeLibrary	KernelBase!GetModuleHandleW
KernelBase!GetProcAddress	KernelBase!LoadLibraryExW	KernelBase!LoadStringW

KernelBase!GetComputerNameExW	KernelBase!GetSystemDirectoryW	KernelBase!GetSystemTimeAsFileTime
KernelBase!GetTickCount	KernelBase!GetTickCount64	KernelBase!GetVersionExW

KernelBase!GetLastError	KernelBase!SetUnhandledExceptionFilter	KernelBase!UnhandledExceptionFilter
ntdll!RtlRestoreLastWin32Error

KernelBase!PathCchAddBackslash	KernelBase!PathCchSkipRoot	KernelBase!PathCchStripPrefix
KernelBase!PathCchStripToRoot

KernelBase!RegCloseKey	KernelBase!RegCreateKeyExW	KernelBase!RegGetValueW	KernelBase!RegOpenKeyExW
KernelBase!RegQueryValueExW	KernelBase!RegSetValueExW

AttachVirtualDisk	DetachVirtualDisk	GetStorageDependencyInformation
GetVirtualDiskInformation	GetVirtualDiskPhysicalPath	OpenVirtualDisk

KernelBase!AdjustTokenPrivileges	KernelBase!AllocateAndInitializeSid	KernelBase!CheckTokenMembership
KernelBase!DuplicateTokenEx	KernelBase!FreeSid