pcsvDevice.dll.mui PCSV Proxy Provider for devices 0efb867ecfac525366fa1d85110b207a

File name:	pcsvDevice.dll.mui
Size:	137216 byte
MD5:	0efb867ecfac525366fa1d85110b207a
SHA1:	1dfef61adbc457ffb218a7f58b69e4c572faa83f
SHA256:	10ec33f506f9dca7ccafb22d346890dce907dd5e6e4165fb5d185744fb18a384
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in Thai language and you cannot find a solution, than check answer in English. Table below helps to know how correctly this phrase sounds in English.

id	Thai	English
1	InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.	InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
2	The Caption property is a short textual description (one- line string) of the object.	The Caption property is a short textual description (one- line string) of the object.
3	The Description property provides a textual description of the object.	The Description property provides a textual description of the object.
4	A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.	A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.
5	2.19.0	2.19.0
6	ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema.	ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema.
7	View is an abstract class that provides a common superclass for classes providing de-normalized, aggregate representations of managed resources. The definition of each sub-class will include properties propagated from the the graph of classes that are used to model the resource in the normalized view. The classes may be resource classes or associations. The definition of how a value is propagated (i.e. source class and value transformations) is required to be specified. Sub-classes may be explicitly constrained to be read only. If a sub-class is not constrained as read only, the designers are strongly encouraged to carefully consider the data synchronization and consistencies issues that may result. The ElementView association may be used to find the instances that form the normalized view of the managed resource.	View is an abstract class that provides a common superclass for classes providing de-normalized, aggregate representations of managed resources. The definition of each sub-class will include properties propagated from the the graph of classes that are used to model the resource in the normalized view. The classes may be resource classes or associations. The definition of how a value is propagated (i.e. source class and value transformations) is required to be specified. Sub-classes may be explicitly constrained to be read only. If a sub-class is not constrained as read only, the designers are strongly encouraged to carefully consider the data synchronization and consistencies issues that may result. The ElementView association may be used to find the instances that form the normalized view of the managed resource.
8	2.26.0	2.26.0
9	A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.	A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.
10	The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.	The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.
11	Indicates the current statuses of the element. 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. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future. "In Service" describes an element being configured, maintained, cleaned, or otherwise administered. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. "Stopped" and "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 element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Power Mode" indicates that the element has additional power model information contained in the Associated PowerManagementService association. OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today\'s environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly recommended that providers or instrumentation provide both the Status and OperationalStatus properties. Further, the first value of OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element.	Indicates the current statuses of the element. 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. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future. "In Service" describes an element being configured, maintained, cleaned, or otherwise administered. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. "Stopped" and "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 element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Power Mode" indicates that the element has additional power model information contained in the Associated PowerManagementService association. OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today\'s environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly recommended that providers or instrumentation provide both the Status and OperationalStatus properties. Further, the first value of OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element.
12	Unknown	Unknown
13	Other	Other
14	OK	OK
15	Degraded	Degraded
16	Stressed	Stressed
17	Predictive Failure	Predictive Failure
18	Error	Error
19	Non-Recoverable Error	Non-Recoverable Error
20	Starting	Starting
21	Stopping	Stopping
22	Stopped	Stopped
23	In Service	In Service
24	No Contact	No Contact
25	Lost Communication	Lost Communication
26	Aborted	Aborted
27	Dormant	Dormant
28	Supporting Entity in Error	Supporting Entity in Error
29	Completed	Completed
30	Power Mode	Power Mode
31	DMTF Reserved	DMTF Reserved
32	Vendor Reserved	Vendor Reserved
33	Strings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then 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.	Strings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then 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.
34	A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons: 1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped. 2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. 3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus.	A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons: 1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped. 2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. 3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus.
35	Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined: "Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. "Critical Failure" (25) - The element is non-functional and recovery might not be possible. "Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. "Minor Failure" (15) - All functionality is available but some might be degraded. "Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. "OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. "Unknown" (0) - The implementation cannot report on HealthState at this time. DMTF has reserved the unused portion of the continuum for additional HealthStates in the future.	Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined: "Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. "Critical Failure" (25) - The element is non-functional and recovery might not be possible. "Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. "Minor Failure" (15) - All functionality is available but some might be degraded. "Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. "OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. "Unknown" (0) - The implementation cannot report on HealthState at this time. DMTF has reserved the unused portion of the continuum for additional HealthStates in the future.
36	Degraded/Warning	Degraded/Warning
37	Minor failure	Minor failure
38	Major failure	Major failure
39	Critical failure	Critical failure
40	Non-recoverable error	Non-recoverable error
41	CommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact. A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Communication OK " indicates communication is established with the element, but does not convey any quality of service. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable.	CommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact. A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Communication OK " indicates communication is established with the element, but does not convey any quality of service. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable.
42	Not Available	Not Available
43	Communication OK	Communication OK
44	DetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element. A Null return indicates the implementation (provider) does not implement this property. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK". "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning normally but a failure is predicted in the near future. "Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems.	DetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element. A Null return indicates the implementation (provider) does not implement this property. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK". "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning normally but a failure is predicted in the near future. "Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems.
45	No Additional Information	No Additional Information
46	OperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions. OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Servicing" describes an element being configured, maintained, cleaned, or otherwise administered. "Starting" describes an element being initialized. "Stopping" describes an element being brought to an orderly stop. "Stopped" and "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 element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Migrating" element is being moved between host elements. "Immigrating" element is being moved to new host element. "Emigrating" element is being moved away from host element. "Shutting Down" describes an element being brought to an abrupt stop. "In Test" element is performing test functions. "Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable. "In Service" describes an element that is in service and operational.	OperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions. OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Servicing" describes an element being configured, maintained, cleaned, or otherwise administered. "Starting" describes an element being initialized. "Stopping" describes an element being brought to an orderly stop. "Stopped" and "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 element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Migrating" element is being moved between host elements. "Immigrating" element is being moved to new host element. "Emigrating" element is being moved away from host element. "Shutting Down" describes an element being brought to an abrupt stop. "In Test" element is performing test functions. "Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable. "In Service" describes an element that is in service and operational.
47	Servicing	Servicing
48	Migrating	Migrating
49	Emigrating	Emigrating
50	Immigrating	Immigrating
51	Snapshotting	Snapshotting
52	Shutting Down	Shutting Down
53	In Test	In Test
54	Transitioning	Transitioning
55	PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents. PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "OK" indicates the ManagedElement is functioning normally. "Degraded" indicates the ManagedElement is functioning below normal. "Error" indicates the ManagedElement is in an Error condition.	PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents. PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "OK" indicates the ManagedElement is functioning normally. "Degraded" indicates the ManagedElement is functioning below normal. "Error" indicates the ManagedElement is in an Error condition.
56	CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include: - software components such as application servers, databases, and applications - operating system components such as files, processes, and threads - device components such as disk drives, controllers, processors, and printers - physical components such as chips and cards.	CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include: - software components such as application servers, databases, and applications - operating system components such as files, processes, and threads - device components such as disk drives, controllers, processors, and printers - physical components such as chips and cards.
57	2.22.0	2.22.0
58	CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.	CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.
59	2.6.0	2.6.0
60	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.	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.
61	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. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested.	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. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested.
62	The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval.	The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval.
63	The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.	The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
64	The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.	The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
65	The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once.	The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once.
66	The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.	The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.
67	January	January
68	February	February
69	March	March
70	April	April
71	May	May
72	June	June
73	July	July
74	August	August
75	September	September
76	October	October
77	November	November
78	December	December
79	The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth. When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.	The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth. When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.
80	A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay.	A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay.
81	-Saturday	-Saturday
82	-Friday	-Friday
83	-Thursday	-Thursday
84	-Wednesday	-Wednesday
85	-Tuesday	-Tuesday
86	-Monday	-Monday
87	-Sunday	-Sunday
88	ExactDayOfMonth	ExactDayOfMonth
89	Sunday	Sunday
90	Monday	Monday
91	Tuesday	Tuesday
92	Wednesday	Wednesday
93	Thursday	Thursday
94	Friday	Friday
95	Saturday	Saturday
96	The time interval after midnight when the Job should be processed. For example, 00000000020000.000000:000 indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.	The time interval after midnight when the Job should be processed. For example, 00000000020000.000000:000 indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.
97	This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time".	This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time".
98	Local Time	Local Time
99	UTC Time	UTC Time
100	The time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely.	The time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely.
101	The User who is to be notified upon the Job completion or failure.	The User who is to be notified upon the Job completion or failure.
102	The User that submitted the Job, or the Service or method name that caused the job to be created.	The User that submitted the Job, or the Service or method name that caused the job to be created.
103	Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job.	Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job.
104	The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property. Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.	The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property. Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.
105	Percent	Percent
106	Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property.	Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property.
107	A vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.	A vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
108	A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.	A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
109	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 5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.	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 5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.
110	Do Not Continue	Do Not Continue
111	Continue With Next Job	Continue With Next Job
112	Re-run Job	Re-run Job
113	Run Recovery Job	Run Recovery Job
114	A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").	A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").
115	KillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction. A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.	KillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction. A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.
116	Success	Success
117	Not Supported	Not Supported
118	Timeout	Timeout
119	Failed	Failed
120	Access Denied	Access Denied
121	Not Found	Not Found
122	Vendor Specific	Vendor Specific
123	Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.	Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.
124	A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system.	A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system.
125	2.10.0	2.10.0
126	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.	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.
127	Communications Error	Communications Error
128	Quality of Service Error	Quality of Service Error
129	Software Error	Software Error
130	Hardware Error	Hardware Error
131	Environmental Error	Environmental Error
132	Security Error	Security Error
133	Oversubscription Error	Oversubscription Error
134	Unavailable Resource Error	Unavailable Resource Error
135	Unsupported Operation Error	Unsupported Operation Error
136	A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.	A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.
137	A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.	A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.
138	An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.	An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.
139	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.	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.
140	An array containing the dynamic content of the message.	An array containing the dynamic content of the message.
141	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.	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.
142	Information	Information
143	Minor	Minor
144	Major	Major
145	Critical	Critical
146	Fatal/NonRecoverable	Fatal/NonRecoverable
147	An enumerated value that describes the probable cause of the error.	An enumerated value that describes the probable cause of the error.
148	Adapter/Card Error	Adapter/Card Error
149	Application Subsystem Failure	Application Subsystem Failure
150	Bandwidth Reduced	Bandwidth Reduced
151	Connection Establishment Error	Connection Establishment Error
152	Communications Protocol Error	Communications Protocol Error
153	Communications Subsystem Failure	Communications Subsystem Failure
154	Configuration/Customization Error	Configuration/Customization Error
155	Congestion	Congestion
156	Corrupt Data	Corrupt Data
157	CPU Cycles Limit Exceeded	CPU Cycles Limit Exceeded
158	Dataset/Modem Error	Dataset/Modem Error
159	Degraded Signal	Degraded Signal
160	DTE-DCE Interface Error	DTE-DCE Interface Error
161	Enclosure Door Open	Enclosure Door Open
162	Equipment Malfunction	Equipment Malfunction
163	Excessive Vibration	Excessive Vibration
164	File Format Error	File Format Error
165	Fire Detected	Fire Detected
166	Flood Detected	Flood Detected
167	Framing Error	Framing Error
168	HVAC Problem	HVAC Problem
169	Humidity Unacceptable	Humidity Unacceptable
170	I/O Device Error	I/O Device Error
171	Input Device Error	Input Device Error
172	LAN Error	LAN Error
173	Non-Toxic Leak Detected	Non-Toxic Leak Detected
174	Local Node Transmission Error	Local Node Transmission Error
175	Loss of Frame	Loss of Frame
176	Loss of Signal	Loss of Signal
177	Material Supply Exhausted	Material Supply Exhausted
178	Multiplexer Problem	Multiplexer Problem
179	Out of Memory	Out of Memory
180	Output Device Error	Output Device Error
181	Performance Degraded	Performance Degraded
182	Power Problem	Power Problem
183	Pressure Unacceptable	Pressure Unacceptable
184	Processor Problem (Internal Machine Error)	Processor Problem (Internal Machine Error)
185	Pump Failure	Pump Failure
186	Queue Size Exceeded	Queue Size Exceeded
187	Receive Failure	Receive Failure
188	Receiver Failure	Receiver Failure
189	Remote Node Transmission Error	Remote Node Transmission Error
190	Resource at or Nearing Capacity	Resource at or Nearing Capacity
191	Response Time Excessive	Response Time Excessive
192	Retransmission Rate Excessive	Retransmission Rate Excessive
193	Software Program Abnormally Terminated	Software Program Abnormally Terminated
194	Software Program Error (Incorrect Results)	Software Program Error (Incorrect Results)
195	Storage Capacity Problem	Storage Capacity Problem
196	Temperature Unacceptable	Temperature Unacceptable
197	Threshold Crossed	Threshold Crossed
198	Timing Problem	Timing Problem
199	Toxic Leak Detected	Toxic Leak Detected
200	Transmit Failure	Transmit Failure
201	Transmitter Failure	Transmitter Failure
202	Underlying Resource Unavailable	Underlying Resource Unavailable
203	Version Mismatch	Version Mismatch
204	Previous Alert Cleared	Previous Alert Cleared
205	Login Attempts Failed	Login Attempts Failed
206	Software Virus Detected	Software Virus Detected
207	Hardware Security Breached	Hardware Security Breached
208	Denial of Service Detected	Denial of Service Detected
209	Security Credential Mismatch	Security Credential Mismatch
210	Unauthorized Access	Unauthorized Access
211	Alarm Received	Alarm Received
212	Loss of Pointer	Loss of Pointer
213	Payload Mismatch	Payload Mismatch
214	Transmission Error	Transmission Error
215	Excessive Error Rate	Excessive Error Rate
216	Trace Problem	Trace Problem
217	Element Unavailable	Element Unavailable
218	Element Missing	Element Missing
219	Loss of Multi Frame	Loss of Multi Frame
220	Broadcast Channel Failure	Broadcast Channel Failure
221	Invalid Message Received	Invalid Message Received
222	Routing Failure	Routing Failure
223	Backplane Failure	Backplane Failure
224	Identifier Duplication	Identifier Duplication
225	Protection Path Failure	Protection Path Failure
226	Sync Loss or Mismatch	Sync Loss or Mismatch
227	Terminal Problem	Terminal Problem
228	Real Time Clock Failure	Real Time Clock Failure
229	Antenna Failure	Antenna Failure
230	Battery Charging Failure	Battery Charging Failure
231	Disk Failure	Disk Failure
232	Frequency Hopping Failure	Frequency Hopping Failure
233	Loss of Redundancy	Loss of Redundancy
234	Power Supply Failure	Power Supply Failure
235	Signal Quality Problem	Signal Quality Problem
236	Battery Discharging	Battery Discharging
237	Battery Failure	Battery Failure
238	Commercial Power Problem	Commercial Power Problem
239	Fan Failure	Fan Failure
240	Engine Failure	Engine Failure
241	Sensor Failure	Sensor Failure
242	Fuse Failure	Fuse Failure
243	Generator Failure	Generator Failure
244	Low Battery	Low Battery
245	Low Fuel	Low Fuel
246	Low Water	Low Water
247	Explosive Gas	Explosive Gas
248	High Winds	High Winds
249	Ice Buildup	Ice Buildup
250	Smoke	Smoke
251	Memory Mismatch	Memory Mismatch
252	Out of CPU Cycles	Out of CPU Cycles
253	Software Environment Problem	Software Environment Problem
254	Software Download Failure	Software Download Failure
255	Element Reinitialized	Element Reinitialized
256	Logging Problems	Logging Problems
257	Leak Detected	Leak Detected
258	Protection Mechanism Failure	Protection Mechanism Failure
259	Protecting Resource Failure	Protecting Resource Failure
260	Database Inconsistency	Database Inconsistency
261	Authentication Failure	Authentication Failure
262	Breach of Confidentiality	Breach of Confidentiality
263	Cable Tamper	Cable Tamper
264	Delayed Information	Delayed Information
265	Duplicate Information	Duplicate Information
266	Information Missing	Information Missing
267	Information Modification	Information Modification
268	Information Out of Sequence	Information Out of Sequence
269	Key Expired	Key Expired
270	Non-Repudiation Failure	Non-Repudiation Failure
271	Out of Hours Activity	Out of Hours Activity
272	Out of Service	Out of Service
273	Procedural Error	Procedural Error
274	Unexpected Information	Unexpected Information
275	A free-form string describing the probable cause of the error.	A free-form string describing the probable cause of the error.
276	A free-form string describing recommended actions to take to resolve the error.	A free-form string describing recommended actions to take to resolve the error.
277	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.	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.
278	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.	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.
279	CIMObjectPath	CIMObjectPath
280	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.	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.
281	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.	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.
282	CIM_ERR_FAILED	CIM_ERR_FAILED
283	CIM_ERR_ACCESS_DENIED	CIM_ERR_ACCESS_DENIED
284	CIM_ERR_INVALID_NAMESPACE	CIM_ERR_INVALID_NAMESPACE
285	CIM_ERR_INVALID_PARAMETER	CIM_ERR_INVALID_PARAMETER
286	CIM_ERR_INVALID_CLASS	CIM_ERR_INVALID_CLASS
287	CIM_ERR_NOT_FOUND	CIM_ERR_NOT_FOUND
288	CIM_ERR_NOT_SUPPORTED	CIM_ERR_NOT_SUPPORTED
289	CIM_ERR_CLASS_HAS_CHILDREN	CIM_ERR_CLASS_HAS_CHILDREN
290	CIM_ERR_CLASS_HAS_INSTANCES	CIM_ERR_CLASS_HAS_INSTANCES
291	CIM_ERR_INVALID_SUPERCLASS	CIM_ERR_INVALID_SUPERCLASS
292	CIM_ERR_ALREADY_EXISTS	CIM_ERR_ALREADY_EXISTS
293	CIM_ERR_NO_SUCH_PROPERTY	CIM_ERR_NO_SUCH_PROPERTY
294	CIM_ERR_TYPE_MISMATCH	CIM_ERR_TYPE_MISMATCH
295	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
296	CIM_ERR_INVALID_QUERY	CIM_ERR_INVALID_QUERY
297	CIM_ERR_METHOD_NOT_AVAILABLE	CIM_ERR_METHOD_NOT_AVAILABLE
298	CIM_ERR_METHOD_NOT_FOUND	CIM_ERR_METHOD_NOT_FOUND
299	CIM_ERR_UNEXPECTED_RESPONSE	CIM_ERR_UNEXPECTED_RESPONSE
300	CIM_ERR_INVALID_RESPONSE_DESTINATION	CIM_ERR_INVALID_RESPONSE_DESTINATION
301	CIM_ERR_NAMESPACE_NOT_EMPTY	CIM_ERR_NAMESPACE_NOT_EMPTY
302	CIM_ERR_INVALID_ENUMERATION_CONTEXT	CIM_ERR_INVALID_ENUMERATION_CONTEXT
303	CIM_ERR_INVALID_OPERATION_TIMEOUT	CIM_ERR_INVALID_OPERATION_TIMEOUT
304	CIM_ERR_PULL_HAS_BEEN_ABANDONED	CIM_ERR_PULL_HAS_BEEN_ABANDONED
305	CIM_ERR_PULL_CANNOT_BE_ABANDONED	CIM_ERR_PULL_CANNOT_BE_ABANDONED
306	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
307	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
308	CIM_ERR_SERVER_LIMITS_EXCEEDED	CIM_ERR_SERVER_LIMITS_EXCEEDED
309	CIM_ERR_SERVER_IS_SHUTTING_DOWN	CIM_ERR_SERVER_IS_SHUTTING_DOWN
310	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
311	A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.	A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.
312	2.22.1	2.22.1
313	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.	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.
314	Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following \'preferred\' algorithm: : Where and are separated by a colon \':\', and where must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID, or that is a registered ID that is assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. If the above \'preferred\' algorithm is not used, the defining entity must assure that the resulting InstanceID is not re-used across any InstanceIDs produced by this or other providers for the NameSpace of this instance. For DMTF defined instances, the \'preferred\' algorithm must be used with the set to \'CIM\'.	Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following \'preferred\' algorithm: : Where and are separated by a colon \':\', and where must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID, or that is a registered ID that is assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. If the above \'preferred\' algorithm is not used, the defining entity must assure that the resulting InstanceID is not re-used across any InstanceIDs produced by this or other providers for the NameSpace of this instance. For DMTF defined instances, the \'preferred\' algorithm must be used with the set to \'CIM\'.
315	The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.)	The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.)
316	JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states: New (2) indicates that the job has never been started. Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state. Running (4) indicates that the Job is running. Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner. Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state. Completed (7) indicates that the job has completed normally. Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job. Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources. Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects. Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both. Query pending (12) waiting for a client to resolve a query	JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states: New (2) indicates that the job has never been started. Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state. Running (4) indicates that the Job is running. Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner. Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state. Completed (7) indicates that the job has completed normally. Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job. Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources. Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects. Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both. Query pending (12) waiting for a client to resolve a query
317	New	New
318	Running	Running
319	Suspended	Suspended
320	Terminated	Terminated
321	Killed	Killed
322	Exception	Exception
323	Service	Service
324	Query Pending	Query Pending
325	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, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.	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, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.
326	The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property. The default is five minutes.	The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property. The default is five minutes.
327	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. If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.	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. If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.
328	Completed with No Error	Completed with No Error
329	Unknown/Unspecified Error	Unknown/Unspecified Error
330	Can NOT complete within Timeout Period	Can NOT complete within Timeout Period
331	Invalid Parameter	Invalid Parameter
332	In Use	In Use
333	Method Parameters Checked - Transition Started	Method Parameters Checked - Transition Started
334	Invalid State Transition	Invalid State Transition
335	Use of Timeout Parameter Not Supported	Use of Timeout Parameter Not Supported
336	Busy	Busy
337	Method Reserved	Method Reserved
338	RequestStateChange changes the state of a job. The possible values are as follows: Start (2) changes the state to \'Running\'. Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.) Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner. Kill (5) terminates the job immediately with no requirement to save data or preserve the state. Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.	RequestStateChange changes the state of a job. The possible values are as follows: Start (2) changes the state to \'Running\'. Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.) Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner. Kill (5) terminates the job immediately with no requirement to save data or preserve the state. Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.
339	Start	Start
340	Suspend	Suspend
341	Terminate	Terminate
342	Kill	Kill
343	A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition. If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.	A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition. If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.
344	When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned.	When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned.
345	Unspecified Error	Unspecified Error
346	If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned.	If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned.
347	A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.	A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.
348	InstanceID is the property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace.	InstanceID is the property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace.
349	This property corresponds to the EnabledState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.EnabledState for details on EnabledState.	This property corresponds to the EnabledState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.EnabledState for details on EnabledState.
350	Enabled	Enabled
351	Disabled	Disabled
352	Not Applicable	Not Applicable
353	Enabled but Offline	Enabled but Offline
354	Deferred	Deferred
355	Quiesce	Quiesce
356	This property corresponds to the RequestedState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.RequestedState for details on RequestedState.	This property corresponds to the RequestedState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.RequestedState for details on RequestedState.
357	Shut Down	Shut Down
358	No Change	No Change
359	Offline	Offline
360	Test	Test
361	Reboot	Reboot
362	Reset	Reset
363	This property corresponds to the OperationalStatus property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.OperationalStatus Description for details.	This property corresponds to the OperationalStatus property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.OperationalStatus Description for details.
364	Relocating	Relocating
365	This property corresponds to the HealthState property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.HealthState for details.	This property corresponds to the HealthState property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.HealthState for details.
366	This property indicates the availability of the FRU Information on this physical computer system. See CIM_PhysicalAssetCapabilities.FRUInfoSupported for details.	This property indicates the availability of the FRU Information on this physical computer system. See CIM_PhysicalAssetCapabilities.FRUInfoSupported for details.
367	This property corresponds to CIM_PhysicalFrame.Tag. See CIM_PhysicalFrame.Tag for details.	This property corresponds to CIM_PhysicalFrame.Tag. See CIM_PhysicalFrame.Tag for details.
368	This property corresponds to CIM_PhysicalFrame.Manufacturer. See CIM_PhysicalFrame.Manufacturer for details.	This property corresponds to CIM_PhysicalFrame.Manufacturer. See CIM_PhysicalFrame.Manufacturer for details.
369	This property corresponds to CIM_PhysicalFrame.Model. See CIM_PhysicalFrame.Model for details.	This property corresponds to CIM_PhysicalFrame.Model. See CIM_PhysicalFrame.Model for details.
370	This property corresponds to CIM_PhysicalFrame.SKU. See CIM_PhysicalFrame.SKU for details.	This property corresponds to CIM_PhysicalFrame.SKU. See CIM_PhysicalFrame.SKU for details.
371	This property corresponds to CIM_PhysicalFrame.SerialNumber. See CIM_PhysicalFrame.SerialNumber for details.	This property corresponds to CIM_PhysicalFrame.SerialNumber. See CIM_PhysicalFrame.SerialNumber for details.
372	This property corresponds to CIM_PhysicalFrame.Version. See CIM_PhysicalFrame.Version for details.	This property corresponds to CIM_PhysicalFrame.Version. See CIM_PhysicalFrame.Version for details.
373	This property corresponds to CIM_PhysicalFrame.PartNumber. See CIM_PhysicalFrame.PartNumber for details.	This property corresponds to CIM_PhysicalFrame.PartNumber. See CIM_PhysicalFrame.PartNumber for details.
374	This property corresponds to PowerUtilizationModesSupported property of CIM_PowerUtilizationManagementCapabilities. See CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported for details.	This property corresponds to PowerUtilizationModesSupported property of CIM_PowerUtilizationManagementCapabilities. See CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported for details.
375	Dynamic	Dynamic
376	Static	Static
377	This property corresponds to the PowerUtilizationMode of the CIM_PowerUtilizationManagementService. See CIM_PowerUtilizationManagementService.PowerUtilizationMode for details.	This property corresponds to the PowerUtilizationMode of the CIM_PowerUtilizationManagementService. See CIM_PowerUtilizationManagementService.PowerUtilizationMode for details.
378	None	None
379	This property corresponds to CIM_PowerAllocationSettingData.Limit. See CIM_PowerAllocationSettingData.Limit for details.	This property corresponds to CIM_PowerAllocationSettingData.Limit. See CIM_PowerAllocationSettingData.Limit for details.
380	User-friendly names of the numeric sensors on the computer system. See CIM_NumericSensor.ElementName for details.	User-friendly names of the numeric sensors on the computer system. See CIM_NumericSensor.ElementName for details.
381	States of numeric sensors. See CIM_NumericSensor.EnabledState for details.	States of numeric sensors. See CIM_NumericSensor.EnabledState for details.
382	Health states of numeric sensors. See CIM_NumericSensor.HealthState for details.	Health states of numeric sensors. See CIM_NumericSensor.HealthState for details.
383	Current states of numeric sensors. See CIM_NumericSensor.CurrentState for details.	Current states of numeric sensors. See CIM_NumericSensor.CurrentState for details.
384	Primary statuses of numeric sensors. See CIM_NumericSensor.PrimaryStatus for details.	Primary statuses of numeric sensors. See CIM_NumericSensor.PrimaryStatus for details.
385	Base units of the values returned by the numeric sensors. See CIM_NumericSensor.BaseUnits for details.	Base units of the values returned by the numeric sensors. See CIM_NumericSensor.BaseUnits for details.
386	Degrees C	Degrees C
387	Degrees F	Degrees F
388	Degrees K	Degrees K
389	Volts	Volts
390	Amps	Amps
391	Watts	Watts
392	Joules	Joules
393	Coulombs	Coulombs
394	VA	VA
395	Nits	Nits
396	Lumens	Lumens
397	Lux	Lux
398	Candelas	Candelas
399	kPa	kPa
400	PSI	PSI
401	Newtons	Newtons
402	CFM	CFM
403	RPM	RPM
404	Hertz	Hertz
405	Seconds	Seconds
406	Minutes	Minutes
407	Hours	Hours
408	Days	Days
409	Weeks	Weeks
410	Mils	Mils
411	Inches	Inches
412	Feet	Feet
413	Cubic Inches	Cubic Inches
414	Cubic Feet	Cubic Feet
415	Meters	Meters
416	Cubic Centimeters	Cubic Centimeters
417	Cubic Meters	Cubic Meters
418	Liters	Liters
419	Fluid Ounces	Fluid Ounces
420	Radians	Radians
421	Steradians	Steradians
422	Revolutions	Revolutions
423	Cycles	Cycles
424	Gravities	Gravities
425	Ounces	Ounces
426	Pounds	Pounds
427	Foot-Pounds	Foot-Pounds
428	Ounce-Inches	Ounce-Inches
429	Gauss	Gauss
430	Gilberts	Gilberts
431	Henries	Henries
432	Farads	Farads
433	Ohms	Ohms
434	Siemens	Siemens
435	Moles	Moles
436	Becquerels	Becquerels
437	PPM (parts/million)	PPM (parts/million)
438	Decibels	Decibels
439	DbA	DbA
440	DbC	DbC
441	Grays	Grays
442	Sieverts	Sieverts
443	Color Temperature Degrees K	Color Temperature Degrees K
444	Bits	Bits
445	Bytes	Bytes
446	Words (data)	Words (data)
447	DoubleWords	DoubleWords
448	QuadWords	QuadWords
449	Percentage	Percentage
450	Pascals	Pascals
451	Unit modifiers for the values returned by the numeric sensors. See CIM_NumericSensor.UnitModifier description for details.	Unit modifiers for the values returned by the numeric sensors. See CIM_NumericSensor.UnitModifier description for details.
452	See CIM_NumericSensor.RateUnits for details.	See CIM_NumericSensor.RateUnits for details.
453	Per MicroSecond	Per MicroSecond
454	Per MilliSecond	Per MilliSecond
455	Per Second	Per Second
456	Per Minute	Per Minute
457	Per Hour	Per Hour
458	Per Day	Per Day
459	Per Week	Per Week
460	Per Month	Per Month
461	Per Year	Per Year
462	See CIM_NumericSensor.CurrentReading for details.	See CIM_NumericSensor.CurrentReading for details.
463	See CIM_NumericSensor.SensorType for details.	See CIM_NumericSensor.SensorType for details.
464	Temperature	Temperature
465	Voltage	Voltage
466	Current	Current
467	Tachometer	Tachometer
468	Counter	Counter
469	Switch	Switch
470	Lock	Lock
471	Humidity	Humidity
472	Smoke Detection	Smoke Detection
473	Presence	Presence
474	Air Flow	Air Flow
475	Power Consumption	Power Consumption
476	Power Production	Power Production
477	Pressure	Pressure
478	See CIM_NumericSensor.OtherSensorTypeDescription for details.	See CIM_NumericSensor.OtherSensorTypeDescription for details.
479	See CIM_NumericSensor.UpperThresholdNonCritical for details.	See CIM_NumericSensor.UpperThresholdNonCritical for details.
480	See CIM_NumericSensor.UpperThresholdCritical description for details.	See CIM_NumericSensor.UpperThresholdCritical description for details.
481	See CIM_NumericSensor.UpperThresholdFatal for details.	See CIM_NumericSensor.UpperThresholdFatal for details.
482	This property represents the identifiers for the underlying logs on this physical computer system. See CIM_RecordLog.InstanceID for details.	This property represents the identifiers for the underlying logs on this physical computer system. See CIM_RecordLog.InstanceID for details.
483	See CIM_RecordLog.MaxNumberOfRecords for details.	See CIM_RecordLog.MaxNumberOfRecords for details.
484	See CIM_RecordLog.CurrentNumberOfRecords for details.	See CIM_RecordLog.CurrentNumberOfRecords for details.
485	See CIM_RecordLog.OverWritePolicy for details.	See CIM_RecordLog.OverWritePolicy for details.
486	Wraps When Full	Wraps When Full
487	Never Overwrites	Never Overwrites
488	See CIM_RecordLog.LogState for details.	See CIM_RecordLog.LogState for details.
489	Normal	Normal
490	Erasing	Erasing
491	Strings identifying the boot sources on this physical computer system. See CIM_BootSourceSetting.StructuredBootString description for details.	Strings identifying the boot sources on this physical computer system. See CIM_BootSourceSetting.StructuredBootString description for details.
492	An array of elements identifying the boot order of the persistent boot configuration that shall be used during the next boot of the computer system, unless the OneTimeBootSource for the next boot is specified. The value of each element in this array is an index referencing an element in the array of StructuredBootString.	An array of elements identifying the boot order of the persistent boot configuration that shall be used during the next boot of the computer system, unless the OneTimeBootSource for the next boot is specified. The value of each element in this array is an index referencing an element in the array of StructuredBootString.
493	This property identifies the boot source that is used for the next one-time boot. The value of this property is an index referencing an element in the array of StructuredBootString.	This property identifies the boot source that is used for the next one-time boot. The value of this property is an index referencing an element in the array of StructuredBootString.
494	This property identifies the number of processors on this physical computer system.	This property identifies the number of processors on this physical computer system.
495	See CIM_ProcessorCapabilities.NumberOfProcessorCores for details.	See CIM_ProcessorCapabilities.NumberOfProcessorCores for details.
496	See CIM_ProcessorCapabilities.NumberOfProcessorThreads for details.	See CIM_ProcessorCapabilities.NumberOfProcessorThreads for details.
497	See CIM_Processor.Family for details.	See CIM_Processor.Family for details.
498	See CIM_Processor.MaxClockSpeed for details.	See CIM_Processor.MaxClockSpeed for details.
499	See CIM_Memory.BlockSize for details.	See CIM_Memory.BlockSize for details.
500	See CIM_Memory.NumberOfBlocks for details.	See CIM_Memory.NumberOfBlocks for details.
501	See CIM_Memory.ConsumableBlocks for details.	See CIM_Memory.ConsumableBlocks for details.
502	The major number component of the current BIOS version information.	The major number component of the current BIOS version information.
503	The minor number component of the current BIOS version information.	The minor number component of the current BIOS version information.
504	The revision number component of the current BIOS version information.	The revision number component of the current BIOS version information.
505	The build number component of the current BIOS version information.	The build number component of the current BIOS version information.
506	The major number component of the version information for the current management firmware on this physical computer system.	The major number component of the version information for the current management firmware on this physical computer system.
507	The minor number component of the version information for the current management firmware on this physical computer system.	The minor number component of the version information for the current management firmware on this physical computer system.
508	The revision number component of the version information for the current management firmware on this physical computer system.	The revision number component of the version information for the current management firmware on this physical computer system.
509	The build number component of the version information for the current management firmware on this physical computer system.	The build number component of the version information for the current management firmware on this physical computer system.
510	The user-friendly name for the current management firmware on this physical computer system.	The user-friendly name for the current management firmware on this physical computer system.
511	The version string for the current management firmware on this physical computer system.	The version string for the current management firmware on this physical computer system.
512	Type information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.OSType for details.	Type information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.OSType for details.
513	Version information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.Version for details.	Version information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.Version for details.
514	EnabledState of the current or last running operating system on this physcial computer system.	EnabledState of the current or last running operating system on this physcial computer system.
515	The BIOS version information in string format.	The BIOS version information in string format.
516	See CIM_ComputerSystem.Dedicated for details.	See CIM_ComputerSystem.Dedicated for details.
517	Not Dedicated	Not Dedicated
518	Storage	Storage
519	Router	Router
520	Layer 3 Switch	Layer 3 Switch
521	Central Office Switch	Central Office Switch
522	Hub	Hub
523	Access Server	Access Server
524	Firewall	Firewall
525	Print	Print
526	I/O	I/O
527	Web Caching	Web Caching
528	Management	Management
529	Block Server	Block Server
530	File Server	File Server
531	Mobile User Device	Mobile User Device
532	Repeater	Repeater
533	Bridge/Extender	Bridge/Extender
534	Gateway	Gateway
535	Storage Virtualizer	Storage Virtualizer
536	Media Library	Media Library
537	ExtenderNode	ExtenderNode
538	NAS Head	NAS Head
539	Self-contained NAS	Self-contained NAS
540	UPS	UPS
541	IP Phone	IP Phone
542	Management Controller	Management Controller
543	Chassis Manager	Chassis Manager
544	Host-based RAID controller	Host-based RAID controller
545	Storage Device Enclosure	Storage Device Enclosure
546	Desktop	Desktop
547	Laptop	Laptop
548	Virtual Tape Library	Virtual Tape Library
549	Virtual Library System	Virtual Library System
550	Network PC/Thin Client	Network PC/Thin Client
551	FC Switch	FC Switch
552	Ethernet Switch	Ethernet Switch
553	See CIM_System.IdentifyingDescriptions for details.	See CIM_System.IdentifyingDescriptions for details.
554	See CIM_ComputerSystem.OtherDedicatedDescriptions for details.	See CIM_ComputerSystem.OtherDedicatedDescriptions for details.
555	See CIM_System.OtherIdentifyingInfo for details.	See CIM_System.OtherIdentifyingInfo for details.
556	See CIM_Processor.CurrentClockSpeed for details.	See CIM_Processor.CurrentClockSpeed for details.
557	See CIM_Sensor.SensorContext for details.	See CIM_Sensor.SensorContext for details.
558	See CIM_NumericSensor.LowerThresholdNonCritical for details.	See CIM_NumericSensor.LowerThresholdNonCritical for details.
559	See CIM_NumericSensor.LowerThresholdCritical description for details.	See CIM_NumericSensor.LowerThresholdCritical description for details.
560	See CIM_NumericSensor.LowerThresholdFatal description for details.	See CIM_NumericSensor.LowerThresholdFatal description for details.
561	An extrinsic method for changing the state of this physical computer system. Requests that the state of the element be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the EnabledState and RequestedState will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost. A return code of 0 shall indicate the state change was successfully initiated. A return code of 1 shall indicate that the method is not supported. A return code of 2 shall indicate that the method failed. A return code of 4096 shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.	An extrinsic method for changing the state of this physical computer system. Requests that the state of the element be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the EnabledState and RequestedState will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost. A return code of 0 shall indicate the state change was successfully initiated. A return code of 1 shall indicate that the method is not supported. A return code of 2 shall indicate that the method failed. A return code of 4096 shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
562	Job Started	Job Started
563	See CIM_ComputerSystem.RequestedStateChange.RequestedState for details.	See CIM_ComputerSystem.RequestedStateChange.RequestedState for details.
564	Defer	Defer
565	May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.	May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.
566	See CIM_ComputerSystem.TimeoutPeriod for details.	See CIM_ComputerSystem.TimeoutPeriod for details.
567	An extrinsic method for clearing a log on this physical computer system. Requests that the Log be cleared of all entries. The return value shall be 0 if the request was successfully executed, 1 if the request is not supported, and 2 if an error occurred. A return code of 4096 shall indicate the request to clear log was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.	An extrinsic method for clearing a log on this physical computer system. Requests that the Log be cleared of all entries. The return value shall be 0 if the request was successfully executed, 1 if the request is not supported, and 2 if an error occurred. A return code of 4096 shall indicate the request to clear log was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
568	Idenfier for the log that is requested to be cleared.	Idenfier for the log that is requested to be cleared.
569	An extrinsic method for installing software on this physical computer system. If 0 is returned, the function completed successfully and no ConcreteJob instance was required. The return value shall be 1 if the request is not supported, and 2 if an error occurred. If 4096 is returned, a ConcreteJob will be started to to perform the install. The Job\'s reference will be returned in the output parameter Job.	An extrinsic method for installing software on this physical computer system. If 0 is returned, the function completed successfully and no ConcreteJob instance was required. The return value shall be 1 if the request is not supported, and 2 if an error occurred. If 4096 is returned, a ConcreteJob will be started to to perform the install. The Job\'s reference will be returned in the output parameter Job.
570	Reference to the job (may be null if job completed).	Reference to the job (may be null if job completed).
571	See CIM_SoftwareIdentity.Classifications for details.	See CIM_SoftwareIdentity.Classifications for details.
572	Firmware	Firmware
573	BIOS/FCode	BIOS/FCode
574	Software Bundle	Software Bundle
575	Management Firmware	Management Firmware
576	See CIM_SoftwareInstallationService.InstallFromURI.URI for details.	See CIM_SoftwareInstallationService.InstallFromURI.URI for details.
577	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptions for details.	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptions for details.
578	Defer target/system reset	Defer target/system reset
579	Force installation	Force installation
580	Install	Install
581	Update	Update
582	Repair	Repair
583	Password	Password
584	Uninstall	Uninstall
585	Log	Log
586	SilentMode	SilentMode
587	AdministrativeMode	AdministrativeMode
588	ScheduleInstallAt	ScheduleInstallAt
589	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues for details.	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues for details.
590	This method is used to change the order of boot sources for the persistent boot configuration specified by the property CIM_PhysicalComputerSystemView.PersistentBootConfigOrder.	This method is used to change the order of boot sources for the persistent boot configuration specified by the property CIM_PhysicalComputerSystemView.PersistentBootConfigOrder.
591	An ordered array of strings representing the order of boot sources.	An ordered array of strings representing the order of boot sources.
592	Reference to the job spawned if the operation continues after the method returns. (May be null if the task is completed).	Reference to the job spawned if the operation continues after the method returns. (May be null if the task is completed).
593	This method is used to set the one time boot source for the next boot on this computer system.	This method is used to set the one time boot source for the next boot on this computer system.
594	A string representing the boot source for next boot.	A string representing the boot source for next boot.
595	This class defines a view class for a physical computer system.	This class defines a view class for a physical computer system.
596	2.35.0	2.35.0
597	A string describing the data structure of the information in the property, RecordData. If the RecordFormat string is , RecordData should be interpreted as a free-form string. To describe the data structure of RecordData, the RecordFormat string should be constructed as follows: - The first character is a delimiter character and is used to parse the remainder of the string into sub-strings. - Each sub-string is separated by the delimiter character and should be in the form of a CIM property declaration (i.e., datatype and property name). This set of declarations may be used to interpret the similarly delimited RecordData property. For example, using a \'*\' delimiter, RecordFormat = "*string ThisDay*uint32 ThisYear*datetime SomeTime" may be used to interpret: RecordData = "*This is Friday*2002*20020807141000.000000-300".	A string describing the data structure of the information in the property, RecordData. If the RecordFormat string is , RecordData should be interpreted as a free-form string. To describe the data structure of RecordData, the RecordFormat string should be constructed as follows: - The first character is a delimiter character and is used to parse the remainder of the string into sub-strings. - Each sub-string is separated by the delimiter character and should be in the form of a CIM property declaration (i.e., datatype and property name). This set of declarations may be used to interpret the similarly delimited RecordData property. For example, using a \'*\' delimiter, RecordFormat = "*string ThisDay*uint32 ThisYear*datetime SomeTime" may be used to interpret: RecordData = "*This is Friday*2002*20020807141000.000000-300".
598	A string containing LogRecord data. If the corresponding RecordFormat property is , or cannot be parsed according to the recommended format, RecordData should be interpreted as a free-form string. If the RecordFormat property contains parseable format information (as recommended in the RecordFormat Description qualifier), the RecordData string SHOULD be parsed in accordance with this format. In this case, RecordData SHOULD begin with the delimiter character and this character SHOULD be used to separate substrings in the manner described. The RecordData string can then be parsed by the data consumer and appropriately typed.	A string containing LogRecord data. If the corresponding RecordFormat property is , or cannot be parsed according to the recommended format, RecordData should be interpreted as a free-form string. If the RecordFormat property contains parseable format information (as recommended in the RecordFormat Description qualifier), the RecordData string SHOULD be parsed in accordance with this format. In this case, RecordData SHOULD begin with the delimiter character and this character SHOULD be used to separate substrings in the manner described. The RecordData string can then be parsed by the data consumer and appropriately typed.
599	A locale indicates a particular geographical, political, or cultural region. The Locale specifies the language used in creating the RecordForLog data. If the Locale property is empty, it is assumed that the default locale is en_US (English). The locale string consists of three sub-strings, separated by underscores: - The first sub-string is the language code, as specified in ISO639. - The second sub-string is the country code, as specified in ISO3166. - The third sub-string is a variant, which is vendor specific. For example, US English appears as: "en_US_WIN", where the "WIN" variant would specify a Windows browser-specific collation (if one exists). Since the variant is not standardized, it is not commonly used and generally is limited to easily recognizable values ("WIN", "UNIX", "EURO", etc.) used in standard environments. The language and country codes are required; the variant may be empty.	A locale indicates a particular geographical, political, or cultural region. The Locale specifies the language used in creating the RecordForLog data. If the Locale property is empty, it is assumed that the default locale is en_US (English). The locale string consists of three sub-strings, separated by underscores: - The first sub-string is the language code, as specified in ISO639. - The second sub-string is the country code, as specified in ISO3166. - The third sub-string is a variant, which is vendor specific. For example, US English appears as: "en_US_WIN", where the "WIN" variant would specify a Windows browser-specific collation (if one exists). Since the variant is not standardized, it is not commonly used and generally is limited to easily recognizable values ("WIN", "UNIX", "EURO", etc.) used in standard environments. The language and country codes are required; the variant may be empty.
600	An enumerated value that describes the severity of the Indication from the notifier\'s point of view: 1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property. 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 Indication is purely informational or its severity is simply unknown.	An enumerated value that describes the severity of the Indication from the notifier\'s point of view: 1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property. 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 Indication is purely informational or its severity is simply unknown.
601	The RecordForLog class is used to instantiate records to be aggregated to a Log.	The RecordForLog class is used to instantiate records to be aggregated to a Log.
602	2.25.0	2.25.0
603	The scoping Log\'s CreationClassName.	The scoping Log\'s CreationClassName.
604	The scoping Log\'s Name.	The scoping Log\'s Name.
605	CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified.	CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified.
606	RecordID, with the MessageTimestamp property, serve to uniquely identify the LogRecord within a MessageLog. Note that this property is different than the RecordNumber parameters of the MessageLog methods. The latter are ordinal values only, useful to track position when iterating through a Log. On the other hand, RecordID is truly an identifier for an instance of LogRecord. It may be set to the record\'s ordinal position, but this is not required.	RecordID, with the MessageTimestamp property, serve to uniquely identify the LogRecord within a MessageLog. Note that this property is different than the RecordNumber parameters of the MessageLog methods. The latter are ordinal values only, useful to track position when iterating through a Log. On the other hand, RecordID is truly an identifier for an instance of LogRecord. It may be set to the record\'s ordinal position, but this is not required.
607	A LogRecord\'s key structure includes a timestamp for the entry. If the timestamp for the entry is unknown, the value 99990101000000.000000+000 SHOULD be used.	A LogRecord\'s key structure includes a timestamp for the entry. If the timestamp for the entry is unknown, the value 99990101000000.000000+000 SHOULD be used.
608	A free-form string describing the LogRecord\'s data structure.	A free-form string describing the LogRecord\'s data structure.
609	The LogRecord object can describe the definitional format for entries in a MessageLog, or can be used to instantiate the actual records in the Log. The latter approach provides a great deal more semantic definition and management control over the individual entries in a MessageLog, than do the record manipulation methods of the Log class. It is recommended that the data in individual Log entries be modeled using subclasses of LogRecord, to avoid the creation of LogRecords with one property (such as RecordData) without semantics. Definitional formats for LogRecords could be specified by establishing a naming convention for the RecordID and Message Timestamp key properties.	The LogRecord object can describe the definitional format for entries in a MessageLog, or can be used to instantiate the actual records in the Log. The latter approach provides a great deal more semantic definition and management control over the individual entries in a MessageLog, than do the record manipulation methods of the Log class. It is recommended that the data in individual Log entries be modeled using subclasses of LogRecord, to avoid the creation of LogRecords with one property (such as RecordData) without semantics. Definitional formats for LogRecords could be specified by establishing a naming convention for the RecordID and Message Timestamp key properties.
610	2.11.0	2.11.0
611	Name of the target PCSV device	Name of the target PCSV device
612	SMBios Guid of the target PCSV device	SMBios Guid of the target PCSV device
613	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.
614	DHCP	DHCP
615	BOOTP	BOOTP
616	IPv4 Address of the target PCSV device	IPv4 Address of the target PCSV device
617	IPv4 Subnet Mask of the target PCSV device	IPv4 Subnet Mask of the target PCSV device
618	IPv4 Default Gateway of the target PCSV device	IPv4 Default Gateway of the target PCSV device
619	LAN MAC Address of the target PCSV device	LAN MAC Address of the target PCSV device
620	SEL Free space in Bytes	SEL Free space in Bytes
621	This is a wrapper method used to set both the one time boot source and persistent boot source added to support the PCSVDevice cmdlets. This just calls the other two methods internally. The API users for this class should call the other methods directlly insted of this. This method will only change one setting at a time, if you pass values for both paramters, then this method will fail.	This is a wrapper method used to set both the one time boot source and persistent boot source added to support the PCSVDevice cmdlets. This just calls the other two methods internally. The API users for this class should call the other methods directlly insted of this. This method will only change one setting at a time, if you pass values for both paramters, then this method will fail.
622	This is a wrapper method used to change the network configuration of the BMC.	This is a wrapper method used to change the network configuration of the BMC.
623	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.
624	This is a wrapper method used to change the BMC user password.	This is a wrapper method used to change the BMC user password.
625	CurrentCredential is a delimited string containing both the current username and password, separated by a colon.	CurrentCredential is a delimited string containing both the current username and password, separated by a colon.
626	NewPassword will be stored on the BMC as the new password for the user specified by the CurrentCredential parameter.	NewPassword will be stored on the BMC as the new password for the user specified by the CurrentCredential parameter.
627	This is a wrapper method used to read BMC SEL log.	This is a wrapper method used to read BMC SEL log.
628	Return BMC SEL entries as an array of MSFT_PCSVLogRecord instances	Return BMC SEL entries as an array of MSFT_PCSVLogRecord instances
10001	The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2; and in the following format: username:password.	The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2; and in the following format: username:password.
10002	An error %1!X! occurred while parsing the credentials. The %2 operation option must be in the following format: username:password.	An error %1!X! occurred while parsing the credentials. The %2 operation option must be in the following format: username:password.
10003	The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2.	The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2.
10004	The %1 operation option must be of type %2.	The %1 operation option must be of type %2.
10005	The requested management protocol type is not supported. Supported types are WSMAN (1) and IPMI (2).	The requested management protocol type is not supported. Supported types are WSMAN (1) and IPMI (2).
10006	The requested authentication type is not supported. The supported authentication types are: Default, Digest, and Basic.	The requested authentication type is not supported. The supported authentication types are: Default, Digest, and Basic.
10007	The requested power state is not supported. The supported power states are: Enabled(2), Disabled(3), and Reset(11).	The requested power state is not supported. The supported power states are: Enabled(2), Disabled(3), and Reset(11).
10008	The requested boot source is not supported on this device. The requested boot source must be one of the values in the StructuredBootString array.	The requested boot source is not supported on this device. The requested boot source must be one of the values in the StructuredBootString array.
10009	The device attempted to start a session using an unsupported authentication algorithm. The supported Authentication algorithms are HMAC_SHA1 and NONE.	The device attempted to start a session using an unsupported authentication algorithm. The supported Authentication algorithms are HMAC_SHA1 and NONE.
10010	The device attempted to start a session using an unsupported integrity algorithm. The supported integrity algorithms are HMAC_SHA1_96 and NONE.	The device attempted to start a session using an unsupported integrity algorithm. The supported integrity algorithms are HMAC_SHA1_96 and NONE.
10011	The device attempted to start a session using an unsupported confidentiality algorithm. The supported confidentiality algorithms are AES_CBC_128 and NONE.	The device attempted to start a session using an unsupported confidentiality algorithm. The supported confidentiality algorithms are AES_CBC_128 and NONE.
10012	The device does not implement any of the supported base profiles. The supported base profiles are: %1, %2, and %3.	The device does not implement any of the supported base profiles. The supported base profiles are: %1, %2, and %3.
10013	An unexpected %1 error %2!X! occurred while processing the request.	An unexpected %1 error %2!X! occurred while processing the request.
10014	The response received from the device was not valid.	The response received from the device was not valid.
10015	The operation did not complete successfully. The response contained the following IPMI Completion Code: %1!x!.	The operation did not complete successfully. The response contained the following IPMI Completion Code: %1!x!.
10016	Cannot connect to device using the given credentials. Verify the credentials and try again.	Cannot connect to device using the given credentials. Verify the credentials and try again.
10017	The device did not respond in the specified timeout period.	The device did not respond in the specified timeout period.
10018	The DMTF %1 profile is not implemented on the device or it is not implemented in the standard way.	The DMTF %1 profile is not implemented on the device or it is not implemented in the standard way.
10019	Restarting device using %1	Restarting device using %1
10020	The operation failed. The device returned the following RMCP+ status code: %1!x!.	The operation failed. The device returned the following RMCP+ status code: %1!x!.
10021	Starting device using %1	Starting device using %1
10022	Stopping device using %1	Stopping device using %1
10023	Set one time boot source to %2 using %1	Set one time boot source to %2 using %1
10024	Getting information from device using %1	Getting information from device using %1
10025	Some capabilities or properties will not be available since the device does not implement the DMTF %1 Profile.	Some capabilities or properties will not be available since the device does not implement the DMTF %1 Profile.
10026	The operation is not supported for this device. The device only supports setting one boot source for Persistent Boot Order.	The operation is not supported for this device. The device only supports setting one boot source for Persistent Boot Order.
10027	The operation is not supported for this device type. This operation is supported for IPMI devices only.	The operation is not supported for this device type. This operation is supported for IPMI devices only.
10028	Set persistent boot order using %1	Set persistent boot order using %1
10029	The parameters passed are not valid. Changing One Time Boot Source and Persistent Boot Order in a single operation is not supported.	The parameters passed are not valid. Changing One Time Boot Source and Persistent Boot Order in a single operation is not supported.
10030	The parameters passed are not valid. Please pass a valid value for one of the boot settings.	The parameters passed are not valid. Please pass a valid value for one of the boot settings.
10031	The operation is not supported on this system. The system does not have a Microsoft IPMI compatible device.	The operation is not supported on this system. The system does not have a Microsoft IPMI compatible device.
10032	Power state management operations are only supported for devices managed via an out-of-band channel. To manage the device using an out-of-band channel please provide device connection information e.g. TargetAddress, Credentials, ManagementProtocol etc.	Power state management operations are only supported for devices managed via an out-of-band channel. To manage the device using an out-of-band channel please provide device connection information e.g. TargetAddress, Credentials, ManagementProtocol etc.
10034	The operation did not complete successfully. IPv4AddressOrigin cannot be set to DHCP with static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.	The operation did not complete successfully. IPv4AddressOrigin cannot be set to DHCP with static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10035	The operation did not complete successfully. IPv4AddressOrigin cannot be set to STATIC without static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.	The operation did not complete successfully. IPv4AddressOrigin cannot be set to STATIC without static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10036	The operation did not complete successfully. %1 is not supported IPv4AddressOrigin value for IPMI protocol. The supported values are: STATIC(3) and DHCP(4)	The operation did not complete successfully. %1 is not supported IPv4AddressOrigin value for IPMI protocol. The supported values are: STATIC(3) and DHCP(4)
10037	The operation did not complete successfully. The IPv4 address '%1' is not a valid IPv4 address.	The operation did not complete successfully. The IPv4 address '%1' is not a valid IPv4 address.
10038	BMC network configuration change are only supported via an in-band channel. To change the network configuration, please execute this command on the remote host directly.	BMC network configuration change are only supported via an in-band channel. To change the network configuration, please execute this command on the remote host directly.
10039	BMC network configuration change receives an unexpected parameter type. A string is expected for IP address.	BMC network configuration change receives an unexpected parameter type. A string is expected for IP address.
10040	BMC password change received an unexpected parameter type. A delimited string is expected for current credential	BMC password change received an unexpected parameter type. A delimited string is expected for current credential
10041	BMC password change received an unexpected parameter type. A string is expected for new password.	BMC password change received an unexpected parameter type. A string is expected for new password.
10042	The current credential did not match those of a valid user on the BMC.	The current credential did not match those of a valid user on the BMC.
10044	2 parameters (CurrentCredential and NewPassword) are required to change BMC user password. At least one of them is missing.	2 parameters (CurrentCredential and NewPassword) are required to change BMC user password. At least one of them is missing.
10045	Username cannot be longer than 16 characters.	Username cannot be longer than 16 characters.
10046	Password cannot be longer than 20 characters.	Password cannot be longer than 20 characters.
10048	Cannot read System Event Log because erase operation is in progress.	Cannot read System Event Log because erase operation is in progress.
10051	Failed to reserve the System Event Log because an erase operation is in progress.	Failed to reserve the System Event Log because an erase operation is in progress.
10052	Cannot clear the System Event Log because the reservation was cancelled by an external event (e.g. a new entry was added, the device was reset, etc.).	Cannot clear the System Event Log because the reservation was cancelled by an external event (e.g. a new entry was added, the device was reset, etc.).
10053	Change network configuration using %1	Change network configuration using %1
10054	Change user password using %1	Change user password using %1
10055	Clear System Event Log using %1	Clear System Event Log using %1
10056	Local Device	Local Device
10057	Gracefully shutting down device using %1	Gracefully shutting down device using %1
10058	Activating SOL payload failed. SOL payload must be activated in the same session.	Activating SOL payload failed. SOL payload must be activated in the same session.
0x90000001	Microsoft-Windows-DAL-Provider	Microsoft-Windows-DAL-Provider
0xB0000001	The Unencrypted request data for IPMI request %1	The Unencrypted request data for IPMI request %1
0xB0000002	The Decrypted response data for IPMI request %1	The Decrypted response data for IPMI request %1
0xB0000003	Starts enumeration of PCSVDevice	Starts enumeration of PCSVDevice
0xB0000004	Stops enumeration of PCSVDevice	Stops enumeration of PCSVDevice
0xB0000005	Starts getting instance of PCSVDevice	Starts getting instance of PCSVDevice
0xB0000006	Stops getting instance of PCSVDevice	Stops getting instance of PCSVDevice
0xB0000007	Start RequestStateChange	Start RequestStateChange
0xB0000008	Stops RequestStateChange	Stops RequestStateChange
0xB0000009	Starts SetOneTimeBootSource	Starts SetOneTimeBootSource
0xB000000A	Stops SetOneTimeBootSource	Stops SetOneTimeBootSource
0xB000000B	Result of PCSVDevice operation	Result of PCSVDevice operation
0xB000000F	Information on IPMI Sent Data	Information on IPMI Sent Data
0xB0000010	Information on IPMI Received Data	Information on IPMI Received Data
0xB0000011	Get operations options	Get operations options
0xB0000012	Starts ModifyPersistentBootConfigOrder	Starts ModifyPersistentBootConfigOrder
0xB0000013	Stops ModifyPersistentBootConfigOrder	Stops ModifyPersistentBootConfigOrder
0xB0000014	Starts ChangeBootConfiguration	Starts ChangeBootConfiguration
0xB0000015	Stops ChangeBootConfiguration	Stops ChangeBootConfiguration
0xB0000016	Starts ChangeNetworkConfiguration	Starts ChangeNetworkConfiguration
0xB0000017	Stops ChangeNetworkConfiguration	Stops ChangeNetworkConfiguration
0xB0000018	Starts ChangeUserPassword	Starts ChangeUserPassword
0xB0000019	Stops ChangeUserPassword	Stops ChangeUserPassword
0xB000001A	Starts getting PCSV device log	Starts getting PCSV device log
0xB000001B	Stops getting PCSV device log	Stops getting PCSV device log
0xB000001C	Starts clearing PCSV device log	Starts clearing PCSV device log
0xB000001D	Stops clearing PCSV device log	Stops clearing PCSV device log
0xB000001E	The request data for in-band IPMI request %1	The request data for in-band IPMI request %1
0xB000001F	The response data for in-band IPMI request %1	The response data for in-band IPMI request %1

File Name:	pcsvDevice.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-devicepro..-provider.resources_31bf3856ad364e35_10.0.15063.0_th-th_785ec273b3cd9e76\
File Size:	134 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	136704
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Dynamic link library
File Subtype:	0
Language Code:	Thai
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	PCSV Proxy Provider for devices
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	pcsvDevice.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	pcsvDevice.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0

pcsvDevice.dll.mui is Multilingual User Interface resource file that contain Thai language for file pcsvDevice.dll (PCSV Proxy Provider for devices).

File Description:	PCSV Proxy Provider for devices
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	pcsvDevice.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	pcsvDevice.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x41E, 1200