| File name: | netnccim.dll.mui |
| Size: | 20480 byte |
| MD5: | b3c7239843107507ae6a109b1c15140d |
| SHA1: | 079db2d90911194e708f2653a1b8b4cda7f74ddc |
| SHA256: | ae774b78e6c17bca5a98ec24125f670bc9028e9a816c2b144931239502f11354 |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Portuguese 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 | 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 | Describes the expected address of the host name used as for the DNS probe. | Describes the expected address of the host name used as for the DNS probe. |
| 12 | This is the host name of a PC known to be on the corporate network. | This is the host name of a PC known to be on the corporate network. |
| 13 | Describes the list of IPv6 corporate site prefixes that should be monitored for corporate connectivity | Describes the list of IPv6 corporate site prefixes that should be monitored for corporate connectivity |
| 14 | This is the URL of the corporate website that will be used to perform an active probe against. | This is the URL of the corporate website that will be used to perform an active probe against. |
| 15 | This is the HTTPS URL of the corporate website that will be used to determine the current domain location i.e. inside or outside corporate. | This is the HTTPS URL of the corporate website that will be used to determine the current domain location i.e. inside or outside corporate. |
| 16 | PolicyStore property defines the store to retrieve the NCSI configuration policy. | PolicyStore property defines the store to retrieve the NCSI configuration policy. |
| 17 | Reset the NCSI configuration. | Reset the NCSI configuration. |
| 18 | Describes the NCSI Policy settings. | Describes the NCSI Policy settings. |
| 19 | Describes the DirectAccess connection status. | Describes the DirectAccess connection status. |
| 20 | Describes the DirectAccess connection substatus. | Describes the DirectAccess connection substatus. |
| 21 | MSFT_DAConnectionStatus represents DirectAccess connection status. | MSFT_DAConnectionStatus represents DirectAccess connection status. |
| 0x1 | Performing operation %1 on Target %2 | Performing operation %1 on Target %2 |
| 0x2 | Enabling site %1 for DirectAccess connectivity | Enabling site %1 for DirectAccess connectivity |
| 0x3 | Disabling manual site selection for DirectAccess connectivity | Disabling manual site selection for DirectAccess connectivity |
| 0x4 | Invalid parameter: %1. | Invalid parameter: %1. |
| 0x5 | Latency must be less than 1000ms. | Latency must be less than 1000ms. |
| 0x6 | Each item in %1 must be of the form \"%2\". | Each item in %1 must be of the form \"%2\". |
| 0x7 | Only one %1 is supported. | Only one %1 is supported. |
| 0x8 | The specified interface was not found on the system. | The specified interface was not found on the system. |
| 0x9 | %1 must be a valid IPv6 prefix. | %1 must be a valid IPv6 prefix. |
| 0xA | Failed to notify IP Helper Service of changes to local configuration. | Failed to notify IP Helper Service of changes to local configuration. |
| 0xB | This functionality is not supported on client SKUs. | This functionality is not supported on client SKUs. |
| 0xC | The WinNAT service is stopped. Please start the service to display configuration from active store. | The WinNAT service is stopped. Please start the service to display configuration from active store. |
| 0xD | Failed to start WinNAT service. | Failed to start WinNAT service. |
| 0xE | %1 cannot contain a semicolon. | %1 cannot contain a semicolon. |
| 0xF | Only the following prefix lengths are allowed for NAT64: 32, 40, 48, 56, 64, and 96. | Only the following prefix lengths are allowed for NAT64: 32, 40, 48, 56, 64, and 96. |
| 0x10 | Ports in port range must be in the range 1024-65535. | Ports in port range must be in the range 1024-65535. |
| 0x11 | To specify %1, %2 must also have a valid value. | To specify %1, %2 must also have a valid value. |
| 0x12 | %1 and %2 cannot be specified at the same time. | %1 and %2 cannot be specified at the same time. |
| 0x13 | Must specify required parameter %1. | Must specify required parameter %1. |
| 0x14 | Either %1 or %2 must be specified. | Either %1 or %2 must be specified. |
| 0x15 | The configuration has been corrupted. | The configuration has been corrupted. |
| 0x16 | Cannot create or modify instances in the specified policy store. | Cannot create or modify instances in the specified policy store. |
| 0x17 | The specified %1 is already in use. | The specified %1 is already in use. |
| 0x18 | None of the specified entry point ranges match the entry point IP address. | None of the specified entry point ranges match the entry point IP address. |
| 0x19 | The specified entry point ranges are not the best match for the entry point IP address. | The specified entry point ranges are not the best match for the entry point IP address. |
| 0x1A | Entry point override has been restricted by your domain administrator. | Entry point override has been restricted by your domain administrator. |
| 0x1B | Network Connectivity Assistant service is stopped or not responding. | Network Connectivity Assistant service is stopped or not responding. |
| 0x1C | ServerShunt and TCP Chimney can't be enabled together. TCP Chimney must be disabled for this operation. | ServerShunt and TCP Chimney can't be enabled together. TCP Chimney must be disabled for this operation. |
| 0x1D | No entry points found with name equal to \"%1\". | No entry points found with name equal to \"%1\". |
| 0x1E | The TCP mapping timeout cannot be less than 30 minutes. | The TCP mapping timeout cannot be less than 30 minutes. |
| 0x1F | State cannot be set to OutsideEnabled for server interfaces. | State cannot be set to OutsideEnabled for server interfaces. |
| File Description: | DA Network Connectivity WMI Provider |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | netnccim.dll |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | netnccim.dll.mui |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x816, 1200 |