| File name: | netdacim.dll.mui |
| Size: | 22528 byte |
| MD5: | 7ee3fc13289425f1817c378f67eed326 |
| SHA1: | 0f9f5db2cbc33dcabfc6bcdc53c1bf8cd42e656c |
| SHA256: | fc9faf9a4f1fb115eeb424b66403a748a41fc6282f9d35844b84eeb467dd3b1f |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in English (U.S.) 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 | English (U.S.) | 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 store in which this configuration object is stored | Policy store in which this configuration object is stored |
| 12 | Friendly name of the site | Friendly name of the site |
| 13 | Indicates the current activation state of the site | Indicates the current activation state of the site |
| 14 | NotSelected | NotSelected |
| 15 | AutomaticallySelected | AutomaticallySelected |
| 16 | ManuallySelected | ManuallySelected |
| 17 | Name of AD site used by the client | Name of AD site used by the client |
| 18 | IPv6 address ranges attributed to a DA site | IPv6 address ranges attributed to a DA site |
| 19 | Teredo server used by the client | Teredo server used by the client |
| 20 | DirectAccess Server address | DirectAccess Server address |
| 21 | Name of IP-HTTPs profile to enable for this site | Name of IP-HTTPs profile to enable for this site |
| 22 | IP address used by the DA client to identify which site to use based on GSLB resolution | IP address used by the DA client to identify which site to use based on GSLB resolution |
| 23 | Enable DA manual site selection | Enable DA manual site selection |
| 24 | Disable DA manual site selection | Disable DA manual site selection |
| 25 | Rename DA site table entry | Rename DA site table entry |
| 26 | Reset DA site table entry configuration | Reset DA site table entry configuration |
| 27 | DA Site table entry | DA Site table entry |
| 28 | Specifies resources on the intranet that are normally accessible to DirectAccess clients. | Specifies resources on the intranet that are normally accessible to DirectAccess clients. |
| 29 | Specifies the Ipv6 addresses of the endpoints of the IPsec tunnels that enable DirectAccess. | Specifies the Ipv6 addresses of the endpoints of the IPsec tunnels that enable DirectAccess. |
| 30 | Specifies whether the user has UI control for the DirectAccess entry when the user clicks the Networking notification area icon. | Specifies whether the user has UI control for the DirectAccess entry when the user clicks the Networking notification area icon. |
| 31 | Specifies whether an entry for DirectAccess connectivity appears when the user clicks the Networking notification area icon. | Specifies whether an entry for DirectAccess connectivity appears when the user clicks the Networking notification area icon. |
| 32 | Specifies the email address to be used when sending the log files that are generated by NCA to the network administrator. | Specifies the email address to be used when sending the log files that are generated by NCA to the network administrator. |
| 33 | Specifies the string that appears for DirectAccess connectivity when the user clicks the Networking notification area icon. | Specifies the string that appears for DirectAccess connectivity when the user clicks the Networking notification area icon. |
| 34 | Specifies whether NCA service operates in passive mode. | Specifies whether NCA service operates in passive mode. |
| 35 | Specifies administrator commands that will be included in logs by NCA service. | Specifies administrator commands that will be included in logs by NCA service. |
| 36 | Specifies whether users are allowed to manually select a DA site. | Specifies whether users are allowed to manually select a DA site. |
| 37 | Specifies a FQDN used to automatically select the current DA site. | Specifies a FQDN used to automatically select the current DA site. |
| 38 | Specifies whether to force tunneling. | Specifies whether to force tunneling. |
| 39 | Default | Default |
| 40 | Enabled | Enabled |
| 41 | Disabled | Disabled |
| 42 | PolicyStore property defines the store to retrieve the NCA configuration policy. | PolicyStore property defines the store to retrieve the NCA configuration policy. |
| 43 | Reset the DAClientExperienceConfiguration configuration. | Reset the DAClientExperienceConfiguration configuration. |
| 44 | DA client experience settings | DA client experience settings |
| 45 | DA Settings change notification | DA Settings change notification |
| 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: | Microsoft Direct Access WMI Provider |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | netdacim.dll |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | netdacim.dll.mui |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x409, 1200 |