netttcim.dll.mui Transition Technology WMI Objects e6f48edffad1fdaab939adac0cdad405

File name:	netttcim.dll.mui
Size:	174080 byte
MD5:	e6f48edffad1fdaab939adac0cdad405
SHA1:	8569427efdba12af64d9909bb5c6b25d54d6f63a
SHA256:	86812321f0dd87246de39680d2fbc9507d4e9bff61dd8b0dc0cfd0c9afd3dee2
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in English (U.S.) 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	English (U.S.)	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	Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. 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 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. 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. 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 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. For DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
8	The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.)	The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.)
9	CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future. Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association. Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration. When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations.	CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future. Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association. Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration. When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations.
10	Superclass SettingData for networking	Superclass SettingData for networking
11	PolicyStore property defines the store to retrieve the 6to4 configuration policy.	PolicyStore property defines the store to retrieve the 6to4 configuration policy.
12	Describes the 6to4 service state. One of the following values: enabled, disabled, default.	Describes the 6to4 service state. One of the following values: enabled, disabled, default.
13	default	default
14	automatic	automatic
15	enabled	enabled
16	disabled	disabled
17	Describes the 6to4 sharing state. One of the following values: enabled, disabled, default.	Describes the 6to4 sharing state. One of the following values: enabled, disabled, default.
18	Resolution interval in minutes.	Resolution interval in minutes.
19	Name of the 6to4 relay.	Name of the 6to4 relay.
20	State of the relay name resolution. One of the following values: enabled, disabled, automatic, default.	State of the relay name resolution. One of the following values: enabled, disabled, automatic, default.
21	Reset the 6to4 configuration.	Reset the 6to4 configuration.
22	Net6to4Configuration represents global 6to4 configuration shared across all 6to4 interfaces.	Net6to4Configuration represents global 6to4 configuration shared across all 6to4 interfaces.
23	The managed element.	The managed element.
24	The SettingData object associated with the element.	The SettingData object associated with the element.
25	An enumerated integer indicating that the referenced setting is a default setting for the element, or that this information is unknown.	An enumerated integer indicating that the referenced setting is a default setting for the element, or that this information is unknown.
26	Unknown	Unknown
27	Is Default	Is Default
28	Is Not Default	Is Not Default
29	An enumerated integer indicating that the referenced setting is currently being used in the operation of the element, or that this information is unknown.	An enumerated integer indicating that the referenced setting is currently being used in the operation of the element, or that this information is unknown.
30	Is Current	Is Current
31	Is Not Current	Is Not Current
32	An enumerated integer indicating whether or not the referenced setting is the next setting to be applied. For example, the application could take place on a re-initialization, reset, reconfiguration request. This could be a permanent setting, or a setting used only one time, as indicated by the flag. If it is a permanent setting then the setting is applied every time the managed element reinitializes, until this flag is manually reset. However, if it is single use, then the flag is automatically cleared after the settings are applied. Also note that if this flag is specified (i.e. set to value other than "Unknown"), then this takes precedence over any SettingData that may have been specified as Default. For example: If the managed element is a computer system, and the value of this flag is "Is Next", then the setting will be effective next time the system resets. And, unless this flag is changed, it will persist for subsequent system resets. However, if this flag is set to "Is Next For Single Use", then this setting will only be used once and the flag would be reset after that to "Is Not Next". So, in the above example, if the system reboots in a quick succession, the setting will not be used at the second reboot.	An enumerated integer indicating whether or not the referenced setting is the next setting to be applied. For example, the application could take place on a re-initialization, reset, reconfiguration request. This could be a permanent setting, or a setting used only one time, as indicated by the flag. If it is a permanent setting then the setting is applied every time the managed element reinitializes, until this flag is manually reset. However, if it is single use, then the flag is automatically cleared after the settings are applied. Also note that if this flag is specified (i.e. set to value other than "Unknown"), then this takes precedence over any SettingData that may have been specified as Default. For example: If the managed element is a computer system, and the value of this flag is "Is Next", then the setting will be effective next time the system resets. And, unless this flag is changed, it will persist for subsequent system resets. However, if this flag is set to "Is Next For Single Use", then this setting will only be used once and the flag would be reset after that to "Is Not Next". So, in the above example, if the system reboots in a quick succession, the setting will not be used at the second reboot.
33	Is Next	Is Next
34	Is Not Next	Is Not Next
35	Is Next For Single Use	Is Next For Single Use
36	2.19.1	2.19.1
37	ElementSettingData represents the association between ManagedElements and applicable setting data. This association also describes whether this is a default or current setting.	ElementSettingData represents the association between ManagedElements and applicable setting data. This association also describes whether this is a default or current setting.
38	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.
39	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.
40	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.
41	Other	Other
42	OK	OK
43	Degraded	Degraded
44	Stressed	Stressed
45	Predictive Failure	Predictive Failure
46	Error	Error
47	Non-Recoverable Error	Non-Recoverable Error
48	Starting	Starting
49	Stopping	Stopping
50	Stopped	Stopped
51	In Service	In Service
52	No Contact	No Contact
53	Lost Communication	Lost Communication
54	Aborted	Aborted
55	Dormant	Dormant
56	Supporting Entity in Error	Supporting Entity in Error
57	Completed	Completed
58	Power Mode	Power Mode
59	DMTF Reserved	DMTF Reserved
60	Vendor Reserved	Vendor Reserved
61	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.
62	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.
63	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.
64	Degraded/Warning	Degraded/Warning
65	Minor failure	Minor failure
66	Major failure	Major failure
67	Critical failure	Critical failure
68	Non-recoverable error	Non-recoverable error
69	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.
70	Not Available	Not Available
71	Communication OK	Communication OK
72	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.
73	No Additional Information	No Additional Information
74	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.
75	Servicing	Servicing
76	Migrating	Migrating
77	Emigrating	Emigrating
78	Immigrating	Immigrating
79	Snapshotting	Snapshotting
80	Shutting Down	Shutting Down
81	In Test	In Test
82	Transitioning	Transitioning
83	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.
84	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.
85	2.22.0	2.22.0
86	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.
87	2.6.0	2.6.0
88	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.
89	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.
90	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.
91	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.
92	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.
93	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.
94	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.
95	January	January
96	February	February
97	March	March
98	April	April
99	May	May
100	June	June
101	July	July
102	August	August
103	September	September
104	October	October
105	November	November
106	December	December
107	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.
108	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.
109	-Saturday	-Saturday
110	-Friday	-Friday
111	-Thursday	-Thursday
112	-Wednesday	-Wednesday
113	-Tuesday	-Tuesday
114	-Monday	-Monday
115	-Sunday	-Sunday
116	ExactDayOfMonth	ExactDayOfMonth
117	Sunday	Sunday
118	Monday	Monday
119	Tuesday	Tuesday
120	Wednesday	Wednesday
121	Thursday	Thursday
122	Friday	Friday
123	Saturday	Saturday
124	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.
125	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".
126	Local Time	Local Time
127	UTC Time	UTC Time
128	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.
129	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.
130	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.
131	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.
132	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.
133	Percent	Percent
134	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.
135	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.
136	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.
137	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.
138	Do Not Continue	Do Not Continue
139	Continue With Next Job	Continue With Next Job
140	Re-run Job	Re-run Job
141	Run Recovery Job	Run Recovery Job
142	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").
143	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.
144	Success	Success
145	Not Supported	Not Supported
146	Timeout	Timeout
147	Failed	Failed
148	Access Denied	Access Denied
149	Not Found	Not Found
150	Vendor Specific	Vendor Specific
151	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.
152	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.
153	2.10.0	2.10.0
154	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.
155	Communications Error	Communications Error
156	Quality of Service Error	Quality of Service Error
157	Software Error	Software Error
158	Hardware Error	Hardware Error
159	Environmental Error	Environmental Error
160	Security Error	Security Error
161	Oversubscription Error	Oversubscription Error
162	Unavailable Resource Error	Unavailable Resource Error
163	Unsupported Operation Error	Unsupported Operation Error
164	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.
165	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.
166	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.
167	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.
168	An array containing the dynamic content of the message.	An array containing the dynamic content of the message.
169	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.
170	Information	Information
171	Minor	Minor
172	Major	Major
173	Critical	Critical
174	Fatal/NonRecoverable	Fatal/NonRecoverable
175	An enumerated value that describes the probable cause of the error.	An enumerated value that describes the probable cause of the error.
176	Adapter/Card Error	Adapter/Card Error
177	Application Subsystem Failure	Application Subsystem Failure
178	Bandwidth Reduced	Bandwidth Reduced
179	Connection Establishment Error	Connection Establishment Error
180	Communications Protocol Error	Communications Protocol Error
181	Communications Subsystem Failure	Communications Subsystem Failure
182	Configuration/Customization Error	Configuration/Customization Error
183	Congestion	Congestion
184	Corrupt Data	Corrupt Data
185	CPU Cycles Limit Exceeded	CPU Cycles Limit Exceeded
186	Dataset/Modem Error	Dataset/Modem Error
187	Degraded Signal	Degraded Signal
188	DTE-DCE Interface Error	DTE-DCE Interface Error
189	Enclosure Door Open	Enclosure Door Open
190	Equipment Malfunction	Equipment Malfunction
191	Excessive Vibration	Excessive Vibration
192	File Format Error	File Format Error
193	Fire Detected	Fire Detected
194	Flood Detected	Flood Detected
195	Framing Error	Framing Error
196	HVAC Problem	HVAC Problem
197	Humidity Unacceptable	Humidity Unacceptable
198	I/O Device Error	I/O Device Error
199	Input Device Error	Input Device Error
200	LAN Error	LAN Error
201	Non-Toxic Leak Detected	Non-Toxic Leak Detected
202	Local Node Transmission Error	Local Node Transmission Error
203	Loss of Frame	Loss of Frame
204	Loss of Signal	Loss of Signal
205	Material Supply Exhausted	Material Supply Exhausted
206	Multiplexer Problem	Multiplexer Problem
207	Out of Memory	Out of Memory
208	Output Device Error	Output Device Error
209	Performance Degraded	Performance Degraded
210	Power Problem	Power Problem
211	Pressure Unacceptable	Pressure Unacceptable
212	Processor Problem (Internal Machine Error)	Processor Problem (Internal Machine Error)
213	Pump Failure	Pump Failure
214	Queue Size Exceeded	Queue Size Exceeded
215	Receive Failure	Receive Failure
216	Receiver Failure	Receiver Failure
217	Remote Node Transmission Error	Remote Node Transmission Error
218	Resource at or Nearing Capacity	Resource at or Nearing Capacity
219	Response Time Excessive	Response Time Excessive
220	Retransmission Rate Excessive	Retransmission Rate Excessive
221	Software Program Abnormally Terminated	Software Program Abnormally Terminated
222	Software Program Error (Incorrect Results)	Software Program Error (Incorrect Results)
223	Storage Capacity Problem	Storage Capacity Problem
224	Temperature Unacceptable	Temperature Unacceptable
225	Threshold Crossed	Threshold Crossed
226	Timing Problem	Timing Problem
227	Toxic Leak Detected	Toxic Leak Detected
228	Transmit Failure	Transmit Failure
229	Transmitter Failure	Transmitter Failure
230	Underlying Resource Unavailable	Underlying Resource Unavailable
231	Version Mismatch	Version Mismatch
232	Previous Alert Cleared	Previous Alert Cleared
233	Login Attempts Failed	Login Attempts Failed
234	Software Virus Detected	Software Virus Detected
235	Hardware Security Breached	Hardware Security Breached
236	Denial of Service Detected	Denial of Service Detected
237	Security Credential Mismatch	Security Credential Mismatch
238	Unauthorized Access	Unauthorized Access
239	Alarm Received	Alarm Received
240	Loss of Pointer	Loss of Pointer
241	Payload Mismatch	Payload Mismatch
242	Transmission Error	Transmission Error
243	Excessive Error Rate	Excessive Error Rate
244	Trace Problem	Trace Problem
245	Element Unavailable	Element Unavailable
246	Element Missing	Element Missing
247	Loss of Multi Frame	Loss of Multi Frame
248	Broadcast Channel Failure	Broadcast Channel Failure
249	Invalid Message Received	Invalid Message Received
250	Routing Failure	Routing Failure
251	Backplane Failure	Backplane Failure
252	Identifier Duplication	Identifier Duplication
253	Protection Path Failure	Protection Path Failure
254	Sync Loss or Mismatch	Sync Loss or Mismatch
255	Terminal Problem	Terminal Problem
256	Real Time Clock Failure	Real Time Clock Failure
257	Antenna Failure	Antenna Failure
258	Battery Charging Failure	Battery Charging Failure
259	Disk Failure	Disk Failure
260	Frequency Hopping Failure	Frequency Hopping Failure
261	Loss of Redundancy	Loss of Redundancy
262	Power Supply Failure	Power Supply Failure
263	Signal Quality Problem	Signal Quality Problem
264	Battery Discharging	Battery Discharging
265	Battery Failure	Battery Failure
266	Commercial Power Problem	Commercial Power Problem
267	Fan Failure	Fan Failure
268	Engine Failure	Engine Failure
269	Sensor Failure	Sensor Failure
270	Fuse Failure	Fuse Failure
271	Generator Failure	Generator Failure
272	Low Battery	Low Battery
273	Low Fuel	Low Fuel
274	Low Water	Low Water
275	Explosive Gas	Explosive Gas
276	High Winds	High Winds
277	Ice Buildup	Ice Buildup
278	Smoke	Smoke
279	Memory Mismatch	Memory Mismatch
280	Out of CPU Cycles	Out of CPU Cycles
281	Software Environment Problem	Software Environment Problem
282	Software Download Failure	Software Download Failure
283	Element Reinitialized	Element Reinitialized
284	Logging Problems	Logging Problems
285	Leak Detected	Leak Detected
286	Protection Mechanism Failure	Protection Mechanism Failure
287	Protecting Resource Failure	Protecting Resource Failure
288	Database Inconsistency	Database Inconsistency
289	Authentication Failure	Authentication Failure
290	Breach of Confidentiality	Breach of Confidentiality
291	Cable Tamper	Cable Tamper
292	Delayed Information	Delayed Information
293	Duplicate Information	Duplicate Information
294	Information Missing	Information Missing
295	Information Modification	Information Modification
296	Information Out of Sequence	Information Out of Sequence
297	Key Expired	Key Expired
298	Non-Repudiation Failure	Non-Repudiation Failure
299	Out of Hours Activity	Out of Hours Activity
300	Out of Service	Out of Service
301	Procedural Error	Procedural Error
302	Unexpected Information	Unexpected Information
303	A free-form string describing the probable cause of the error.	A free-form string describing the probable cause of the error.
304	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.
305	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.
306	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.
307	CIMObjectPath	CIMObjectPath
308	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.
309	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.
310	CIM_ERR_FAILED	CIM_ERR_FAILED
311	CIM_ERR_ACCESS_DENIED	CIM_ERR_ACCESS_DENIED
312	CIM_ERR_INVALID_NAMESPACE	CIM_ERR_INVALID_NAMESPACE
313	CIM_ERR_INVALID_PARAMETER	CIM_ERR_INVALID_PARAMETER
314	CIM_ERR_INVALID_CLASS	CIM_ERR_INVALID_CLASS
315	CIM_ERR_NOT_FOUND	CIM_ERR_NOT_FOUND
316	CIM_ERR_NOT_SUPPORTED	CIM_ERR_NOT_SUPPORTED
317	CIM_ERR_CLASS_HAS_CHILDREN	CIM_ERR_CLASS_HAS_CHILDREN
318	CIM_ERR_CLASS_HAS_INSTANCES	CIM_ERR_CLASS_HAS_INSTANCES
319	CIM_ERR_INVALID_SUPERCLASS	CIM_ERR_INVALID_SUPERCLASS
320	CIM_ERR_ALREADY_EXISTS	CIM_ERR_ALREADY_EXISTS
321	CIM_ERR_NO_SUCH_PROPERTY	CIM_ERR_NO_SUCH_PROPERTY
322	CIM_ERR_TYPE_MISMATCH	CIM_ERR_TYPE_MISMATCH
323	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
324	CIM_ERR_INVALID_QUERY	CIM_ERR_INVALID_QUERY
325	CIM_ERR_METHOD_NOT_AVAILABLE	CIM_ERR_METHOD_NOT_AVAILABLE
326	CIM_ERR_METHOD_NOT_FOUND	CIM_ERR_METHOD_NOT_FOUND
327	CIM_ERR_UNEXPECTED_RESPONSE	CIM_ERR_UNEXPECTED_RESPONSE
328	CIM_ERR_INVALID_RESPONSE_DESTINATION	CIM_ERR_INVALID_RESPONSE_DESTINATION
329	CIM_ERR_NAMESPACE_NOT_EMPTY	CIM_ERR_NAMESPACE_NOT_EMPTY
330	CIM_ERR_INVALID_ENUMERATION_CONTEXT	CIM_ERR_INVALID_ENUMERATION_CONTEXT
331	CIM_ERR_INVALID_OPERATION_TIMEOUT	CIM_ERR_INVALID_OPERATION_TIMEOUT
332	CIM_ERR_PULL_HAS_BEEN_ABANDONED	CIM_ERR_PULL_HAS_BEEN_ABANDONED
333	CIM_ERR_PULL_CANNOT_BE_ABANDONED	CIM_ERR_PULL_CANNOT_BE_ABANDONED
334	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
335	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
336	CIM_ERR_SERVER_LIMITS_EXCEEDED	CIM_ERR_SERVER_LIMITS_EXCEEDED
337	CIM_ERR_SERVER_IS_SHUTTING_DOWN	CIM_ERR_SERVER_IS_SHUTTING_DOWN
338	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
339	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.
340	2.22.1	2.22.1
341	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.
342	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\'.
343	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.)
344	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
345	New	New
346	Running	Running
347	Suspended	Suspended
348	Terminated	Terminated
349	Killed	Killed
350	Exception	Exception
351	Service	Service
352	Query Pending	Query Pending
353	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.
354	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.
355	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.
356	Completed with No Error	Completed with No Error
357	Unknown/Unspecified Error	Unknown/Unspecified Error
358	Can NOT complete within Timeout Period	Can NOT complete within Timeout Period
359	Invalid Parameter	Invalid Parameter
360	In Use	In Use
361	Method Parameters Checked - Transition Started	Method Parameters Checked - Transition Started
362	Invalid State Transition	Invalid State Transition
363	Use of Timeout Parameter Not Supported	Use of Timeout Parameter Not Supported
364	Busy	Busy
365	Method Reserved	Method Reserved
366	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.
367	Start	Start
368	Suspend	Suspend
369	Terminate	Terminate
370	Kill	Kill
371	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.
372	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.
373	Unspecified Error	Unspecified Error
374	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.
375	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.
376	EnabledState is an integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following text briefly summarizes the various enabled and disabled states: Enabled (2) indicates that the element is or could be executing commands, will process any queued commands, and queues new requests. Disabled (3) indicates that the element will not execute commands and will drop any new requests. Shutting Down (4) indicates that the element is in the process of going to a Disabled state. Not Applicable (5) indicates the element does not support being enabled or disabled. Enabled but Offline (6) indicates that the element might be completing commands, and will drop any new requests. Test (7) indicates that the element is in a test state. Deferred (8) indicates that the element might be completing commands, but will queue any new requests. Quiesce (9) indicates that the element is enabled but in a restricted mode. Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued.	EnabledState is an integer enumeration that indicates the enabled and disabled states of an element. It can also indicate the transitions between these requested states. For example, shutting down (value=4) and starting (value=10) are transient states between enabled and disabled. The following text briefly summarizes the various enabled and disabled states: Enabled (2) indicates that the element is or could be executing commands, will process any queued commands, and queues new requests. Disabled (3) indicates that the element will not execute commands and will drop any new requests. Shutting Down (4) indicates that the element is in the process of going to a Disabled state. Not Applicable (5) indicates the element does not support being enabled or disabled. Enabled but Offline (6) indicates that the element might be completing commands, and will drop any new requests. Test (7) indicates that the element is in a test state. Deferred (8) indicates that the element might be completing commands, but will queue any new requests. Quiesce (9) indicates that the element is enabled but in a restricted mode. Starting (10) indicates that the element is in the process of going to an Enabled state. New requests are queued.
377	Enabled	Enabled
378	Disabled	Disabled
379	Not Applicable	Not Applicable
380	Enabled but Offline	Enabled but Offline
381	Deferred	Deferred
382	Quiesce	Quiesce
383	A string that describes the enabled or disabled state of the element when the EnabledState property is set to 1 ("Other"). This property must be set to null when EnabledState is any value other than 1.	A string that describes the enabled or disabled state of the element when the EnabledState property is set to 1 ("Other"). This property must be set to null when EnabledState is any value other than 1.
384	RequestedState is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by EnabledState. This property is provided to compare the last requested and current enabled or disabled states. Note that when EnabledState is set to 5 ("Not Applicable"), then this property has no meaning. Refer to the EnabledState property description for explanations of the values in the RequestedState enumeration. "Unknown" (0) indicates the last requested state for the element is unknown. Note that the value "No Change" (5) has been deprecated in lieu of indicating the last requested state is "Unknown" (0). If the last requested or desired state is unknown, RequestedState should have the value "Unknown" (0), but may have the value "No Change" (5).Offline (6) indicates that the element has been requested to transition to the Enabled but Offline EnabledState. It should be noted that there are two new values in RequestedState that build on the statuses of EnabledState. These are "Reboot" (10) and "Reset" (11). Reboot refers to doing a "Shut Down" and then moving to an "Enabled" state. Reset indicates that the element is first "Disabled" and then "Enabled". The distinction between requesting "Shut Down" and "Disabled" should also be noted. Shut Down requests an orderly transition to the Disabled state, and might involve removing power, to completely erase any existing state. The Disabled state requests an immediate disabling of the element, such that it will not execute or accept any commands or processing requests. This property is set as the result of a method invocation (such as Start or StopService on CIM_Service), or can be overridden and defined as WRITEable in a subclass. The method approach is considered superior to a WRITEable property, because it allows an explicit invocation of the operation and the return of a result code. If knowledge of the last RequestedState is not supported for the EnabledLogicalElement, the property shall be NULL or have the value 12 "Not Applicable".	RequestedState is an integer enumeration that indicates the last requested or desired state for the element, irrespective of the mechanism through which it was requested. The actual state of the element is represented by EnabledState. This property is provided to compare the last requested and current enabled or disabled states. Note that when EnabledState is set to 5 ("Not Applicable"), then this property has no meaning. Refer to the EnabledState property description for explanations of the values in the RequestedState enumeration. "Unknown" (0) indicates the last requested state for the element is unknown. Note that the value "No Change" (5) has been deprecated in lieu of indicating the last requested state is "Unknown" (0). If the last requested or desired state is unknown, RequestedState should have the value "Unknown" (0), but may have the value "No Change" (5).Offline (6) indicates that the element has been requested to transition to the Enabled but Offline EnabledState. It should be noted that there are two new values in RequestedState that build on the statuses of EnabledState. These are "Reboot" (10) and "Reset" (11). Reboot refers to doing a "Shut Down" and then moving to an "Enabled" state. Reset indicates that the element is first "Disabled" and then "Enabled". The distinction between requesting "Shut Down" and "Disabled" should also be noted. Shut Down requests an orderly transition to the Disabled state, and might involve removing power, to completely erase any existing state. The Disabled state requests an immediate disabling of the element, such that it will not execute or accept any commands or processing requests. This property is set as the result of a method invocation (such as Start or StopService on CIM_Service), or can be overridden and defined as WRITEable in a subclass. The method approach is considered superior to a WRITEable property, because it allows an explicit invocation of the operation and the return of a result code. If knowledge of the last RequestedState is not supported for the EnabledLogicalElement, the property shall be NULL or have the value 12 "Not Applicable".
385	Shut Down	Shut Down
386	No Change	No Change
387	Offline	Offline
388	Test	Test
389	Reboot	Reboot
390	Reset	Reset
391	An enumerated value indicating an administrator\'s default or startup configuration for the Enabled State of an element. By default, the element is "Enabled" (value=2).	An enumerated value indicating an administrator\'s default or startup configuration for the Enabled State of an element. By default, the element is "Enabled" (value=2).
392	No Default	No Default
393	The date or time when the EnabledState of the element last changed. If the state of the element 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 EnabledState of the element last changed. If the state of the element 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.
394	AvailableRequestedStates indicates the possible values for the RequestedState parameter of the method RequestStateChange, used to initiate a state change. The values listed shall be a subset of the values contained in the RequestedStatesSupported property of the associated instance of CIM_EnabledLogicalElementCapabilities where the values selected are a function of the current state of the CIM_EnabledLogicalElement. This property may be non-null if an implementation is able to advertise the set of possible values as a function of the current state. This property shall be null if an implementation is unable to determine the set of possible values as a function of the current state.	AvailableRequestedStates indicates the possible values for the RequestedState parameter of the method RequestStateChange, used to initiate a state change. The values listed shall be a subset of the values contained in the RequestedStatesSupported property of the associated instance of CIM_EnabledLogicalElementCapabilities where the values selected are a function of the current state of the CIM_EnabledLogicalElement. This property may be non-null if an implementation is able to advertise the set of possible values as a function of the current state. This property shall be null if an implementation is unable to determine the set of possible values as a function of the current state.
395	Defer	Defer
396	TransitioningToState indicates the target state to which the instance is transitioning. A value of 5 "No Change" shall indicate that no transition is in progress.A value of 12 "Not Applicable" shall indicate the implementation does not support representing ongoing transitions. A value other than 5 or 12 shall identify the state to which the element is in the process of transitioning.	TransitioningToState indicates the target state to which the instance is transitioning. A value of 5 "No Change" shall indicate that no transition is in progress.A value of 12 "Not Applicable" shall indicate the implementation does not support representing ongoing transitions. A value other than 5 or 12 shall identify the state to which the element is in the process of transitioning.
397	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 of the element 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 3 shall indicate that the state transition cannot complete within the interval specified by the TimeoutPeriod parameter. A return code of 4096 (0x1000) shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job. Any other return code indicates an error condition.	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 of the element 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 3 shall indicate that the state transition cannot complete within the interval specified by the TimeoutPeriod parameter. A return code of 4096 (0x1000) shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job. Any other return code indicates an error condition.
398	Unknown or Unspecified Error	Unknown or Unspecified Error
399	Cannot complete within Timeout Period	Cannot complete within Timeout Period
400	Method Parameters Checked - Job Started	Method Parameters Checked - Job Started
401	The state requested for the element. This information will be placed into the RequestedState property of the instance if the return code of the RequestStateChange method is 0 (\'Completed with No Error\'), or 4096 (0x1000) (\'Job Started\'). Refer to the description of the EnabledState and RequestedState properties for the detailed explanations of the RequestedState values.	The state requested for the element. This information will be placed into the RequestedState property of the instance if the return code of the RequestStateChange method is 0 (\'Completed with No Error\'), or 4096 (0x1000) (\'Job Started\'). Refer to the description of the EnabledState and RequestedState properties for the detailed explanations of the RequestedState values.
402	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.
403	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\' shall 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\' shall be returned.
404	This class extends LogicalElement to abstract the concept of an element that is enabled and disabled, such as a LogicalDevice or a ServiceAccessPoint.	This class extends LogicalElement to abstract the concept of an element that is enabled and disabled, such as a LogicalDevice or a ServiceAccessPoint.
405	The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the functionality that is managed. This functionality is described in more detail in the Description property of the object.	The Name property uniquely identifies the ServiceAccessPoint and provides an indication of the functionality that is managed. This functionality is described in more detail in the Description property of the object.
406	The CreationClassName of the scoping System.	The CreationClassName of the scoping System.
407	The Name of the scoping System.	The Name of the scoping System.
408	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.
409	CIM_ServiceAccessPoint represents the ability to utilize or invoke a Service. Access points represent that a Service is made available for other entities to use.	CIM_ServiceAccessPoint represents the ability to utilize or invoke a Service. Access points represent that a Service is made available for other entities to use.
410	A string that identifies this ProtocolEndpoint with either a port or an interface on a device. To ensure uniqueness, the Name property should be prepended or appended with information from the Type or OtherTypeDescription properties. The method selected is described in the NameFormat property of this class.	A string that identifies this ProtocolEndpoint with either a port or an interface on a device. To ensure uniqueness, the Name property should be prepended or appended with information from the Type or OtherTypeDescription properties. The method selected is described in the NameFormat property of this class.
411	NameFormat contains the naming heuristic that is selected to ensure that the value of the Name property is unique. For example, you might choose to prepend the name of the port or interface with the Type of ProtocolEndpoint (for example, IPv4) of this instance followed by an underscore.	NameFormat contains the naming heuristic that is selected to ensure that the value of the Name property is unique. For example, you might choose to prepend the name of the port or interface with the Type of ProtocolEndpoint (for example, IPv4) of this instance followed by an underscore.
412	Note: This property is deprecated in lieu of the ProtocolIFType enumeration. This deprecation was done to have better alignment between the IF-MIB of the IETF and this CIM class. Deprecated description: ProtocolType is an enumeration that provides information to categorize and classify different instances of this class. For most instances, information in this enumeration and the definition of the subclass overlap. However, there are several cases where a specific subclass of ProtocolEndpoint is not required (for example, there is no Fibre Channel subclass of ProtocolEndpoint). Therefore, this property is needed to define the type of Endpoint.	Note: This property is deprecated in lieu of the ProtocolIFType enumeration. This deprecation was done to have better alignment between the IF-MIB of the IETF and this CIM class. Deprecated description: ProtocolType is an enumeration that provides information to categorize and classify different instances of this class. For most instances, information in this enumeration and the definition of the subclass overlap. However, there are several cases where a specific subclass of ProtocolEndpoint is not required (for example, there is no Fibre Channel subclass of ProtocolEndpoint). Therefore, this property is needed to define the type of Endpoint.
413	IPv4	IPv4
414	IPv6	IPv6
415	IPX	IPX
416	AppleTalk	AppleTalk
417	DECnet	DECnet
418	SNA	SNA
419	CONP	CONP
420	CLNP	CLNP
421	VINES	VINES
422	XNS	XNS
423	ATM	ATM
424	Frame Relay	Frame Relay
425	Ethernet	Ethernet
426	TokenRing	TokenRing
427	FDDI	FDDI
428	Infiniband	Infiniband
429	Fibre Channel	Fibre Channel
430	ISDN BRI Endpoint	ISDN BRI Endpoint
431	ISDN B Channel Endpoint	ISDN B Channel Endpoint
432	ISDN D Channel Endpoint	ISDN D Channel Endpoint
433	IPv4/v6	IPv4/v6
434	BGP	BGP
435	OSPF	OSPF
436	MPLS	MPLS
437	UDP	UDP
438	TCP	TCP
439	ProtocolIFType is an enumeration that is synchronized with the IANA ifType MIB. The ifType MIB is maintained at the URL, http://www.iana.org/assignments/ianaiftype-mib. Also, additional values defined by the DMTF are included. The property is used to categorize and classify instances of the ProtocolEndpoint class. Note that if the ProtocolIFType is set to 1 (Other), then the type information should be provided in the OtherTypeDescription string property.	ProtocolIFType is an enumeration that is synchronized with the IANA ifType MIB. The ifType MIB is maintained at the URL, http://www.iana.org/assignments/ianaiftype-mib. Also, additional values defined by the DMTF are included. The property is used to categorize and classify instances of the ProtocolEndpoint class. Note that if the ProtocolIFType is set to 1 (Other), then the type information should be provided in the OtherTypeDescription string property.
440	Regular 1822	Regular 1822
441	HDH 1822	HDH 1822
442	DDN X.25	DDN X.25
443	RFC877 X.25	RFC877 X.25
444	Ethernet CSMA/CD	Ethernet CSMA/CD
445	ISO 802.3 CSMA/CD	ISO 802.3 CSMA/CD
446	ISO 802.4 Token Bus	ISO 802.4 Token Bus
447	ISO 802.5 Token Ring	ISO 802.5 Token Ring
448	ISO 802.6 MAN	ISO 802.6 MAN
449	StarLAN	StarLAN
450	Proteon 10Mbit	Proteon 10Mbit
451	Proteon 80Mbit	Proteon 80Mbit
452	HyperChannel	HyperChannel
453	LAP-B	LAP-B
454	SDLC	SDLC
455	DS1	DS1
456	E1	E1
457	Basic ISDN	Basic ISDN
458	Primary ISDN	Primary ISDN
459	Proprietary Point-to-Point Serial	Proprietary Point-to-Point Serial
460	PPP	PPP
461	Software Loopback	Software Loopback
462	EON	EON
463	Ethernet 3Mbit	Ethernet 3Mbit
464	NSIP	NSIP
465	SLIP	SLIP
466	Ultra	Ultra
467	DS3	DS3
468	SIP	SIP
469	RS-232	RS-232
470	Parallel	Parallel
471	ARCNet	ARCNet
472	ARCNet Plus	ARCNet Plus
473	MIO X.25	MIO X.25
474	SONET	SONET
475	X.25 PLE	X.25 PLE
476	ISO 802.211c	ISO 802.211c
477	LocalTalk	LocalTalk
478	SMDS DXI	SMDS DXI
479	Frame Relay Service	Frame Relay Service
480	V.35	V.35
481	HSSI	HSSI
482	HIPPI	HIPPI
483	Modem	Modem
484	AAL5	AAL5
485	SONET Path	SONET Path
486	SONET VT	SONET VT
487	SMDS ICIP	SMDS ICIP
488	Proprietary Virtual/Internal	Proprietary Virtual/Internal
489	Proprietary Multiplexor	Proprietary Multiplexor
490	IEEE 802.12	IEEE 802.12
491	HIPPI Interface	HIPPI Interface
492	Frame Relay Interconnect	Frame Relay Interconnect
493	ATM Emulated LAN for 802.3	ATM Emulated LAN for 802.3
494	ATM Emulated LAN for 802.5	ATM Emulated LAN for 802.5
495	ATM Emulated Circuit	ATM Emulated Circuit
496	Fast Ethernet (100BaseT)	Fast Ethernet (100BaseT)
497	ISDN	ISDN
498	V.11	V.11
499	V.36	V.36
500	G703 at 64K	G703 at 64K
501	G703 at 2Mb	G703 at 2Mb
502	QLLC	QLLC
503	Fast Ethernet 100BaseFX	Fast Ethernet 100BaseFX
504	Channel	Channel
505	IEEE 802.11	IEEE 802.11
506	IBM 260/370 OEMI Channel	IBM 260/370 OEMI Channel
507	ESCON	ESCON
508	Data Link Switching	Data Link Switching
509	ISDN S/T Interface	ISDN S/T Interface
510	ISDN U Interface	ISDN U Interface
511	LAP-D	LAP-D
512	IP Switch	IP Switch
513	Remote Source Route Bridging	Remote Source Route Bridging
514	ATM Logical	ATM Logical
515	DS0	DS0
516	DS0 Bundle	DS0 Bundle
517	BSC	BSC
518	Async	Async
519	Combat Net Radio	Combat Net Radio
520	ISO 802.5r DTR	ISO 802.5r DTR
521	Ext Pos Loc Report System	Ext Pos Loc Report System
522	AppleTalk Remote Access Protocol	AppleTalk Remote Access Protocol
523	Proprietary Connectionless	Proprietary Connectionless
524	ITU X.29 Host PAD	ITU X.29 Host PAD
525	ITU X.3 Terminal PAD	ITU X.3 Terminal PAD
526	Frame Relay MPI	Frame Relay MPI
527	ITU X.213	ITU X.213
528	ADSL	ADSL
529	RADSL	RADSL
530	SDSL	SDSL
531	VDSL	VDSL
532	ISO 802.5 CRFP	ISO 802.5 CRFP
533	Myrinet	Myrinet
534	Voice Receive and Transmit	Voice Receive and Transmit
535	Voice Foreign Exchange Office	Voice Foreign Exchange Office
536	Voice Foreign Exchange Service	Voice Foreign Exchange Service
537	Voice Encapsulation	Voice Encapsulation
538	Voice over IP	Voice over IP
539	ATM DXI	ATM DXI
540	ATM FUNI	ATM FUNI
541	ATM IMA	ATM IMA
542	PPP Multilink Bundle	PPP Multilink Bundle
543	IP over CDLC	IP over CDLC
544	IP over CLAW	IP over CLAW
545	Stack to Stack	Stack to Stack
546	Virtual IP Address	Virtual IP Address
547	MPC	MPC
548	IP over ATM	IP over ATM
549	ISO 802.5j Fibre Token Ring	ISO 802.5j Fibre Token Ring
550	TDLC	TDLC
551	Gigabit Ethernet	Gigabit Ethernet
552	HDLC	HDLC
553	LAP-F	LAP-F
554	V.37	V.37
555	X.25 MLP	X.25 MLP
556	X.25 Hunt Group	X.25 Hunt Group
557	Transp HDLC	Transp HDLC
558	Interleave Channel	Interleave Channel
559	FAST Channel	FAST Channel
560	IP (for APPN HPR in IP Networks)	IP (for APPN HPR in IP Networks)
561	CATV MAC Layer	CATV MAC Layer
562	CATV Downstream	CATV Downstream
563	CATV Upstream	CATV Upstream
564	Avalon 12MPP Switch	Avalon 12MPP Switch
565	Tunnel	Tunnel
566	Coffee	Coffee
567	Circuit Emulation Service	Circuit Emulation Service
568	ATM SubInterface	ATM SubInterface
569	Layer 2 VLAN using 802.1Q	Layer 2 VLAN using 802.1Q
570	Layer 3 VLAN using IP	Layer 3 VLAN using IP
571	Layer 3 VLAN using IPX	Layer 3 VLAN using IPX
572	Digital Power Line	Digital Power Line
573	Multimedia Mail over IP	Multimedia Mail over IP
574	DTM	DTM
575	DCN	DCN
576	IP Forwarding	IP Forwarding
577	MSDSL	MSDSL
578	IEEE 1394	IEEE 1394
579	IF-GSN/HIPPI-6400	IF-GSN/HIPPI-6400
580	DVB-RCC MAC Layer	DVB-RCC MAC Layer
581	DVB-RCC Downstream	DVB-RCC Downstream
582	DVB-RCC Upstream	DVB-RCC Upstream
583	ATM Virtual	ATM Virtual
584	MPLS Tunnel	MPLS Tunnel
585	SRP	SRP
586	Voice over ATM	Voice over ATM
587	Voice over Frame Relay	Voice over Frame Relay
588	ISDL	ISDL
589	Composite Link	Composite Link
590	SS7 Signaling Link	SS7 Signaling Link
591	Proprietary P2P Wireless	Proprietary P2P Wireless
592	Frame Forward	Frame Forward
593	RFC1483 Multiprotocol over ATM	RFC1483 Multiprotocol over ATM
594	USB	USB
595	IEEE 802.3ad Link Aggregate	IEEE 802.3ad Link Aggregate
596	BGP Policy Accounting	BGP Policy Accounting
597	FRF .16 Multilink FR	FRF .16 Multilink FR
598	H.323 Gatekeeper	H.323 Gatekeeper
599	H.323 Proxy	H.323 Proxy
600	Multi-Frequency Signaling Link	Multi-Frequency Signaling Link
601	HDSL-2	HDSL-2
602	S-HDSL	S-HDSL
603	DS1 Facility Data Link	DS1 Facility Data Link
604	Packet over SONET/SDH	Packet over SONET/SDH
605	DVB-ASI Input	DVB-ASI Input
606	DVB-ASI Output	DVB-ASI Output
607	Power Line	Power Line
608	Non Facility Associated Signaling	Non Facility Associated Signaling
609	TR008	TR008
610	GR303 RDT	GR303 RDT
611	GR303 IDT	GR303 IDT
612	ISUP	ISUP
613	Proprietary Wireless MAC Layer	Proprietary Wireless MAC Layer
614	Proprietary Wireless Downstream	Proprietary Wireless Downstream
615	Proprietary Wireless Upstream	Proprietary Wireless Upstream
616	HIPERLAN Type 2	HIPERLAN Type 2
617	Proprietary Broadband Wireless Access Point to Mulipoint	Proprietary Broadband Wireless Access Point to Mulipoint
618	SONET Overhead Channel	SONET Overhead Channel
619	Digital Wrapper Overhead Channel	Digital Wrapper Overhead Channel
620	ATM Adaptation Layer 2	ATM Adaptation Layer 2
621	Radio MAC	Radio MAC
622	ATM Radio	ATM Radio
623	Inter Machine Trunk	Inter Machine Trunk
624	MVL DSL	MVL DSL
625	Long Read DSL	Long Read DSL
626	Frame Relay DLCI Endpoint	Frame Relay DLCI Endpoint
627	ATM VCI Endpoint	ATM VCI Endpoint
628	Optical Channel	Optical Channel
629	Optical Transport	Optical Transport
630	Proprietary ATM	Proprietary ATM
631	Voice over Cable	Voice over Cable
632	TE Link	TE Link
633	Q.2931	Q.2931
634	Virtual Trunk Group	Virtual Trunk Group
635	SIP Trunk Group	SIP Trunk Group
636	SIP Signaling	SIP Signaling
637	CATV Upstream Channel	CATV Upstream Channel
638	Econet	Econet
639	FSAN 155Mb PON	FSAN 155Mb PON
640	FSAN 622Mb PON	FSAN 622Mb PON
641	Transparent Bridge	Transparent Bridge
642	Line Group	Line Group
643	Voice E&M Feature Group	Voice E&M Feature Group
644	Voice FGD EANA	Voice FGD EANA
645	Voice DID	Voice DID
646	MPEG Transport	MPEG Transport
647	6To4	6To4
648	GTP	GTP
649	Paradyne EtherLoop 1	Paradyne EtherLoop 1
650	Paradyne EtherLoop 2	Paradyne EtherLoop 2
651	Optical Channel Group	Optical Channel Group
652	HomePNA	HomePNA
653	GFP	GFP
654	ciscoISLvlan	ciscoISLvlan
655	actelisMetaLOOP	actelisMetaLOOP
656	Fcip	Fcip
657	IANA Reserved	IANA Reserved
658	802.11a	802.11a
659	802.11b	802.11b
660	802.11g	802.11g
661	802.11h	802.11h
662	NFS	NFS
663	CIFS	CIFS
664	DAFS	DAFS
665	WebDAV	WebDAV
666	HTTP	HTTP
667	FTP	FTP
668	NDMP	NDMP
669	Telnet	Telnet
670	SSH	SSH
671	SM CLP	SM CLP
672	SMTP	SMTP
673	LDAP	LDAP
674	RDP	RDP
675	HTTPS	HTTPS
676	A string that describes the type of ProtocolEndpoint when the Type property of this class (or any of its subclasses) is set to 1 (Other). This property should be set to null when the Type property is any value other than 1.	A string that describes the type of ProtocolEndpoint when the Type property of this class (or any of its subclasses) is set to 1 (Other). This property should be set to null when the Type property is any value other than 1.
677	A communication point from which data can be sent or received. ProtocolEndpoints link system or computer interfaces to LogicalNetworks.	A communication point from which data can be sent or received. ProtocolEndpoints link system or computer interfaces to LogicalNetworks.
678	2.15.0	2.15.0
679	A label or identifier for the LAN Segment to which the Endpoint is connected. If the Endpoint is not currently active/connected or this information is not known, then LANID is NULL.	A label or identifier for the LAN Segment to which the Endpoint is connected. If the Endpoint is not currently active/connected or this information is not known, then LANID is NULL.
680	An indication of the kind of technology used on the LAN. This property is deprecated in lieu of ProtocolType, which is an enumeration inherited from ProtocolEndpoint and which includes the Values specified here.	An indication of the kind of technology used on the LAN. This property is deprecated in lieu of ProtocolType, which is an enumeration inherited from ProtocolEndpoint and which includes the Values specified here.
681	A free-form string that describes the type of technology used on the LAN when the value of the LANType property is equal to 1 (i.e., "Other"). This property is deprecated since its purpose overlaps with OtherTypeDescription, which which is inherited from ProtocolEndpoint.	A free-form string that describes the type of technology used on the LAN when the value of the LANType property is equal to 1 (i.e., "Other"). This property is deprecated since its purpose overlaps with OtherTypeDescription, which which is inherited from ProtocolEndpoint.
682	The principal unicast address used in communication with the LANEndpoint. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.	The principal unicast address used in communication with the LANEndpoint. The MAC address is formatted as twelve hexadecimal digits (e.g., "010203040506"), with each pair representing one of the six octets of the MAC address in "canonical" bit order according to RFC 2469.
683	Other unicast addresses that may be used to communicate with the LANEndpoint.	Other unicast addresses that may be used to communicate with the LANEndpoint.
684	Multicast addresses to which the LANEndpoint listens.	Multicast addresses to which the LANEndpoint listens.
685	The largest information field that may be sent or received by the LANEndpoint.	The largest information field that may be sent or received by the LANEndpoint.
686	Bits	Bits
687	A communication endpoint which, when its associated interface device is connected to a LAN, may send and receive data frames. LANEndpoints include Ethernet, Token Ring and FDDI interfaces.	A communication endpoint which, when its associated interface device is connected to a LAN, may send and receive data frames. LANEndpoints include Ethernet, Token Ring and FDDI interfaces.
688	2.7.0	2.7.0
689	6to4 tunnel interface	6to4 tunnel interface
690	6to4 global settings associated with this interface	6to4 global settings associated with this interface
691	This class represents per-interface 6to4 Configuration settings.	This class represents per-interface 6to4 Configuration settings.
692	Indicates whether DNS64 is enabled or disabled	Indicates whether DNS64 is enabled or disabled
693	If true, do not send quad-A query before sending A query	If true, do not send quad-A query before sending A query
694	Delay in ms between sending quad-A query and A query	Delay in ms between sending quad-A query and A query
695	If true, return synthesized quad-A response even if A record was found	If true, return synthesized quad-A response even if A record was found
696	Mapping of IPv4 address ranges to IPv4 prefixes	Mapping of IPv4 address ranges to IPv4 prefixes
697	List of addresses that DNS64 should not translate	List of addresses that DNS64 should not translate
698	Name of interface on which to send outgoing queries	Name of interface on which to send outgoing queries
699	Names of interfaces on which to accept incoming queries	Names of interfaces on which to accept incoming queries
700	Enable DNS64	Enable DNS64
701	Disable DNS64	Disable DNS64
702	Reset DNS64 configuration	Reset DNS64 configuration
703	Configuration settings for DNS64	Configuration settings for DNS64
704	The scoping System\'s CreationClassName.	The scoping System\'s CreationClassName.
705	The scoping System\'s Name.	The scoping System\'s Name.
706	An address or other identifying information to uniquely name the LogicalDevice.	An address or other identifying information to uniquely name the LogicalDevice.
707	Boolean indicating that the Device can be power managed. The use of this property has been deprecated. Instead, the existence of an associated PowerManagementCapabilities class (associated using the ElementCapabilities relationhip) indicates that power management is supported.	Boolean indicating that the Device can be power managed. The use of this property has been deprecated. Instead, the existence of an associated PowerManagementCapabilities class (associated using the ElementCapabilities relationhip) indicates that power management is supported.
708	An enumerated array describing the power management capabilities of the Device. The use of this property has been deprecated. Instead, the PowerCapabilites property in an associated PowerManagementCapabilities class should be used.	An enumerated array describing the power management capabilities of the Device. The use of this property has been deprecated. Instead, the PowerCapabilites property in an associated PowerManagementCapabilities class should be used.
709	Power Saving Modes Entered Automatically	Power Saving Modes Entered Automatically
710	Power State Settable	Power State Settable
711	Power Cycling Supported	Power Cycling Supported
712	Timed Power On Supported	Timed Power On Supported
713	The primary availability and status of the Device. (Additional status information can be specified using the Additional Availability array property.) For example, the Availability property indicates that the Device is running and has full power (value=3), or is in a warning (4), test (5), degraded (10) or power save state (values 13-15 and 17). Regarding the Power Save states, these are defined as follows: Value 13 ("Power Save - Unknown") indicates that the Device is known to be in a power save mode, but its exact status in this mode is unknown; 14 ("Power Save - Low Power Mode") indicates that the Device is in a power save state but still functioning, and may exhibit degraded performance; 15 ("Power Save - Standby") describes that the Device is not functioning but could be brought to full power \'quickly\'; and value 17 ("Power Save - Warning") indicates that the Device is in a warning state, though also in a power save mode.	The primary availability and status of the Device. (Additional status information can be specified using the Additional Availability array property.) For example, the Availability property indicates that the Device is running and has full power (value=3), or is in a warning (4), test (5), degraded (10) or power save state (values 13-15 and 17). Regarding the Power Save states, these are defined as follows: Value 13 ("Power Save - Unknown") indicates that the Device is known to be in a power save mode, but its exact status in this mode is unknown; 14 ("Power Save - Low Power Mode") indicates that the Device is in a power save state but still functioning, and may exhibit degraded performance; 15 ("Power Save - Standby") describes that the Device is not functioning but could be brought to full power \'quickly\'; and value 17 ("Power Save - Warning") indicates that the Device is in a warning state, though also in a power save mode.
714	Running/Full Power	Running/Full Power
715	Warning	Warning
716	Power Off	Power Off
717	Off Line	Off Line
718	Off Duty	Off Duty
719	Not Installed	Not Installed
720	Install Error	Install Error
721	Power Save - Unknown	Power Save - Unknown
722	Power Save - Low Power Mode	Power Save - Low Power Mode
723	Power Save - Standby	Power Save - Standby
724	Power Cycle	Power Cycle
725	Power Save - Warning	Power Save - Warning
726	Paused	Paused
727	Not Ready	Not Ready
728	Not Configured	Not Configured
729	Quiesced	Quiesced
730	The StatusInfo property indicates whether the Logical Device is in an enabled (value = 3), disabled (value = 4) or some other (1) or unknown (2) state. If this property does not apply to the LogicalDevice, the value, 5 ("Not Applicable"), should be used. StatusInfo has been deprecated in lieu of a more clearly named property with additional enumerated values (EnabledState), that is inherited from ManagedSystemElement. If a Device is ("Enabled")(value=3), it has been powered up, and is configured and operational. The Device may or may not be functionally active, depending on whether its Availability (or AdditionalAvailability) indicate that it is ("Running/Full Power")(value=3) or ("Off line") (value=8). In an enabled but offline mode, a Device may be performing out-of-band requests, such as running Diagnostics. If ("Disabled") StatusInfo value=4), a Device can only be "enabled" or powered off. In a personal computer environment, ("Disabled") means that the Device\'s driver is not available in the stack. In other environments, a Device can be disabled by removing its configuration file. A disabled device is physically present in a System and consuming resources, but can not be communicated with until a load of a driver, a load of a configuration file or some other "enabling" activity has occurred.	The StatusInfo property indicates whether the Logical Device is in an enabled (value = 3), disabled (value = 4) or some other (1) or unknown (2) state. If this property does not apply to the LogicalDevice, the value, 5 ("Not Applicable"), should be used. StatusInfo has been deprecated in lieu of a more clearly named property with additional enumerated values (EnabledState), that is inherited from ManagedSystemElement. If a Device is ("Enabled")(value=3), it has been powered up, and is configured and operational. The Device may or may not be functionally active, depending on whether its Availability (or AdditionalAvailability) indicate that it is ("Running/Full Power")(value=3) or ("Off line") (value=8). In an enabled but offline mode, a Device may be performing out-of-band requests, such as running Diagnostics. If ("Disabled") StatusInfo value=4), a Device can only be "enabled" or powered off. In a personal computer environment, ("Disabled") means that the Device\'s driver is not available in the stack. In other environments, a Device can be disabled by removing its configuration file. A disabled device is physically present in a System and consuming resources, but can not be communicated with until a load of a driver, a load of a configuration file or some other "enabling" activity has occurred.
731	LastErrorCode captures the last error code reported by the LogicalDevice.	LastErrorCode captures the last error code reported by the LogicalDevice.
732	ErrorDescription is a free-form string supplying more information about the error recorded in LastErrorCode, and information on any corrective actions that may be taken.	ErrorDescription is a free-form string supplying more information about the error recorded in LastErrorCode, and information on any corrective actions that may be taken.
733	ErrorCleared is a boolean property indicating that the error reported in LastErrorCode is now cleared.	ErrorCleared is a boolean property indicating that the error reported in LastErrorCode is now cleared.
734	OtherIdentifyingInfo captures additional data, beyond DeviceID information, that could be used to identify a LogicalDevice. One example would be to hold the Operating System\'s user friendly name for the Device in this property.	OtherIdentifyingInfo captures additional data, beyond DeviceID information, that could be used to identify a LogicalDevice. One example would be to hold the Operating System\'s user friendly name for the Device in this property.
735	The number of consecutive hours that this Device has been powered, since its last power cycle.	The number of consecutive hours that this Device has been powered, since its last power cycle.
736	Hours	Hours
737	The total number of hours that this Device has been powered.	The total number of hours that this Device has been powered.
738	An array of free-form strings providing explanations and details behind the entries in the OtherIdentifyingInfo array. Note, each entry of this array is related to the entry in OtherIdentifyingInfo that is located at the same index.	An array of free-form strings providing explanations and details behind the entries in the OtherIdentifyingInfo array. Note, each entry of this array is related to the entry in OtherIdentifyingInfo that is located at the same index.
739	Additional availability and status of the Device, beyond that specified in the Availability property. The Availability property denotes the primary status and availability of the Device. In some cases, this will not be sufficient to denote the complete status of the Device. In those cases, the AdditionalAvailability property can be used to provide further information. For example, a Device\'s primary Availability may be "Off line" (value=8), but it may also be in a low power state (AdditonalAvailability value=14), or the Device could be running Diagnostics (AdditionalAvailability value=5, "In Test").	Additional availability and status of the Device, beyond that specified in the Availability property. The Availability property denotes the primary status and availability of the Device. In some cases, this will not be sufficient to denote the complete status of the Device. In those cases, the AdditionalAvailability property can be used to provide further information. For example, a Device\'s primary Availability may be "Off line" (value=8), but it may also be in a low power state (AdditonalAvailability value=14), or the Device could be running Diagnostics (AdditionalAvailability value=5, "In Test").
740	The MaxQuiesceTime property has been deprecated. When evaluating the use of Quiesce, it was determine that this single property is not adequate for describing when a device will automatically exit a quiescent state. In fact, the most likely scenario for a device to exit a quiescent state was determined to be based on the number of outstanding requests queued rather than on a maximum time. This will be re-evaluated and repositioned later. Maximum time in milliseconds, that a Device can run in a "Quiesced" state. A Device\'s state is defined in its Availability and AdditionalAvailability properties, where "Quiesced" is conveyed by the value 21. What occurs at the end of the time limit is device-specific. The Device may unquiesce, may offline or take other action. A value of 0 indicates that a Device can remain quiesced indefinitely.	The MaxQuiesceTime property has been deprecated. When evaluating the use of Quiesce, it was determine that this single property is not adequate for describing when a device will automatically exit a quiescent state. In fact, the most likely scenario for a device to exit a quiescent state was determined to be based on the number of outstanding requests queued rather than on a maximum time. This will be re-evaluated and repositioned later. Maximum time in milliseconds, that a Device can run in a "Quiesced" state. A Device\'s state is defined in its Availability and AdditionalAvailability properties, where "Quiesced" is conveyed by the value 21. What occurs at the end of the time limit is device-specific. The Device may unquiesce, may offline or take other action. A value of 0 indicates that a Device can remain quiesced indefinitely.
741	MilliSeconds	MilliSeconds
742	Sets the power state of the Device. The use of this method has been deprecated. Instead, use the SetPowerState method in the associated PowerManagementService class.	Sets the power state of the Device. The use of this method has been deprecated. Instead, use the SetPowerState method in the associated PowerManagementService class.
743	The power state to set.	The power state to set.
744	Full Power	Full Power
745	Power Save - Other	Power Save - Other
746	Time indicates when the power state should be set, either as a regular date-time value or as an interval value (where the interval begins when the method invocation is received.	Time indicates when the power state should be set, either as a regular date-time value or as an interval value (where the interval begins when the method invocation is received.
747	Requests a reset of the LogicalDevice. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.	Requests a reset of the LogicalDevice. The return value should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
748	The EnableDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method. Requests that the LogicalDevice be enabled ("Enabled" input parameter = TRUE) or disabled (= FALSE). If successful, the Device\'s StatusInfo/EnabledState properties should reflect the desired state (enabled/disabled). Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the EnableDevice method should set the RequestedState property appropriately. The return code should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.	The EnableDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method. Requests that the LogicalDevice be enabled ("Enabled" input parameter = TRUE) or disabled (= FALSE). If successful, the Device\'s StatusInfo/EnabledState properties should reflect the desired state (enabled/disabled). Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the EnableDevice method should set the RequestedState property appropriately. The return code should be 0 if the request was successfully executed, 1 if the request is not supported and some other value if an error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
749	If TRUE enable the device, if FALSE disable the device.	If TRUE enable the device, if FALSE disable the device.
750	The OnlineDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method. Requests that the LogicalDevice be brought online ("Online" input parameter = TRUE) or taken offline (= FALSE). "Online" indicates that the Device is ready to accept requests, and is operational and fully functioning. In this case, the Device\'s Availability property would be set to a value of 3 ("Running/Full Power"). "Offline" indicates that a Device is powered up and operational, but not processing functional requests. In an offline state, a Device may be capable of running diagnostics or generating operational alerts. For example, when the "Offline" button is pushed on a Printer, the Device is no longer available to process print jobs, but could be available for diagnostics or maintenance. If this method is successful, the Device\'s Availability and AdditionalAvailability properties should reflect the updated status. If a failure occurs trying to bring the Device online or offline, it should remain in its current state. IE, the request, if unsuccessful, should not leave the Device in an indeterminate state. When bringing a Device back "Online", from an "Offline" mode, the Device should be restored to its last "Online" state, if at all possible. Only a Device that has an EnabledState/StatusInfo of "Enabled" and has been configured can be brought online or taken offline. OnlineDevice should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier. Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the OnlineDevice method should set the RequestedState property appropriately.	The OnlineDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method. Requests that the LogicalDevice be brought online ("Online" input parameter = TRUE) or taken offline (= FALSE). "Online" indicates that the Device is ready to accept requests, and is operational and fully functioning. In this case, the Device\'s Availability property would be set to a value of 3 ("Running/Full Power"). "Offline" indicates that a Device is powered up and operational, but not processing functional requests. In an offline state, a Device may be capable of running diagnostics or generating operational alerts. For example, when the "Offline" button is pushed on a Printer, the Device is no longer available to process print jobs, but could be available for diagnostics or maintenance. If this method is successful, the Device\'s Availability and AdditionalAvailability properties should reflect the updated status. If a failure occurs trying to bring the Device online or offline, it should remain in its current state. IE, the request, if unsuccessful, should not leave the Device in an indeterminate state. When bringing a Device back "Online", from an "Offline" mode, the Device should be restored to its last "Online" state, if at all possible. Only a Device that has an EnabledState/StatusInfo of "Enabled" and has been configured can be brought online or taken offline. OnlineDevice should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier. Note that this method\'s function overlaps with the RequestedState property. RequestedState was added to the model to maintain a record (i.e., a persisted value) of the last state request. Invoking the OnlineDevice method should set the RequestedState property appropriately.
751	If TRUE, take the device online, if FALSE, take the device OFFLINE.	If TRUE, take the device online, if FALSE, take the device OFFLINE.
752	The QuiesceDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method. Requests that the LogicalDevice cleanly cease all current activity ("Quiesce" input parameter = TRUE) or resume activity (= FALSE). For this method to quiesce a Device, that Device should have an Availability (or Additional Availability) of "Running/Full Power" (value=3) and an EnabledStatus/StatusInfo of "Enabled". For example, if quiesced, a Device may then be offlined for diagnostics, or disabled for power off and hot swap. For the method to "unquiesce" a Device, that Device should have an Availability (or AdditionalAvailability) of "Quiesced" (value=21) and an EnabledStatus/StatusInfo of "Enabled". In this case, the Device would be returned to an "Enabled" and "Running/Full Power" status. The method\'s return code should indicate the success or failure of the quiesce. It should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.	The QuiesceDevice method has been deprecated in lieu of the more general RequestStateChange method that directly overlaps with the functionality provided by this method. Requests that the LogicalDevice cleanly cease all current activity ("Quiesce" input parameter = TRUE) or resume activity (= FALSE). For this method to quiesce a Device, that Device should have an Availability (or Additional Availability) of "Running/Full Power" (value=3) and an EnabledStatus/StatusInfo of "Enabled". For example, if quiesced, a Device may then be offlined for diagnostics, or disabled for power off and hot swap. For the method to "unquiesce" a Device, that Device should have an Availability (or AdditionalAvailability) of "Quiesced" (value=21) and an EnabledStatus/StatusInfo of "Enabled". In this case, the Device would be returned to an "Enabled" and "Running/Full Power" status. The method\'s return code should indicate the success or failure of the quiesce. It should return 0 if successful, 1 if the request is not supported at all, 2 if the request is not supported due to the current state of the Device, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
753	If set to TRUE then cleanly cease all activity, if FALSE resume activity.	If set to TRUE then cleanly cease all activity, if FALSE resume activity.
754	Requests that the Device capture its current configuration, setup and/or state information in a backing store. The goal would be to use this information at a later time (via the RestoreProperties method), to return a Device to its present "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.	Requests that the Device capture its current configuration, setup and/or state information in a backing store. The goal would be to use this information at a later time (via the RestoreProperties method), to return a Device to its present "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
755	Requests that the Device re-establish its configuration, setup and/or state information from a backing store. The intent is to capture this information at an earlier time (via the SaveProperties method), and use it to return a Device to this earlier "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.	Requests that the Device re-establish its configuration, setup and/or state information from a backing store. The intent is to capture this information at an earlier time (via the SaveProperties method), and use it to return a Device to this earlier "condition". This method may not be supported by all Devices. The method should return 0 if successful, 1 if the request is not supported, and some other value if any other error occurred. In a subclass, the set of possible return codes could be specified, using a ValueMap qualifier on the method. The strings to which the ValueMap contents are \'translated\' may also be specified in the subclass as a Values array qualifier.
756	An abstraction or emulation of a hardware entity, that may or may not be Realized in physical hardware. Any characteristics of a LogicalDevice that are used to manage its operation or configuration are contained in, or associated with, the LogicalDevice object. Examples of the operational properties of a Printer would be paper sizes supported, or detected errors. Examples of the configuration properties of a Sensor Device would be threshold settings. Various configurations could exist for a LogicalDevice. These configurations could be contained in Setting objects and associated with the LogicalDevice.	An abstraction or emulation of a hardware entity, that may or may not be Realized in physical hardware. Any characteristics of a LogicalDevice that are used to manage its operation or configuration are contained in, or associated with, the LogicalDevice object. Examples of the operational properties of a Printer would be paper sizes supported, or detected errors. Examples of the configuration properties of a Sensor Device would be threshold settings. Various configurations could exist for a LogicalDevice. These configurations could be contained in Setting objects and associated with the LogicalDevice.
757	2.8.0	2.8.0
758	The bandwidth of the Port in Bits per Second.	The bandwidth of the Port in Bits per Second.
759	Bits per Second	Bits per Second
760	The maximum bandwidth of the Port in Bits per Second.	The maximum bandwidth of the Port in Bits per Second.
761	The requested bandwidth of the Port in Bits per Second. The actual bandwidth is reported in LogicalPort.Speed.	The requested bandwidth of the Port in Bits per Second. The actual bandwidth is reported in LogicalPort.Speed.
762	In some circumstances, a LogicalPort might be identifiable as a front end or back end port. An example of this situation would be a storage array that might have back end ports to communicate with disk drives and front end ports to communicate with hosts. If there is no restriction on the use of the port, then the value should be set to \'not restricted\'.	In some circumstances, a LogicalPort might be identifiable as a front end or back end port. An example of this situation would be a storage array that might have back end ports to communicate with disk drives and front end ports to communicate with hosts. If there is no restriction on the use of the port, then the value should be set to \'not restricted\'.
763	Front-end only	Front-end only
764	Back-end only	Back-end only
765	Not restricted	Not restricted
766	PortType is defined to force consistent naming of the \'type\' property in subclasses and to guarantee unique enum values for all instances of NetworkPort. When set to 1 ("Other"), related property OtherPortType contains a string description of the type of port. A range of values, DMTF_Reserved, has been defined that allows subclasses to override and define their specific types of ports.	PortType is defined to force consistent naming of the \'type\' property in subclasses and to guarantee unique enum values for all instances of NetworkPort. When set to 1 ("Other"), related property OtherPortType contains a string description of the type of port. A range of values, DMTF_Reserved, has been defined that allows subclasses to override and define their specific types of ports.
767	Describes the type of module, when PortType is set to 1 ("Other").	Describes the type of module, when PortType is set to 1 ("Other").
768	The abstraction of a port or connection point of a Device. This object should be instantiated when the Port has independent management characteristics from the Device that includes it. Examples are a Fibre Channel Port and a USB Port.	The abstraction of a port or connection point of a Device. This object should be instantiated when the Port has independent management characteristics from the Device that includes it. Examples are a Fibre Channel Port and a USB Port.
769	The current bandwidth of the Port in Bits per Second. For ports that vary in bandwidth or for those where no accurate estimation can be made, this property should contain the nominal bandwidth.	The current bandwidth of the Port in Bits per Second. For ports that vary in bandwidth or for those where no accurate estimation can be made, this property should contain the nominal bandwidth.
770	Note: The use of this property is deprecated in lieu of CIM_LogicalPort.PortType. Deprecated description: The type of module, when PortType is set to 1 ("Other".)	Note: The use of this property is deprecated in lieu of CIM_LogicalPort.PortType. Deprecated description: The type of module, when PortType is set to 1 ("Other".)
771	NetworkPorts are often numbered relative to either a logical module or a network element.	NetworkPorts are often numbered relative to either a logical module or a network element.
772	An enumeration of the types of links. When set to 1 ("Other"), the related property OtherLinkTechnology contains a string description of the type of link.	An enumeration of the types of links. When set to 1 ("Other"), the related property OtherLinkTechnology contains a string description of the type of link.
773	IB	IB
774	FC	FC
775	Token Ring	Token Ring
776	Infrared	Infrared
777	BlueTooth	BlueTooth
778	Wireless LAN	Wireless LAN
779	A string value that describes LinkTechnology when it is set to 1, "Other".	A string value that describes LinkTechnology when it is set to 1, "Other".
780	PermanentAddress defines the network address that is hardcoded into a port. This \'hardcoded\' address can be changed using a firmware upgrade or a software configuration. When this change is made, the field should be updated at the same time. PermanentAddress should be left blank if no \'hardcoded\' address exists for the NetworkAdapter.	PermanentAddress defines the network address that is hardcoded into a port. This \'hardcoded\' address can be changed using a firmware upgrade or a software configuration. When this change is made, the field should be updated at the same time. PermanentAddress should be left blank if no \'hardcoded\' address exists for the NetworkAdapter.
781	An array of strings that indicates the network addresses for the port.	An array of strings that indicates the network addresses for the port.
782	Boolean that indicates that the port is operating in full duplex mode.	Boolean that indicates that the port is operating in full duplex mode.
783	A Boolean that indicates whether the NetworkPort is capable of automatically determining the speed or other communications characteristics of the attached network media.	A Boolean that indicates whether the NetworkPort is capable of automatically determining the speed or other communications characteristics of the attached network media.
784	The maximum transmission unit (MTU) that can be supported.	The maximum transmission unit (MTU) that can be supported.
785	Bytes	Bytes
786	The active or negotiated maximum transmission unit (MTU) that can be supported.	The active or negotiated maximum transmission unit (MTU) that can be supported.
787	NetworkPort is the logical representation of network communications hardware such as a physical connector and the setup or operation of the network chips, at the lowest layers of a network stack.	NetworkPort is the logical representation of network communications hardware such as a physical connector and the setup or operation of the network chips, at the lowest layers of a network stack.
788	Network interface on which DNS queries are sent or received	Network interface on which DNS queries are sent or received
789	DNS64 settings associated with this interface	DNS64 settings associated with this interface
790	Association between DNS64 settings and accept/send interfaces	Association between DNS64 settings and accept/send interfaces
791	Number of successful AAAA queries	Number of successful AAAA queries
792	Number of failed AAAA queries	Number of failed AAAA queries
793	Number of synthesized AAAA queries	Number of synthesized AAAA queries
794	Number of translated PTR queries	Number of translated PTR queries
795	Number of succeeded non-AAAA queries	Number of succeeded non-AAAA queries
796	Number of failed non-AAAA queries	Number of failed non-AAAA queries
797	Query counters for DNS64	Query counters for DNS64
798	Configuration type of this instance	Configuration type of this instance
799	Local	Local
800	GroupPolicy	GroupPolicy
801	ProfileGP	ProfileGP
802	Type of the interface	Type of the interface
803	Client	Client
804	Server	Server
805	State of the interface	State of the interface
806	Default	Default
807	Authentication mode	Authentication mode
808	None	None
809	Certificates	Certificates
810	Url on which the server interface listens for HTTP(S) requests OR Url to which the client interface sends HTTP(S) requests	Url on which the server interface listens for HTTP(S) requests OR Url to which the client interface sends HTTP(S) requests
811	Friendly name of the profile	Friendly name of the profile
812	Indicates whether the profile is active or not	Indicates whether the profile is active or not
813	Toggles Strong Certificate revocation list checking	Toggles Strong Certificate revocation list checking
814	Policy store in which this configuration object is stored	Policy store in which this configuration object is stored
815	Manually activate specified IP-HTTPs profile	Manually activate specified IP-HTTPs profile
816	Disable manual activation of IP-HTTPs profile	Disable manual activation of IP-HTTPs profile
817	Add HTTP SSL certificate	Add HTTP SSL certificate
818	Remove all HTTP SSL certificates	Remove all HTTP SSL certificates
819	Rename IP-HTTPs profile	Rename IP-HTTPs profile
820	Reset IP-HTTPs configuration	Reset IP-HTTPs configuration
821	Configuration settings for IP-HTTPs	Configuration settings for IP-HTTPs
822	IP-HTTPs tunnel interface	IP-HTTPs tunnel interface
823	IP-HTTPs global settings associated with this interface	IP-HTTPs global settings associated with this interface
824	Status of the IP-HTTPs interface	Status of the IP-HTTPs interface
825	Last error code for the IP-HTTPs interface	Last error code for the IP-HTTPs interface
826	This class represents per-interface IP-HTTPs Configuration settings.	This class represents per-interface IP-HTTPs Configuration settings.
827	PolicyStore property defines the store to retrieve the ISATAP configuration policy.	PolicyStore property defines the store to retrieve the ISATAP configuration policy.
828	Describes the ISATAP service state. One of the following values: disabled, enabled or default.	Describes the ISATAP service state. One of the following values: disabled, enabled or default.
829	Name of the ISATAP router.	Name of the ISATAP router.
830	The state of the ISATAP resolution. One of the following values: disabled, enabled, default.	The state of the ISATAP resolution. One of the following values: disabled, enabled, default.
831	Reset the ISATAP configuration.	Reset the ISATAP configuration.
832	This class represents global ISATAP Configuration shared across all ISATAP interfaces.	This class represents global ISATAP Configuration shared across all ISATAP interfaces.
833	ISATAP tunnel interface	ISATAP tunnel interface
834	ISATAP global settings associated with this interface	ISATAP global settings associated with this interface
835	This class represents per-interface ISATAP Configuration settings.	This class represents per-interface ISATAP Configuration settings.
836	Name of this instance of WinNAT	Name of this instance of WinNAT
837	Store in which this configuration object is stored	Store in which this configuration object is stored
838	PersistentStore	PersistentStore
839	ActiveStore	ActiveStore
840	Indicates whether NAT is enabled or disabled	Indicates whether NAT is enabled or disabled
841	Names of inbound interfaces	Names of inbound interfaces
842	Names of outbound interfaces	Names of outbound interfaces
843	Mapping of IPv4 address ranges to IPv6 prefixes	Mapping of IPv4 address ranges to IPv6 prefixes
844	Dedicated IPv4 address pool and port range	Dedicated IPv4 address pool and port range
845	Idle timout for established TCP sessions	Idle timout for established TCP sessions
846	Enable NAT64	Enable NAT64
847	Disable NAT64	Disable NAT64
848	Configuration settings for NAT	Configuration settings for NAT
849	Network interface on which NAT64 operates	Network interface on which NAT64 operates
850	NAT64 settings associated with this interface	NAT64 settings associated with this interface
851	Association between NAT64 settings and inbound/outbound interfaces	Association between NAT64 settings and inbound/outbound interfaces
852	Transport protocol being translated	Transport protocol being translated
853	Inbound address and port	Inbound address and port
854	Outbound address and port	Outbound address and port
855	NAT outbound address and port	NAT outbound address and port
856	Current active sessions for NAT	Current active sessions for NAT
857	PolicyStore property defines the store to retrieve the Teredo configuration policy.	PolicyStore property defines the store to retrieve the Teredo configuration policy.
858	Describes the Teredo service. One of the following values: disabled, client, enterpriseclient, natawareclient, server, default.	Describes the Teredo service. One of the following values: disabled, client, enterpriseclient, natawareclient, server, default.
859	relay	relay
860	client	client
861	server	server
862	enterpriseclient	enterpriseclient
863	natawareclient	natawareclient
864	Describes the name or IPv4 address of the Teredo server.	Describes the name or IPv4 address of the Teredo server.
865	Client refresh interval (in seconds).	Client refresh interval (in seconds).
866	Client's UDP port.	Client's UDP port.
867	IPv4 address of the server virtual ip. Not applicable if running as teredo client.	IPv4 address of the server virtual ip. Not applicable if running as teredo client.
868	This policy setting allows you to set Teredo to be ready to communicate, a process referred to as qualification. By default, Teredo enters a dormant state when not in use. The qualification process brings it out of a dormant state.	This policy setting allows you to set Teredo to be ready to communicate, a process referred to as qualification. By default, Teredo enters a dormant state when not in use. The qualification process brings it out of a dormant state.
869	If enabled, bypasses the tunnel miniport and IPv4 routing layer for high throughput on the Teredo Relay functionality of the Teredo Server.	If enabled, bypasses the tunnel miniport and IPv4 routing layer for high throughput on the Teredo Relay functionality of the Teredo Server.
870	Reset the Teredo configuration.	Reset the Teredo configuration.
871	NetTeredoConfiguration represents global Teredo configuration shared across all Teredo interfaces.	NetTeredoConfiguration represents global Teredo configuration shared across all Teredo interfaces.
872	Teredo tunnel interface	Teredo tunnel interface
873	Teredo global settings associated with this interface	Teredo global settings associated with this interface
874	Specifies the state of the teredo interface	Specifies the state of the teredo interface
875	Specifies the error of the teredo interface	Specifies the error of the teredo interface
876	This class represents per-interface Teredo Configuration settings.	This class represents per-interface Teredo Configuration settings.
0x1	Performing operation %1 on Target %2	Performing operation %1 on Target %2
0x2	Enabling site %1 for DirectAccess connectivity	Enabling site %1 for DirectAccess connectivity
0x3	Disabling manual site selection for DirectAccess connectivity	Disabling manual site selection for DirectAccess connectivity
0x4	Invalid parameter: %1.	Invalid parameter: %1.
0x5	Latency must be less than 1000ms.	Latency must be less than 1000ms.
0x6	Each item in %1 must be of the form \"%2\".	Each item in %1 must be of the form \"%2\".
0x7	Only one %1 is supported.	Only one %1 is supported.
0x8	The specified interface was not found on the system.	The specified interface was not found on the system.
0x9	%1 must be a valid IPv6 prefix.	%1 must be a valid IPv6 prefix.
0xA	Failed to notify IP Helper Service of changes to local configuration.	Failed to notify IP Helper Service of changes to local configuration.
0xB	This functionality is not supported on client SKUs.	This functionality is not supported on client SKUs.
0xC	The WinNAT service is stopped. Please start the service to display configuration from active store.	The WinNAT service is stopped. Please start the service to display configuration from active store.
0xD	Failed to start WinNAT service.	Failed to start WinNAT service.
0xE	%1 cannot contain a semicolon.	%1 cannot contain a semicolon.
0xF	Only the following prefix lengths are allowed for NAT64: 32, 40, 48, 56, 64, and 96.	Only the following prefix lengths are allowed for NAT64: 32, 40, 48, 56, 64, and 96.
0x10	Ports in port range must be in the range 1024-65535.	Ports in port range must be in the range 1024-65535.
0x11	To specify %1, %2 must also have a valid value.	To specify %1, %2 must also have a valid value.
0x12	%1 and %2 cannot be specified at the same time.	%1 and %2 cannot be specified at the same time.
0x13	Must specify required parameter %1.	Must specify required parameter %1.
0x14	Either %1 or %2 must be specified.	Either %1 or %2 must be specified.
0x15	The configuration has been corrupted.	The configuration has been corrupted.
0x16	Cannot create or modify instances in the specified policy store.	Cannot create or modify instances in the specified policy store.
0x17	The specified %1 is already in use.	The specified %1 is already in use.
0x18	None of the specified entry point ranges match the entry point IP address.	None of the specified entry point ranges match the entry point IP address.
0x19	The specified entry point ranges are not the best match for the entry point IP address.	The specified entry point ranges are not the best match for the entry point IP address.
0x1A	Entry point override has been restricted by your domain administrator.	Entry point override has been restricted by your domain administrator.
0x1B	Network Connectivity Assistant service is stopped or not responding.	Network Connectivity Assistant service is stopped or not responding.
0x1C	ServerShunt and TCP Chimney can't be enabled together. TCP Chimney must be disabled for this operation.	ServerShunt and TCP Chimney can't be enabled together. TCP Chimney must be disabled for this operation.
0x1D	No entry points found with name equal to \"%1\".	No entry points found with name equal to \"%1\".
0x1E	The TCP mapping timeout cannot be less than 30 minutes.	The TCP mapping timeout cannot be less than 30 minutes.
0x1F	State cannot be set to OutsideEnabled for server interfaces.	State cannot be set to OutsideEnabled for server interfaces.

File Name:	netttcim.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-i..ation-net.resources_31bf3856ad364e35_10.0.15063.0_en-us_a43f798bbebe0009\
File Size:	170 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:	173568
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:	English (U.S.)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	Transition Technology WMI Objects
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	netttcim.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	netttcim.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Directory:	%WINDIR%\WinSxS\x86_microsoft-windows-i..ation-net.resources_31bf3856ad364e35_10.0.15063.0_en-us_4820de0806608ed3\

netttcim.dll.mui is Multilingual User Interface resource file that contain English (U.S.) language for file netttcim.dll (Transition Technology WMI Objects).

File Description:	Transition Technology WMI Objects
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	netttcim.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	netttcim.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x409, 1200