| File name: | NetEventPacketCapture.dll.mui |
| Size: | 51200 byte |
| MD5: | 00fa6d86e813090f56555f7727ac061f |
| SHA1: | 93ce000e90c2407cd4f33e5182ffd4b2ef4726b4 |
| SHA256: | a01e66379db9e5013f9bc59cfeb8137d1c77143aefd0f91d97a909016fd52364 |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Arabic 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 | Arabic | 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 | 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. |
| 8 | 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. |
| 9 | 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. |
| 10 | Unknown | Unknown |
| 11 | Other | Other |
| 12 | OK | OK |
| 13 | Degraded | Degraded |
| 14 | Stressed | Stressed |
| 15 | Predictive Failure | Predictive Failure |
| 16 | Error | Error |
| 17 | Non-Recoverable Error | Non-Recoverable Error |
| 18 | Starting | Starting |
| 19 | Stopping | Stopping |
| 20 | Stopped | Stopped |
| 21 | In Service | In Service |
| 22 | No Contact | No Contact |
| 23 | Lost Communication | Lost Communication |
| 24 | Aborted | Aborted |
| 25 | Dormant | Dormant |
| 26 | Supporting Entity in Error | Supporting Entity in Error |
| 27 | Completed | Completed |
| 28 | Power Mode | Power Mode |
| 29 | DMTF Reserved | DMTF Reserved |
| 30 | Vendor Reserved | Vendor Reserved |
| 31 | 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. |
| 32 | 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. |
| 33 | 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. |
| 34 | Degraded/Warning | Degraded/Warning |
| 35 | Minor failure | Minor failure |
| 36 | Major failure | Major failure |
| 37 | Critical failure | Critical failure |
| 38 | Non-recoverable error | Non-recoverable error |
| 39 | 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. |
| 40 | Not Available | Not Available |
| 41 | Communication OK | Communication OK |
| 42 | 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. |
| 43 | No Additional Information | No Additional Information |
| 44 | 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. |
| 45 | Servicing | Servicing |
| 46 | Migrating | Migrating |
| 47 | Emigrating | Emigrating |
| 48 | Immigrating | Immigrating |
| 49 | Snapshotting | Snapshotting |
| 50 | Shutting Down | Shutting Down |
| 51 | In Test | In Test |
| 52 | Transitioning | Transitioning |
| 53 | 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. |
| 54 | 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. |
| 55 | 2.22.0 | 2.22.0 |
| 56 | 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. |
| 57 | 2.6.0 | 2.6.0 |
| 58 | The friendly name of the session. | The friendly name of the session. |
| 59 | Guid, the unique Id of the session | Guid, the unique Id of the session |
| 60 | The mode of the capture - SaveToFile, RealtimeRPC, RealtimeLocal. | The mode of the capture - SaveToFile, RealtimeRPC, RealtimeLocal. |
| 61 | The local filename to which event capture traces will be written to. Only valid when CaptureMode equals SaveToFile | The local filename to which event capture traces will be written to. Only valid when CaptureMode equals SaveToFile |
| 62 | The maximum size of the local file to which event capture traces will be written to, in MB. Only valid when CaptureMode equals SaveToFile. Minimum value is 1. When set to 0, there is no limit on the file size. | The maximum size of the local file to which event capture traces will be written to, in MB. Only valid when CaptureMode equals SaveToFile. Minimum value is 1. When set to 0, there is no limit on the file size. |
| 63 | The trace buffer size for the ETW session. The value range is 1KB to 1024KB. | The trace buffer size for the ETW session. The value range is 1KB to 1024KB. |
| 64 | The maximum number of trace buffers used for the ETW session. | The maximum number of trace buffers used for the ETW session. |
| 65 | The current status of the Session - Running, Stopped, Failed | The current status of the Session - Running, Stopped, Failed |
| 66 | Starts the event capture, applying the session configuration | Starts the event capture, applying the session configuration |
| 67 | Stops the event capture | Stops the event capture |
| 68 | This class encapsulates an ETW capture session on a computer. | This class encapsulates an ETW capture session on a computer. |
| 69 | The name of the provider | The name of the provider |
| 70 | Guid, the unique id of the provider installed on the computer. | Guid, the unique id of the provider installed on the computer. |
| 71 | Guid, the unique id of the session, when part of a session. NULL Guid otherwise. | Guid, the unique id of the session, when part of a session. NULL Guid otherwise. |
| 72 | The session of the provider, when part of a session. | The session of the provider, when part of a session. |
| 73 | The maximum event level for the event capture. | The maximum event level for the event capture. |
| 74 | The MatchAnyKeyword mask specified for the event capture. | The MatchAnyKeyword mask specified for the event capture. |
| 75 | The MatchAllKeyword mask specified for the event capture. | The MatchAllKeyword mask specified for the event capture. |
| 76 | This class encapsulates an ETW provider on a computer for the event capture. | This class encapsulates an ETW provider on a computer for the event capture. |
| 77 | This class encapsulates an ETW provider on a computer for the event capture | This class encapsulates an ETW provider on a computer for the event capture |
| 78 | Type of the capture - Physical, VMSwitch or Both | Type of the capture - Physical, VMSwitch or Both |
| 79 | Specifies if the capture is required at each possible layer in the target networking stack, or just the default layer. For a VMSwitch, the filter is installed at the top of the extension stack by default. For a physical network adapater, the filter is installed just above the miniport. | Specifies if the capture is required at each possible layer in the target networking stack, or just the default layer. For a VMSwitch, the filter is installed at the top of the extension stack by default. For a physical network adapater, the filter is installed just above the miniport. |
| 80 | Specifies MAC Addresses or LinkLayerAddress for filtering | Specifies MAC Addresses or LinkLayerAddress for filtering |
| 81 | Specifies the EtherType for filtering | Specifies the EtherType for filtering |
| 82 | Specifies the IP Addresses(V4/V6) for filtering | Specifies the IP Addresses(V4/V6) for filtering |
| 83 | Specifies the IP Protocols for filtering | Specifies the IP Protocols for filtering |
| 84 | Specifies the packet truncation length in bytes. The default is 128. The minimum is 14. The value of zero disables truncation. | Specifies the packet truncation length in bytes. The default is 128. The minimum is 14. The value of zero disables truncation. |
| 85 | Specifies the direction of the traffic to be captured when Vm Targets are added - Ingress, Egress or IngressAndEgress. | Specifies the direction of the traffic to be captured when Vm Targets are added - Ingress, Egress or IngressAndEgress. |
| 86 | This class encapsulates the Packet Capture Filter ETW provider on a computer | This class encapsulates the Packet Capture Filter ETW provider on a computer |
| 87 | Name of the object | Name of the object |
| 88 | The Unique identifying key of the object. | The Unique identifying key of the object. |
| 89 | Name of the packet capture provider. | Name of the packet capture provider. |
| 90 | Current status of the Capture. | Current status of the Capture. |
| 91 | This class encapsulates a Packet Capture Target on a computer | This class encapsulates a Packet Capture Target on a computer |
| 92 | The friendly name or description of the target network adapter. | The friendly name or description of the target network adapter. |
| 93 | MAC controller promiscuous mode setting. | MAC controller promiscuous mode setting. |
| 94 | This class encapsulates a target network adapter, on which the traffic is to be captured. | This class encapsulates a target network adapter, on which the traffic is to be captured. |
| 95 | The MacAddress or the LinkLayerAddress of the VM Network Adapter. | The MacAddress or the LinkLayerAddress of the VM Network Adapter. |
| 96 | The name of the virtual switch the VM network adapter is connected to. | The name of the virtual switch the VM network adapter is connected to. |
| 97 | The port name of the VM network adapter. | The port name of the VM network adapter. |
| 98 | The name of the virtual machine that the VM network adapter belongs to. | The name of the virtual machine that the VM network adapter belongs to. |
| 99 | The Id of the virtual machine that the VM network adapter belongs to. | The Id of the virtual machine that the VM network adapter belongs to. |
| 100 | This class encapsulates a VM Network Adapter, that corresponds to a port on a virtual switch, on which the traffic is to be captured. | This class encapsulates a VM Network Adapter, that corresponds to a port on a virtual switch, on which the traffic is to be captured. |
| 101 | Encapsulates a Virtual Switch on the hyper-v host, on which the traffic is to be captured. | Encapsulates a Virtual Switch on the hyper-v host, on which the traffic is to be captured. |
| 102 | The parent element in the association. | The parent element in the association. |
| 103 | The child element in the association. | The child element in the association. |
| 104 | 2.7.0 | 2.7.0 |
| 105 | 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. |
| 106 | Identifies the packet capture provider. | Identifies the packet capture provider. |
| 107 | Identifies the packet capture target. | Identifies the packet capture target. |
| 108 | This class encapsulates the association between the packet capture provider and a packet capture target. | This class encapsulates the association between the packet capture provider and a packet capture target. |
| 109 | Identifies the session | Identifies the session |
| 110 | Identifies the provider | Identifies the provider |
| 111 | This class encapsulates an association between a session and a provider | This class encapsulates an association between a session and a provider |
| 112 | WFP layer set | WFP layer set |
| 113 | Whether include the discarded packet events | Whether include the discarded packet events |
| 114 | Specifies the TCP ports for filtering | Specifies the TCP ports for filtering |
| 115 | Specifies the UDP ports for filtering | Specifies the UDP ports for filtering |
| 116 | This class encapsulates the WFP Capture Filter ETW provider on a computer | This class encapsulates the WFP Capture Filter ETW provider on a computer |
| 117 | Designates one or more destination MAC addresses to filter on. Network traffic is logged when the filter matches. | Designates one or more destination MAC addresses to filter on. Network traffic is logged when the filter matches. |
| 118 | Designates one or more TCP ports to filter on. Network traffic is logged when the filter matches. | Designates one or more TCP ports to filter on. Network traffic is logged when the filter matches. |
| 119 | Designates one or more UDP Ports to filter on. Network traffic is logged when the filter matches. | Designates one or more UDP Ports to filter on. Network traffic is logged when the filter matches. |
| 120 | Designates one or more source MAC addresses to filter on. Network traffic is logged when the filter matches. | Designates one or more source MAC addresses to filter on. Network traffic is logged when the filter matches. |
| 121 | Designates one or more VLAN Ids to filter on. Network traffic is logged when the filter matches. | Designates one or more VLAN Ids to filter on. Network traffic is logged when the filter matches. |
| 122 | Designates one or more GRE keys to filter on. Network traffic is logged when the filter matches. | Designates one or more GRE keys to filter on. Network traffic is logged when the filter matches. |
| 123 | Designates one or more VXLAN TNI values to filter on. Network traffic is logged when the filter matches. | Designates one or more VXLAN TNI values to filter on. Network traffic is logged when the filter matches. |
| 124 | Designates one or more Source IP addresses to filter on. Network traffic is logged when the filter matches. | Designates one or more Source IP addresses to filter on. Network traffic is logged when the filter matches. |
| 125 | Designates one or more destination IP addresses to filter on. Network traffic is logged when the filter matches. | Designates one or more destination IP addresses to filter on. Network traffic is logged when the filter matches. |
| 126 | Designates one or more IP protocols (such as TCP or UDP) to filter on. Network traffic is logged when the filter matches. | Designates one or more IP protocols (such as TCP or UDP) to filter on. Network traffic is logged when the filter matches. |
| 127 | Designates the direction of the traffic flows to trace - Inbound, Outbound, or InboundOutbound. | Designates the direction of the traffic flows to trace - Inbound, Outbound, or InboundOutbound. |
| 128 | Specifies the friendly name of the switch to limit tracing to.
This is used in conjunction with the PortIds filter to enable tracing per-packet events on one or more switch ports. |
Specifies the friendly name of the switch to limit tracing to.
This is used in conjunction with the PortIds filter to enable tracing per-packet events on one or more switch ports. |
| 129 | Designates the switch ports to limit per-packet event tracing to.
Events are traced if the filter matches. To limit tracing to a particular flow, use more granular filters (e.g., address, and direction filters). |
Designates the switch ports to limit per-packet event tracing to.
Events are traced if the filter matches. To limit tracing to a particular flow, use more granular filters (e.g., address, and direction filters). |
| 130 | Configures the Virtual Filtering Platform ETW provider on a computer. | Configures the Virtual Filtering Platform ETW provider on a computer. |
| 131 | Specifies the friendly name of the switch to limit tracing to. This is used in conjunction with the PortIds filter to enabled tracing per-packet events on one or more switch ports. | Specifies the friendly name of the switch to limit tracing to. This is used in conjunction with the PortIds filter to enabled tracing per-packet events on one or more switch ports. |
| 132 | Designates the switch ports to limit per-packet event tracing to. Events are traced if the filter matches. | Designates the switch ports to limit per-packet event tracing to. Events are traced if the filter matches. |
| 133 | Configures the Hyper-V Virtual Switch ETW provider that is part of the NetEventSession. | Configures the Hyper-V Virtual Switch ETW provider that is part of the NetEventSession. |
| 5001 | Another Session already exists on this computer with the name '%1!s!'. | Another Session already exists on this computer with the name '%1!s!'. |
| 5002 | There are no sessions on this computer with the name '%1!s!'. | There are no sessions on this computer with the name '%1!s!'. |
| 5003 | '%1!s!' is not a valid Session name. | '%1!s!' is not a valid Session name. |
| 5004 | Session:'%1!s!' already running on this computer. | Session:'%1!s!' already running on this computer. |
| 5005 | There are no ETW Providers on this computer that match the name '%1!s!'. | There are no ETW Providers on this computer that match the name '%1!s!'. |
| 5006 | There are no Network Adapters on this computer that match the name '%1!s!'. | There are no Network Adapters on this computer that match the name '%1!s!'. |
| 5007 | There are no VM Switches on this computer that match the name '%1!s!'. | There are no VM Switches on this computer that match the name '%1!s!'. |
| 5008 | There are no VM Network Adapters on this computer that match the name '%1!s!'. | There are no VM Network Adapters on this computer that match the name '%1!s!'. |
| 5009 | 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. |
| 5010 | Access Denied. This operation requires administrator privileges. | Access Denied. This operation requires administrator privileges. |
| 5011 | Invalid format. Please check the value of the parameter:'%1!s!' | Invalid format. Please check the value of the parameter:'%1!s!' |
| 5012 | You need to specify parameters '%1!s!' for this operation. | You need to specify parameters '%1!s!' for this operation. |
| 5013 | %1!s! and %2!s! | %1!s! and %2!s! |
| 5101 | Creates Session with Name:'%1!s!' CaptureMode:{%2!s!}, LocalFilePath:'%3!s!', MaxFileSize:'%4!u!', MaxNumberOfBuffers:'%5!u!, and TraceBufferSize:'%6!u!'. | Creates Session with Name:'%1!s!' CaptureMode:{%2!s!}, LocalFilePath:'%3!s!', MaxFileSize:'%4!u!', MaxNumberOfBuffers:'%5!u!, and TraceBufferSize:'%6!u!'. |
| 5102 | Starts the ETW Session:'%1!s!' on this computer. | Starts the ETW Session:'%1!s!' on this computer. |
| 5103 | Stops the ETW Session:'%1!s!' on this computer. | Stops the ETW Session:'%1!s!' on this computer. |
| 5104 | Removes the ETW Session:'%1!s!' from this computer. | Removes the ETW Session:'%1!s!' from this computer. |
| 5105 | Adds the ETW Provider:'%1!s!' to the Session:'%2!s!' with Level:'%3!u!', MatchAllKeywords:'4%!I64!' and MatchAnyKeywords:'%5!I64!' | Adds the ETW Provider:'%1!s!' to the Session:'%2!s!' with Level:'%3!u!', MatchAllKeywords:'4%!I64!' and MatchAnyKeywords:'%5!I64!' |
| 5106 | Removes the ETW Provider:'%1!s!' from Session:'%2!s!'. | Removes the ETW Provider:'%1!s!' from Session:'%2!s!'. |
| 5107 | Adds the Packet Capture ETW Provider:'%1!s!' to the Session:'%2!s!' with Level:'%3!u!', MatchAllKeywords:'4%!I64!', MatchAnyKeywords:'%5!I64!', CaptureType:'%6!s!, MultiLayer:'%7!u!, LinkLayerAddress:'%8!s!', EtherType:'%9!s!', IpAddresses:'%10!s!', IpProtocols:'%11!s!', TruncationLength:'%12!u!' and VmCaptureDirection:'%13!s!' | Adds the Packet Capture ETW Provider:'%1!s!' to the Session:'%2!s!' with Level:'%3!u!', MatchAllKeywords:'4%!I64!', MatchAnyKeywords:'%5!I64!', CaptureType:'%6!s!, MultiLayer:'%7!u!, LinkLayerAddress:'%8!s!', EtherType:'%9!s!', IpAddresses:'%10!s!', IpProtocols:'%11!s!', TruncationLength:'%12!u!' and VmCaptureDirection:'%13!s!' |
| 5108 | Removes the Packet Capture ETW Provider:'%1!s!' from Session:'%2!s!'. | Removes the Packet Capture ETW Provider:'%1!s!' from Session:'%2!s!'. |
| 5109 | Adds Network Adapter:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. | Adds Network Adapter:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5110 | Removes Network Adapter:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. | Removes Network Adapter:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5111 | Adds VM Network Adapter:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. | Adds VM Network Adapter:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5112 | Removes VM Network Adapter:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. | Removes VM Network Adapter:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5113 | Adds VMSwitch:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. | Adds VMSwitch:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5114 | Removes VMSwitch:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. | Removes VMSwitch:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5115 | %1!s! %2!s! | %1!s! %2!s! |
| 5116 | '%1!s!' | '%1!s!' |
| 5117 | '%1!s!', | '%1!s!', |
| File Description: | NetEvent Packet Capture Provider |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | NetEventPacketCapture.dll |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | NetEventPacketCapture.dll.mui |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x401, 1200 |