NetPeerDistCim.dll.mui BranchCache WMI Provider e54481a61140335cd93e428be9335102

File info

File name: NetPeerDistCim.dll.mui
Size: 67072 byte
MD5: e54481a61140335cd93e428be9335102
SHA1: df90844bcffee7d290bf8868a4907c4031a96bac
SHA256: d46eaa79cc53a742bf625710dee05b1706bc8274d21b04a5f96f986c66667ed0
Operating systems: Windows 10
Extension: MUI

Translations messages and strings

If an error occurred or the following message in Danish 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 Danish English
1InstanceID 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.
2The 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.
3The Description property provides a textual description of the object. The Description property provides a textual description of the object.
4A 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.
52.19.0 2.19.0
6ManagedElement 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.
7A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed. A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.
8The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property. 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.
9Indicates 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.
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.
10Unknown Unknown
11Other Other
12OK OK
13Degraded Degraded
14Stressed Stressed
15Predictive Failure Predictive Failure
16Error Error
17Non-Recoverable Error Non-Recoverable Error
18Starting Starting
19Stopping Stopping
20Stopped Stopped
21In Service In Service
22No Contact No Contact
23Lost Communication Lost Communication
24Aborted Aborted
25Dormant Dormant
26Supporting Entity in Error Supporting Entity in Error
27Completed Completed
28Power Mode Power Mode
29DMTF Reserved DMTF Reserved
30Vendor Reserved Vendor Reserved
31Strings 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. 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.
32A 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.
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.
33Indicates 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.
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.
34Degraded/Warning Degraded/Warning
35Minor failure Minor failure
36Major failure Major failure
37Critical failure Critical failure
38Non-recoverable error Non-recoverable error
39CommunicationStatus 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.
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.
40Not Available Not Available
41Communication OK Communication OK
42DetailedStatus 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.
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.
43No Additional Information No Additional Information
44OperatingStatus 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.
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.
45Servicing Servicing
46Migrating Migrating
47Emigrating Emigrating
48Immigrating Immigrating
49Snapshotting Snapshotting
50Shutting Down Shutting Down
51In Test In Test
52Transitioning Transitioning
53PrimaryStatus 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.
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.
54CIM_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.
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.
552.22.0 2.22.0
56CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices. CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.
572.6.0 2.6.0
58Within 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.
59The 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.)
60CIM_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.
61Superclass SettingData for networking Superclass SettingData for networking
62Describes settings related to BranchCache Describes settings related to BranchCache
63The current operating mode of this BranchCache client The current operating mode of this BranchCache client
64Disabled Disabled
65LocalCache LocalCache
66DistributedCache DistributedCache
67HostedCache HostedCache
68The content information version this client will request from content servers The content information version this client will request from content servers
69Windows7 Windows7
70Windows8 Windows8
71Indicates if Distributed Caching is enabled Indicates if Distributed Caching is enabled
72Indicates if this client will serve other distributed caching peers when operating on battery power Indicates if this client will serve other distributed caching peers when operating on battery power
73Hosted cache servers to which this client will connect Hosted cache servers to which this client will connect
74Indicates if Hosted Cache discovery is enabled Indicates if Hosted Cache discovery is enabled
75The version of the hosted cache server The version of the hosted cache server
76The minimum network latency, in milliseconds, before the SMB client will use BranchCache The minimum network latency, in milliseconds, before the SMB client will use BranchCache
77Describes settings related to the BranchCache client role Describes settings related to the BranchCache client role
78Indicates if BranchCache content server functionality is enabled Indicates if BranchCache content server functionality is enabled
79Describes settings related to the BranchCache content server role Describes settings related to the BranchCache content server role
80Indicates if BranchCache hosted cache server is enabled Indicates if BranchCache hosted cache server is enabled
81The authentication mode for hosted cache clients The authentication mode for hosted cache clients
82None None
83Domain Domain
84Indicates if BranchCache hosted cache server Scp registration is enabled Indicates if BranchCache hosted cache server Scp registration is enabled
85Describes settings related to the BranchCache hosted cache server role Describes settings related to the BranchCache hosted cache server role
86The status of the BranchCache Content Retrieval HTTP URL Reservation The status of the BranchCache Content Retrieval HTTP URL Reservation
87The status of the BranchCache Hosted Cache HTTP URL Reservation The status of the BranchCache Hosted Cache HTTP URL Reservation
88The status of the BranchCache Hosted Cache HTTPS URL Reservation The status of the BranchCache Hosted Cache HTTPS URL Reservation
89The status of the BranchCache Content Retrieval Firewall Rules The status of the BranchCache Content Retrieval Firewall Rules
90The status of the BranchCache Peer Discovery Firewall Rules The status of the BranchCache Peer Discovery Firewall Rules
91The status of the BranchCache Hosted Cache Server Firewall Rules The status of the BranchCache Hosted Cache Server Firewall Rules
92The status of the BranchCache Hosted Cache Client Firewall Rules The status of the BranchCache Hosted Cache Client Firewall Rules
93The port number on which BranchCache is listening for incoming download requests The port number on which BranchCache is listening for incoming download requests
94The port number to which BranchCache will send outgoing download requests The port number to which BranchCache will send outgoing download requests
95The port to which this hosted cache client will offer content to the hosted cache server on its HTTP channel The port to which this hosted cache client will offer content to the hosted cache server on its HTTP channel
96The port to which this hosted cache client will offer content to the hosted cache server on its HTTPS channel The port to which this hosted cache client will offer content to the hosted cache server on its HTTPS channel
97The port on which this hosted cache server will listen for incoming offer messages on its HTTP channel The port on which this hosted cache server will listen for incoming offer messages on its HTTP channel
98The port on which this hosted cache server will listen for incoming offer messages on its HTTPS channel The port on which this hosted cache server will listen for incoming offer messages on its HTTPS channel
99Describes BranchCache networking settings Describes BranchCache networking settings
100Identifies an instance of MSFT_BranchCacheStore Identifies an instance of MSFT_BranchCacheStore
101The maximum cache file size, represented as a percentage of the disk volume on which the cache is stored The maximum cache file size, represented as a percentage of the disk volume on which the cache is stored
102The maximum cache file size, in bytes The maximum cache file size, in bytes
103The size of the cache file on disk, in bytes The size of the cache file on disk, in bytes
104The directory path where the cache file is located The directory path where the cache file is located
105Describes a BranchCache cache Describes a BranchCache cache
106The current size of the cached data, in bytes The current size of the cached data, in bytes
107Describes a BranchCache primary cache Describes a BranchCache primary cache
108Describes a BranchCache hash cache Describes a BranchCache hash cache
109Describes a BranchCache secondary cache Describes a BranchCache secondary cache
110Describes a BranchCache data cache extension Describes a BranchCache data cache extension
111DataCacheExtensions DataCacheExtensions
112Represents a BranchCache data cache Represents a BranchCache data cache
113Identifies an instance of MSFT_BranchCache Identifies an instance of MSFT_BranchCache
114Indicates if BranchCache is enabled Indicates if BranchCache is enabled
115The current status of the BranchCache service The current status of the BranchCache service
116Running Running
117The start type of the BranchCache service The start type of the BranchCache service
118Manual Manual
119Automatic Automatic
120Configuration related to the BranchCache client role Configuration related to the BranchCache client role
121Configuration related to the BranchCache content server role Configuration related to the BranchCache content server role
122Describes configuration related to the BranchCache hosted cache server role Describes configuration related to the BranchCache hosted cache server role
123BranchCache networking configuration BranchCache networking configuration
124BranchCache hash cache BranchCache hash cache
125BranchCache data cache BranchCache data cache
126Describes overall configuration and state for BranchCache Describes overall configuration and state for BranchCache
127Enables BranchCache and configures a machine to operate in distributed cache mode. Enables BranchCache and configures a machine to operate in distributed cache mode.
129Indicates the operation should not prompt for confirmation Indicates the operation should not prompt for confirmation
130Configures BranchCache to operate in hosted cache client mode. Configures BranchCache to operate in hosted cache client mode.
131Names of the hosted cache servers to use. Names of the hosted cache servers to use.
132Version of the offer protocol to use when contacting this hosted cache server. Version of the offer protocol to use when contacting this hosted cache server.
133Indicates the client should locate hosted cache servers using service connection points. Indicates the client should locate hosted cache servers using service connection points.
134Enables the BranchCache service in local caching mode. Enables the BranchCache service in local caching mode.
135Disables the BranchCache service. Disables the BranchCache service.
136Deletes a cache file. Deletes a cache file.
137The cache extension which should be removed The cache extension which should be removed
138Specifies the cache file to operate on. Specifies the cache file to operate on.
139Modifies the cache file configuration. Modifies the cache file configuration.
140The cache which should be modified The cache which should be modified
141Specifies the new location on disk for this this cache file. Specifies the new location on disk for this this cache file.
142Specifies the new size (in terms of disk percentage) of this cache file. Specifies the new size (in terms of disk percentage) of this cache file.
143Specifies the new size of this cache file. Specifies the new size of this cache file.
144Indicates the cache should be defragmented Indicates the cache should be defragmented
146Indicates the modified cache should be output Indicates the modified cache should be output
148Deletes all data in all cache files. Deletes all data in all cache files.
149Imports the cryptographic key used in the generation of segment secrets. Imports the cryptographic key used in the generation of segment secrets.
150Path of the file containing the key information to import. Path of the file containing the key information to import.
151Passphrase for the file containing the key information. Passphrase for the file containing the key information.
152Exports a secret key to a file. Exports a secret key to a file.
153Path of the file that will contain the key information. Path of the file that will contain the key information.
154Passphrase used to encrypt the file containing the key information. Passphrase used to encrypt the file containing the key information.
155Specifies the authentication scheme for clients. Specifies the authentication scheme for clients.
156Specifies the authentication mode. Specifies the authentication mode.
157Client may be instructed to operate in a downgraded mode, in which it will issue specified version requests to content servers. Client may be instructed to operate in a downgraded mode, in which it will issue specified version requests to content servers.
158Specifies whether or not the client should operate in a downgraded mode and which version should be used. Specifies whether or not the client should operate in a downgraded mode and which version should be used.
159Configures a client to listen for content discovery requests in distributed cache mode when operating on battery. Configures a client to listen for content discovery requests in distributed cache mode when operating on battery.
160A client may be configured to not listen for content discovery requests in distributed cache mode when operating on battery. A client may be configured to not listen for content discovery requests in distributed cache mode when operating on battery.
161Sets the minimum latency that must exist between client and server before transparent caching functions are utilized. Sets the minimum latency that must exist between client and server before transparent caching functions are utilized.
162Minimum latency that must exist between client and server before BranchCache should be used. Minimum latency that must exist between client and server before BranchCache should be used.
163Sets the cryptographic key used in the generation of segment secrets. Sets the cryptographic key used in the generation of segment secrets.
164Passphrase to use in the computation of the server secret key. Passphrase to use in the computation of the server secret key.
165Adds a new republication cache file to increase the amount of storage available on a hosted cache server. Adds a new republication cache file to increase the amount of storage available on a hosted cache server.
166Indicates the newly created cache extension should be output Indicates the newly created cache extension should be output
167Disables downgrading, so that the client will no longer request the specified version of content information from servers. Disables downgrading, so that the client will no longer request the specified version of content information from servers.
168Configures BranchCache to operate in hosted cache server mode. Configures BranchCache to operate in hosted cache server mode.
169Indicates the hosted cache server should register a service connection point Indicates the hosted cache server should register a service connection point
170Resets BranchCache to a default configuration. Resets BranchCache to a default configuration.
171If True, resets only the Windows firewall rules. If True, resets only the Windows firewall rules.
172If True, resets only the Performance Counters. If True, resets only the Performance Counters.
173Creates hashes for web content Creates hashes for web content
174Specifies the file or folder to be hashed Specifies the file or folder to be hashed
175Specifies the version of the BranchCache hashing scheme to use Specifies the version of the BranchCache hashing scheme to use
176Indicates the hashes should be saved to a staging area for future export Indicates the hashes should be saved to a staging area for future export
177Specifies a temporary folder to output staging data to Specifies a temporary folder to output staging data to
178Specifies a reference file from a previous execution Specifies a reference file from a previous execution
179Specifies the operation should be applied to subfolders Specifies the operation should be applied to subfolders
180Creates hashes for file content Creates hashes for file content
181Exports a cache package Exports a cache package
182Indicates the contents of the local data cache will be included in the package Indicates the contents of the local data cache will be included in the package
183Specifies the path to the data package Specifies the path to the data package
184Specifies the location of the cache files to be packaged Specifies the location of the cache files to be packaged
185Specifies the path where an output reference file should be generated Specifies the path where an output reference file should be generated
186Imports a cache package Imports a cache package
187Specifies the cache package to import Specifies the cache package to import
188Sets the maximum age of an entry in the data cache. Sets the maximum age of an entry in the data cache.
189The maximum number of days a cache entry is valid in the data cache. The maximum number of days a cache entry is valid in the data cache.
190Indicates the operation should not prompt for confirmation. Indicates the operation should not prompt for confirmation.
191BranchCache task orchestrator BranchCache task orchestrator
1001BranchCache BranchCache
1002Default Default
1006Content Retrieval URL Reservation Content Retrieval URL Reservation
1007Hosted Cache URL Reservation Hosted Cache URL Reservation
1008Hosted Cache HTTP URL Reservation Hosted Cache HTTP URL Reservation
1009"BranchCache - Content Retrieval (Uses HTTP)" "BranchCache - Content Retrieval (Uses HTTP)"
1010"BranchCache - Peer Discovery (Uses WSD)" "BranchCache - Peer Discovery (Uses WSD)"
1011"BranchCache - Hosted Cache Server (Uses HTTPS)" "BranchCache - Hosted Cache Server (Uses HTTPS)"
1012"BranchCache - Hosted Cache Client (Uses HTTPS)" "BranchCache - Hosted Cache Client (Uses HTTPS)"
2001Adding Data Cache Extension at %1!s! Adding Data Cache Extension at %1!s!
2003Removing Data Cache Extension from %1!s! Removing Data Cache Extension from %1!s!
2004Clearing the cache Clearing the cache
2005Modifying Registry settings Modifying Registry settings
2006Setting Service Start Type to %1!s! Setting Service Start Type to %1!s!
2007Configuring URL Reservation url=%1!s!, sddl=%2!s! Configuring URL Reservation url=%1!s!, sddl=%2!s!
2008Deleting Hash Cache at %1!s! Deleting Hash Cache at %1!s!
2009Deleting Data Cache at %1!s! Deleting Data Cache at %1!s!
2010Deleting Data Cache Extension at %1!s! Deleting Data Cache Extension at %1!s!
2011Starting Service Starting Service
2012Stopping Service Stopping Service
2013Enabling Firewall Rule Group %1!s! Enabling Firewall Rule Group %1!s!
2014Disabling Firewall Rule Group %1!s! Disabling Firewall Rule Group %1!s!
2015Enabling Service Enabling Service
2016Disabling Service Disabling Service
2017Exporting Data Cache Exporting Data Cache
2018Importing Secret key Importing Secret key
2019Exporting Secret key Exporting Secret key
2020Importing Cache package Importing Cache package
2021Moving Reference file from %1!s! to %2!s! Moving Reference file from %1!s! to %2!s!
2022Packing files from %1!s! Packing files from %1!s!
2023Unpacking files at %1!s! Unpacking files at %1!s!
2024Generating hashes Generating hashes
2025Resetting Registry values Resetting Registry values
2026Setting Cache at %1!s! Setting Cache at %1!s!
2027Setting Secret Key Setting Secret Key
2028Execute Add-BCDataCacheExtension Execute Add-BCDataCacheExtension
2029Execute Clear-BCCache Execute Clear-BCCache
2030Execute Disable-BC Execute Disable-BC
2031Execute Disable-BCDowngrading Execute Disable-BCDowngrading
2032Execute Disable-BCServeOnBattery Execute Disable-BCServeOnBattery
2033Execute Enable-BCDistributed Execute Enable-BCDistributed
2034Execute Enable-BCDowngrading Execute Enable-BCDowngrading
2035Execute Enable-BCHostedClient Execute Enable-BCHostedClient
2036Execute Enable-BCHostedServer Execute Enable-BCHostedServer
2037Execute Enable-BCLocal Execute Enable-BCLocal
2038Execute Enable-BCServeOnBattery Execute Enable-BCServeOnBattery
2039Execute Export-BCCachePackage Execute Export-BCCachePackage
2040Execute Export-BCSecretKey Execute Export-BCSecretKey
2041Execute Import-BCCachePackage Execute Import-BCCachePackage
2042Execute Import-BCSecretKey Execute Import-BCSecretKey
2043Execute Publish-BCFileContent Execute Publish-BCFileContent
2044Execute Publish-BCWebContent Execute Publish-BCWebContent
2045Execute Remove-BCDataCacheExtension Execute Remove-BCDataCacheExtension
2046Execute Reset-BC Execute Reset-BC
2047Execute Set-BCAuthentication Execute Set-BCAuthentication
2048Execute Set-BCCache Execute Set-BCCache
2049Execute Set-BCMinSMBLatency Execute Set-BCMinSMBLatency
2050Execute Set-BCSecretKey Execute Set-BCSecretKey
2051Package generated - %1!s! Package generated - %1!s!
2052Creating directory - %1!s! Creating directory - %1!s!
2053Deleting directory - %1!s! Deleting directory - %1!s!
2054Generating Reference file at %1!s! Generating Reference file at %1!s!
2055Generating Staging data at %1!s! Generating Staging data at %1!s!
2056Execute Set-BCDataCacheEntryMaxAge Execute Set-BCDataCacheEntryMaxAge
2057Resetting Performance Counters Resetting Performance Counters
3002Could not flush the local cache. Could not flush the local cache.
3003Could not write to the system registry. Could not write to the system registry.
3004Could not restore system registry defaults. Could not restore system registry defaults.
3005Could not query the Service Control Manager. Could not query the Service Control Manager.
3006Could not configure service start type. Could not configure service start type.
3007Could not read HTTP Server configuration. Could not read HTTP Server configuration.
3008Could not modify HTTP Server configuration. Could not modify HTTP Server configuration.
3009The specified cache size is zero or less. The specified cache size is zero or less.
3010Could not stop the service. Could not stop the service.
3011Could not configure directory security - %1!s! Could not configure directory security - %1!s!
3012Could not query secret store. Could not query secret store.
3013Could not export key. Please ensure the output directory exists. Could not export key. Please ensure the output directory exists.
3014Source and Destination paths are identical. Source and Destination paths are identical.
3015Could not read the Windows Firewall configuration. Could not read the Windows Firewall configuration.
3016Could not modify the Windows Firewall configuration. Could not modify the Windows Firewall configuration.
3018Could not import key. Please ensure the import file exists and the passphrase is correct. Could not import key. Please ensure the import file exists and the passphrase is correct.
3019Could not pack files. Could not pack files.
3020Could not configure service shutdown timeout. Could not configure service shutdown timeout.
3021Could not start the service. Could not start the service.
3022Could not unpack files. Could not unpack files.
3023Could not create directory - %1!s! Could not create directory - %1!s!
3024Could not generate a new secret key. Could not generate a new secret key.
3025The specified cache size is below the minimum. The specified cache size is below the minimum.
3026The specified data cache extension size is too large to be supported by the current configuration. The specified data cache extension size is too large to be supported by the current configuration.
3027The specified data cache is too small to be supported by the current configuration. The specified data cache is too small to be supported by the current configuration.
3028Cannot remove the data cache. Only data cache extensions may be removed. Cannot remove the data cache. Only data cache extensions may be removed.
3029There is no cache at the specified path. There is no cache at the specified path.
3030Could not generate hashes. Could not generate hashes.
3031Could not refresh configuration. Could not refresh configuration.
3032Could not move the reference file. Could not move the reference file.
3033Could not read from the system registry. Could not read from the system registry.
3034File not found - %1!s!. File not found - %1!s!.
3035Directory not found - %1!s! Directory not found - %1!s!
3036File already exists - %1!s! File already exists - %1!s!
3037Directory already exists - %1!s! Directory already exists - %1!s!
3038Cannot modify local configuration because the setting is configured in policy. Cannot modify local configuration because the setting is configured in policy.
3039Could not validate secret key file path - %1!s! Could not validate secret key file path - %1!s!
3040Invalid percentage. Only values between 1 and 100 are valid. Invalid percentage. Only values between 1 and 100 are valid.
3041Mandatory size argument not present. Mandatory size argument not present.
3042Invalid Version. Only values 1 or 2 are valid. Invalid Version. Only values 1 or 2 are valid.
3043Invalid combination of hosted server names and hosted server version. Invalid combination of hosted server names and hosted server version.
3044Atleast one hosted cache server must be specified. Atleast one hosted cache server must be specified.
3045Hosted cache server location is not valid - %1!s! Hosted cache server location is not valid - %1!s!
3046Hosted cache server not found - %1!s! Hosted cache server not found - %1!s!
3047Hosted cache server address resolution failed - %1!s! Hosted cache server address resolution failed - %1!s!
3048Hosted cache server address is numeric - %1!s! Hosted cache server address is numeric - %1!s!
3049Hosted cache server version outside acceptable range. Hosted cache server version outside acceptable range.
3050Hosted Cache Server Mode cannot be used in this version of Windows. Hosted Cache Server Mode cannot be used in this version of Windows.
3051Could not validate path - %1!s! Could not validate path - %1!s!
3052Could not validate passphrase - %1!s! Could not validate passphrase - %1!s!
3053Cannot move a data cache when a policy store is specified. Cannot move a data cache when a policy store is specified.
3054Invalid Mode parameter. Invalid Mode parameter.
3055Cannot specify size in bytes when a policy store is specified. Cannot specify size in bytes when a policy store is specified.
3056Size argument outside acceptable range. Size argument outside acceptable range.
3057Cannot defragment when a policy store is specified. Cannot defragment when a policy store is specified.
3058No operation specified. No operation specified.
3059Cannot use passthru when a policy store is specified. Cannot use passthru when a policy store is specified.
3060Mandatory mode parameter not specified. Mandatory mode parameter not specified.
3061Client Authentication is only valid in Hosted Cache Server Mode. Client Authentication is only valid in Hosted Cache Server Mode.
3062Mandatory latency parameter not specified. Mandatory latency parameter not specified.
3063Could not save changes to group policy. Could not save changes to group policy.
3064Current group policy configuration prevents local firewall rules from being applied. The BranchCache configuration will be changed, but changes to the local BranchCache firewall rules will not take effect. Current group policy configuration prevents local firewall rules from being applied. The BranchCache configuration will be changed, but changes to the local BranchCache firewall rules will not take effect.
3065Cannot specify both size and percentage. Cannot specify both size and percentage.
3066Directory is not on an NTFS volume - %1!s! Directory is not on an NTFS volume - %1!s!
3067Directory path is too long - %1!s! Directory path is too long - %1!s!
3068Directory must be empty - %1!s! Directory must be empty - %1!s!
3069Serve on Battery setting is only valid in Distributed Mode. Serve on Battery setting is only valid in Distributed Mode.
3070Mandatory path parameter not specified. Mandatory path parameter not specified.
3071Could not validate policy store - %1!s! Could not validate policy store - %1!s!
3072This command requires elevation. This command requires elevation.
3073Could not access the Windows Firewall configuration. Could not access the Windows Firewall configuration.
3074Cannot add a Data Cache Extension. Exceeded permissible count. Cannot add a Data Cache Extension. Exceeded permissible count.
3075Mandatory cache parameter not specified. Mandatory cache parameter not specified.
3076Hosted cache SCP registration is not supported on writeable domain controllers. Hosted cache SCP registration is not supported on writeable domain controllers.
3077Cannot move multiple caches to a single location. Cannot move multiple caches to a single location.
3078BranchCache service is not installed. BranchCache service is not installed.
3079Cannot publish file content. Please ensure "BranchCache for Network Files" role service is installed. Cannot publish file content. Please ensure "BranchCache for Network Files" role service is installed.
3080Mandatory age parameter not specified. Mandatory age parameter not specified.
3081Invalid age. Please enter a value greater than 0. Invalid age. Please enter a value greater than 0.
3082Hosted Cache SCP is not supported on workstation that is not a member of a domain. Hosted Cache SCP is not supported on workstation that is not a member of a domain.

EXIF

File Name:NetPeerDistCim.dll.mui
Directory:%WINDIR%\WinSxS\amd64_microsoft-windows-p..st-common.resources_31bf3856ad364e35_10.0.15063.0_da-dk_d589149f23b8aeec\
File Size:66 kB
File Permissions:rw-rw-rw-
File Type:Win32 DLL
File Type Extension:dll
MIME Type:application/octet-stream
Machine Type:Intel 386 or later, and compatibles
Time Stamp:0000:00:00 00:00:00
PE Type:PE32
Linker Version:14.10
Code Size:0
Initialized Data Size:66560
Uninitialized Data Size:0
Entry Point:0x0000
OS Version:10.0
Image Version:10.0
Subsystem Version:6.0
Subsystem:Windows GUI
File Version Number:10.0.15063.0
Product Version Number:10.0.15063.0
File Flags Mask:0x003f
File Flags:(none)
File OS:Windows NT 32-bit
Object File Type:Dynamic link library
File Subtype:0
Language Code:Danish
Character Set:Unicode
Company Name:Microsoft Corporation
File Description:BranchCache WMI Provider
File Version:10.0.15063.0 (WinBuild.160101.0800)
Internal Name:NetPeerDistCim.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original File Name:NetPeerDistCim.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0

What is NetPeerDistCim.dll.mui?

NetPeerDistCim.dll.mui is Multilingual User Interface resource file that contain Danish language for file NetPeerDistCim.dll (BranchCache WMI Provider).

File version info

File Description:BranchCache WMI Provider
File Version:10.0.15063.0 (WinBuild.160101.0800)
Company Name:Microsoft Corporation
Internal Name:NetPeerDistCim.dll
Legal Copyright:© Microsoft Corporation. All rights reserved.
Original Filename:NetPeerDistCim.dll.mui
Product Name:Microsoft® Windows® Operating System
Product Version:10.0.15063.0
Translation:0x406, 1200