| File name: | NetEventPacketCapture.dll.mui |
| Size: | 21504 byte |
| MD5: | e1e2de9623043b5456012a5959a861d5 |
| SHA1: | f2acb7985e04f0f51775462a0ee1582a89f8d279 |
| SHA256: | 45fa9fd70db5074d339500223490c42347adb95cd217878d99801f3351ce0d31 |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Chinese (Simplified) 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 | Chinese (Simplified) | English |
|---|---|---|
| 1 | InstanceID 是一个可选属性，可用于在实例化 Namespace 的作用域内模糊并唯一地标识此类的实例。此类的各种子类可能会替代此属性，使其成为必要属性或密钥。此类子类可能还会修改首选的算法，以确保唯一性（如下方所定义）。 为确保在 NameSpace 内的唯一性，InstanceID 的值应使用以下“首选”算法来构造: : 其中 和 以冒号 (:) 分隔，并且 中必须包含用于创建或定义 InstanceID 的版权、商标或商业实体拥有的其他唯一名称，或者公认世界权威机构向该商业实体分配的注册 ID。(此要求与架构类名称的 _ 结构类似。) 此外，为确保唯一性， 中必须包含一个冒号 (:)。在使用此算法时，InstanceID 中的第一个冒号必须位于 和 之间。 由商业实体选择，不得再用于标识其他基础(实际)元素。如果 不为空并且不使用上述“首选”算法，则负责定义的实体必须保证最终构造的 InstanceID 不会在此提供程序或任何其他提供程序为此实例的 NameSpace 创建的任何 InstanceID 中发生重复使用情况。 如果对于 DMTF 定义的实例， 未设置为空，则必须使用“首选”算法，并且将 设置为 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 | Caption 属性是关于对象的简短文字描述(只有一行的字符串)。 | The Caption property is a short textual description (one- line string) of the object. |
| 3 | Description 属性提供关于对象的文字描述。 | The Description property provides a textual description of the object. |
| 4 | 对象的用户友好名称。此属性允许每个实例在其密钥属性、标识数据和描述信息之外创建一个用户友好名称。 请注意，ManagedSystemElement 的 Name 属性也被定义为用户友好名称。但是，该属性通常被分类为密钥子类。正常情况下，同一属性无法在不引起任何不一致的情况下既标识身份又充当用户友好名称。如果存在 Name 属性并且其不是密钥属性(例如 LogicalDevice 的该属性)，则 Name 属性和 ElementName 属性中可显示相同的信息。请注意，如果存在 CIM_EnabledLogicalElementCapabilities 的关联实例，则此属性可能会受在该类的 ElementNameMask 和 MaxElementNameLen 属性中定义的限制所限。 |
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 是一个抽象类，为 CIM 架构中的非关联类提供一个公共超类(即继承树的顶部)。 | 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. |
| 8 | Name 属性定义对象的名称标签。在被分类为子类时，Name 属性可能会被替代为密钥属性。 | 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 | 表明元素的当前状态。定义了各种工作状态。其中的许多枚举\值都一目了然。但是，也有少数值并非如此，以下将对这些值予以详细说明。 “已强调”表明元素正在工作，但是需要注意。过载、过热等都属于“强调”状态。 “预测故障”表明元素表面上正在工作，但是预计不久会出现故障。 “正在维修”说明元素正在接受配置、维护、清洁或其他方式的管理。 “无连接”表明监视系统了解此元素，但是一直无法与其建立通信。 “通信中断”表明 ManagedSystem 元素已知存在，并且过去曾成功建立联系，但是现在不可访问。 “已停止”和“已中止”类似，只是前者暗示正常有序地停止，而后者暗示紧急停止，元素的状态和配置可能需要更新。 “休止”表明元素处于非活动状态或静态。 “支持实体出错”表明此元素可能“良好”，但是此元素所依赖的另一个元素可能出现错误。由于低层网络问题而无法工作的网络服务或端点就属于这种情况。 “已完成”表明该元素已完成操作。此值应与“良好”、“错误”或“已降级”组合使用，使客户端可以确定整个操作是已经良好地完成(已通过)、已经完成但出现错误(出现故障)，还是已经完成但是降级(操作已完成，但是未“良好”地完成或未报告错误)。 “电源模式”表明元素在 Associated PowerManagementService 关联中包含其他电源模式信息。 OperationalStatus 替换 ManagedSystemElement 的 Status 属性，以便提供一致的枚举方法，满足实现数组属性的需要，从而可以从现在\的环境迁移到未来的环境。以前未进行此更改是因为需要 DEPRECATED 限定符。由于在管理应用程序中广泛使用现有的 Status 属性，强烈建议提供程序/工具同时提供 Status 和 OperationalStatus 属性。此外，OperationalStatus 的第一个值应包含元素的主要状态。如果有 Status 属性，则 Status (由于是单值)也应提供元素的主要状态。 |
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 |
| 11 | 其他 | Other |
| 12 | 良好 | OK |
| 13 | 已降级 | Degraded |
| 14 | 已强调 | Stressed |
| 15 | 预测故障 | Predictive Failure |
| 16 | 错误 | Error |
| 17 | 不可恢复的错误 | Non-Recoverable Error |
| 18 | 正在启动 | Starting |
| 19 | 正在停止 | Stopping |
| 20 | 已停止 | Stopped |
| 21 | 正在维修 | In Service |
| 22 | 无连接 | No Contact |
| 23 | 通信中断 | Lost Communication |
| 24 | 已中止 | Aborted |
| 25 | 休止 | Dormant |
| 26 | 支持实体出错 | Supporting Entity in Error |
| 27 | 已完成 | Completed |
| 28 | 电源模式 | Power Mode |
| 29 | DMTF 保留 | DMTF Reserved |
| 30 | 供应商保留 | Vendor Reserved |
| 31 | 描述各种 OperationalStatus 数组值的字符串。例如，如果为 OperationalStatus 分配的值为“正在停止”，则此属性可能包含对对象停止原因的描述。请注意，此数组中的项与 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 | 表明对象当前状态的字符串。定义了各种工作和非工作状态。此属性替代 OperationalStatus 被弃用，后者在枚举中包括相同的语义。此更改出于以下 3 个原因: 1) 以数组的形式更准确地定义状态。当某个状态实际上是多值属性时(例如，某个元素的状态可能是“良好”和“已停止”)，这种定义便能克服通过单个值描述状态的局限性。 2) MaxLen 为 10 的限制太严格，无法清楚地描述枚举值。 3) 对 uint16 数据类型的更改在定义 CIM V2.0 时已讨论。但是，现有的 V1.0 使用的是字符串属性，不希望修改其代码。因此，Status 归属到 Schema 中。使用 Deprecated 限定符可以保留现有的属性，同时允许使用 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 | 表明元素当前的运行状况。此属性表明此元素(不必是其子组件)的运行状况。可能的值为 0 到 30，其中 5 意味着元素完全正常，30 意味着元素完全无法工作。定义的状态集如下: “不可恢复的错误”(30) - 元素以失败而告终，并且无法恢复。此元素提供的所有功能均已丧失。 “关键故障”(25) - 元素无法工作，并且可能无法恢复。 “主要故障”(20) - 元素失败。此组件的部分或全部功能可能已降级或无法使用。 “次要故障”(15) - 所有功能均可以使用，但是有些功能可能已降级。 “已降级/警告”(10) - 元素正在工作，并且提供所有功能。但是元素未实现最佳效果。例如，元素可能未实现最佳性能或报告了可恢复的错误。 “良好”(5) - 元素功能完全正常，使用正常的操作参数工作，没有出现错误。 “未知”(0) - 此时无法报告 HealthState。 DMTF 在状态集中为以后增加 HealthStates 保留了未用的部分。 |
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 |
| 35 | 次要故障 | Minor failure |
| 36 | 主要故障 | Major failure |
| 37 | 关键故障 | Critical failure |
| 39 | CommunicationStatus 表明检测与基础 ManagedElement 的通信能力。CommunicationStatus 包含以下某个值: 未知、无、通信良好、通信中断或无连接。 如果返回空值，则表明该检测(提供程序)未实现此属性。 “未知”表明该实现一般情况下能返回此属性，但是当前无法返回。 “不可用”表明该检测(提供程序)能返回此属性的值，但是一直无法为此硬件返回此属性的值，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “通信良好”表明已与元素建立了通信，但是未传输任何服务质量信息。 “无连接”表明监视系统了解此元素，但是一直无法与其建立通信 “通信中断”表明 ManagedElement 元素已知存在，并且过去曾成功建立联系，但是现在不可访问。 |
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 |
| 41 | 通信良好 | Communication OK |
| 42 | DetailedStatus 作为 PrimaryStatus 的补充，可提供其他状态详细信息。它包含以下某个值: 不可用、无其他信息、已强调、预测故障、错误、不可恢复的错误或支持实体出错。DetailedStatus 是对元素 PrimaryStatus 的扩充。 如果返回空值，则表明该检测(提供程序)未实现此属性。 “不可用”表明该检测(提供程序)能返回此属性的值，但是一直无法为此硬件返回此属性的值，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “无其他信息”表明元素如 PrimaryStatus 的“良好”状态所示在正常工作。 “已强调”表明元素正在工作，但是需要注意。过载、过热等都属于“强调”状态。 “已强调”表明元素正在工作，但是需要注意。过载、过热等都属于“强调”状态。 “预测故障”表明元素表面上正在工作，但是预计不久会出现故障。 “正在维修”说明元素正在接受配置、维护、清洁或其他方式的管理。 “无法恢复的错误”表明此元素出现需要人工干预的错误。 “支持实体出错”表明此元素可能“良好”，但是此元素所依赖的另一个元素可能出现错误。由于低层网络问题而无法工作的网络服务或端点就属于这种情况。 |
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 |
| 44 | OperatingStatus 提供针对元素工作状况的当前状态值，可用于提供有关 EnabledState 值的更多详细信息。当元素从一种状态向另一种状态过渡时，例如元素处于 EnabledState 与 RequestedState 之间的过渡或其他过渡期，OperatingStatus 还可以提供过渡状态信息。 OperatingStatus 包含以下某个值:未知、不可用、正在使用、正在启动、正在停止、已停止、已中止、已休止、已完成、正在迁移、正在向外迁移、正在向内迁移、正在拍摄快照、正在关闭或正在测试 如果返回空值，则表明该检测(提供程序)未实现此属性。 “未知”表明该实现一般情况下能返回此属性，但是当前无法返回。 “无”表明该检测(提供程序)能返回此属性的值，但是一直无法为此硬件返回此属性的值，或者由于此属性并不提供任何有意义的信息(例如某个属性只是为了向另一个属性添加附加信息)，因而有意未使用此属性。 “正在维修”说明元素正在接受配置、维护、清洁或其他方式的管理。 “正在启动”表明元素正在初始化。 “正在停止”表明元素正在进入有序的停止状态。 “已停止”和“已中止”类似，只是前者暗示正常有序地停止，而后者暗示紧急停止，元素的状态和配置可能需要更新。 “休止”表明元素处于非活动状态或静态。 “已完成”表明该元素已完成操作。此值应与 PrimaryStatus 中的“良好”、“错误”或“已降级”组合使用，使客户端可以确定整个操作是已经良好地完成(已通过)、已经完成但出现错误(出现故障)，还是已经完成但是降级(操作已完成，但是未“良好”地完成或未报告错误)。 “正在迁移”表明元素正在宿主元素之间移动。 “正在向内迁移”表明元素正在向某个新的宿主元素移入。 “正在向外迁移”表明元素正在从宿主元素移出。 “正在关闭”表明元素正在进入紧急停止状态。 “正在测试”表明元素正在执行测试功能。 “正在过渡”表明元素处于两种状态之间的过渡期，即该元素目前在前一状态和下一状态中均不完全可用。在没有其他适用的值可以表明到某个特定状态的过渡时，应使用此值。 “正在工作”表明元素正在工作，可以使用。 |
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 |
| 46 | 正在迁移 | Migrating |
| 47 | 正在迁出 | Emigrating |
| 48 | 正在迁入 | Immigrating |
| 49 | 正在快照 | Snapshotting |
| 50 | 正在关闭 | Shutting Down |
| 51 | 正在测试 | In Test |
| 52 | 正在转换 | Transitioning |
| 53 | PrimaryStatus 提供了一个高级状态值，用来对应状态的红-黄-绿三种类型展示。该值应与 DetailedStatus 一同使用，这样才能提供 ManagedElement 及其子组件的高级和详细的运行状况状态。 PrimaryStatus 的值包括: 未知、正常、降级或错误。“未知”表示执行通常能够返回此属性，但当时还无法返回。 “正常”表示 ManagedElement 运行正常。 “降级”表示 ManagedElement 运行在正常级别之下。 “错误”表示 ManagedElement 出现了错误状况。 |
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 是 System Element 层次结构的基类。任何可辨别的系统组件都能包含在此类中。系统组件的示例包括: - 应用程序服务器、数据库和应用程序等软件组件 - 文件、进程和线程等操作系统组件 - 磁盘驱动器、控制器、处理器和打印机等设备组件 - 芯片和卡等物理组件。 |
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 是所有代表抽象系统组件(例如文件、进程或 LogicalDevice)的系统组件的基类。 | 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. |
| 59 | GUID，会话的唯一 ID | Guid, the unique Id of the session |
| 60 | 捕获的模式 - SaveToFile、RealtimeRPC、RealtimeLocal。 | The mode of the capture - SaveToFile, RealtimeRPC, RealtimeLocal. |
| 61 | 事件捕获跟踪将写入到的本地文件名。只有当 CaptureMode 等于 SaveToFile 时才有效 | The local filename to which event capture traces will be written to. Only valid when CaptureMode equals SaveToFile |
| 62 | 事件捕获跟踪将写入到的本地文件的最大大小(以 MB 为单位)。只有当 CaptureMode 等于 SaveToFile 时才有效。最小值为 1。如果设置为 0，则文件大小没有限制。 | 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 | ETW 会话的跟踪缓冲区大小。值范围为 1KB 到 1024KB。 | The trace buffer size for the ETW session. The value range is 1KB to 1024KB. |
| 64 | 用于 ETW 会话的跟踪缓冲区的最大数目。 | The maximum number of trace buffers used for the ETW session. |
| 65 | 会话的当前状态 - “正在运行”、“已停止”、“失败” | The current status of the Session - Running, Stopped, Failed |
| 66 | 启动事件捕获，同时应用会话配置 | Starts the event capture, applying the session configuration |
| 67 | 停止事件捕获 | Stops the event capture |
| 68 | 此类将封装计算机上的 ETW 捕获会话。 | This class encapsulates an ETW capture session on a computer. |
| 69 | 提供程序的名称 | The name of the provider |
| 70 | GUID，计算机上安装的提供程序的唯一 ID。 | Guid, the unique id of the provider installed on the computer. |
| 71 | Guid，会话的唯一 ID，属于会话的一部分，否则 Guid 为 NULL。 | 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. |
| 73 | 事件捕获的最高事件级别。 | The maximum event level for the event capture. |
| 74 | 为事件捕获指定的 MatchAnyKeyword 掩码。 | The MatchAnyKeyword mask specified for the event capture. |
| 75 | 为事件捕获指定的 MatchAllKeyword 掩码。 | The MatchAllKeyword mask specified for the event capture. |
| 76 | 此类将封装计算机上用于事件捕获的 ETW 提供程序。 | This class encapsulates an ETW provider on a computer for the event capture. |
| 77 | 此类将封装计算机上用于事件捕获的 ETW 提供程序 | This class encapsulates an ETW provider on a computer for the event capture |
| 78 | 捕获的类型 -“物理”、"VMSwitch" 或“两者” | Type of the capture - Physical, VMSwitch or Both |
| 79 | 指定是目标网络堆栈中的每个可能层都需要捕获，还是只有默认层才需要捕获。对于 VMSwitch，筛选器将默认安装在扩展堆栈之上。对于物理网络适配器，筛选器将安装在微型端口上方。 | 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 | 指定用于筛选的 MAC 地址或 LinkLayerAddress | Specifies MAC Addresses or LinkLayerAddress for filtering |
| 81 | 指定用于筛选的 EtherType | Specifies the EtherType for filtering |
| 82 | 指定用于筛选的 IP 地址(V4/V6) | Specifies the IP Addresses(V4/V6) for filtering |
| 83 | 指定用于筛选的 IP 协议 | Specifies the IP Protocols for filtering |
| 84 | 指定数据包截断长度(以字节为单位)。默认长度为 128，最小长度为 14。如果值为零，则禁用截断。 | Specifies the packet truncation length in bytes. The default is 128. The minimum is 14. The value of zero disables truncation. |
| 85 | 指定添加 VM 目标时要捕获的流量方向 -“入口”、“出口”或 "IngressAndEgress"。 | Specifies the direction of the traffic to be captured when Vm Targets are added - Ingress, Egress or IngressAndEgress. |
| 86 | 此类将封装计算机上的数据包捕获筛选器 ETW 提供程序 | This class encapsulates the Packet Capture Filter ETW provider on a computer |
| 87 | 对象的名称 | Name of the object |
| 88 | 对象的唯一标识键。 | The Unique identifying key of the object. |
| 89 | 数据包捕获提供程序的名称。 | Name of the packet capture provider. |
| 90 | 捕获的当前状态。 | Current status of the Capture. |
| 91 | 此类将封装计算机上的数据包捕获目标 | This class encapsulates a Packet Capture Target on a computer |
| 92 | 目标网络适配器的友好名称或描述。 | The friendly name or description of the target network adapter. |
| 93 | MAC 控制器混杂模式设置。 | MAC controller promiscuous mode setting. |
| 94 | 此类将封装要在其上捕获流量的目标网络适配器。 | This class encapsulates a target network adapter, on which the traffic is to be captured. |
| 95 | VM 网络适配器的 MacAddress 或 LinkLayerAddress。 | The MacAddress or the LinkLayerAddress of the VM Network Adapter. |
| 96 | VM 网络适配器连接到的虚拟交换机的名称。 | The name of the virtual switch the VM network adapter is connected to. |
| 97 | VM 网络适配器的端口名称。 | The port name of the VM network adapter. |
| 98 | VM 网络适配器所属的虚拟机的名称。 | The name of the virtual machine that the VM network adapter belongs to. |
| 99 | VM 网络适配器所属的虚拟机的 ID。 | The Id of the virtual machine that the VM network adapter belongs to. |
| 100 | 此类封装了一个 VM 网络适配器，该适配器与要捕获其流量的虚拟交换机上的端口相对应。 | 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 | 封装要捕获其流量的 hyper-v 主机上的虚拟交换机。 | Encapsulates a Virtual Switch on the hyper-v host, on which the traffic is to be captured. |
| 102 | 关联中的父元素。 | The parent element in the association. |
| 103 | 关联中的子元素。 | The child element in the association. |
| 104 | 2.7.0 | 2.7.0 |
| 105 | CIM_Component 是一种一般性关联，用于在托管元素间建立“从属”关系。例如，它可用于定义系统的多个组件或多个部分。 | 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. |
| 107 | 标识数据包捕获目标。 | Identifies the packet capture target. |
| 108 | 此类封装数据包捕获提供程序与数据包捕获目标之间的关联。 | This class encapsulates the association between the packet capture provider and a packet capture target. |
| 109 | 标识会话 | Identifies the session |
| 110 | 标识提供程序 | Identifies the provider |
| 111 | 此类将封装会话与提供程序之间的关联 | This class encapsulates an association between a session and a provider |
| 112 | WFP 层集 | WFP layer set |
| 113 | 是否包括丢弃的数据包事件 | Whether include the discarded packet events |
| 114 | 指定用于筛选的 TCP 端口 | Specifies the TCP ports for filtering |
| 115 | 指定用于筛选的 UDP 端口 | Specifies the UDP ports for filtering |
| 116 | 此类将封装计算机上的 WFP 捕获筛选器 ETW 提供程序 | This class encapsulates the WFP Capture Filter ETW provider on a computer |
| 117 | 指定一个或多个要筛选的目标 MAC 地址。筛选器匹配时将记录网络流量。 | Designates one or more destination MAC addresses to filter on. Network traffic is logged when the filter matches. |
| 118 | 指定一个或多个要筛选的 TCP 端口。筛选器匹配时将记录网络流量。 | Designates one or more TCP ports to filter on. Network traffic is logged when the filter matches. |
| 119 | 指定一个或多个要筛选的 UDP 端口。筛选器匹配时将记录网络流量。 | Designates one or more UDP Ports to filter on. Network traffic is logged when the filter matches. |
| 120 | 指定一个或多个要筛选的源 MAC 地址。筛选器匹配时将记录网络流量。 | Designates one or more source MAC addresses to filter on. Network traffic is logged when the filter matches. |
| 121 | 指定一个或多个要筛选的 VLAN ID。筛选器匹配时将记录网络流量。 | Designates one or more VLAN Ids to filter on. Network traffic is logged when the filter matches. |
| 122 | 指定一个或多个要筛选的 GRE 密钥。筛选器匹配时将记录网络流量。 | Designates one or more GRE keys to filter on. Network traffic is logged when the filter matches. |
| 123 | 指定一个或多个要筛选的 VXLAN TNI 值。筛选器匹配时将记录网络流量。 | Designates one or more VXLAN TNI values to filter on. Network traffic is logged when the filter matches. |
| 124 | 指定一个或多个要筛选的源 IP 地址。筛选器匹配时将记录网络流量。 | Designates one or more Source IP addresses to filter on. Network traffic is logged when the filter matches. |
| 125 | 指定一个或多个要筛选的目标 IP 地址。筛选器匹配时将记录网络流量。 | Designates one or more destination IP addresses to filter on. Network traffic is logged when the filter matches. |
| 126 | 指定一个或多个要筛选的 IP 协议(例如 TCP 或 UDP)。筛选器匹配时将记录网络流量。 | Designates one or more IP protocols (such as TCP or UDP) to filter on. Network traffic is logged when the filter matches. |
| 127 | 指定要跟踪的流量方向 - Inbound、Outbound 或 InboundOutbound。 | Designates the direction of the traffic flows to trace - Inbound, Outbound, or InboundOutbound. |
| 128 | 指定要将跟踪限制到的交换机的友好名称。
此值将与 PortIds 筛选器结合使用，以便在一个或多个交换机端口上启用每个数据包事件的跟踪。 |
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). |
| 130 | 在计算机上配置虚拟筛选平台 ETW 提供程序。 | Configures the Virtual Filtering Platform ETW provider on a computer. |
| 131 | 指定要将跟踪限制到的交换机的友好名称。此值将与 PortIds 筛选器结合使用，以便在一个或多个交换机端口上启用每个数据包事件的跟踪。 | 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. |
| 133 | 配置属于 NetEventSession 的 Hyper-V 虚拟交换机 ETW 提供程序。 | Configures the Hyper-V Virtual Switch ETW provider that is part of the NetEventSession. |
| 5001 | 此计算机上已存在另一个名为 "%1!s!" 的会话。 | Another Session already exists on this computer with the name '%1!s!'. |
| 5002 | 此计算机上没有名为 "%1!s!" 的会话。 | There are no sessions on this computer with the name '%1!s!'. |
| 5003 | "%1!s!" 不是有效的会话名称。 | '%1!s!' is not a valid Session name. |
| 5004 | 会话 "%1!s!" 已在此计算机上运行。 | Session:'%1!s!' already running on this computer. |
| 5005 | 此计算机上没有与名称 "%1!s!" 匹配的 ETW 提供程序。 | There are no ETW Providers on this computer that match the name '%1!s!'. |
| 5006 | 此计算机上没有与名称 "%1!s!" 匹配的网络适配器。 | There are no Network Adapters on this computer that match the name '%1!s!'. |
| 5007 | 此计算机上没有与名称 "%1!s!" 匹配的 VM 交换机。 | There are no VM Switches on this computer that match the name '%1!s!'. |
| 5008 | 此计算机上没有与名称 "%1!s!" 匹配的 VM 网络适配器。 | There are no VM Network Adapters on this computer that match the name '%1!s!'. |
| 5009 | 操作超时。无法执行请求的操作，因为 "%1!s!" 当前正在更新网络配置。 | Operation timed out. Cannot perform requested operation as '%1!s!' is currently updating network configuration. |
| 5010 | 拒绝访问。此操作需要管理员特权。 | Access Denied. This operation requires administrator privileges. |
| 5011 | 格式无效。请检查参数的值: "%1!s!" | Invalid format. Please check the value of the parameter:'%1!s!' |
| 5012 | 需要为此操作指定参数 "%1!s!"。 | You need to specify parameters '%1!s!' for this operation. |
| 5013 | %1!s! 和 %2!s! | %1!s! and %2!s! |
| 5101 | 创建会话，名称: "%1!s!"，CaptureMode:{%2!s!}，LocalFilePath: "%3!s!"，MaxFileSize: "%4!u!"，MaxNumberOfBuffers: "%5!u!"，以及 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 | 在此计算机上启动 ETW 会话 "%1!s!"。 | Starts the ETW Session:'%1!s!' on this computer. |
| 5103 | 在此计算机上停止 ETW 会话 "%1!s!"。 | Stops the ETW Session:'%1!s!' on this computer. |
| 5104 | 从此计算机上删除 ETW 会话 "%1!s!"。 | Removes the ETW Session:'%1!s!' from this computer. |
| 5105 | 将 ETW 提供程序 "%1!s!" 添加到会话 "%2!s!"，级别: "%3!u!"，MatchAllKeywords: "4%!I64!"，以及 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 | 从会话 "%2!s!" 中删除 ETW 提供程序 "%1!s!"。 | Removes the ETW Provider:'%1!s!' from Session:'%2!s!'. |
| 5107 | 将数据包捕获 ETW 提供程序 "%1!s!" 添加到会话 "%2!s!"，级别: "%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!"，以及 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 | 从会话 "%2!s!" 中删除数据包捕获 ETW 提供程序 "%1!s!"。 | Removes the Packet Capture ETW Provider:'%1!s!' from Session:'%2!s!'. |
| 5109 | 将网络适配器 "%1!s!" 添加到会话 "%3!s!" 中的数据包捕获 ETW 提供程序 "%2!s!" 以筛选流量。 | Adds Network Adapter:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5110 | 将网络适配器 "%1!s!" 从会话 "%3!s!" 中的数据包捕获 ETW 提供程序 "%2!s!" 中删除以筛选流量。 | Removes Network Adapter:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5111 | 将 VM 网络适配器 "%1!s!" 添加到会话 "%3!s!" 中的数据包捕获 ETW 提供程序 "%2!s!" 以筛选流量。 | Adds VM Network Adapter:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5112 | 将 VM 网络适配器 "%1!s!" 从会话 "%3!s!" 中的数据包捕获 ETW 提供程序 "%2!s!" 中删除以筛选流量。 | Removes VM Network Adapter:'%1!s!' from the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5113 | 将 VMSwitch "%1!s!" 添加到会话 "%3!s!" 中的数据包捕获 ETW 提供程序 "%2!s!" 以筛选流量。 | Adds VMSwitch:'%1!s!' to the Packet Capture ETW Provider:'%2!s!' in Session:'%3!s!' for filtering traffic. |
| 5114 | 将 VMSwitch "%1!s!" 从会话 "%3!s!" 中的数据包捕获 ETW 提供程序 "%2!s!" 中删除以筛选流量。 | 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 数据包捕获提供程序 |
| 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: | 0x804, 1200 |