| File name: | qoswmi.dll.mui |
| Size: | 29184 byte |
| MD5: | 6a9bb0fdf53fab16172103ddd42ddb19 |
| SHA1: | 1c6456f48f7740c25e319083da5d3e2b1d27d10b |
| SHA256: | 5d3ae78af7d7ae22922f8f75aed629c7c8e06fb0f4698294cd82e755be253e77 |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Ukrainian 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 | Ukrainian | English |
|---|---|---|
| 1 | InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM. |
InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM. |
| 2 | The Caption property is a short textual description (one- line string) of the object. | The Caption property is a short textual description (one- line string) of the object. |
| 3 | The Description property provides a textual description of the object. | The Description property provides a textual description of the object. |
| 4 | A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class. |
A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class. |
| 5 | 2.19.0 | 2.19.0 |
| 6 | ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. | ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema. |
| 7 | Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. For DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM. |
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. For DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM. |
| 8 | The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.) | The user-friendly name for this instance of SettingData. In addition, the user-friendly name can be used as an index property for a search or query. (Note: The name does not have to be unique within a namespace.) |
| 9 | CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future. Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association. Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration. When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations. |
CIM_SettingData is used to represent configuration and and operational parameters for CIM_ManagedElement instances. There are a number of different uses of CIM_SettingData supported in the model today. Additional uses may be defined in the future. Instances of CIM_SettingData may represent Aspects of a CIM_ManagedElement instance. This is modeled using the CIM_SettingsDefineState association. CIM_SettingData may be used to define capabilities when associated to an instance of CIM_Capabilities through the CIM_SettingsDefineCapabilities association. Instances of CIM_SettingData may represent different types of configurations for a CIM_ManagedElement, including persistent configurations, in progress configuration changes, or requested configurations. The CIM_ElementSettingData association is used to model the relationship between a CIM_SettingData instance and the CIM_ManagedElement for which it is a configuration. When an instance of CIM_SettingData represents a configuration, the current operational values for the parameters of the element are reflected by properties in the Element itself or by properties in its associations. These properties do not have to be the same values that are present in the SettingData object. For example, a modem might have a SettingData baud rate of 56Kb/sec but be operating at 19.2Kb/sec. Note: The CIM_SettingData class is very similar to CIM_Setting, yet both classes are present in the model because many implementations have successfully used CIM_Setting. However, issues have arisen that could not be resolved without defining a new class. Therefore, until a new major release occurs, both classes will exist in the model. Refer to the Core White Paper for additional information. SettingData instances can be aggregated together into higher- level SettingData objects using ConcreteComponent associations. |
| 10 | Superclass SettingData for networking | Superclass SettingData for networking |
| 11 | Policy name. | Policy name. |
| 12 | Policy version if read from GPO. | Policy version if read from GPO. |
| 13 | The owner of this policy. | The owner of this policy. |
| 14 | Domain | Domain |
| 15 | Public | Public |
| 16 | Private | Private |
| 17 | The network profiles for which the policy applies. | The network profiles for which the policy applies. |
| 18 | The precedence value of the policy. | The precedence value of the policy. |
| 19 | None | None |
| 20 | Default | Default |
| 21 | iSCSI | iSCSI |
| 22 | FCoE | FCoE |
| 23 | SMB | SMB |
| 24 | NFS | NFS |
| 25 | LiveMigration | LiveMigration |
| 26 | The optional match condition template that, if specified, overrides all other match conditions with predefined conditions. For example, the iSCSI template has a predefined match on TCP well-known port 3260. | The optional match condition template that, if specified, overrides all other match conditions with predefined conditions. For example, the iSCSI template has a predefined match on TCP well-known port 3260. |
| 27 | The user SID or name filter match condition. | The user SID or name filter match condition. |
| 28 | The application path name filter condition. | The application path name filter condition. |
| 29 | N/A | N/A |
| 30 | TCP | TCP |
| 31 | UDP | UDP |
| 32 | Both | Both |
| 33 | The IP protocol filter condition. If set to 0, then all the following fields are ignored: IPPortMatchCondition, IPSrcPrefixMatchCondition, IPSrcPortStartMatchCondition, IPSrcPortEndMatchCondition, IPDstPrefixMatchCondition, IPDstPrefixMatchCondition, and IPDstPortEndMatchCondition. | The IP protocol filter condition. If set to 0, then all the following fields are ignored: IPPortMatchCondition, IPSrcPrefixMatchCondition, IPSrcPortStartMatchCondition, IPSrcPortEndMatchCondition, IPDstPrefixMatchCondition, IPDstPrefixMatchCondition, and IPDstPortEndMatchCondition. |
| 34 | The IP well-known port filter condition. This matches either the local port number or the remote port number of a supported IP connection. This type of filter is especially effective if the port number is a well-known number assigned by the IANA. If the value of this field is non-zero, then all the following fields are ignored: IPSrcPrefixMatchCondition, IPSrcPortStartMatchCondition, IPSrcPortEndMatchCondition, IPDstPrefixMatchCondition, IPDstPortMatchCondition, and IPDstPortEndMatchCondition. | The IP well-known port filter condition. This matches either the local port number or the remote port number of a supported IP connection. This type of filter is especially effective if the port number is a well-known number assigned by the IANA. If the value of this field is non-zero, then all the following fields are ignored: IPSrcPrefixMatchCondition, IPSrcPortStartMatchCondition, IPSrcPortEndMatchCondition, IPDstPrefixMatchCondition, IPDstPortMatchCondition, and IPDstPortEndMatchCondition. |
| 35 | The optional source IP prefix filter condition. Where applicable, both the source and destination prefix families must match. Examples of valid prefixes: 192.168.1.1, 192.168.1.0/24, or fe80::1001:2046/128 | The optional source IP prefix filter condition. Where applicable, both the source and destination prefix families must match. Examples of valid prefixes: 192.168.1.1, 192.168.1.0/24, or fe80::1001:2046/128 |
| 36 | The optional lower-bound of the source port filter condition. If only a single port value is required, then IPSrcPortStartMatchCondition and IPSrcPortEndMatchCondition must match. If the source port filter condition is not required, set both fields to zero. | The optional lower-bound of the source port filter condition. If only a single port value is required, then IPSrcPortStartMatchCondition and IPSrcPortEndMatchCondition must match. If the source port filter condition is not required, set both fields to zero. |
| 37 | The upper-bound of the source port filter condition. This field complements IPSrcPortStartMatchCondition. | The upper-bound of the source port filter condition. This field complements IPSrcPortStartMatchCondition. |
| 38 | The optional destination IP prefix filter condition. Where applicable, both the source and destination prefix families must match. Examples of valid prefixes: 192.168.1.1, 192.168.1.0/24, or fe80::1001:2046/128 | The optional destination IP prefix filter condition. Where applicable, both the source and destination prefix families must match. Examples of valid prefixes: 192.168.1.1, 192.168.1.0/24, or fe80::1001:2046/128 |
| 39 | The optional lower-bound of the destination port filter condition. If only a single port value is required, then IPDstPortStartMatchCondition and IPDstPortEndMatchCondition must match. If the destination port filter condition is not required, set both fields to zero. | The optional lower-bound of the destination port filter condition. If only a single port value is required, then IPDstPortStartMatchCondition and IPDstPortEndMatchCondition must match. If the destination port filter condition is not required, set both fields to zero. |
| 40 | The upper-bound of the destination port filter condition. This field complements IPDstPortStartMatchCondition. | The upper-bound of the destination port filter condition. This field complements IPDstPortStartMatchCondition. |
| 41 | The optional URI filter condition. This condition may only be combined with the URIRecursiveMatchCondition, IPDstAddressMatchCondition, IPDstPortStartMatchCondition, and IPDstPortEndMatchCondition fields. | The optional URI filter condition. This condition may only be combined with the URIRecursiveMatchCondition, IPDstAddressMatchCondition, IPDstPortStartMatchCondition, and IPDstPortEndMatchCondition fields. |
| 42 | This filter condition supplements URIMatchCondition. If set, the URI match happens for all resources with the base path indicated by URIMatchCondition. Otherwise, a match only happens for a resource with the exact URI. | This filter condition supplements URIMatchCondition. If set, the URI match happens for all resources with the base path indicated by URIMatchCondition. Otherwise, a match only happens for a resource with the exact URI. |
| 43 | The NetworkDirect port filter condition. This filter is only applicable if the Data Center Bridging server feature is installed. Otherwise, the policy is effectively no-op. | The NetworkDirect port filter condition. This filter is only applicable if the Data Center Bridging server feature is installed. Otherwise, the policy is effectively no-op. |
| 44 | The NT Job Object identifier filter condition. | The NT Job Object identifier filter condition. |
| 45 | The 802.1p priority action. Set to -1 if not used. | The 802.1p priority action. Set to -1 if not used. |
| 46 | The DSCP action. Set to -1 if not used. | The DSCP action. Set to -1 if not used. |
| 47 | The minimum bandwidth weight action. Set to 0 if not used. | The minimum bandwidth weight action. Set to 0 if not used. |
| 48 | Bits per Second | Bits per Second |
| 49 | The bandwidth throttle rate action in bits per second unit. Set to 0 if not used. | The bandwidth throttle rate action in bits per second unit. Set to 0 if not used. |
| 50 | A QoS policy. | A QoS policy. |
| 1000 | Group Policy (Machine) | Group Policy (Machine) |
| 1001 | Group Policy (%1!s!) | Group Policy (%1!s!) |
| 1002 | PowerShell / WMI | PowerShell / WMI |
| 1003 | Unknown (%1!s!) | Unknown (%1!s!) |
| 1004 | All | All |
| 1016 | $True | $True |
| 1017 | $False | $False |
| 1018 | Cluster | Cluster |
| 1019 | NT Job Object | NT Job Object |
| 2000 | Policy name may not be empty. | Policy name may not be empty. |
| 2001 | Policy name may not exceed 2047 characters. | Policy name may not exceed 2047 characters. |
| 2002 | Policy name may not contain any of the following symbols: \()/#*[] | Policy name may not contain any of the following symbols: \()/#*[] |
| 2003 | URI based policy is only supported in GPO store. | URI based policy is only supported in GPO store. |
| 2004 | URI based policy may only specify a 32-bit throttle rate value. | URI based policy may only specify a 32-bit throttle rate value. |
| 2005 | At most one Template parameter can be specified at any time. | At most one Template parameter can be specified at any time. |
| 2006 | Invalid user name. | Invalid user name. |
| 2007 | Start and end port numbers must be used as a pair. | Start and end port numbers must be used as a pair. |
| 2008 | Start and end port numbers must be specified or omitted as a pair. | Start and end port numbers must be specified or omitted as a pair. |
| 2009 | Start port number must not be greater than end port number. | Start port number must not be greater than end port number. |
| 2010 | Invalid IP protocol. | Invalid IP protocol. |
| 2011 | Invalid source IP prefix. | Invalid source IP prefix. |
| 2012 | Invalid destination IP prefix. | Invalid destination IP prefix. |
| 2013 | Invalid IEEE 802.1p tag value. | Invalid IEEE 802.1p tag value. |
| 2014 | Invalid DSCP tag value. | Invalid DSCP tag value. |
| 2015 | A FCoE template policy may only include the PriorityValue parameter. | A FCoE template policy may only include the PriorityValue parameter. |
| 2016 | A iSCSI/LiveMigration/NFS/SMB/Default/Cluster template policy may only include any combination of PriorityValue, DSCPValue, MinBandwidthWeight, and ThrottleRate parameters. | A iSCSI/LiveMigration/NFS/SMB/Default/Cluster template policy may only include any combination of PriorityValue, DSCPValue, MinBandwidthWeight, and ThrottleRate parameters. |
| 2017 | A NetDirectPort policy may only include the PriorityValue parameter. | A NetDirectPort policy may only include the PriorityValue parameter. |
| 2018 | A URI policy may only include any combination of URIRecursive, IPDstPrefix, DSCPValue, and ThrottleRate parameters. | A URI policy may only include any combination of URIRecursive, IPDstPrefix, DSCPValue, and ThrottleRate parameters. |
| 2019 | A well-known IP port policy must include the IPProtocol parameter and any combination of User, AppPathName, PriorityValue, DSCPValue, MinBandwidthWeight, and ThrottleRate parameters. | A well-known IP port policy must include the IPProtocol parameter and any combination of User, AppPathName, PriorityValue, DSCPValue, MinBandwidthWeight, and ThrottleRate parameters. |
| 2020 | An IP policy may only include any combination of User, AppPathName, IPProtocol, IPSrcPrefix, IPSrcPortStart, IPSrcPortEnd, IPDstPrefix, IPDstPortStart, IPDstPortEnd, PriorityValue, DSCPValue, MinBandwidthWeight, and ThrottleRate parameters. | An IP policy may only include any combination of User, AppPathName, IPProtocol, IPSrcPrefix, IPSrcPortStart, IPSrcPortEnd, IPDstPrefix, IPDstPortStart, IPDstPortEnd, PriorityValue, DSCPValue, MinBandwidthWeight, and ThrottleRate parameters. |
| 2021 | The IPProtocol parameter must be specified if any combinations of IPSrcPrefix, IPSrcPortStart, IPSrcPortEnd, IPDstPrefix, IPDstPortStart, or IPDstPortEnd are used. | The IPProtocol parameter must be specified if any combinations of IPSrcPrefix, IPSrcPortStart, IPSrcPortEnd, IPDstPrefix, IPDstPortStart, or IPDstPortEnd are used. |
| 2022 | At least one policy action must be specified, i.e. PriorityValue, DSCPValue, MinBandwidthWeight, or ThrottleRate. | At least one policy action must be specified, i.e. PriorityValue, DSCPValue, MinBandwidthWeight, or ThrottleRate. |
| 2023 | Invalid IP prefix length. | Invalid IP prefix length. |
| 2024 | Corrupted policy information detected in registry. | Corrupted policy information detected in registry. |
| 2025 | Invalid domain policy store path. Please use either the "gpo:\" or "ldap://" format. | Invalid domain policy store path. Please use either the "gpo:\" or "ldap://" format. |
| 2026 | Group policy object not found on domain controller. | Group policy object not found on domain controller. |
| 2027 | Found an invalid group policy object on domain controller. | Found an invalid group policy object on domain controller. |
| 2028 | Cannot create policy because it already exists. | Cannot create policy because it already exists. |
| 2029 | Locating Group Policy Object | Locating Group Policy Object |
| 2030 | Searching for domain controller of domain %1!s!. | Searching for domain controller of domain %1!s!. |
| 2031 | Contacting the domain controller %1!s!. | Contacting the domain controller %1!s!. |
| 2032 | Searching for object %1!s! on domain controller %2!s!. | Searching for object %1!s! on domain controller %2!s!. |
| 2033 | Found group policy object%1!s! on domain controller %2!s!. | Found group policy object%1!s! on domain controller %2!s!. |
| 2034 | Note that policies containing minimum bandwidth specifications might not always be able to achieve their bandwidth target if there are other policies configured that do not also specify minimum bandwidth weights. | Note that policies containing minimum bandwidth specifications might not always be able to achieve their bandwidth target if there are other policies configured that do not also specify minimum bandwidth weights. |
| 3000 | New-NetQosPolicy -Name %1!s! -Store %2!s! | New-NetQosPolicy -Name %1!s! -Store %2!s! |
| 3001 | Set-NetQosPolicy -Name %1!s! -Store %2!s! | Set-NetQosPolicy -Name %1!s! -Store %2!s! |
| 3002 | Remove-NetQosPolicy -Name %1!s! -Store %2!s! | Remove-NetQosPolicy -Name %1!s! -Store %2!s! |
| 3100 | -Precedence %1!u! | -Precedence %1!u! |
| 3101 | -NetworkProfile %1!s! | -NetworkProfile %1!s! |
| 3102 | -NetworkProfile %1!s!,%2!s! | -NetworkProfile %1!s!,%2!s! |
| 3103 | -Template %1!s! | -Template %1!s! |
| 3104 | -User %1!s! | -User %1!s! |
| 3105 | -AppPathName %1!s! | -AppPathName %1!s! |
| 3106 | -NetDirectPort %1!u! | -NetDirectPort %1!u! |
| 3107 | -IPProtocol %1!s! | -IPProtocol %1!s! |
| 3108 | -IPPort %1!u! | -IPPort %1!u! |
| 3109 | -IPSrcPrefix %1!s! | -IPSrcPrefix %1!s! |
| 3110 | -IPSrcPort %1!u! | -IPSrcPort %1!u! |
| 3111 | -IPSrcPortStart %1!u! -IPSrcPortEnd %2!u! | -IPSrcPortStart %1!u! -IPSrcPortEnd %2!u! |
| 3112 | -IPDstPrefix %1!s! | -IPDstPrefix %1!s! |
| 3113 | -IPDstPort %1!u! | -IPDstPort %1!u! |
| 3114 | -IPDstPortStart %1!u! -IPDstPortEnd %2!u! | -IPDstPortStart %1!u! -IPDstPortEnd %2!u! |
| 3115 | -URI %1!s! -URIRecursive %2!s! | -URI %1!s! -URIRecursive %2!s! |
| 3116 | -PriorityValue %1!u! | -PriorityValue %1!u! |
| 3117 | -DSCPValue %1!u! | -DSCPValue %1!u! |
| 3118 | -MinBandwidthWeight %1!u! | -MinBandwidthWeight %1!u! |
| 3119 | -ThrottleRate %1!s! | -ThrottleRate %1!s! |
| File Description: | Network QoS WMI Module |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | QOSWMI.DLL |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | QOSWMI.DLL.MUI |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x422, 1200 |