NetTCPIP.dll.mui TCPIP WMI Provider aa1d6aeabeeb9c31e1a1325081b9c2cc

File name:	NetTCPIP.dll.mui
Size:	225792 byte
MD5:	aa1d6aeabeeb9c31e1a1325081b9c2cc
SHA1:	8bf8c16d9930778dd6b6afd56a43d97d6be0c240
SHA256:	9184a363de273cf6473c7d124b4137d45c56ab07deaf2b449aace37b4a3da6c9
Operating systems:	Windows 10
Extension:	MUI

If an error occurred or the following message in Finnish 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	Finnish	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. 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 creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This 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 resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance\'s NameSpace. 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 creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This 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 resultant InstanceID is not re-used across any InstanceIDs produced by this or other providers for this instance\'s NameSpace. For DMTF defined instances, the \'preferred\' algorithm MUST be used with the set to \'CIM\'.
8	The address which serves as the destination to be reached.	The address which serves as the destination to be reached.
9	The specific administrative distance of this route, overriding any default distances specified by the system or routing service.	The specific administrative distance of this route, overriding any default distances specified by the system or routing service.
10	RouteMetric provides a numeric indication as to the preference of this route, compared to other routes that reach the same destination.	RouteMetric provides a numeric indication as to the preference of this route, compared to other routes that reach the same destination.
11	TRUE indicates that this is a static route, and FALSE indicates a dynamically-learned route.	TRUE indicates that this is a static route, and FALSE indicates a dynamically-learned route.
12	An enumerated integer indicating whether the route is administrator-defined (value=2), computed (via a routing protocol/algorithm, value=3) or the actual route implemented in the network (value=4). The default is a computed route.	An enumerated integer indicating whether the route is administrator-defined (value=2), computed (via a routing protocol/algorithm, value=3) or the actual route implemented in the network (value=4). The default is a computed route.
13	Administrator Defined Route	Administrator Defined Route
14	Computed Route	Computed Route
15	Actual Route	Actual Route
16	NextHopRoute represents one of a series of \'hops\' to reach a network destination. A route is administratively defined, or calculated/learned by a particular routing process. A ConcreteDependency associaton may be instantiated between a route and its routing service to indicate this. (In this scenario, the route is dependent on the service.)	NextHopRoute represents one of a series of \'hops\' to reach a network destination. A route is administratively defined, or calculated/learned by a particular routing process. A ConcreteDependency associaton may be instantiated between a route and its routing service to indicate this. (In this scenario, the route is dependent on the service.)
17	The destination prefix.	The destination prefix.
18	The user-friendly interface index.	The user-friendly interface index.
19	The user-friendly interface name.	The user-friendly interface name.
20	The next hop address or gateway address.	The next hop address or gateway address.
21	One of the following values: No: Not advertised in Route Advertisements. This is the default. Age: Advertised in Route Advertisements with a finite lifetime. Yes: Advertised in Route Advertisements with an infinite lifetime.	One of the following values: No: Not advertised in Route Advertisements. This is the default. Age: Advertised in Route Advertisements with a finite lifetime. Yes: Advertised in Route Advertisements with an infinite lifetime.
22	No	No
23	Age	Age
24	Yes	Yes
25	Lifetime over which the route is valid. The default value is infinite.	Lifetime over which the route is valid. The default value is infinite.
26	Lifetime over which the route is preferred. The default value is infinite.	Lifetime over which the route is preferred. The default value is infinite.
27	One of the following values: Active: Change only lasts until next boot. Persistent: Change is persistent. This is the default.	One of the following values: Active: Change only lasts until next boot. Persistent: Change is persistent. This is the default.
28	Persistent	Persistent
29	Active	Active
30	To indicate whether the address family for this route is v4 or v6.	To indicate whether the address family for this route is v4 or v6.
31	IPv4	IPv4
32	IPv6	IPv6
33	The routing mechanism via which this route was learned.	The routing mechanism via which this route was learned.
34	Other	Other
35	Local	Local
36	NetMgmt	NetMgmt
37	Icmp	Icmp
38	Egp	Egp
39	Ggp	Ggp
40	Hello	Hello
41	Rip	Rip
42	IsIs	IsIs
43	EsIs	EsIs
44	Igrp	Igrp
45	Bbn	Bbn
46	Ospf	Ospf
47	Bgp	Bgp
48	Idpr	Idpr
49	Eigrp	Eigrp
50	Dvmrp	Dvmrp
51	Rpl	Rpl
52	Dhcp	Dhcp
53	The compartment in which route(s) are located.	The compartment in which route(s) are located.
54	State of the route.	State of the route.
55	Alive	Alive
56	Dead	Dead
57	Probe	Probe
58	The metric of the route's interface.	The metric of the route's interface.
59	Create the Route.	Create the Route.
60	Finds the best local IP address and best route to reach the specified remote address.	Finds the best local IP address and best route to reach the specified remote address.
61	Represents the Route class in TCPIP WMIv2 provider.	Represents the Route class in TCPIP WMIv2 provider.
62	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.
63	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.
64	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.
65	Unknown	Unknown
66	OK	OK
67	Degraded	Degraded
68	Stressed	Stressed
69	Predictive Failure	Predictive Failure
70	Error	Error
71	Non-Recoverable Error	Non-Recoverable Error
72	Starting	Starting
73	Stopping	Stopping
74	Stopped	Stopped
75	In Service	In Service
76	No Contact	No Contact
77	Lost Communication	Lost Communication
78	Aborted	Aborted
79	Dormant	Dormant
80	Supporting Entity in Error	Supporting Entity in Error
81	Completed	Completed
82	Power Mode	Power Mode
83	DMTF Reserved	DMTF Reserved
84	Vendor Reserved	Vendor Reserved
85	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.
86	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.
87	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.
88	Degraded/Warning	Degraded/Warning
89	Minor failure	Minor failure
90	Major failure	Major failure
91	Critical failure	Critical failure
92	Non-recoverable error	Non-recoverable error
93	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.
94	Not Available	Not Available
95	Communication OK	Communication OK
96	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.
97	No Additional Information	No Additional Information
98	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.
99	Servicing	Servicing
100	Migrating	Migrating
101	Emigrating	Emigrating
102	Immigrating	Immigrating
103	Snapshotting	Snapshotting
104	Shutting Down	Shutting Down
105	In Test	In Test
106	Transitioning	Transitioning
107	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.
108	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.
109	2.22.0	2.22.0
110	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.
111	2.6.0	2.6.0
112	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.
113	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.
114	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.
115	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.
116	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.
117	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.
118	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.
119	January	January
120	February	February
121	March	March
122	April	April
123	May	May
124	June	June
125	July	July
126	August	August
127	September	September
128	October	October
129	November	November
130	December	December
131	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.
132	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.
133	-Saturday	-Saturday
134	-Friday	-Friday
135	-Thursday	-Thursday
136	-Wednesday	-Wednesday
137	-Tuesday	-Tuesday
138	-Monday	-Monday
139	-Sunday	-Sunday
140	ExactDayOfMonth	ExactDayOfMonth
141	Sunday	Sunday
142	Monday	Monday
143	Tuesday	Tuesday
144	Wednesday	Wednesday
145	Thursday	Thursday
146	Friday	Friday
147	Saturday	Saturday
148	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.
149	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".
150	Local Time	Local Time
151	UTC Time	UTC Time
152	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.
153	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.
154	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.
155	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.
156	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.
157	Percent	Percent
158	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.
159	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.
160	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.
161	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.
162	Do Not Continue	Do Not Continue
163	Continue With Next Job	Continue With Next Job
164	Re-run Job	Re-run Job
165	Run Recovery Job	Run Recovery Job
166	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").
167	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.
168	Success	Success
169	Not Supported	Not Supported
170	Timeout	Timeout
171	Failed	Failed
172	Access Denied	Access Denied
173	Not Found	Not Found
174	Vendor Specific	Vendor Specific
175	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.
176	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.
177	2.10.0	2.10.0
178	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.
179	Communications Error	Communications Error
180	Quality of Service Error	Quality of Service Error
181	Software Error	Software Error
182	Hardware Error	Hardware Error
183	Environmental Error	Environmental Error
184	Security Error	Security Error
185	Oversubscription Error	Oversubscription Error
186	Unavailable Resource Error	Unavailable Resource Error
187	Unsupported Operation Error	Unsupported Operation Error
188	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.
189	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.
190	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.
191	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.
192	An array containing the dynamic content of the message.	An array containing the dynamic content of the message.
193	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.
194	Information	Information
195	Minor	Minor
196	Major	Major
197	Critical	Critical
198	Fatal/NonRecoverable	Fatal/NonRecoverable
199	An enumerated value that describes the probable cause of the error.	An enumerated value that describes the probable cause of the error.
200	Adapter/Card Error	Adapter/Card Error
201	Application Subsystem Failure	Application Subsystem Failure
202	Bandwidth Reduced	Bandwidth Reduced
203	Connection Establishment Error	Connection Establishment Error
204	Communications Protocol Error	Communications Protocol Error
205	Communications Subsystem Failure	Communications Subsystem Failure
206	Configuration/Customization Error	Configuration/Customization Error
207	Congestion	Congestion
208	Corrupt Data	Corrupt Data
209	CPU Cycles Limit Exceeded	CPU Cycles Limit Exceeded
210	Dataset/Modem Error	Dataset/Modem Error
211	Degraded Signal	Degraded Signal
212	DTE-DCE Interface Error	DTE-DCE Interface Error
213	Enclosure Door Open	Enclosure Door Open
214	Equipment Malfunction	Equipment Malfunction
215	Excessive Vibration	Excessive Vibration
216	File Format Error	File Format Error
217	Fire Detected	Fire Detected
218	Flood Detected	Flood Detected
219	Framing Error	Framing Error
220	HVAC Problem	HVAC Problem
221	Humidity Unacceptable	Humidity Unacceptable
222	I/O Device Error	I/O Device Error
223	Input Device Error	Input Device Error
224	LAN Error	LAN Error
225	Non-Toxic Leak Detected	Non-Toxic Leak Detected
226	Local Node Transmission Error	Local Node Transmission Error
227	Loss of Frame	Loss of Frame
228	Loss of Signal	Loss of Signal
229	Material Supply Exhausted	Material Supply Exhausted
230	Multiplexer Problem	Multiplexer Problem
231	Out of Memory	Out of Memory
232	Output Device Error	Output Device Error
233	Performance Degraded	Performance Degraded
234	Power Problem	Power Problem
235	Pressure Unacceptable	Pressure Unacceptable
236	Processor Problem (Internal Machine Error)	Processor Problem (Internal Machine Error)
237	Pump Failure	Pump Failure
238	Queue Size Exceeded	Queue Size Exceeded
239	Receive Failure	Receive Failure
240	Receiver Failure	Receiver Failure
241	Remote Node Transmission Error	Remote Node Transmission Error
242	Resource at or Nearing Capacity	Resource at or Nearing Capacity
243	Response Time Excessive	Response Time Excessive
244	Retransmission Rate Excessive	Retransmission Rate Excessive
245	Software Program Abnormally Terminated	Software Program Abnormally Terminated
246	Software Program Error (Incorrect Results)	Software Program Error (Incorrect Results)
247	Storage Capacity Problem	Storage Capacity Problem
248	Temperature Unacceptable	Temperature Unacceptable
249	Threshold Crossed	Threshold Crossed
250	Timing Problem	Timing Problem
251	Toxic Leak Detected	Toxic Leak Detected
252	Transmit Failure	Transmit Failure
253	Transmitter Failure	Transmitter Failure
254	Underlying Resource Unavailable	Underlying Resource Unavailable
255	Version Mismatch	Version Mismatch
256	Previous Alert Cleared	Previous Alert Cleared
257	Login Attempts Failed	Login Attempts Failed
258	Software Virus Detected	Software Virus Detected
259	Hardware Security Breached	Hardware Security Breached
260	Denial of Service Detected	Denial of Service Detected
261	Security Credential Mismatch	Security Credential Mismatch
262	Unauthorized Access	Unauthorized Access
263	Alarm Received	Alarm Received
264	Loss of Pointer	Loss of Pointer
265	Payload Mismatch	Payload Mismatch
266	Transmission Error	Transmission Error
267	Excessive Error Rate	Excessive Error Rate
268	Trace Problem	Trace Problem
269	Element Unavailable	Element Unavailable
270	Element Missing	Element Missing
271	Loss of Multi Frame	Loss of Multi Frame
272	Broadcast Channel Failure	Broadcast Channel Failure
273	Invalid Message Received	Invalid Message Received
274	Routing Failure	Routing Failure
275	Backplane Failure	Backplane Failure
276	Identifier Duplication	Identifier Duplication
277	Protection Path Failure	Protection Path Failure
278	Sync Loss or Mismatch	Sync Loss or Mismatch
279	Terminal Problem	Terminal Problem
280	Real Time Clock Failure	Real Time Clock Failure
281	Antenna Failure	Antenna Failure
282	Battery Charging Failure	Battery Charging Failure
283	Disk Failure	Disk Failure
284	Frequency Hopping Failure	Frequency Hopping Failure
285	Loss of Redundancy	Loss of Redundancy
286	Power Supply Failure	Power Supply Failure
287	Signal Quality Problem	Signal Quality Problem
288	Battery Discharging	Battery Discharging
289	Battery Failure	Battery Failure
290	Commercial Power Problem	Commercial Power Problem
291	Fan Failure	Fan Failure
292	Engine Failure	Engine Failure
293	Sensor Failure	Sensor Failure
294	Fuse Failure	Fuse Failure
295	Generator Failure	Generator Failure
296	Low Battery	Low Battery
297	Low Fuel	Low Fuel
298	Low Water	Low Water
299	Explosive Gas	Explosive Gas
300	High Winds	High Winds
301	Ice Buildup	Ice Buildup
302	Smoke	Smoke
303	Memory Mismatch	Memory Mismatch
304	Out of CPU Cycles	Out of CPU Cycles
305	Software Environment Problem	Software Environment Problem
306	Software Download Failure	Software Download Failure
307	Element Reinitialized	Element Reinitialized
308	Logging Problems	Logging Problems
309	Leak Detected	Leak Detected
310	Protection Mechanism Failure	Protection Mechanism Failure
311	Protecting Resource Failure	Protecting Resource Failure
312	Database Inconsistency	Database Inconsistency
313	Authentication Failure	Authentication Failure
314	Breach of Confidentiality	Breach of Confidentiality
315	Cable Tamper	Cable Tamper
316	Delayed Information	Delayed Information
317	Duplicate Information	Duplicate Information
318	Information Missing	Information Missing
319	Information Modification	Information Modification
320	Information Out of Sequence	Information Out of Sequence
321	Key Expired	Key Expired
322	Non-Repudiation Failure	Non-Repudiation Failure
323	Out of Hours Activity	Out of Hours Activity
324	Out of Service	Out of Service
325	Procedural Error	Procedural Error
326	Unexpected Information	Unexpected Information
327	A free-form string describing the probable cause of the error.	A free-form string describing the probable cause of the error.
328	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.
329	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.
330	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.
331	CIMObjectPath	CIMObjectPath
332	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.
333	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.
334	CIM_ERR_FAILED	CIM_ERR_FAILED
335	CIM_ERR_ACCESS_DENIED	CIM_ERR_ACCESS_DENIED
336	CIM_ERR_INVALID_NAMESPACE	CIM_ERR_INVALID_NAMESPACE
337	CIM_ERR_INVALID_PARAMETER	CIM_ERR_INVALID_PARAMETER
338	CIM_ERR_INVALID_CLASS	CIM_ERR_INVALID_CLASS
339	CIM_ERR_NOT_FOUND	CIM_ERR_NOT_FOUND
340	CIM_ERR_NOT_SUPPORTED	CIM_ERR_NOT_SUPPORTED
341	CIM_ERR_CLASS_HAS_CHILDREN	CIM_ERR_CLASS_HAS_CHILDREN
342	CIM_ERR_CLASS_HAS_INSTANCES	CIM_ERR_CLASS_HAS_INSTANCES
343	CIM_ERR_INVALID_SUPERCLASS	CIM_ERR_INVALID_SUPERCLASS
344	CIM_ERR_ALREADY_EXISTS	CIM_ERR_ALREADY_EXISTS
345	CIM_ERR_NO_SUCH_PROPERTY	CIM_ERR_NO_SUCH_PROPERTY
346	CIM_ERR_TYPE_MISMATCH	CIM_ERR_TYPE_MISMATCH
347	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
348	CIM_ERR_INVALID_QUERY	CIM_ERR_INVALID_QUERY
349	CIM_ERR_METHOD_NOT_AVAILABLE	CIM_ERR_METHOD_NOT_AVAILABLE
350	CIM_ERR_METHOD_NOT_FOUND	CIM_ERR_METHOD_NOT_FOUND
351	CIM_ERR_UNEXPECTED_RESPONSE	CIM_ERR_UNEXPECTED_RESPONSE
352	CIM_ERR_INVALID_RESPONSE_DESTINATION	CIM_ERR_INVALID_RESPONSE_DESTINATION
353	CIM_ERR_NAMESPACE_NOT_EMPTY	CIM_ERR_NAMESPACE_NOT_EMPTY
354	CIM_ERR_INVALID_ENUMERATION_CONTEXT	CIM_ERR_INVALID_ENUMERATION_CONTEXT
355	CIM_ERR_INVALID_OPERATION_TIMEOUT	CIM_ERR_INVALID_OPERATION_TIMEOUT
356	CIM_ERR_PULL_HAS_BEEN_ABANDONED	CIM_ERR_PULL_HAS_BEEN_ABANDONED
357	CIM_ERR_PULL_CANNOT_BE_ABANDONED	CIM_ERR_PULL_CANNOT_BE_ABANDONED
358	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
359	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
360	CIM_ERR_SERVER_LIMITS_EXCEEDED	CIM_ERR_SERVER_LIMITS_EXCEEDED
361	CIM_ERR_SERVER_IS_SHUTTING_DOWN	CIM_ERR_SERVER_IS_SHUTTING_DOWN
362	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
363	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.
364	2.22.1	2.22.1
365	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.
366	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\'.
367	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.)
368	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
369	New	New
370	Running	Running
371	Suspended	Suspended
372	Terminated	Terminated
373	Killed	Killed
374	Exception	Exception
375	Service	Service
376	Query Pending	Query Pending
377	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.
378	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.
379	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.
380	Completed with No Error	Completed with No Error
381	Unknown/Unspecified Error	Unknown/Unspecified Error
382	Can NOT complete within Timeout Period	Can NOT complete within Timeout Period
383	Invalid Parameter	Invalid Parameter
384	In Use	In Use
385	Method Parameters Checked - Transition Started	Method Parameters Checked - Transition Started
386	Invalid State Transition	Invalid State Transition
387	Use of Timeout Parameter Not Supported	Use of Timeout Parameter Not Supported
388	Busy	Busy
389	Method Reserved	Method Reserved
390	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.
391	Start	Start
392	Suspend	Suspend
393	Terminate	Terminate
394	Kill	Kill
395	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.
396	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.
397	Unspecified Error	Unspecified Error
398	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.
399	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.
400	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.
401	Enabled	Enabled
402	Disabled	Disabled
403	Not Applicable	Not Applicable
404	Enabled but Offline	Enabled but Offline
405	Deferred	Deferred
406	Quiesce	Quiesce
407	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.
408	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".
409	Shut Down	Shut Down
410	No Change	No Change
411	Offline	Offline
412	Test	Test
413	Reboot	Reboot
414	Reset	Reset
415	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).
416	No Default	No Default
417	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.
418	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.
419	Defer	Defer
420	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.
421	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.
422	Unknown or Unspecified Error	Unknown or Unspecified Error
423	Cannot complete within Timeout Period	Cannot complete within Timeout Period
424	Method Parameters Checked - Job Started	Method Parameters Checked - Job Started
425	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.
426	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.
427	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.
428	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.
429	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.
430	The CreationClassName of the scoping System.	The CreationClassName of the scoping System.
431	The Name of the scoping System.	The Name of the scoping System.
432	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.
433	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.
434	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.
435	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.
436	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.
437	IPX	IPX
438	AppleTalk	AppleTalk
439	DECnet	DECnet
440	SNA	SNA
441	CONP	CONP
442	CLNP	CLNP
443	VINES	VINES
444	XNS	XNS
445	ATM	ATM
446	Frame Relay	Frame Relay
447	Ethernet	Ethernet
448	TokenRing	TokenRing
449	FDDI	FDDI
450	Infiniband	Infiniband
451	Fibre Channel	Fibre Channel
452	ISDN BRI Endpoint	ISDN BRI Endpoint
453	ISDN B Channel Endpoint	ISDN B Channel Endpoint
454	ISDN D Channel Endpoint	ISDN D Channel Endpoint
455	IPv4/v6	IPv4/v6
456	BGP	BGP
457	OSPF	OSPF
458	MPLS	MPLS
459	UDP	UDP
460	TCP	TCP
461	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.
462	Regular 1822	Regular 1822
463	HDH 1822	HDH 1822
464	DDN X.25	DDN X.25
465	RFC877 X.25	RFC877 X.25
466	Ethernet CSMA/CD	Ethernet CSMA/CD
467	ISO 802.3 CSMA/CD	ISO 802.3 CSMA/CD
468	ISO 802.4 Token Bus	ISO 802.4 Token Bus
469	ISO 802.5 Token Ring	ISO 802.5 Token Ring
470	ISO 802.6 MAN	ISO 802.6 MAN
471	StarLAN	StarLAN
472	Proteon 10Mbit	Proteon 10Mbit
473	Proteon 80Mbit	Proteon 80Mbit
474	HyperChannel	HyperChannel
475	LAP-B	LAP-B
476	SDLC	SDLC
477	DS1	DS1
478	E1	E1
479	Basic ISDN	Basic ISDN
480	Primary ISDN	Primary ISDN
481	Proprietary Point-to-Point Serial	Proprietary Point-to-Point Serial
482	PPP	PPP
483	Software Loopback	Software Loopback
484	EON	EON
485	Ethernet 3Mbit	Ethernet 3Mbit
486	NSIP	NSIP
487	SLIP	SLIP
488	Ultra	Ultra
489	DS3	DS3
490	SIP	SIP
491	RS-232	RS-232
492	Parallel	Parallel
493	ARCNet	ARCNet
494	ARCNet Plus	ARCNet Plus
495	MIO X.25	MIO X.25
496	SONET	SONET
497	X.25 PLE	X.25 PLE
498	ISO 802.211c	ISO 802.211c
499	LocalTalk	LocalTalk
500	SMDS DXI	SMDS DXI
501	Frame Relay Service	Frame Relay Service
502	V.35	V.35
503	HSSI	HSSI
504	HIPPI	HIPPI
505	Modem	Modem
506	AAL5	AAL5
507	SONET Path	SONET Path
508	SONET VT	SONET VT
509	SMDS ICIP	SMDS ICIP
510	Proprietary Virtual/Internal	Proprietary Virtual/Internal
511	Proprietary Multiplexor	Proprietary Multiplexor
512	IEEE 802.12	IEEE 802.12
513	HIPPI Interface	HIPPI Interface
514	Frame Relay Interconnect	Frame Relay Interconnect
515	ATM Emulated LAN for 802.3	ATM Emulated LAN for 802.3
516	ATM Emulated LAN for 802.5	ATM Emulated LAN for 802.5
517	ATM Emulated Circuit	ATM Emulated Circuit
518	Fast Ethernet (100BaseT)	Fast Ethernet (100BaseT)
519	ISDN	ISDN
520	V.11	V.11
521	V.36	V.36
522	G703 at 64K	G703 at 64K
523	G703 at 2Mb	G703 at 2Mb
524	QLLC	QLLC
525	Fast Ethernet 100BaseFX	Fast Ethernet 100BaseFX
526	Channel	Channel
527	IEEE 802.11	IEEE 802.11
528	IBM 260/370 OEMI Channel	IBM 260/370 OEMI Channel
529	ESCON	ESCON
530	Data Link Switching	Data Link Switching
531	ISDN S/T Interface	ISDN S/T Interface
532	ISDN U Interface	ISDN U Interface
533	LAP-D	LAP-D
534	IP Switch	IP Switch
535	Remote Source Route Bridging	Remote Source Route Bridging
536	ATM Logical	ATM Logical
537	DS0	DS0
538	DS0 Bundle	DS0 Bundle
539	BSC	BSC
540	Async	Async
541	Combat Net Radio	Combat Net Radio
542	ISO 802.5r DTR	ISO 802.5r DTR
543	Ext Pos Loc Report System	Ext Pos Loc Report System
544	AppleTalk Remote Access Protocol	AppleTalk Remote Access Protocol
545	Proprietary Connectionless	Proprietary Connectionless
546	ITU X.29 Host PAD	ITU X.29 Host PAD
547	ITU X.3 Terminal PAD	ITU X.3 Terminal PAD
548	Frame Relay MPI	Frame Relay MPI
549	ITU X.213	ITU X.213
550	ADSL	ADSL
551	RADSL	RADSL
552	SDSL	SDSL
553	VDSL	VDSL
554	ISO 802.5 CRFP	ISO 802.5 CRFP
555	Myrinet	Myrinet
556	Voice Receive and Transmit	Voice Receive and Transmit
557	Voice Foreign Exchange Office	Voice Foreign Exchange Office
558	Voice Foreign Exchange Service	Voice Foreign Exchange Service
559	Voice Encapsulation	Voice Encapsulation
560	Voice over IP	Voice over IP
561	ATM DXI	ATM DXI
562	ATM FUNI	ATM FUNI
563	ATM IMA	ATM IMA
564	PPP Multilink Bundle	PPP Multilink Bundle
565	IP over CDLC	IP over CDLC
566	IP over CLAW	IP over CLAW
567	Stack to Stack	Stack to Stack
568	Virtual IP Address	Virtual IP Address
569	MPC	MPC
570	IP over ATM	IP over ATM
571	ISO 802.5j Fibre Token Ring	ISO 802.5j Fibre Token Ring
572	TDLC	TDLC
573	Gigabit Ethernet	Gigabit Ethernet
574	HDLC	HDLC
575	LAP-F	LAP-F
576	V.37	V.37
577	X.25 MLP	X.25 MLP
578	X.25 Hunt Group	X.25 Hunt Group
579	Transp HDLC	Transp HDLC
580	Interleave Channel	Interleave Channel
581	FAST Channel	FAST Channel
582	IP (for APPN HPR in IP Networks)	IP (for APPN HPR in IP Networks)
583	CATV MAC Layer	CATV MAC Layer
584	CATV Downstream	CATV Downstream
585	CATV Upstream	CATV Upstream
586	Avalon 12MPP Switch	Avalon 12MPP Switch
587	Tunnel	Tunnel
588	Coffee	Coffee
589	Circuit Emulation Service	Circuit Emulation Service
590	ATM SubInterface	ATM SubInterface
591	Layer 2 VLAN using 802.1Q	Layer 2 VLAN using 802.1Q
592	Layer 3 VLAN using IP	Layer 3 VLAN using IP
593	Layer 3 VLAN using IPX	Layer 3 VLAN using IPX
594	Digital Power Line	Digital Power Line
595	Multimedia Mail over IP	Multimedia Mail over IP
596	DTM	DTM
597	DCN	DCN
598	IP Forwarding	IP Forwarding
599	MSDSL	MSDSL
600	IEEE 1394	IEEE 1394
601	IF-GSN/HIPPI-6400	IF-GSN/HIPPI-6400
602	DVB-RCC MAC Layer	DVB-RCC MAC Layer
603	DVB-RCC Downstream	DVB-RCC Downstream
604	DVB-RCC Upstream	DVB-RCC Upstream
605	ATM Virtual	ATM Virtual
606	MPLS Tunnel	MPLS Tunnel
607	SRP	SRP
608	Voice over ATM	Voice over ATM
609	Voice over Frame Relay	Voice over Frame Relay
610	ISDL	ISDL
611	Composite Link	Composite Link
612	SS7 Signaling Link	SS7 Signaling Link
613	Proprietary P2P Wireless	Proprietary P2P Wireless
614	Frame Forward	Frame Forward
615	RFC1483 Multiprotocol over ATM	RFC1483 Multiprotocol over ATM
616	USB	USB
617	IEEE 802.3ad Link Aggregate	IEEE 802.3ad Link Aggregate
618	BGP Policy Accounting	BGP Policy Accounting
619	FRF .16 Multilink FR	FRF .16 Multilink FR
620	H.323 Gatekeeper	H.323 Gatekeeper
621	H.323 Proxy	H.323 Proxy
622	Multi-Frequency Signaling Link	Multi-Frequency Signaling Link
623	HDSL-2	HDSL-2
624	S-HDSL	S-HDSL
625	DS1 Facility Data Link	DS1 Facility Data Link
626	Packet over SONET/SDH	Packet over SONET/SDH
627	DVB-ASI Input	DVB-ASI Input
628	DVB-ASI Output	DVB-ASI Output
629	Power Line	Power Line
630	Non Facility Associated Signaling	Non Facility Associated Signaling
631	TR008	TR008
632	GR303 RDT	GR303 RDT
633	GR303 IDT	GR303 IDT
634	ISUP	ISUP
635	Proprietary Wireless MAC Layer	Proprietary Wireless MAC Layer
636	Proprietary Wireless Downstream	Proprietary Wireless Downstream
637	Proprietary Wireless Upstream	Proprietary Wireless Upstream
638	HIPERLAN Type 2	HIPERLAN Type 2
639	Proprietary Broadband Wireless Access Point to Mulipoint	Proprietary Broadband Wireless Access Point to Mulipoint
640	SONET Overhead Channel	SONET Overhead Channel
641	Digital Wrapper Overhead Channel	Digital Wrapper Overhead Channel
642	ATM Adaptation Layer 2	ATM Adaptation Layer 2
643	Radio MAC	Radio MAC
644	ATM Radio	ATM Radio
645	Inter Machine Trunk	Inter Machine Trunk
646	MVL DSL	MVL DSL
647	Long Read DSL	Long Read DSL
648	Frame Relay DLCI Endpoint	Frame Relay DLCI Endpoint
649	ATM VCI Endpoint	ATM VCI Endpoint
650	Optical Channel	Optical Channel
651	Optical Transport	Optical Transport
652	Proprietary ATM	Proprietary ATM
653	Voice over Cable	Voice over Cable
654	TE Link	TE Link
655	Q.2931	Q.2931
656	Virtual Trunk Group	Virtual Trunk Group
657	SIP Trunk Group	SIP Trunk Group
658	SIP Signaling	SIP Signaling
659	CATV Upstream Channel	CATV Upstream Channel
660	Econet	Econet
661	FSAN 155Mb PON	FSAN 155Mb PON
662	FSAN 622Mb PON	FSAN 622Mb PON
663	Transparent Bridge	Transparent Bridge
664	Line Group	Line Group
665	Voice E&M Feature Group	Voice E&M Feature Group
666	Voice FGD EANA	Voice FGD EANA
667	Voice DID	Voice DID
668	MPEG Transport	MPEG Transport
669	6To4	6To4
670	GTP	GTP
671	Paradyne EtherLoop 1	Paradyne EtherLoop 1
672	Paradyne EtherLoop 2	Paradyne EtherLoop 2
673	Optical Channel Group	Optical Channel Group
674	HomePNA	HomePNA
675	GFP	GFP
676	ciscoISLvlan	ciscoISLvlan
677	actelisMetaLOOP	actelisMetaLOOP
678	Fcip	Fcip
679	IANA Reserved	IANA Reserved
680	802.11a	802.11a
681	802.11b	802.11b
682	802.11g	802.11g
683	802.11h	802.11h
684	NFS	NFS
685	CIFS	CIFS
686	DAFS	DAFS
687	WebDAV	WebDAV
688	HTTP	HTTP
689	FTP	FTP
690	NDMP	NDMP
691	Telnet	Telnet
692	SSH	SSH
693	SM CLP	SM CLP
694	SMTP	SMTP
695	LDAP	LDAP
696	RDP	RDP
697	HTTPS	HTTPS
698	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.
699	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.
700	2.15.0	2.15.0
701	ProtocolIFType\'s enumeration is limited to IP-related and reserved values for this subclass of ProtocolEndpoint.	ProtocolIFType\'s enumeration is limited to IP-related and reserved values for this subclass of ProtocolEndpoint.
702	The IPv4 address that this ProtocolEndpoint represents.	The IPv4 address that this ProtocolEndpoint represents.
703	The IPv6 address that this ProtocolEndpoint represents.	The IPv6 address that this ProtocolEndpoint represents.
704	The IP address that this ProtocolEndpoint represents, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40). This single property is deprecated to replace it by specific IPv4 and v6 addresses.	The IP address that this ProtocolEndpoint represents, formatted according to the appropriate convention as defined in the AddressType property of this class (e.g., 171.79.6.40). This single property is deprecated to replace it by specific IPv4 and v6 addresses.
705	The mask for the IPv4 address of this ProtocolEndpoint, if one is defined.	The mask for the IPv4 address of this ProtocolEndpoint, if one is defined.
706	The prefix length for the IPv6 address of this Protocol Endpoint, if one is defined.	The prefix length for the IPv6 address of this Protocol Endpoint, if one is defined.
707	An enumeration that describes the format of the Address property. It is deprecated since it is not needed, as the class contains both IPv4 and v6 addresses).	An enumeration that describes the format of the Address property. It is deprecated since it is not needed, as the class contains both IPv4 and v6 addresses).
708	This property explicitly defines support for different versions of the IP protocol, for this Endpoint. It is deprecated since the ProtocolIFType also provides this functionality by describing an endpoint as IPv4 only (value=4096), IPv6 only (value=4097), or IPv4/v6 (value=4098).	This property explicitly defines support for different versions of the IP protocol, for this Endpoint. It is deprecated since the ProtocolIFType also provides this functionality by describing an endpoint as IPv4 only (value=4096), IPv6 only (value=4097), or IPv4/v6 (value=4098).
709	IPv4 Only	IPv4 Only
710	IPv6 Only	IPv6 Only
711	Both IPv4 and IPv6	Both IPv4 and IPv6
712	AddressOrigin identifies the method by which the IP Address, Subnet Mask, and Gateway were assigned to the IPProtocolEndpoint.A value of 3 "Static" shall indicate the values were assigned manually. A value of 4 "DHCP" shall indicate the values were assigned utilizing the Dynamic Host Configuration Protocol. See RFC 2131 and related. A value of 5 "BOOTP" shall indicate the values were assigned utilizing BOOTP. See RFC 951 and related. A value of 6 "IPv4 Link Local" shall indicate the values were assigned using the IPv4 Link Local protocol. See RFC 3927. A value of 7 "DHCPv6" shall indicate the values were assigned using DHCPv6. See RFC 3315. A value of 8 "IPv6 AutoConfig" shall indicate the values were assinged using the IPv6 AutoConfig Protocol. See RFC 4862.	AddressOrigin identifies the method by which the IP Address, Subnet Mask, and Gateway were assigned to the IPProtocolEndpoint.A value of 3 "Static" shall indicate the values were assigned manually. A value of 4 "DHCP" shall indicate the values were assigned utilizing the Dynamic Host Configuration Protocol. See RFC 2131 and related. A value of 5 "BOOTP" shall indicate the values were assigned utilizing BOOTP. See RFC 951 and related. A value of 6 "IPv4 Link Local" shall indicate the values were assigned using the IPv4 Link Local protocol. See RFC 3927. A value of 7 "DHCPv6" shall indicate the values were assigned using DHCPv6. See RFC 3315. A value of 8 "IPv6 AutoConfig" shall indicate the values were assinged using the IPv6 AutoConfig Protocol. See RFC 4862.
713	Static	Static
714	DHCP	DHCP
715	BOOTP	BOOTP
716	IPv4 Link Local	IPv4 Link Local
717	DHCPv6	DHCPv6
718	IPv6AutoConfig	IPv6AutoConfig
719	A ProtocolEndpoint that is dedicated to running IP.	A ProtocolEndpoint that is dedicated to running IP.
720	2.19.1	2.19.1
721	The IP address.	The IP address.
722	To indicate whether the address family for this IP address is v4 or v6.	To indicate whether the address family for this IP address is v4 or v6.
723	One of the following values: Unicast: Marks the address as a unicast address. This is the default. Anycast: Marks the address as an anycast address.	One of the following values: Unicast: Marks the address as a unicast address. This is the default. Anycast: Marks the address as an anycast address.
724	Unicast	Unicast
725	Anycast	Anycast
726	One of the following values: Active: Set only lasts until next boot. Persistent: Set is persistent (default).	One of the following values: Active: Set only lasts until next boot. Persistent: Set is persistent (default).
727	Prefix origin of this address.	Prefix origin of this address.
728	Manual	Manual
729	WellKnown	WellKnown
730	RouterAdvertisement	RouterAdvertisement
731	Suffix origin of this address.	Suffix origin of this address.
732	Link	Link
733	Random	Random
734	Address lifetime state.	Address lifetime state.
735	Invalid	Invalid
736	Tentative	Tentative
737	Duplicate	Duplicate
738	Deprecated	Deprecated
739	Preferred	Preferred
740	Lifetime over which the address is valid. The default value is infinite.	Lifetime over which the address is valid. The default value is infinite.
741	Lifetime over which the address is preferred. The default value is infinite.	Lifetime over which the address is preferred. The default value is infinite.
742	Do not use the address as source address for any outgoing packet unless explictly asked to.	Do not use the address as source address for any outgoing packet unless explictly asked to.
743	Create the IPAddress.	Create the IPAddress.
744	The representation of IPv4 address and IPv6 address.	The representation of IPv4 address and IPv6 address.
745	Access or addressing information or a combination of this information for a remote connection. This information can be a host name, network address, or similar information.	Access or addressing information or a combination of this information for a remote connection. This information can be a host name, network address, or similar information.
746	An enumerated integer that describes the format and interpretation of the AccessInfo property. 206\'Parameterized URL\'- a URL containing ${parameterName} strings. Those strings are intended to be replaced in their entirety by the value of the named parameter. The interpretation of such parameters is not defined by this subclass. As an example use: If a parameter named \'CompanyURL\' has a value of \'www.DMTF.org\' and the value of AccessInfo was \'http:\${CompanyURL}\', then the resultant URL is intended to be \'http:\www.dmtf.org\'.	An enumerated integer that describes the format and interpretation of the AccessInfo property. 206\'Parameterized URL\'- a URL containing ${parameterName} strings. Those strings are intended to be replaced in their entirety by the value of the named parameter. The interpretation of such parameters is not defined by this subclass. As an example use: If a parameter named \'CompanyURL\' has a value of \'www.DMTF.org\' and the value of AccessInfo was \'http:\${CompanyURL}\', then the resultant URL is intended to be \'http:\www.dmtf.org\'.
747	Host Name	Host Name
748	IPv4 Address	IPv4 Address
749	IPv6 Address	IPv6 Address
750	IPX Address	IPX Address
751	DECnet Address	DECnet Address
752	SNA Address	SNA Address
753	Autonomous System Number	Autonomous System Number
754	MPLS Label	MPLS Label
755	IPv4 Subnet Address	IPv4 Subnet Address
756	IPv6 Subnet Address	IPv6 Subnet Address
757	IPv4 Address Range	IPv4 Address Range
758	IPv6 Address Range	IPv6 Address Range
759	Dial String	Dial String
760	Ethernet Address	Ethernet Address
761	Token Ring Address	Token Ring Address
762	ATM Address	ATM Address
763	Frame Relay Address	Frame Relay Address
764	URL	URL
765	FQDN	FQDN
766	User FQDN	User FQDN
767	DER ASN1 DN	DER ASN1 DN
768	DER ASN1 GN	DER ASN1 GN
769	Key ID	Key ID
770	Parameterized URL	Parameterized URL
771	Describes the format when the property InfoFormat is set to 1 (Other).	Describes the format when the property InfoFormat is set to 1 (Other).
772	The AccessContext property identifies the role this RemoteServiceAccessPoint is playing in the hosting system.	The AccessContext property identifies the role this RemoteServiceAccessPoint is playing in the hosting system.
773	Default Gateway	Default Gateway
774	DNS Server	DNS Server
775	SNMP Trap Destination	SNMP Trap Destination
776	MPLS Tunnel Destination	MPLS Tunnel Destination
777	DHCP Server	DHCP Server
778	SMTP Server	SMTP Server
779	LDAP Server	LDAP Server
780	Network Time Protocol (NTP) Server	Network Time Protocol (NTP) Server
781	Management Service	Management Service
782	When the AccessContext property contains a value of 1, "Other" then this is a free form string providing more information about the role of RemoteServiceAccessPoint in the hosting system.	When the AccessContext property contains a value of 1, "Other" then this is a free form string providing more information about the role of RemoteServiceAccessPoint in the hosting system.
783	RemoteServiceAccessPoint describes access or addressing information or a combination of this information for a remote connection that is known to a local network element. This information is scoped or contained by the local network element, because this is the context in which the connection is remote. The relevance of the remote access point and information on its use are described by subclassing RemoteServiceAccessPoint or by associating to it.	RemoteServiceAccessPoint describes access or addressing information or a combination of this information for a remote connection that is known to a local network element. This information is scoped or contained by the local network element, because this is the context in which the connection is remote. The relevance of the remote access point and information on its use are described by subclassing RemoteServiceAccessPoint or by associating to it.
784	2.21.0	2.21.0
785	Network address of neighbor.	Network address of neighbor.
786	User-friendly interface index.	User-friendly interface index.
787	User-friendly interface name.	User-friendly interface name.
788	Link layer address of neighbor.	Link layer address of neighbor.
789	One of the following values: - active: Address will disappear on next boot. - persistent: Address will be persistent. This is the default.	One of the following values: - active: Address will disappear on next boot. - persistent: Address will be persistent. This is the default.
790	Neighbor Discovery State.	Neighbor Discovery State.
791	Unreachable	Unreachable
792	Incomplete	Incomplete
793	Delay	Delay
794	Stale	Stale
795	Reachable	Reachable
796	Permanent	Permanent
797	To indicate whether the address family for this neighbor is v4 or v6.	To indicate whether the address family for this neighbor is v4 or v6.
798	Create the Neighbor.	Create the Neighbor.
799	Represents the Neighbor in TCPIP WMIv2	Represents the Neighbor in TCPIP WMIv2
800	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.
801	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.
802	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.
803	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.
804	Other unicast addresses that may be used to communicate with the LANEndpoint.	Other unicast addresses that may be used to communicate with the LANEndpoint.
805	Multicast addresses to which the LANEndpoint listens.	Multicast addresses to which the LANEndpoint listens.
806	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.
807	Bits	Bits
808	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.
809	2.7.0	2.7.0
810	To indicate whether the address family for this interface is v4 or v6.	To indicate whether the address family for this interface is v4 or v6.
811	Whether forwarding is enabled for incoming packets on this interface. Default is Disabled.	Whether forwarding is enabled for incoming packets on this interface. Default is Disabled.
812	Whether MSS clamping is enabled for outgoing forwarded packets on this interface. Default is Disabled.	Whether MSS clamping is enabled for outgoing forwarded packets on this interface. Default is Disabled.
813	Whether router advertisments are to be sent on this interface. Default is Disabled.	Whether router advertisments are to be sent on this interface. Default is Disabled.
814	The Network Layer MTU of this interface. The default is the natural MTU of the link.	The Network Layer MTU of this interface. The default is the natural MTU of the link.
815	Interface metric, added to route metrics for all routes over the interface. Default is automatic.	Interface metric, added to route metrics for all routes over the interface. Default is automatic.
816	Whether neighbor unreachability detection is enabled. Default depends on type of interface.	Whether neighbor unreachability detection is enabled. Default depends on type of interface.
817	Base reachable time (in ms).	Base reachable time (in ms).
818	Retransmit time (in ms).	Retransmit time (in ms).
819	Number of duplicate address detection transmits.	Number of duplicate address detection transmits.
820	Can be enabled, disabled, or controlled by DHCP.	Can be enabled, disabled, or controlled by DHCP.
821	ControlledByDHCP	ControlledByDHCP
822	Unchanged	Unchanged
823	Whether to use a stateful protocol (i.e., DHCP) to obtain an address. Setting this parameter will have no effect on an interface that has router discovery enabled & advertising disabled. In that case the parameter is controlled by router discovery.	Whether to use a stateful protocol (i.e., DHCP) to obtain an address. Setting this parameter will have no effect on an interface that has router discovery enabled & advertising disabled. In that case the parameter is controlled by router discovery.
824	Whether to use a stateful protocol (i.e., DHCP) to obtain configuration information other than addresses. Setting this parameter will have no effect on an interface that has router discovery enabled & advertising disabled. In that case the parameter is controlled by router discovery.	Whether to use a stateful protocol (i.e., DHCP) to obtain configuration information other than addresses. Setting this parameter will have no effect on an interface that has router discovery enabled & advertising disabled. In that case the parameter is controlled by router discovery.
825	Whether weak host sends are enabled.	Whether weak host sends are enabled.
826	Whether weak host receives are enabled.	Whether weak host receives are enabled.
827	Ignores default routes on the interface. Default: Disabled.	Ignores default routes on the interface. Default: Disabled.
828	Router lifetime. Default is 1800 seconds.	Router lifetime. Default is 1800 seconds.
829	Whether the interface should advertise itself as a default router regardless of whether the node has a default route itself. Valid only for advertising interfaces.	Whether the interface should advertise itself as a default router regardless of whether the node has a default route itself. Valid only for advertising interfaces.
830	Hop limit in outbound traffic.	Hop limit in outbound traffic.
831	- active: Set only lasts until next boot. - persistent: Set is persistent.	- active: Set only lasts until next boot. - persistent: Set is persistent.
832	To indicate that ARP, Neighbor Discovery, Wake-On-LAN patterns should be turned on.	To indicate that ARP, Neighbor Discovery, Wake-On-LAN patterns should be turned on.
833	To indicate that direct MAC Wake-On-LAN patterns should be turned on.	To indicate that direct MAC Wake-On-LAN patterns should be turned on.
834	To control ECN codepoints for outgoing packets. Four possible values: - Disabled - UseEct1 - UseEct0 - AppDecide	To control ECN codepoints for outgoing packets. Four possible values: - Disabled - UseEct1 - UseEct0 - AppDecide
835	UseEct1	UseEct1
836	UseEct0	UseEct0
837	AppDecide	AppDecide
838	To control whether DHCP is enabled on this IPInterface. Two possible values: - Disabled - Enabled	To control whether DHCP is enabled on this IPInterface. Two possible values: - Disabled - Enabled
839	Reachable time (in ms).	Reachable time (in ms).
840	To control whether to use automatic metric. Two possible values: - Disabled - Enabled	To control whether to use automatic metric. Two possible values: - Disabled - Enabled
841	To show whether to neighbor discovery is supported. Two possible values: - No - Yes	To show whether to neighbor discovery is supported. Two possible values: - No - Yes
842	To show whether the interface is connected or not. Two possible values: - Connected - Disconnected	To show whether the interface is connected or not. Two possible values: - Connected - Disconnected
843	Disconnected	Disconnected
844	Connected	Connected
845	Duplicate address detection retransmit time (in ms).	Duplicate address detection retransmit time (in ms).
846	Routing compartment identifier.	Routing compartment identifier.
847	Network isolation identifier.	Network isolation identifier.
848	Locally unique identifier of the lowest interface in the stack.	Locally unique identifier of the lowest interface in the stack.
849	Represents the Interface class of Microsoft TCPIP WMIv2 provider.	Represents the Interface class of Microsoft TCPIP WMIv2 provider.
850	Default HopLimit of packets sent.	Default HopLimit of packets sent.
851	Maximum number of neighbor cache entries.	Maximum number of neighbor cache entries.
852	Maximum number of route cache entries.	Maximum number of route cache entries.
853	Maximum size of reassembly buffer in bytes.	Maximum size of reassembly buffer in bytes.
854	Whether the path cache is updated in response to ICMP redirect packets.	Whether the path cache is updated in response to ICMP redirect packets.
855	Determines the behavior for source routed packets. Per RFC 5095 support for forwarding of source routed IPv6 packets has been removed, and the setting forward now has the same effect as dontforward.	Determines the behavior for source routed packets. Per RFC 5095 support for forwarding of source routed IPv6 packets has been removed, and the setting forward now has the same effect as dontforward.
856	Forward	Forward
857	DontForward	DontForward
858	Drop	Drop
859	Whether media sense is enabled or not.	Whether media sense is enabled or not.
860	Whether media sense logging is enabled or not.	Whether media sense logging is enabled or not.
861	Level of multicast support. - None: Multicast packets can neither be sent nor received - SendOnly: Multicast packets can be sent but not received - All: Multicast packets can be sent as well as received	Level of multicast support. - None: Multicast packets can neither be sent nor received - SendOnly: Multicast packets can be sent but not received - All: Multicast packets can be sent as well as received
862	None	None
863	SendOnly	SendOnly
864	All	All
865	Maximum IGMP/MLD version supported by the host.	Maximum IGMP/MLD version supported by the host.
866	Version1	Version1
867	Version2	Version2
868	Version3	Version3
869	Whether multicast packets can be forwarded.	Whether multicast packets can be forwarded.
870	Whether fragments should be collected into groups before being forwarded.	Whether fragments should be collected into groups before being forwarded.
871	Whether interface identifiers are randomized.	Whether interface identifiers are randomized.
872	Whether the computer will respond to ICMP Address mask packets	Whether the computer will respond to ICMP Address mask packets
873	Whether dead gateway detection is enabled. Default is enabled.	Whether dead gateway detection is enabled. Default is enabled.
874	The base class of IPv4 and IPv6 protocol for Microsoft TCPIP WMIv2 provider.	The base class of IPv4 and IPv6 protocol for Microsoft TCPIP WMIv2 provider.
875	Minimum value of IPv4 MTU. The default value is 576. The value can range between 352 and 576.	Minimum value of IPv4 MTU. The default value is 576. The value can range between 352 and 576.
876	Represents the IPv4 protocol of Microsoft TCPIP WMIv2 provider.	Represents the IPv4 protocol of Microsoft TCPIP WMIv2 provider.
877	Whether temporary addresses are enabled. It takes one of the following values: - No: Don't use temporary addresses. - Yes: Use temporary addresses. - Always: Use temporary addresses and always generate a new temporary address each time a network is connected.	Whether temporary addresses are enabled. It takes one of the following values: - No: Don't use temporary addresses. - Yes: Use temporary addresses. - Always: Use temporary addresses and always generate a new temporary address each time a network is connected.
878	Always	Always
879	Maximum duplicate address detection attempts for temporary addresses. The default value is 3.	Maximum duplicate address detection attempts for temporary addresses. The default value is 3.
880	Maximum lifetime over which a temporary address is valid. The default value is 7 days.	Maximum lifetime over which a temporary address is valid. The default value is 7 days.
881	Maximum lifetime over which a temporary address is preferred. The default value is 1 day.	Maximum lifetime over which a temporary address is preferred. The default value is 1 day.
882	Time prior to deprecating a temporary address when a new address is generated. The default value is 5 seconds.	Time prior to deprecating a temporary address when a new address is generated. The default value is 5 seconds.
883	Maximum time to desynchronize temporary address preferred lifetimes. The default value is 10 minutes.	Maximum time to desynchronize temporary address preferred lifetimes. The default value is 10 minutes.
884	Represents the IPv6 protocol for Microsoft TCPIP WMIv2 provider.	Represents the IPv6 protocol for Microsoft TCPIP WMIv2 provider.
885	Prefix of the policy.	Prefix of the policy.
886	Precedence value in the policy table, used for sorting destination addresses.	Precedence value in the policy table, used for sorting destination addresses.
887	Label value that allows for policies that prefer a particular source address prefix for use with a destination address prefix.	Label value that allows for policies that prefer a particular source address prefix for use with a destination address prefix.
888	One of the following values: Active: Change only lasts until next boot. Persistent: Change is persistent.	One of the following values: Active: Change only lasts until next boot. Persistent: Change is persistent.
889	Create the PrefixPolicy.	Create the PrefixPolicy.
890	Represents the prefix policy for Microsoft TCPIP WMIv2 provider.	Represents the prefix policy for Microsoft TCPIP WMIv2 provider.
891	A user-friendly name of this policy-related object.	A user-friendly name of this policy-related object.
892	An array of keywords for characterizing / categorizing policy objects. Keywords are of one of two types: - Keywords defined in this and other MOFs, or in DMTF white papers. These keywords provide a vendor- independent, installation-independent way of characterizing policy objects. - Installation-dependent keywords for characterizing policy objects. Examples include \'Engineering\', \'Billing\', and \'Review in December 2000\'. This MOF defines the following keywords: \'UNKNOWN\', \'CONFIGURATION\', \'USAGE\', \'SECURITY\', \'SERVICE\', \'MOTIVATIONAL\', \'INSTALLATION\', and \'EVENT\'. These concepts are self-explanatory and are further discussed in the SLA/Policy White Paper. One additional keyword is defined: \'POLICY\'. The role of this keyword is to identify policy-related instances that may not be otherwise identifiable, in some implementations. The keyword \'POLICY\' is NOT mutually exclusive of the other keywords specified above.	An array of keywords for characterizing / categorizing policy objects. Keywords are of one of two types: - Keywords defined in this and other MOFs, or in DMTF white papers. These keywords provide a vendor- independent, installation-independent way of characterizing policy objects. - Installation-dependent keywords for characterizing policy objects. Examples include \'Engineering\', \'Billing\', and \'Review in December 2000\'. This MOF defines the following keywords: \'UNKNOWN\', \'CONFIGURATION\', \'USAGE\', \'SECURITY\', \'SERVICE\', \'MOTIVATIONAL\', \'INSTALLATION\', and \'EVENT\'. These concepts are self-explanatory and are further discussed in the SLA/Policy White Paper. One additional keyword is defined: \'POLICY\'. The role of this keyword is to identify policy-related instances that may not be otherwise identifiable, in some implementations. The keyword \'POLICY\' is NOT mutually exclusive of the other keywords specified above.
893	An abstract class defining the common properties of the policy managed elements derived from CIM_Policy. The subclasses are used to create rules and groups of rules that work together to form a coherent set of policies within an administrative domain or set of domains.	An abstract class defining the common properties of the policy managed elements derived from CIM_Policy. The subclasses are used to create rules and groups of rules that work together to form a coherent set of policies within an administrative domain or set of domains.
894	The name of the class or the subclass used in the creation of the System object in whose scope this PolicyAction is defined. This property helps to identify the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action. Note that this property, and the analogous property SystemName, do not represent propagated keys from an instance of the class System. Instead, they are properties defined in the context of this class, which repeat the values from the instance of System to which this PolicyAction is related, either directly via the PolicyActionInPolicyRepository association or indirectly via the PolicyActionInPolicyRule aggregation.	The name of the class or the subclass used in the creation of the System object in whose scope this PolicyAction is defined. This property helps to identify the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action. Note that this property, and the analogous property SystemName, do not represent propagated keys from an instance of the class System. Instead, they are properties defined in the context of this class, which repeat the values from the instance of System to which this PolicyAction is related, either directly via the PolicyActionInPolicyRepository association or indirectly via the PolicyActionInPolicyRule aggregation.
895	The name of the System object in whose scope this PolicyAction is defined. This property completes the identification of the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action.	The name of the System object in whose scope this PolicyAction is defined. This property completes the identification of the System object in whose scope this instance of PolicyAction exists. For a rule-specific PolicyAction, this is the System in whose context the PolicyRule is defined. For a reusable PolicyAction, this is the instance of PolicyRepository (which is a subclass of System) that holds the Action.
896	For a rule-specific PolicyAction, the CreationClassName of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.	For a rule-specific PolicyAction, the CreationClassName of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.
897	For a rule-specific PolicyAction, the name of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.	For a rule-specific PolicyAction, the name of the PolicyRule object with which this Action is associated. For a reusable PolicyAction, a special value, \'NO RULE\', should be used to indicate that this Action is reusable and not associated with a single PolicyRule.
898	A user-friendly name of this PolicyAction.	A user-friendly name of this PolicyAction.
899	DoActionLogging causes a log message to be generated when the action is performed.	DoActionLogging causes a log message to be generated when the action is performed.
900	A class representing a rule-specific or reusable policy action to be performed if the PolicyConditions for a Policy Rule evaluate to TRUE. Since all operational details of a PolicyAction are provided in subclasses of this object, this class is abstract.	A class representing a rule-specific or reusable policy action to be performed if the PolicyConditions for a Policy Rule evaluate to TRUE. Since all operational details of a PolicyAction are provided in subclasses of this object, this class is abstract.
901	2.8.0	2.8.0
902	One of the following values: - DatacenterCustom, InternetCustom, Datacenter, Compat, Internet, Automatic.	One of the following values: - DatacenterCustom, InternetCustom, Datacenter, Compat, Internet, Automatic.
903	Controls TCP retransmission timeout in milliseconds. Value can range from 20 milliseconds to 300 milliseconds.	Controls TCP retransmission timeout in milliseconds. Value can range from 20 milliseconds to 300 milliseconds.
904	Controls initial congestion window in Maximum Segment Size. Values can range from 2 to 64 MSS.	Controls initial congestion window in Maximum Segment Size. Values can range from 2 to 64 MSS.
905	Controls whether congestion window is restarted.	Controls whether congestion window is restarted.
906	One of the following values: - Disabled: Disable memory pressure protection. - Enabled : Enable memory pressure protection. - Default : Restore memory pressure protection state to the system default.	One of the following values: - Disabled: Disable memory pressure protection. - Enabled : Enable memory pressure protection. - Default : Restore memory pressure protection state to the system default.
907	Default	Default
908	Controls the congestion provider. One of the following values: - Default - CTCP - DCTCP	Controls the congestion provider. One of the following values: - Default - CTCP - DCTCP
909	CTCP	CTCP
910	DCTCP	DCTCP
911	One of the following values: - Disabled: Fix the receive window at its default value. - HighlyRestricted: Allow the receive window to grow beyond its default value, but do so very conservatively. - Restricted: Allow the receive window to grow beyond its default value, but limit such growth in some scenarios. - Normal: Allow the receive window to grow to accommodate almost all scenarios. - Experimental: Allow the receive window to grow to accomodate extreme scenarios.	One of the following values: - Disabled: Fix the receive window at its default value. - HighlyRestricted: Allow the receive window to grow beyond its default value, but do so very conservatively. - Restricted: Allow the receive window to grow beyond its default value, but limit such growth in some scenarios. - Normal: Allow the receive window to grow to accommodate almost all scenarios. - Experimental: Allow the receive window to grow to accomodate extreme scenarios.
912	HighlyRestricted	HighlyRestricted
913	Restricted	Restricted
914	Normal	Normal
915	Experimental	Experimental
916	Controls the TCP ECN Capability. Disabled by default in client, enabled by default in server. The value can be one of the following values: - Disabled: Disable ECN Capability. - Enabled : Enable ECN Capability.	Controls the TCP ECN Capability. Disabled by default in client, enabled by default in server. The value can be one of the following values: - Disabled: Disable ECN Capability. - Enabled : Enable ECN Capability.
917	One of the following values: - Disabled: Disable RFC 1323 timestamps. - Enabled: Enable RFC 1323 timestamps.	One of the following values: - Disabled: Disable RFC 1323 timestamps. - Enabled: Enable RFC 1323 timestamps.
918	Connect (SYN) retransmit timeout (in milliseconds). default: 3000.	Connect (SYN) retransmit timeout (in milliseconds). default: 3000.
919	One of the following values: - Disabled: Disable window scaling heuristics. - Enabled : Enable window scaling heuristics.	One of the following values: - Disabled: Disable window scaling heuristics. - Enabled : Enable window scaling heuristics.
920	Starting port number between 1 and 65535.	Starting port number between 1 and 65535.
921	Number of ports starting from the DynamicPortRangeStartPort for dynamic port range.	Number of ports starting from the DynamicPortRangeStartPort for dynamic port range.
922	One of the following values: - Disabled: Set the receive window at its default value. - HighlyRestricted: Allow the receive window to grow beyond its default value, but do so very conservatively. - Restricted: Allow the receive window to grow beyond its default value, but limit such growth in some scenarios. - Normal: Allow the receive window to grow to accomodate almost all scenarios. - Experimental: Allow the receive window to grow to accomodate extreme scenarios.	One of the following values: - Disabled: Set the receive window at its default value. - HighlyRestricted: Allow the receive window to grow beyond its default value, but do so very conservatively. - Restricted: Allow the receive window to grow beyond its default value, but limit such growth in some scenarios. - Normal: Allow the receive window to grow to accomodate almost all scenarios. - Experimental: Allow the receive window to grow to accomodate extreme scenarios.
923	The effective setting of auto-tuning level. This can be one of the following value: - Local: the effective auto-tuning level is from the local setting - GroupPolicy: the effective auto-tuning level is from the group policy setting	The effective setting of auto-tuning level. This can be one of the following value: - Local: the effective auto-tuning level is from the local setting - GroupPolicy: the effective auto-tuning level is from the group policy setting
924	GroupPolicy	GroupPolicy
925	Controls TCP delayed ACK time-out in milliseconds. Value can range from 10 milliseconds to 600 milliseconds.	Controls TCP delayed ACK time-out in milliseconds. Value can range from 10 milliseconds to 600 milliseconds.
926	Specifies the number of ACKs that will be outstanding before the delayed ACK timer is ignored. Value can range from 1 to 255.	Specifies the number of ACKs that will be outstanding before the delayed ACK timer is ignored. Value can range from 1 to 255.
927	Controls whether Automatic template chooses between custom templates. - Disabled: Automatic chooses between Datacenter and Internet. - Enabled: Automatic chooses between DatacenterCustom and InternetCustom.	Controls whether Automatic template chooses between custom templates. - Disabled: Automatic chooses between Datacenter and Internet. - Enabled: Automatic chooses between DatacenterCustom and InternetCustom.
928	One of the following values: - Disabled: Disable rtt resiliency for non sack clients. - Enabled : Enable rtt resiliency for non sack clients.	One of the following values: - Disabled: Disable rtt resiliency for non sack clients. - Enabled : Enable rtt resiliency for non sack clients.
929	One of the following values: - Disabled: Disable force window scaling on retransmit. - Enabled : Enable force window scaling on retransmit.	One of the following values: - Disabled: Disable force window scaling on retransmit. - Enabled : Enable force window scaling on retransmit.
930	Specifies the number of connect retry attempts using SYN packets. Value can range from 2 to 8.	Specifies the number of connect retry attempts using SYN packets. Value can range from 2 to 8.
931	Starting automatic reuse port number between 1025 and 65535.	Starting automatic reuse port number between 1025 and 65535.
932	Number of ports starting from the AutoReusePortRangeStartPort for automatic reuse port range.	Number of ports starting from the AutoReusePortRangeStartPort for automatic reuse port range.
933	Represents the TCP parameter setting for Microsoft TCPIP WMIv2 provider.	Represents the TCP parameter setting for Microsoft TCPIP WMIv2 provider.
934	Represents the UDP parameter setting for Microsoft TCPIP WMIv2 provider.	Represents the UDP parameter setting for Microsoft TCPIP WMIv2 provider.
935	The Name property defines the label by which the Filter Entry is known and uniquely identified.	The Name property defines the label by which the Filter Entry is known and uniquely identified.
936	The scoping ComputerSystem\'s CreationClassName.	The scoping ComputerSystem\'s CreationClassName.
937	The scoping ComputerSystem\'s Name.	The scoping ComputerSystem\'s Name.
938	Boolean indicating that the match condition described in the properties of the FilterEntryBase subclass should be negated. This property is defined for ease of use when filtering on simple negations - for example, to select all source ports except 162. It is not recommended that this Boolean be set to True when filtering on multiple criteria, such as defining an IPHeadersFilter based on source/destination addresses, ports, and DiffServ Code Points.	Boolean indicating that the match condition described in the properties of the FilterEntryBase subclass should be negated. This property is defined for ease of use when filtering on simple negations - for example, to select all source ports except 162. It is not recommended that this Boolean be set to True when filtering on multiple criteria, such as defining an IPHeadersFilter based on source/destination addresses, ports, and DiffServ Code Points.
939	A FilterList aggregates instances of (subclasses of) FilterEntryBase via the aggregation EntriesInFilterList. The filter entries are always ANDed together when grouped by the FilterList. Note that it is possible to aggregate different types of filters into a single FilterList - for example, packet header filters (represented by the IpHeadersFilter class) and IPsec security filters. A FilterList is weak to the network device (e.g., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class.	A FilterList aggregates instances of (subclasses of) FilterEntryBase via the aggregation EntriesInFilterList. The filter entries are always ANDed together when grouped by the FilterList. Note that it is possible to aggregate different types of filters into a single FilterList - for example, packet header filters (represented by the IpHeadersFilter class) and IPsec security filters. A FilterList is weak to the network device (e.g., the ComputerSystem) that contains it. Hence, the ComputerSystem keys are propagated to this class.
940	One of the following protocols: - TCP - UDP	One of the following protocols: - TCP - UDP
941	The start of the local port number.	The start of the local port number.
942	The end of the local port number.	The end of the local port number.
943	The start of the remote port number.	The start of the remote port number.
944	The end of the remote port number.	The end of the remote port number.
945	The destination prefix to be filtered.	The destination prefix to be filtered.
946	The associated TCPSetting's SettingName.	The associated TCPSetting's SettingName.
947	Represents the filter for transport protocol parameter setting for Microsoft TCPIP WMI v2 provider.	Represents the filter for transport protocol parameter setting for Microsoft TCPIP WMI v2 provider.
948	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 creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This 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 . (For DMTF defined instances, the \'preferred\' algorithm MUST be used with the set to \'CIM\'.) MUST include either a vendor specified unique identifier, or if mapping from an ITU M.3100 environment, the trailID, connectionID or subNetworkConnectionID of the instances of PipeR2.	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 creating/defining the InstanceID, or is a registered ID that is assigned to the business entity by a recognized global authority. (This 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 . (For DMTF defined instances, the \'preferred\' algorithm MUST be used with the set to \'CIM\'.) MUST include either a vendor specified unique identifier, or if mapping from an ITU M.3100 environment, the trailID, connectionID or subNetworkConnectionID of the instances of PipeR2.
949	Indicates whether the pipe is bi-directional (value = 2), unidirectional (value = 3), or this information is not known (value = 0). For unidirectional pipes, the source and sink are indicated by a property (SourceOrSink) of the association, EndpointOfNetworkPipe.	Indicates whether the pipe is bi-directional (value = 2), unidirectional (value = 3), or this information is not known (value = 0). For unidirectional pipes, the source and sink are indicated by a property (SourceOrSink) of the association, EndpointOfNetworkPipe.
950	Bi-Directional	Bi-Directional
951	Unidirectional	Unidirectional
952	Indicates whether the pipe is composed of lower-level pipes, and if so, how these lower-level pipes are aggregated (in parallel or in sequence). The specific instances of NetworkPipe that are combined are described using the NetworkPipeComposition association. In the context of M.3100, the ability to be composed of lower-level pipes is modeled as a Trail. A Trail is made up of one or more Connections. (Note that both Trails and Connections are subclasses of Pipe). Because of the flexibility of the NetworkPipeComposition association, there is no need to subclass NetworkPipe, as was done in M.3100, but merely to instantiate the NetworkPipeComposition association to describe the bundling of the lower-level pipes (i.e., the connections), or the sequencing of them.	Indicates whether the pipe is composed of lower-level pipes, and if so, how these lower-level pipes are aggregated (in parallel or in sequence). The specific instances of NetworkPipe that are combined are described using the NetworkPipeComposition association. In the context of M.3100, the ability to be composed of lower-level pipes is modeled as a Trail. A Trail is made up of one or more Connections. (Note that both Trails and Connections are subclasses of Pipe). Because of the flexibility of the NetworkPipeComposition association, there is no need to subclass NetworkPipe, as was done in M.3100, but merely to instantiate the NetworkPipeComposition association to describe the bundling of the lower-level pipes (i.e., the connections), or the sequencing of them.
953	No Lower-Level Composition	No Lower-Level Composition
954	Combined In Parallel	Combined In Parallel
955	Combined In Sequence	Combined In Sequence
956	NetworkPipe is a subclass of EnabledLogicalElement, representing the state and management of a connection or trail between endpoints. This object is different than the association between the endpoints (CIM_ActiveConnection) since the emphasis is NOT on the endpoints but on the management of the pipe itself - its state, configuration, etc. NetworkPipes are defined in the context of a CIM_Network and represent the \'transfer of information . . . between . . . endpoints\'. These concepts are aligned with the definition of the Pipe object in ITU\'s M.3100 specification.	NetworkPipe is a subclass of EnabledLogicalElement, representing the state and management of a connection or trail between endpoints. This object is different than the association between the endpoints (CIM_ActiveConnection) since the emphasis is NOT on the endpoints but on the management of the pipe itself - its state, configuration, etc. NetworkPipes are defined in the context of a CIM_Network and represent the \'transfer of information . . . between . . . endpoints\'. These concepts are aligned with the definition of the Pipe object in ITU\'s M.3100 specification.
957	The local address of the connection.	The local address of the connection.
958	The local port of the connection.	The local port of the connection.
959	The PID of the owning process.	The PID of the owning process.
960	Creation time.	Creation time.
961	Represents the transport connection class for Microsoft TCPIP WMIv2 provider.	Represents the transport connection class for Microsoft TCPIP WMIv2 provider.
962	The remote address of the TCP connection.	The remote address of the TCP connection.
963	The remote port of the TCP connection.	The remote port of the TCP connection.
964	The state of the TCP connection. The value can be: - Closed, - Listen, - SynSent, - SynReceived, - Established, - FinWait1, - FinWait2, - CloseWait, - Closing, - LastAck, - TimeWait	The state of the TCP connection. The value can be: - Closed, - Listen, - SynSent, - SynReceived, - Established, - FinWait1, - FinWait2, - CloseWait, - Closing, - LastAck, - TimeWait
965	Closed	Closed
966	Listen	Listen
967	SynSent	SynSent
968	SynReceived	SynReceived
969	Established	Established
970	FinWait1	FinWait1
971	FinWait2	FinWait2
972	CloseWait	CloseWait
973	Closing	Closing
974	LastAck	LastAck
975	TimeWait	TimeWait
976	DeleteTCB	DeleteTCB
977	The setting applied for this TCP connection. The value can be: - Internet, - Datacenter, - Compat, - InternetCustom, - DatacenterCustom	The setting applied for this TCP connection. The value can be: - Internet, - Datacenter, - Compat, - InternetCustom, - DatacenterCustom
978	Internet	Internet
979	Datacenter	Datacenter
980	Compat	Compat
981	DatacenterCustom	DatacenterCustom
982	InternetCustom	InternetCustom
983	The TCP_CONNECTION_OFFLOAD_STATE of the TCP connection.	The TCP_CONNECTION_OFFLOAD_STATE of the TCP connection.
984	InHost	InHost
985	Offloading	Offloading
986	Offloaded	Offloaded
987	Uploading	Uploading
988	Represents the TCP connection class for Microsoft TCPIP WMIv2 provider.	Represents the TCP connection class for Microsoft TCPIP WMIv2 provider.
989	Represents the UDP connection class for Microsoft TCPIP WMIv2 provider.	Represents the UDP connection class for Microsoft TCPIP WMIv2 provider.
990	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.
991	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.)
992	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.
993	Superclass SettingData for networking	Superclass SettingData for networking
994	Whether to turn on receive side scaling. One of the following values: - Disabled - Enabled	Whether to turn on receive side scaling. One of the following values: - Disabled - Enabled
995	Whether to turn on receive segment coalescing. One of the following values: - Disabled - Enabled	Whether to turn on receive segment coalescing. One of the following values: - Disabled - Enabled
996	Whether to turn on Chimney offload. One of the following values: - Disabled - Enabled - Automatic	Whether to turn on Chimney offload. One of the following values: - Disabled - Enabled - Automatic
997	Automatic	Automatic
998	Whether to turn on task offload. One of the following values: - Disabled - Enabled	Whether to turn on task offload. One of the following values: - Disabled - Enabled
999	Whether to turn on NetworkDirect. One of the following values: - Disabled - Enabled	Whether to turn on NetworkDirect. One of the following values: - Disabled - Enabled
1000	Whether to turn on packet coalescing filters. One of the following values: - Disabled - Enabled	Whether to turn on packet coalescing filters. One of the following values: - Disabled - Enabled
1001	Whether NetworkDirect connectivity outside of local IP subnet is allowed or not. One of the following values: - Blocked - Allowed	Whether NetworkDirect connectivity outside of local IP subnet is allowed or not. One of the following values: - Blocked - Allowed
1002	Blocked	Blocked
1003	Allowed	Allowed
1004	Represents the offload global setting class for Microsoft TCPIP WMIv2 provider.	Represents the offload global setting class for Microsoft TCPIP WMIv2 provider.
1005	Antecedent represents the independent object in this association.	Antecedent represents the independent object in this association.
1006	Dependent represents the object that is dependent on the Antecedent.	Dependent represents the object that is dependent on the Antecedent.
1007	CIM_Dependency is a generic association used to establish dependency relationships between ManagedElements.	CIM_Dependency is a generic association used to establish dependency relationships between ManagedElements.
1008	The endpoint used to reach the route\'s destination.	The endpoint used to reach the route\'s destination.
1009	The route using the endpoint.	The route using the endpoint.
1010	RouteUsesEndpoint depicts the relationship between a next hop route and the local Endpoint that is used to transmit the traffic to the \'next hop\'.	RouteUsesEndpoint depicts the relationship between a next hop route and the local Endpoint that is used to transmit the traffic to the \'next hop\'.
1011	The route associated with the interface	The route associated with the interface
1012	Represents the IPInterfaceRoute association class in TCPIP WMIv2 provider.	Represents the IPInterfaceRoute association class in TCPIP WMIv2 provider.
1013	The required ServiceAccessPoint.	The required ServiceAccessPoint.
1014	The ServiceAccessPoint that is dependent on an underlying SAP.	The ServiceAccessPoint that is dependent on an underlying SAP.
1015	CIM_SAPSAPDependency is an association between one ServiceAccessPoint and another ServiceAccessPoint that indicates that the latter is required for the former to utilize or connect with its Service. For example, to print to a network printer, local Print Access Points must utilize underlying network-related SAPs, or ProtocolEndpoints, to send the print request.	CIM_SAPSAPDependency is an association between one ServiceAccessPoint and another ServiceAccessPoint that indicates that the latter is required for the former to utilize or connect with its Service. For example, to print to a network printer, local Print Access Points must utilize underlying network-related SAPs, or ProtocolEndpoints, to send the print request.
1016	The lower-level endpoint that is accessed by the SAP.	The lower-level endpoint that is accessed by the SAP.
1017	The AccessPoint or ProtocolEndpoint that is dependent on the lower-level endpoint.	The AccessPoint or ProtocolEndpoint that is dependent on the lower-level endpoint.
1018	This association establishes a ServiceAccessPoint as a requestor of protocol services from a ProtocolEndpoint. Typically, this association runs between SAPs and endpoints on a single system. Because a ProtocolEndpoint is a kind of ServiceAccessPoint, this binding can be used to establish a layering of two protocols, with the upper layer represented by the Dependent and the lower layer represented by the Antecedent.	This association establishes a ServiceAccessPoint as a requestor of protocol services from a ProtocolEndpoint. Typically, this association runs between SAPs and endpoints on a single system. Because a ProtocolEndpoint is a kind of ServiceAccessPoint, this binding can be used to establish a layering of two protocols, with the upper layer represented by the Dependent and the lower layer represented by the Antecedent.
1019	The underlying LANEndpoint, which is depended upon.	The underlying LANEndpoint, which is depended upon.
1020	The AccessPoint or ProtocolEndpoint dependent on the LANEndpoint.	The AccessPoint or ProtocolEndpoint dependent on the LANEndpoint.
1021	This describes the framing method for the upper layer SAP or Endpoint that is bound to the LANEndpoint. Note: "Raw802.3" is only known to be used with the IPX protocol.	This describes the framing method for the upper layer SAP or Endpoint that is bound to the LANEndpoint. Note: "Raw802.3" is only known to be used with the IPX protocol.
1022	802.2	802.2
1023	SNAP	SNAP
1024	Raw802.3	Raw802.3
1025	This association makes explicit the dependency of a SAP or ProtocolEndpoint on an underlying LANEndpoint, on the same system.	This association makes explicit the dependency of a SAP or ProtocolEndpoint on an underlying LANEndpoint, on the same system.
1026	The IPInterface associated with the IP addresses.	The IPInterface associated with the IP addresses.
1027	The IP address associated with the IP interface	The IP address associated with the IP interface
1028	Represents the IPInterfaceIPAddress association class in TCPIP WMIv2 provider.	Represents the IPInterfaceIPAddress association class in TCPIP WMIv2 provider.
1029	The IPInterface used to reach the neighbor.	The IPInterface used to reach the neighbor.
1030	The neighbor associated with the IP interface	The neighbor associated with the IP interface
1031	Represents the IPInterfaceNeighbor association class in TCPIP WMIv2 provider.	Represents the IPInterfaceNeighbor association class in TCPIP WMIv2 provider.
1032	The scoping System\'s CreationClassName.	The scoping System\'s CreationClassName.
1033	The scoping System\'s Name.	The scoping System\'s Name.
1034	An address or other identifying information to uniquely name the LogicalDevice.	An address or other identifying information to uniquely name the LogicalDevice.
1035	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.
1036	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.
1037	Power Saving Modes Entered Automatically	Power Saving Modes Entered Automatically
1038	Power State Settable	Power State Settable
1039	Power Cycling Supported	Power Cycling Supported
1040	Timed Power On Supported	Timed Power On Supported
1041	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.
1042	Running/Full Power	Running/Full Power
1043	Warning	Warning
1044	Power Off	Power Off
1045	Off Line	Off Line
1046	Off Duty	Off Duty
1047	Not Installed	Not Installed
1048	Install Error	Install Error
1049	Power Save - Unknown	Power Save - Unknown
1050	Power Save - Low Power Mode	Power Save - Low Power Mode
1051	Power Save - Standby	Power Save - Standby
1052	Power Cycle	Power Cycle
1053	Power Save - Warning	Power Save - Warning
1054	Paused	Paused
1055	Not Ready	Not Ready
1056	Not Configured	Not Configured
1057	Quiesced	Quiesced
1058	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.
1059	LastErrorCode captures the last error code reported by the LogicalDevice.	LastErrorCode captures the last error code reported by the LogicalDevice.
1060	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.
1061	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.
1062	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.
1063	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.
1064	Hours	Hours
1065	The total number of hours that this Device has been powered.	The total number of hours that this Device has been powered.
1066	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.
1067	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").
1068	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.
1069	MilliSeconds	MilliSeconds
1070	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.
1071	The power state to set.	The power state to set.
1072	Full Power	Full Power
1073	Power Save - Other	Power Save - Other
1074	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.
1075	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.
1076	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.
1077	If TRUE enable the device, if FALSE disable the device.	If TRUE enable the device, if FALSE disable the device.
1078	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.
1079	If TRUE, take the device online, if FALSE, take the device OFFLINE.	If TRUE, take the device online, if FALSE, take the device OFFLINE.
1080	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.
1081	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.
1082	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.
1083	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.
1084	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.
1085	The LogicalDevice.	The LogicalDevice.
1086	The ServiceAccessPoint implemented using the LogicalDevice.	The ServiceAccessPoint implemented using the LogicalDevice.
1087	An association between a ServiceAccessPoint (SAP) and how it is implemented. The cardinality of this association is many-to-many. A SAP can be provided by more than one LogicalDevice, operating in conjunction. And, any Device can provide more than one ServiceAccessPoint. When many LogicalDevices are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the AccessPoint. If different implementations of a SAP exist, each of these implementations would result in individual instantiations of the ServiceAccessPoint object. These individual instantiations would then have associations to the unique implementations.	An association between a ServiceAccessPoint (SAP) and how it is implemented. The cardinality of this association is many-to-many. A SAP can be provided by more than one LogicalDevice, operating in conjunction. And, any Device can provide more than one ServiceAccessPoint. When many LogicalDevices are associated with a single SAP, it is assumed that these elements operate in conjunction to provide the AccessPoint. If different implementations of a SAP exist, each of these implementations would result in individual instantiations of the ServiceAccessPoint object. These individual instantiations would then have associations to the unique implementations.
1088	The bandwidth of the Port in Bits per Second.	The bandwidth of the Port in Bits per Second.
1089	Bits per Second	Bits per Second
1090	The maximum bandwidth of the Port in Bits per Second.	The maximum bandwidth of the Port in Bits per Second.
1091	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.
1092	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\'.
1093	Front-end only	Front-end only
1094	Back-end only	Back-end only
1095	Not restricted	Not restricted
1096	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.
1097	Describes the type of module, when PortType is set to 1 ("Other").	Describes the type of module, when PortType is set to 1 ("Other").
1098	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.
1099	The LogicalPort that represents the Device behind the ProtocolEndpoint.	The LogicalPort that represents the Device behind the ProtocolEndpoint.
1100	The ProtocolEndpoint that is implemented on the LogicalPort.	The ProtocolEndpoint that is implemented on the LogicalPort.
1101	PortImplementsEndpoint associates a LogicalPort with one or more ProtocolEndpoints that are implemented on it. This class specializes the DeviceSAPImplementation association. It indicates that the referenced Endpoint is dependent on the operations of the Port Device.	PortImplementsEndpoint associates a LogicalPort with one or more ProtocolEndpoints that are implemented on it. This class specializes the DeviceSAPImplementation association. It indicates that the referenced Endpoint is dependent on the operations of the Port Device.
1102	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.
1103	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".)
1104	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.
1105	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.
1106	IB	IB
1107	FC	FC
1108	Token Ring	Token Ring
1109	Infrared	Infrared
1110	BlueTooth	BlueTooth
1111	Wireless LAN	Wireless LAN
1112	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".
1113	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.
1114	An array of strings that indicates the network addresses for the port.	An array of strings that indicates the network addresses for the port.
1115	Boolean that indicates that the port is operating in full duplex mode.	Boolean that indicates that the port is operating in full duplex mode.
1116	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.
1117	The maximum transmission unit (MTU) that can be supported.	The maximum transmission unit (MTU) that can be supported.
1118	Bytes	Bytes
1119	The active or negotiated maximum transmission unit (MTU) that can be supported.	The active or negotiated maximum transmission unit (MTU) that can be supported.
1120	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.
1121	The IPInterface associated with the NetworkPort.	The IPInterface associated with the NetworkPort.
1122	The NetworkPort associated with the IPInterface	The NetworkPort associated with the IPInterface
1123	Represents the IPInterfaceAdapter association class in TCPIP WMIv2 provider.	Represents the IPInterfaceAdapter association class in TCPIP WMIv2 provider.
1124	The filter associated with the TCP setting.	The filter associated with the TCP setting.
1125	The TCP setting associated with the filter	The TCP setting associated with the filter
1126	Represents the TransportFilterTCPSetting association class in TCPIP WMIv2 provider.	Represents the TransportFilterTCPSetting association class in TCPIP WMIv2 provider.
1127	Compartment identifier.	Compartment identifier.
1128	Compartment globally unique identifier.	Compartment globally unique identifier.
1129	User-friendly compartment description.	User-friendly compartment description.
1130	Compartment type.	Compartment type.
1131	Unspecified	Unspecified
1132	Native	Native
1133	RoutingDomain	RoutingDomain
1134	Represents the Compartment for Microsoft TCPIP WMIv2 provider.	Represents the Compartment for Microsoft TCPIP WMIv2 provider.
0x1	Can not find the required property %1	Can not find the required property %1
0x2	Not all required properties are specified: %1 and either one of %2 %3	Not all required properties are specified: %1 and either one of %2 %3
0x3	Not all required properties are specified: either one of %1 %2 and either one of %3 %4	Not all required properties are specified: either one of %1 %2 and either one of %3 %4
0x4	Not all required properties are specified: %1 %2 and either one of %3 %4	Not all required properties are specified: %1 %2 and either one of %3 %4
0x5	Not all required properties are specified: %1 and either %2 %3 %4 %5 or %6 %7	Not all required properties are specified: %1 and either %2 %3 %4 %5 or %6 %7
0x6	Only the custom templates InternetCustom and DatacenterCustom can be modified.	Only the custom templates InternetCustom and DatacenterCustom can be modified.
0x7	%1 must be the same as %2, %3 must be the same as %4 or only one of the ranges must be wildcard (0, 65535)	%1 must be the same as %2, %3 must be the same as %4 or only one of the ranges must be wildcard (0, 65535)
0x8	Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6	Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6
0x9	Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6 %7 %8 %9 %10	Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6 %7 %8 %9 %10
0xA	Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12	Properties that need modification should not include any of the following %1 %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12
0xB	Instance %1 %2 not found	Instance %1 %2 not found
0xC	Instance %1 already exists	Instance %1 already exists
0xD	Invalid parameter %1 %2, %3 should not be specified	Invalid parameter %1 %2, %3 should not be specified
0xE	Invalid parameter %1 Days: %2!lu! Hours: %3!lu! Minutes: %4!lu! Seconds: %5!lu! Microseconds: %6!lu!	Invalid parameter %1 Days: %2!lu! Hours: %3!lu! Minutes: %4!lu! Seconds: %5!lu! Microseconds: %6!lu!
0xF	Invalid parameter %1	Invalid parameter %1
0x10	Invalid parameter %1 %2	Invalid parameter %1 %2
0x11	Invalid parameter %1 %2 %3 %4	Invalid parameter %1 %2 %3 %4
0x12	Invalid parameter %1 %2!lu!	Invalid parameter %1 %2!lu!
0x13	Inconsistent parameters %1 %2 and %3 %4	Inconsistent parameters %1 %2 and %3 %4
0x14	Value of property %1 should be at most the value of property %2	Value of property %1 should be at most the value of property %2
0x15	Value of property %1 should be at most %2!lu!	Value of property %1 should be at most %2!lu!
0x16	Property %1 is read-only	Property %1 is read-only
0x17	This feature is available on servers only.	This feature is available on servers only.
0x18	Properties %1 and %2 should have values at the same time	Properties %1 and %2 should have values at the same time
0x19	Properties %1 and %2 should not have values at the same time	Properties %1 and %2 should not have values at the same time
0x1A	When property %1 is %2!lu!, %3 and %4 can not be set	When property %1 is %2!lu!, %3 and %4 can not be set
0x1B	Properties %1 %2 %3 %4 and %5 %6 should not have values at the same time	Properties %1 %2 %3 %4 and %5 %6 should not have values at the same time
0x1C	Can only modify/create/delete Neighbor object whose State is Permanent	Can only modify/create/delete Neighbor object whose State is Permanent
0x1D	Default loopback address cannot be deleted	Default loopback address cannot be deleted
0x1E	Default loopback route cannot be deleted	Default loopback route cannot be deleted
0x1F	IPv4 protocol is not installed.	IPv4 protocol is not installed.
0x20	This feature is not available on servers.	This feature is not available on servers.
0x21	DefaultGateway %1 is not on the same network segment (subnet) that is defined by the IP address %2 and PrefixLength %3!lu!.	DefaultGateway %1 is not on the same network segment (subnet) that is defined by the IP address %2 and PrefixLength %3!lu!.
0x22	Interface %1 does not support setting LinkLayerAddress.	Interface %1 does not support setting LinkLayerAddress.
0x23	The parameter %1 must be specified.	The parameter %1 must be specified.
0x24	Both IP addresses must be from the same address family.	Both IP addresses must be from the same address family.

File Name:	NetTCPIP.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-windows-t..2provider.resources_31bf3856ad364e35_10.0.15063.0_fi-fi_4ab855283b9793ef\
File Size:	220 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:	225280
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:	Finnish
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	TCPIP WMI Provider
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	NetTCPIP.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	NetTCPIP.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0

NetTCPIP.dll.mui is Multilingual User Interface resource file that contain Finnish language for file NetTCPIP.dll (TCPIP WMI Provider).

File Description:	TCPIP WMI Provider
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	NetTCPIP.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	NetTCPIP.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x40B, 1200