| File name: | ndisimplatcim.dll.mui |
| Size: | 112640 byte |
| MD5: | 352d15199ab3c3d940608944f5fdfac5 |
| SHA1: | 3b58afa0ec80664f9a87697011aedde52b5fb2c9 |
| SHA256: | 13b02b09ff0c6968d77dcbd6654433d887d248b397bd4f64a83128e6ed13e996 |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Swedish 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 | Swedish | 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 | Team GUID associated with this team | Team GUID associated with this team |
| 8 | Name of the team | Name of the team |
| 9 | Represents a team in the IM Platform | Represents a team in the IM Platform |
| 10 | 1.0 | 1.0 |
| 11 | The teaming mode value for all providers | The teaming mode value for all providers |
| 12 | The load balancing algorithm for all providers | The load balancing algorithm for all providers |
| 13 | Current operational status of the team | Current operational status of the team |
| 14 | Renames a team | Renames a team |
| 15 | Represents an LBFO team | Represents an LBFO team |
| 16 | The NetcfgInstanceId of the LWF | The NetcfgInstanceId of the LWF |
| 17 | The display name of this LWF | The display name of this LWF |
| 18 | Represents an IMPlatform Provider | Represents an IMPlatform Provider |
| 19 | Represents an Lbfo Provider | Represents an Lbfo Provider |
| 20 | 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. |
| 21 | 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. |
| 22 | 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. |
| 23 | Unknown | Unknown |
| 24 | Other | Other |
| 25 | OK | OK |
| 26 | Degraded | Degraded |
| 27 | Stressed | Stressed |
| 28 | Predictive Failure | Predictive Failure |
| 29 | Error | Error |
| 30 | Non-Recoverable Error | Non-Recoverable Error |
| 31 | Starting | Starting |
| 32 | Stopping | Stopping |
| 33 | Stopped | Stopped |
| 34 | In Service | In Service |
| 35 | No Contact | No Contact |
| 36 | Lost Communication | Lost Communication |
| 37 | Aborted | Aborted |
| 38 | Dormant | Dormant |
| 39 | Supporting Entity in Error | Supporting Entity in Error |
| 40 | Completed | Completed |
| 41 | Power Mode | Power Mode |
| 42 | DMTF Reserved | DMTF Reserved |
| 43 | Vendor Reserved | Vendor Reserved |
| 44 | 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. |
| 45 | 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. |
| 46 | 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. |
| 47 | Degraded/Warning | Degraded/Warning |
| 48 | Minor failure | Minor failure |
| 49 | Major failure | Major failure |
| 50 | Critical failure | Critical failure |
| 51 | Non-recoverable error | Non-recoverable error |
| 52 | 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. |
| 53 | Not Available | Not Available |
| 54 | Communication OK | Communication OK |
| 55 | 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. |
| 56 | No Additional Information | No Additional Information |
| 57 | 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. |
| 58 | Servicing | Servicing |
| 59 | Migrating | Migrating |
| 60 | Emigrating | Emigrating |
| 61 | Immigrating | Immigrating |
| 62 | Snapshotting | Snapshotting |
| 63 | Shutting Down | Shutting Down |
| 64 | In Test | In Test |
| 65 | Transitioning | Transitioning |
| 66 | 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. |
| 67 | 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. |
| 68 | 2.22.0 | 2.22.0 |
| 69 | 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. |
| 70 | 2.6.0 | 2.6.0 |
| 71 | 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. |
| 72 | 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. |
| 73 | 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. |
| 74 | 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. |
| 75 | 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. |
| 76 | 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. |
| 77 | 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. |
| 78 | January | January |
| 79 | February | February |
| 80 | March | March |
| 81 | April | April |
| 82 | May | May |
| 83 | June | June |
| 84 | July | July |
| 85 | August | August |
| 86 | September | September |
| 87 | October | October |
| 88 | November | November |
| 89 | December | December |
| 90 | 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. |
| 91 | 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. |
| 92 | -Saturday | -Saturday |
| 93 | -Friday | -Friday |
| 94 | -Thursday | -Thursday |
| 95 | -Wednesday | -Wednesday |
| 96 | -Tuesday | -Tuesday |
| 97 | -Monday | -Monday |
| 98 | -Sunday | -Sunday |
| 99 | ExactDayOfMonth | ExactDayOfMonth |
| 100 | Sunday | Sunday |
| 101 | Monday | Monday |
| 102 | Tuesday | Tuesday |
| 103 | Wednesday | Wednesday |
| 104 | Thursday | Thursday |
| 105 | Friday | Friday |
| 106 | Saturday | Saturday |
| 107 | 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. |
| 108 | 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". |
| 109 | Local Time | Local Time |
| 110 | UTC Time | UTC Time |
| 111 | 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. |
| 112 | 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. |
| 113 | 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. |
| 114 | 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. |
| 115 | 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. |
| 116 | Percent | Percent |
| 117 | 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. |
| 118 | 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. |
| 119 | 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. |
| 120 | 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. |
| 121 | Do Not Continue | Do Not Continue |
| 122 | Continue With Next Job | Continue With Next Job |
| 123 | Re-run Job | Re-run Job |
| 124 | Run Recovery Job | Run Recovery Job |
| 125 | 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"). |
| 126 | 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. |
| 127 | Success | Success |
| 128 | Not Supported | Not Supported |
| 129 | Timeout | Timeout |
| 130 | Failed | Failed |
| 131 | Access Denied | Access Denied |
| 132 | Not Found | Not Found |
| 133 | Vendor Specific | Vendor Specific |
| 134 | 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. |
| 135 | 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. |
| 136 | 2.10.0 | 2.10.0 |
| 137 | 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. |
| 138 | Communications Error | Communications Error |
| 139 | Quality of Service Error | Quality of Service Error |
| 140 | Software Error | Software Error |
| 141 | Hardware Error | Hardware Error |
| 142 | Environmental Error | Environmental Error |
| 143 | Security Error | Security Error |
| 144 | Oversubscription Error | Oversubscription Error |
| 145 | Unavailable Resource Error | Unavailable Resource Error |
| 146 | Unsupported Operation Error | Unsupported Operation Error |
| 147 | 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. |
| 148 | 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. |
| 149 | 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. |
| 150 | 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. |
| 151 | An array containing the dynamic content of the message. | An array containing the dynamic content of the message. |
| 152 | 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. |
| 153 | Information | Information |
| 154 | Minor | Minor |
| 155 | Major | Major |
| 156 | Critical | Critical |
| 157 | Fatal/NonRecoverable | Fatal/NonRecoverable |
| 158 | An enumerated value that describes the probable cause of the error. | An enumerated value that describes the probable cause of the error. |
| 159 | Adapter/Card Error | Adapter/Card Error |
| 160 | Application Subsystem Failure | Application Subsystem Failure |
| 161 | Bandwidth Reduced | Bandwidth Reduced |
| 162 | Connection Establishment Error | Connection Establishment Error |
| 163 | Communications Protocol Error | Communications Protocol Error |
| 164 | Communications Subsystem Failure | Communications Subsystem Failure |
| 165 | Configuration/Customization Error | Configuration/Customization Error |
| 166 | Congestion | Congestion |
| 167 | Corrupt Data | Corrupt Data |
| 168 | CPU Cycles Limit Exceeded | CPU Cycles Limit Exceeded |
| 169 | Dataset/Modem Error | Dataset/Modem Error |
| 170 | Degraded Signal | Degraded Signal |
| 171 | DTE-DCE Interface Error | DTE-DCE Interface Error |
| 172 | Enclosure Door Open | Enclosure Door Open |
| 173 | Equipment Malfunction | Equipment Malfunction |
| 174 | Excessive Vibration | Excessive Vibration |
| 175 | File Format Error | File Format Error |
| 176 | Fire Detected | Fire Detected |
| 177 | Flood Detected | Flood Detected |
| 178 | Framing Error | Framing Error |
| 179 | HVAC Problem | HVAC Problem |
| 180 | Humidity Unacceptable | Humidity Unacceptable |
| 181 | I/O Device Error | I/O Device Error |
| 182 | Input Device Error | Input Device Error |
| 183 | LAN Error | LAN Error |
| 184 | Non-Toxic Leak Detected | Non-Toxic Leak Detected |
| 185 | Local Node Transmission Error | Local Node Transmission Error |
| 186 | Loss of Frame | Loss of Frame |
| 187 | Loss of Signal | Loss of Signal |
| 188 | Material Supply Exhausted | Material Supply Exhausted |
| 189 | Multiplexer Problem | Multiplexer Problem |
| 190 | Out of Memory | Out of Memory |
| 191 | Output Device Error | Output Device Error |
| 192 | Performance Degraded | Performance Degraded |
| 193 | Power Problem | Power Problem |
| 194 | Pressure Unacceptable | Pressure Unacceptable |
| 195 | Processor Problem (Internal Machine Error) | Processor Problem (Internal Machine Error) |
| 196 | Pump Failure | Pump Failure |
| 197 | Queue Size Exceeded | Queue Size Exceeded |
| 198 | Receive Failure | Receive Failure |
| 199 | Receiver Failure | Receiver Failure |
| 200 | Remote Node Transmission Error | Remote Node Transmission Error |
| 201 | Resource at or Nearing Capacity | Resource at or Nearing Capacity |
| 202 | Response Time Excessive | Response Time Excessive |
| 203 | Retransmission Rate Excessive | Retransmission Rate Excessive |
| 204 | Software Program Abnormally Terminated | Software Program Abnormally Terminated |
| 205 | Software Program Error (Incorrect Results) | Software Program Error (Incorrect Results) |
| 206 | Storage Capacity Problem | Storage Capacity Problem |
| 207 | Temperature Unacceptable | Temperature Unacceptable |
| 208 | Threshold Crossed | Threshold Crossed |
| 209 | Timing Problem | Timing Problem |
| 210 | Toxic Leak Detected | Toxic Leak Detected |
| 211 | Transmit Failure | Transmit Failure |
| 212 | Transmitter Failure | Transmitter Failure |
| 213 | Underlying Resource Unavailable | Underlying Resource Unavailable |
| 214 | Version Mismatch | Version Mismatch |
| 215 | Previous Alert Cleared | Previous Alert Cleared |
| 216 | Login Attempts Failed | Login Attempts Failed |
| 217 | Software Virus Detected | Software Virus Detected |
| 218 | Hardware Security Breached | Hardware Security Breached |
| 219 | Denial of Service Detected | Denial of Service Detected |
| 220 | Security Credential Mismatch | Security Credential Mismatch |
| 221 | Unauthorized Access | Unauthorized Access |
| 222 | Alarm Received | Alarm Received |
| 223 | Loss of Pointer | Loss of Pointer |
| 224 | Payload Mismatch | Payload Mismatch |
| 225 | Transmission Error | Transmission Error |
| 226 | Excessive Error Rate | Excessive Error Rate |
| 227 | Trace Problem | Trace Problem |
| 228 | Element Unavailable | Element Unavailable |
| 229 | Element Missing | Element Missing |
| 230 | Loss of Multi Frame | Loss of Multi Frame |
| 231 | Broadcast Channel Failure | Broadcast Channel Failure |
| 232 | Invalid Message Received | Invalid Message Received |
| 233 | Routing Failure | Routing Failure |
| 234 | Backplane Failure | Backplane Failure |
| 235 | Identifier Duplication | Identifier Duplication |
| 236 | Protection Path Failure | Protection Path Failure |
| 237 | Sync Loss or Mismatch | Sync Loss or Mismatch |
| 238 | Terminal Problem | Terminal Problem |
| 239 | Real Time Clock Failure | Real Time Clock Failure |
| 240 | Antenna Failure | Antenna Failure |
| 241 | Battery Charging Failure | Battery Charging Failure |
| 242 | Disk Failure | Disk Failure |
| 243 | Frequency Hopping Failure | Frequency Hopping Failure |
| 244 | Loss of Redundancy | Loss of Redundancy |
| 245 | Power Supply Failure | Power Supply Failure |
| 246 | Signal Quality Problem | Signal Quality Problem |
| 247 | Battery Discharging | Battery Discharging |
| 248 | Battery Failure | Battery Failure |
| 249 | Commercial Power Problem | Commercial Power Problem |
| 250 | Fan Failure | Fan Failure |
| 251 | Engine Failure | Engine Failure |
| 252 | Sensor Failure | Sensor Failure |
| 253 | Fuse Failure | Fuse Failure |
| 254 | Generator Failure | Generator Failure |
| 255 | Low Battery | Low Battery |
| 256 | Low Fuel | Low Fuel |
| 257 | Low Water | Low Water |
| 258 | Explosive Gas | Explosive Gas |
| 259 | High Winds | High Winds |
| 260 | Ice Buildup | Ice Buildup |
| 261 | Smoke | Smoke |
| 262 | Memory Mismatch | Memory Mismatch |
| 263 | Out of CPU Cycles | Out of CPU Cycles |
| 264 | Software Environment Problem | Software Environment Problem |
| 265 | Software Download Failure | Software Download Failure |
| 266 | Element Reinitialized | Element Reinitialized |
| 267 | Logging Problems | Logging Problems |
| 268 | Leak Detected | Leak Detected |
| 269 | Protection Mechanism Failure | Protection Mechanism Failure |
| 270 | Protecting Resource Failure | Protecting Resource Failure |
| 271 | Database Inconsistency | Database Inconsistency |
| 272 | Authentication Failure | Authentication Failure |
| 273 | Breach of Confidentiality | Breach of Confidentiality |
| 274 | Cable Tamper | Cable Tamper |
| 275 | Delayed Information | Delayed Information |
| 276 | Duplicate Information | Duplicate Information |
| 277 | Information Missing | Information Missing |
| 278 | Information Modification | Information Modification |
| 279 | Information Out of Sequence | Information Out of Sequence |
| 280 | Key Expired | Key Expired |
| 281 | Non-Repudiation Failure | Non-Repudiation Failure |
| 282 | Out of Hours Activity | Out of Hours Activity |
| 283 | Out of Service | Out of Service |
| 284 | Procedural Error | Procedural Error |
| 285 | Unexpected Information | Unexpected Information |
| 286 | A free-form string describing the probable cause of the error. | A free-form string describing the probable cause of the error. |
| 287 | 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. |
| 288 | 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. |
| 289 | 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. |
| 290 | CIMObjectPath | CIMObjectPath |
| 291 | 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. |
| 292 | 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. |
| 293 | CIM_ERR_FAILED | CIM_ERR_FAILED |
| 294 | CIM_ERR_ACCESS_DENIED | CIM_ERR_ACCESS_DENIED |
| 295 | CIM_ERR_INVALID_NAMESPACE | CIM_ERR_INVALID_NAMESPACE |
| 296 | CIM_ERR_INVALID_PARAMETER | CIM_ERR_INVALID_PARAMETER |
| 297 | CIM_ERR_INVALID_CLASS | CIM_ERR_INVALID_CLASS |
| 298 | CIM_ERR_NOT_FOUND | CIM_ERR_NOT_FOUND |
| 299 | CIM_ERR_NOT_SUPPORTED | CIM_ERR_NOT_SUPPORTED |
| 300 | CIM_ERR_CLASS_HAS_CHILDREN | CIM_ERR_CLASS_HAS_CHILDREN |
| 301 | CIM_ERR_CLASS_HAS_INSTANCES | CIM_ERR_CLASS_HAS_INSTANCES |
| 302 | CIM_ERR_INVALID_SUPERCLASS | CIM_ERR_INVALID_SUPERCLASS |
| 303 | CIM_ERR_ALREADY_EXISTS | CIM_ERR_ALREADY_EXISTS |
| 304 | CIM_ERR_NO_SUCH_PROPERTY | CIM_ERR_NO_SUCH_PROPERTY |
| 305 | CIM_ERR_TYPE_MISMATCH | CIM_ERR_TYPE_MISMATCH |
| 306 | CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED | CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED |
| 307 | CIM_ERR_INVALID_QUERY | CIM_ERR_INVALID_QUERY |
| 308 | CIM_ERR_METHOD_NOT_AVAILABLE | CIM_ERR_METHOD_NOT_AVAILABLE |
| 309 | CIM_ERR_METHOD_NOT_FOUND | CIM_ERR_METHOD_NOT_FOUND |
| 310 | CIM_ERR_UNEXPECTED_RESPONSE | CIM_ERR_UNEXPECTED_RESPONSE |
| 311 | CIM_ERR_INVALID_RESPONSE_DESTINATION | CIM_ERR_INVALID_RESPONSE_DESTINATION |
| 312 | CIM_ERR_NAMESPACE_NOT_EMPTY | CIM_ERR_NAMESPACE_NOT_EMPTY |
| 313 | CIM_ERR_INVALID_ENUMERATION_CONTEXT | CIM_ERR_INVALID_ENUMERATION_CONTEXT |
| 314 | CIM_ERR_INVALID_OPERATION_TIMEOUT | CIM_ERR_INVALID_OPERATION_TIMEOUT |
| 315 | CIM_ERR_PULL_HAS_BEEN_ABANDONED | CIM_ERR_PULL_HAS_BEEN_ABANDONED |
| 316 | CIM_ERR_PULL_CANNOT_BE_ABANDONED | CIM_ERR_PULL_CANNOT_BE_ABANDONED |
| 317 | CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED | CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED |
| 318 | CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED | CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED |
| 319 | CIM_ERR_SERVER_LIMITS_EXCEEDED | CIM_ERR_SERVER_LIMITS_EXCEEDED |
| 320 | CIM_ERR_SERVER_IS_SHUTTING_DOWN | CIM_ERR_SERVER_IS_SHUTTING_DOWN |
| 321 | CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED | CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED |
| 322 | 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. |
| 323 | 2.22.1 | 2.22.1 |
| 324 | 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. |
| 325 | 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\'. |
| 326 | 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.) |
| 327 | 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 |
| 328 | New | New |
| 329 | Running | Running |
| 330 | Suspended | Suspended |
| 331 | Terminated | Terminated |
| 332 | Killed | Killed |
| 333 | Exception | Exception |
| 334 | Service | Service |
| 335 | Query Pending | Query Pending |
| 336 | 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. |
| 337 | 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. |
| 338 | 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. |
| 339 | Completed with No Error | Completed with No Error |
| 340 | Unknown/Unspecified Error | Unknown/Unspecified Error |
| 341 | Can NOT complete within Timeout Period | Can NOT complete within Timeout Period |
| 342 | Invalid Parameter | Invalid Parameter |
| 343 | In Use | In Use |
| 344 | Method Parameters Checked - Transition Started | Method Parameters Checked - Transition Started |
| 345 | Invalid State Transition | Invalid State Transition |
| 346 | Use of Timeout Parameter Not Supported | Use of Timeout Parameter Not Supported |
| 347 | Busy | Busy |
| 348 | Method Reserved | Method Reserved |
| 349 | 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. |
| 350 | Start | Start |
| 351 | Suspend | Suspend |
| 352 | Terminate | Terminate |
| 353 | Kill | Kill |
| 354 | 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. |
| 355 | 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. |
| 356 | Unspecified Error | Unspecified Error |
| 357 | 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. |
| 358 | 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. |
| 359 | 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. |
| 360 | Enabled | Enabled |
| 361 | Disabled | Disabled |
| 362 | Not Applicable | Not Applicable |
| 363 | Enabled but Offline | Enabled but Offline |
| 364 | Deferred | Deferred |
| 365 | Quiesce | Quiesce |
| 366 | 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. |
| 367 | 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". |
| 368 | Shut Down | Shut Down |
| 369 | No Change | No Change |
| 370 | Offline | Offline |
| 371 | Test | Test |
| 372 | Reboot | Reboot |
| 373 | Reset | Reset |
| 374 | 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). |
| 375 | No Default | No Default |
| 376 | 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. |
| 377 | 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. |
| 378 | Defer | Defer |
| 379 | 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. |
| 380 | 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. |
| 381 | Unknown or Unspecified Error | Unknown or Unspecified Error |
| 382 | Cannot complete within Timeout Period | Cannot complete within Timeout Period |
| 383 | Method Parameters Checked - Job Started | Method Parameters Checked - Job Started |
| 384 | 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. |
| 385 | 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. |
| 386 | 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. |
| 387 | 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. |
| 388 | NetCfgInstanceId of this adapter | NetCfgInstanceId of this adapter |
| 389 | IfAlias of the member adapter | IfAlias of the member adapter |
| 390 | IfDescr of the member adapter | IfDescr of the member adapter |
| 391 | Name of the team this is a member of | Name of the team this is a member of |
| 392 | Transmission speed of the adapter | Transmission speed of the adapter |
| 393 | Receive speed of the adapter | Receive speed of the adapter |
| 394 | Failure reason | Failure reason |
| 395 | Represents Network Adapters used in IM Platform, ie. the members and team nics | Represents Network Adapters used in IM Platform, ie. the members and team nics |
| 396 | Administrative role of this member in the team | Administrative role of this member in the team |
| 397 | Current operational mode of this member in the team | Current operational mode of this member in the team |
| 398 | Represents members of an lbfo team | Represents members of an lbfo team |
| 399 | VlanID of the TeamNic | VlanID of the TeamNic |
| 400 | Whether the TeamNic is the primary TeamNic | Whether the TeamNic is the primary TeamNic |
| 401 | Whether the TeamNic is the default TeamNic | Whether the TeamNic is the default TeamNic |
| 402 | Represents a NetAdapter that is a TNic for an Lbfo Team | Represents a NetAdapter that is a TNic for an Lbfo Team |
| 403 | The parent element in the association. | The parent element in the association. |
| 404 | The child element in the association. | The child element in the association. |
| 405 | 2.7.0 | 2.7.0 |
| 406 | CIM_Component is a generic association used to establish \'part of\' relationships between Managed Elements. For example, it could be used to define the components or parts of a System. | CIM_Component is a generic association used to establish \'part of\' relationships between Managed Elements. For example, it could be used to define the components or parts of a System. |
| 407 | The LbfoTeam associated with the LbfoTeamMember | The LbfoTeam associated with the LbfoTeamMember |
| 408 | The LbfoTeamMember associated with the LbfoTeam | The LbfoTeamMember associated with the LbfoTeam |
| 409 | Represents an association between an lbfo team and its members | Represents an association between an lbfo team and its members |
| 410 | The LbfoTeam associated with the LbfoTeamNic | The LbfoTeam associated with the LbfoTeamNic |
| 411 | The LbfoTeamNic associated with the LbfoTeam | The LbfoTeamNic associated with the LbfoTeam |
| 412 | Represents an association between an Lbfo Team and its TNics | Represents an association between an Lbfo Team and its TNics |
| 413 | The LbfoTeam associated with the LbfoTeamProvider | The LbfoTeam associated with the LbfoTeamProvider |
| 414 | The LbfoTeamProvider associated with the LbfoTeam | The LbfoTeamProvider associated with the LbfoTeam |
| 415 | Represents an association between an lbfo team and its providers | Represents an association between an lbfo team and its providers |
| 416 | Sets the LACP connection timeout to either Slow (90 seconds) or Fast (3 seconds, default). | Sets the LACP connection timeout to either Slow (90 seconds) or Fast (3 seconds, default). |
| 6001 | General failure | General failure |
| 6002 | A team already exists with name '%1!s!' | A team already exists with name '%1!s!' |
| 6004 | '%1!s!' is already a member of another team ('%2!s!') | '%1!s!' is already a member of another team ('%2!s!') |
| 6005 | Member '%1!s!' cannot be teamed as it has a Hyper-V role enabled on it | Member '%1!s!' cannot be teamed as it has a Hyper-V role enabled on it |
| 6006 | Cannot remove the only member '%1!s!' of team '%2!s!' | Cannot remove the only member '%1!s!' of team '%2!s!' |
| 6009 | There is no team on this system with the name '%1!s!' | There is no team on this system with the name '%1!s!' |
| 6011 | Validation failed and changes to the system are rolled back. | Validation failed and changes to the system are rolled back. |
| 6012 | '%1!s!' is not a valid Team name. Team name cannot contain tabs, only spaces, or any of the following characters: \/:*?|" and must be less than %2!u! characters long | '%1!s!' is not a valid Team name. Team name cannot contain tabs, only spaces, or any of the following characters: \/:*?|" and must be less than %2!u! characters long |
| 6014 | Operation timed out: Cannot perform requested operation as '%1!s!' is currently updating network configuration | Operation timed out: Cannot perform requested operation as '%1!s!' is currently updating network configuration |
| 6015 | Operation timed out: Operation failed and unable to rollback the changes as '%1!s!' is currently updating network configuration | Operation timed out: Operation failed and unable to rollback the changes as '%1!s!' is currently updating network configuration |
| 6016 | Operation timed out: TeamNic installation did not complete in a timely manner. Check if all TeamMembers are disabled | Operation timed out: TeamNic installation did not complete in a timely manner. Check if all TeamMembers are disabled |
| 6017 | Access Denied. This operation requires administrator privileges. | Access Denied. This operation requires administrator privileges. |
| 7004 | '%1!s!' is already a member of this team ('%2!s!') | '%1!s!' is already a member of this team ('%2!s!') |
| 7008 | VlanID %1!u! is already being used by another TeamNic '%2!s!' in team '%3!s!' | VlanID %1!u! is already being used by another TeamNic '%2!s!' in team '%3!s!' |
| 7009 | Another NIC already exists on this system with the name '%1!s!' | Another NIC already exists on this system with the name '%1!s!' |
| 7010 | Cannot remove the primary TeamNic ('%1!s!') of the team ('%2!s!') | Cannot remove the primary TeamNic ('%1!s!') of the team ('%2!s!') |
| 7012 | Team '%1!s!' already has the Member %2!s! in 'Standby' mode. A team can have at most one 'Standby' member. | Team '%1!s!' already has the Member %2!s! in 'Standby' mode. A team can have at most one 'Standby' member. |
| 7013 | There are no teamable NetAdapters on this system that match Name '%1!s!' | There are no teamable NetAdapters on this system that match Name '%1!s!' |
| 7015 | '%1!s!' is not an LBFO team | '%1!s!' is not an LBFO team |
| 7016 | Cannot set non-primary TeamNic ('%1!s!') in team '%2!s!' as Default TeamNic | Cannot set non-primary TeamNic ('%1!s!') in team '%2!s!' as Default TeamNic |
| 7019 | '%1!s!' is not a valid TeamNic name. Team name cannot contain tabs, only spaces, or any of the following characters: \/:*?|" and must be less than %2!u! characters long | '%1!s!' is not a valid TeamNic name. Team name cannot contain tabs, only spaces, or any of the following characters: \/:*?|" and must be less than %2!u! characters long |
| 7020 | 'SwitchIndependent' is the only TeamingMode value supported in a Virtual Machine | 'SwitchIndependent' is the only TeamingMode value supported in a Virtual Machine |
| 7021 | The only valid LoadBalancingAlgorithms in a Virtual Machine are 'TransportPorts', 'IPAddresses', and 'MacAddresses' | The only valid LoadBalancingAlgorithms in a Virtual Machine are 'TransportPorts', 'IPAddresses', and 'MacAddresses' |
| 7022 | Operation timed out: Cannot perform requested operation as another NetLbfo operation is in progress | Operation timed out: Cannot perform requested operation as another NetLbfo operation is in progress |
| 7026 | There are no teamable NetAdapters on the system matching TeamMembers parameter | There are no teamable NetAdapters on the system matching TeamMembers parameter |
| 7028 | Members can be set to the 'Standby' AdministrativeMode only in the 'SwitchIndependent' TeamingMode | Members can be set to the 'Standby' AdministrativeMode only in the 'SwitchIndependent' TeamingMode |
| 7029 | The LBFO feature is not currently enabled, or LBFO is not supported on this SKU. | The LBFO feature is not currently enabled, or LBFO is not supported on this SKU. |
| 7030 | Adding %1!s! 'Standby' members to Team '%2!s!'. A team cannot have more than one 'Standby' Member. | Adding %1!s! 'Standby' members to Team '%2!s!'. A team cannot have more than one 'Standby' Member. |
| 7031 | Cannot set the mutually exclusive options 'Default' and 'VlanID' together. | Cannot set the mutually exclusive options 'Default' and 'VlanID' together. |
| 7032 | The team '%1!s!' already has %2!u! TeamNics, the maximum number allowed. | The team '%1!s!' already has %2!u! TeamNics, the maximum number allowed. |
| 7033 | Cannot add adapter '%1!s!' as a member to the team '%2!s!' as it is currently not enabled. Please enable it and retry. | Cannot add adapter '%1!s!' as a member to the team '%2!s!' as it is currently not enabled. Please enable it and retry. |
| 7034 | Cannot rename a team in this manner. Use Rename instead. | Cannot rename a team in this manner. Use Rename instead. |
| 7035 | Invalid LoadBalancingAlgorithm | Invalid LoadBalancingAlgorithm |
| 7036 | Invalid TeamingMode | Invalid TeamingMode |
| 7037 | Try again: Another component made changes to the network driver configuration that interfered with this LBFO change | Try again: Another component made changes to the network driver configuration that interfered with this LBFO change |
| 7038 | Invalid LacpTimer | Invalid LacpTimer |
| 7039 | Cannot set LacpTimer on teams that are not in 'Lacp' TeamingMode | Cannot set LacpTimer on teams that are not in 'Lacp' TeamingMode |
| 8001 | %1!s! | %1!s! |
| 8002 | %1!s! - VLAN %2!u! | %1!s! - VLAN %2!u! |
| 9001 | Creates Team:'%1!s!' with TeamMembers:{%2!s!}, TeamNicName:'%3!s!', TeamingMode:'%4!s!' and LoadBalancingAlgorithm:'%5!s!'. | Creates Team:'%1!s!' with TeamMembers:{%2!s!}, TeamNicName:'%3!s!', TeamingMode:'%4!s!' and LoadBalancingAlgorithm:'%5!s!'. |
| 9002 | Removes the Team:'%1!s!' from the system. | Removes the Team:'%1!s!' from the system. |
| 9003 | Changes the Name of the Team from '%1!s!' to '%2!s!'. | Changes the Name of the Team from '%1!s!' to '%2!s!'. |
| 9004 | Changes the TeamingMode for Team '%1!s!' from '%2!s!' to '%3!s!'. | Changes the TeamingMode for Team '%1!s!' from '%2!s!' to '%3!s!'. |
| 9005 | Changes the LoadBalancingAlgorithm for Team '%1!s!' from '%2!s!' to '%3!s!'. | Changes the LoadBalancingAlgorithm for Team '%1!s!' from '%2!s!' to '%3!s!'. |
| 9006 | Changes the LacpTimer for Team '%1!s!' to '%2!s!'. | Changes the LacpTimer for Team '%1!s!' to '%2!s!'. |
| 9007 | Creates Team:'%1!s!' with TeamMembers:{%2!s!}, TeamNicName:'%3!s!', TeamingMode:'%4!s!', LoadBalancingAlgorithm:'%5!s!' and LACP Timer:'%6!s!'. | Creates Team:'%1!s!' with TeamMembers:{%2!s!}, TeamNicName:'%3!s!', TeamingMode:'%4!s!', LoadBalancingAlgorithm:'%5!s!' and LACP Timer:'%6!s!'. |
| 9020 | Adds the Member:'%1!s!' with AdministrativeMode:'%2!s!' to the Team:'%3!s!' | Adds the Member:'%1!s!' with AdministrativeMode:'%2!s!' to the Team:'%3!s!' |
| 9021 | Removes the Member:'%1!s!' from Team:'%2!s!'. | Removes the Member:'%1!s!' from Team:'%2!s!'. |
| 9022 | Changes the AdministrativeMode for Member:'%1!s!' from '%2!s!' to '%3!s!' in Team:'%4!s!'. | Changes the AdministrativeMode for Member:'%1!s!' from '%2!s!' to '%3!s!' in Team:'%4!s!'. |
| 9040 | Adds TeamNic:'%1!s!' with VlanID:%2!u! to the Team:'%3!s!'. | Adds TeamNic:'%1!s!' with VlanID:%2!u! to the Team:'%3!s!'. |
| 9041 | Removes TeamNic:'%1!s!' from the Team:'%2!s!'. | Removes TeamNic:'%1!s!' from the Team:'%2!s!'. |
| 9042 | Sets VlanID for TeamNic:'%1!s!' from 'Default' to %2!u! in Team:'%3!s!'. | Sets VlanID for TeamNic:'%1!s!' from 'Default' to %2!u! in Team:'%3!s!'. |
| 9043 | Sets to 'Default' TeamNic:'%1!s!' from VlanID:%2!u! in Team:'%3!s!'. | Sets to 'Default' TeamNic:'%1!s!' from VlanID:%2!u! in Team:'%3!s!'. |
| 9044 | Changes the VlanID for TeamNic:'%1!s!' from %2!u! to %3!u! in Team:'%4!s!'. | Changes the VlanID for TeamNic:'%1!s!' from %2!u! to %3!u! in Team:'%4!s!'. |
| File Description: | NDIS IM Platform WMI Provider |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | ndisimplatwmi.DLL |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | ndisimplatwmi.DLL.MUI |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x41D, 1200 |