| File name: | dcbwmi.dll.mui |
| Size: | 19968 byte |
| MD5: | 2a5c0fc6359596a486ee699f71db4361 |
| SHA1: | 45d259b060f4403d4c8925d3d78a0c0c1d917f03 |
| SHA256: | 065be5da88b1511efbd86e57d0581eb5d13bbf6b7cb9416610824b5704a12eac |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Portuguese (Brazilian) 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 | Portuguese (Brazilian) | 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 | The name of the traffic class. | The name of the traffic class. |
| 12 | Strict | Strict |
| 13 | ETS | ETS |
| 14 | The assigned Transmission Selection Algorithm. | The assigned Transmission Selection Algorithm. |
| 15 | Percent | Percent |
| 16 | The assigned minimum bandwidth percentage value if the ETS algorithm is used. Otherwise, this must be zero. | The assigned minimum bandwidth percentage value if the ETS algorithm is used. Otherwise, this must be zero. |
| 17 | The assigned priority values. | The assigned priority values. |
| 18 | Global | Global |
| 19 | AdapterSpecific | AdapterSpecific |
| 20 | The policy set this traffic class is from, either global, or adapter-specific. | The policy set this traffic class is from, either global, or adapter-specific. |
| 21 | The interface alias this traffic class applies to. | The interface alias this traffic class applies to. |
| 22 | The interface index this traffic class applies to. | The interface index this traffic class applies to. |
| 23 | Switch the traffic class policy between global and per adapter setting. | Switch the traffic class policy between global and per adapter setting. |
| 24 | The settings for a QoS traffic class. | The settings for a QoS traffic class. |
| 25 | The name of the flow control class. | The name of the flow control class. |
| 26 | Priority value. | Priority value. |
| 27 | Flow control enabled for priority. | Flow control enabled for priority. |
| 28 | The policy set this setting is from, either global, or adapter-specific. | The policy set this setting is from, either global, or adapter-specific. |
| 29 | The interface alias this setting applies to. | The interface alias this setting applies to. |
| 30 | The interface index this setting applies to. | The interface index this setting applies to. |
| 31 | Disables flow control on priority. | Disables flow control on priority. |
| 32 | Enables flow control on priority. | Enables flow control on priority. |
| 33 | Switch the PFC setting between global and per adapter setting. | Switch the PFC setting between global and per adapter setting. |
| 34 | The link level flow control settings for an IEEE 802.1p priority. | The link level flow control settings for an IEEE 802.1p priority. |
| 35 | The local machine is Willing to accept remote DCBX settings. | The local machine is Willing to accept remote DCBX settings. |
| 36 | Switch the DCBx setting between global and per adapter setting. | Switch the DCBx setting between global and per adapter setting. |
| 37 | The DCB Willing state. | The DCB Willing state. |
| 1000 | [Default] | [Default] |
| 2000 | Traffic class name may not be longer than 64 characters. | Traffic class name may not be longer than 64 characters. |
| 2001 | Could not query configuration database. Please re-install the Data Center Bridging feature in Server Manager UI. | Could not query configuration database. Please re-install the Data Center Bridging feature in Server Manager UI. |
| 2002 | Please specify a traffic class name. | Please specify a traffic class name. |
| 2003 | Traffic class name may not contain any of the following symbols: \()/#*[] | Traffic class name may not contain any of the following symbols: \()/#*[] |
| 2004 | Default traffic class is not mutable. | Default traffic class is not mutable. |
| 2005 | Algorithm parameter is missing. | Algorithm parameter is missing. |
| 2006 | Invalid Algorithm specified. Valid algorithms are: ETS, and STRICT | Invalid Algorithm specified. Valid algorithms are: ETS, and STRICT |
| 2007 | Priority parameter is missing. | Priority parameter is missing. |
| 2008 | Invalid Priority specified. | Invalid Priority specified. |
| 2009 | Bandwidth parameter is missing for ETS algorithm. | Bandwidth parameter is missing for ETS algorithm. |
| 2010 | Invalid Bandwidth value specified. Valid values must be between 1 and 100, inclusive. | Invalid Bandwidth value specified. Valid values must be between 1 and 100, inclusive. |
| 2011 | Willing parameter is missing. | Willing parameter is missing. |
| 2012 | Duplicate traffic class name. | Duplicate traffic class name. |
| 11000 | New-NetQosTrafficClass -Name "%1!s!" | New-NetQosTrafficClass -Name "%1!s!" |
| 11001 | Set-NetQosTrafficClass -Name "%1!s!" | Set-NetQosTrafficClass -Name "%1!s!" |
| 11002 | Remove-NetQosTrafficClass -Name "%1!s!" | Remove-NetQosTrafficClass -Name "%1!s!" |
| 11003 | Set-NetQosDcbxSetting -Willing %1!s! | Set-NetQosDcbxSetting -Willing %1!s! |
| 11004 | Set-NetQosFlowControl -Priority %1!u! -Enabled %2!s! | Set-NetQosFlowControl -Priority %1!u! -Enabled %2!s! |
| 11005 | Enable-NetQosFlowControl -Priority %1!u! | Enable-NetQosFlowControl -Priority %1!u! |
| 11006 | Disable-NetQosFlowControl -Priority %1!u! | Disable-NetQosFlowControl -Priority %1!u! |
| 11007 | Switch-NetQosTrafficClass -PolicySet %1!s! | Switch-NetQosTrafficClass -PolicySet %1!s! |
| 11008 | Switch-NetQosFlowControl -PolicySet %1!s! | Switch-NetQosFlowControl -PolicySet %1!s! |
| 11009 | Switch-NetQosDcbxSetting -PolicySet %1!s! | Switch-NetQosDcbxSetting -PolicySet %1!s! |
| 11010 | -Algorithm ETS | -Algorithm ETS |
| 11011 | -Algorithm Strict | -Algorithm Strict |
| 11012 | -Bandwidth %1!u! | -Bandwidth %1!u! |
| 11013 | -Priority %1!s! | -Priority %1!s! |
| 11020 | $true | $true |
| 11021 | $false | $false |
| 11030 | -InterfaceAlias "%1!s!" | -InterfaceAlias "%1!s!" |
| 11031 | -InterfaceIndex %1!u! | -InterfaceIndex %1!u! |
| File Description: | DCB QOS WMI Provider |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | DCBWMI.DLL |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | DCBWMI.DLL.MUI |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x416, 1200 |