????

Your IP : 216.73.216.152


Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/DscCore.dll.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$��<߱�R���R���R�U�����R�U�P���R�Rich��R�PEL�!�

���@  �8.rdata�@@.rsrc� �@@�lCn
T88�lCn$��8.rdata8x.rdata$zzzdbg p.rsrc$01p.@�.rsrc$02 �gm���ˉ���JH��o0���,n���lCnh�(�@�����I�������(�@�X�p����������� �!�"0�#H�$`�%x�&��'��(��)��*��+�, �-8�.P�/h�0��1��2��3��4��5��6�7(�8@�?X�@p�A��E��F��G��H��I�J�K0�LH�M`�Nx�O��P��R��S��T��U�V �X8�YP�^h�_��`��a��b��e��f��g	�k(	�n@	�oX	�qp	�r�	��	�	�		�		�		�		�		
	
	(
	8
	H
	X
	h
	x
	�
	�
	�
	�
	�
	�
	�
	�
			(	8	H	X	h	x	�	�	�	�	�	�	�	�			(	8	H	X	h	x	�	�	�	�	�	�	�	�	
	
	(
	8
	H
	X
	h
	x
	�
	�
	�
	�
	�
	�
	�
	�
			(	8	H	Xp.�� /���/b�P0Z��0���5*��6<�;���=��h>@��>��?��4A^��D��4H��,J �LO(�tS(��V���[��X^<��`���l��t�
��J�́��P�*�|����������t�����!��"����ܼ��`��l�h������`�8�������l����T�h��l����\�d�	�p�6����`
<������� �
�p+��@;&�hA$��E ��Lr� O�� T��U���U���X��(d��{~���
�����P��	����Ԣ�ܭD� ���гv�H�`���x�MUI�����SW,u=��&٘�m��V��H4!�s�@{���MUIen-US3Base schema for all native configuration providers.#Rollback to previous configuration.!This represents a key-value pair.PAStarts the consistency check.PAKSend the configuration document to the managed node and save it as pending.kSend the configuration document to the managed node and use Configuration Agent to apply the configuration.�Send the configuration document to the managed node and use Configuration Agent to apply the configuration using the Get method.bSend the configuration document to the managed node and test it against the current configuration.VSet Local Configuration Manager settings that are used to control Configuration Agent.VGet Local Configuration Manager settings that are used to control Configuration Agent.'Stopping the configuration in progress.PA�Local Configuration Manager that controls the states of configuration files and uses Configuration Agent to apply the configurations.PAhThe time interval between consecutive runs for reapplying the configuration to get to the desired state.2The certificate ID used to locate the certificate.HThe configuration ID used to get the configuration from the pull server.6Name of the configuration and module Download Manager.1Custom data that is specific to Download Manager.MThe time interval between consecutive runs to get the action from the server.%Local Configuration Manager settings.SUserName is the name of the user that an authorization service maps to an identity.JThe UserPassword property may contain a password used to access resources.2Credential to use for DSC configuration providers.'Default credential to access resources.Reboot node if needed.,The configuration apply mode for the server.	ApplyOnlyApplyAndMonitorApplyAndAutoCorrectJThe refresh mode for the server. Valid values are Pull, Push and Disabled.4Overwrite modules when downloading from Pull Server.PushPullDisabledBusy-Current state of local configuration manager.
PendingReboot3Use Configuration Agent to apply the configuration.PAAn unique identifier of client.;Compatible versions of current local configuration manager./Current version of local configuration manager.+String URL of the download manager location@Web report manager class inheriting from OMI_ReportManager class1Class defining the configuration download manager8Class defining the structure of resource module managersClass defining a report managerKWeb download manager class inheriting from OMI_ConfigurationDownloadManagerZFile configuration download manager class inheriting from OMI_ConfigurationDownloadManager2String URL of the resource module manager locationPAKWeb resource module manager class inheriting from OMI_ResourceModuleManager,String UNC path of the File resource managerRFile resource module manager class inheriting from OMI_ResourceModuleManager classlArray of configuration download manager objects that contain location information to download configurationsYArray of resource module managers pointing to a location to download missing DSCResources2Class for holding properties of a resource object.XArray of report managers pointing to a location that would help generate reports for DSC.Default credential to access the file location.Boolean variable to allow unsecure connections7String UNC source path of the download manager locationPA:Field to display whether the resource is in desired state.(Description of the partial configurationQDefines the resources that are exclusive to this particular partial configurationLThe configuration repository source that this partial configuration will useZA dependency variable indicating which partial configuration must be applied prior to this.This represents a Partial Configuration class.@Array of partial configurations that are specified to be applied)URL of the server used by report manager.IThe certificate ID used to locate the certificate for secure connections.GSpecifies whether report manager can use unsecure connection over http."Unique Id for a resource instance.DSource Info to correlate it back to powershell configuration script.+List of resources this resource depends on./Name of the module that supports this resource.3Version  of the module that supports this resource.+Name of the configuration this is a part of0Base schema for all Metaconfiguration resources.CClass for holding properties of a resource object in desired state.GClass for holding properties of a resource object not in desired state.,Date and time when the resource was started.+Time taken to process entire configuration."Reboot was requested for resource.=Initial property values of the resource before it is enacted.:Final property values of the resource after it is enacted.Status of configuration.SuccessFailureAborted
InProgress1Date and time when the configuration was started.*Reboot was requested during configuration.Type of Configuration.InitialConsistencyRebootReadOnly%Job ID associated with configuration.Meta data of configuration.+Total number of resources in configuration.Mode of configuration.(Version of LCM at time of configuration..NetBIOS name of node at time of configuration.,IP Address of node at time of configuration.-MAC address of node at time of configuration.8Meta-Configuration information at time of configuration.7Resources successfully configured in the configuration.&Resources failed in the configuration.;Class for holding propertis of configuration status object.%Get the configuration status history.The resource name like File.The instance name like file1.CResulting streamed output from GetConfigurationResultOutput method.�Send the configuration document to the managed node and start using the Configuration Agent to apply the configuration. Use GetConfigurationResultOutput to retrieve result output.CRetrieve the Configuration Agent output relating to a specific job.Time taken to process resource.-Locale of the node running the configuration.6Number of days to retain configuration status history.Error returned by the provider.FError encountered in local configuration manager during configuration.!Removing the configuration files.%Message for incoming requests to DSC.The enumeration for DebugMode.NoneForceModuleImportAll"Execute Get on a provider directly"Execute Set on a provider directly#Execute Test on a provider directly#The action after reboot the server.ContinueConfigurationStopConfigurationPrimary classification of the error. The following values are defined: 
2 - Communications Error. Errors of this type are principally associated with the procedures and/or processes required to convey information from one point to another. 
3 - Quality of Service Error. Errors of this type are principally associated with failures that result in reduced functionality or performance. 
4 - Software Error. Error of this type are principally associated with a software or processing fault. 
5 - Hardware Error. Errors of this type are principally associated with an equipment or hardware failure. 
6 - Environmental Error. Errors of this type are principally associated with a failure condition relating the to facility, or other environmental considerations. 
7 - Security Error. Errors of this type are associated with security violations, detection of viruses, and similar issues. 
8 - Oversubscription Error. Errors of this type are principally associated with the failure to allocate sufficient resources to complete the operation. 
9 - Unavailable Resource Error. Errors of this type are principally associated with the failure to access a required resource. 
10 -Unsupported Operation Error. Errors of this type are principally associated with requests that are not supported.UnknownPAOtherCommunications ErrorQuality of Service ErrorSoftware ErrorHardware ErrorEnvironmental ErrorSecurity ErrorOversubscription ErrorUnavailable Resource ErrorUnsupported Operation Error
DMTF Reserved[A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.A string that uniquely identifies the entity that owns the definition of the format of the Message described in this instance. OwningEntity MUST include a copyrighted, trademarked or otherwise unique name that is owned by the business entity or standards body defining the format.kAn opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.The formatted message. This message is constructed by combining some or all of the dynamic elements specified in the MessageArguments property with the static elements uniquely identified by the MessageID in a message registry or other catalog associated with the OwningEntity.7An array containing the dynamic content of the message.An enumerated value that describes the severity of the Indication from the notifier\'s point of view: 
0 - the Perceived Severity of the indication is unknown or indeterminate. 
1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property. 
2 - Information should be used when providing an informative response. 
3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 
4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 
5 - Major should be used to indicate action is needed NOW. 
6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 
7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it\'s too late to take remedial action. 
2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the Error is purely informational or its severity is simply unknown.InformationDegraded/WarningMinorMajorCriticalFatal/NonRecoverableCAn enumerated value that describes the probable cause of the error.Adapter/Card ErrorApplication Subsystem FailureBandwidth ReducedConnection Establishment ErrorCommunications Protocol Error Communications Subsystem Failure!Configuration/Customization Error
CongestionCorrupt DataCPU Cycles Limit ExceededDataset/Modem ErrorDegraded SignalDTE-DCE Interface ErrorEnclosure Door OpenEquipment MalfunctionExcessive VibrationFile Format Error
Fire DetectedFlood Detected
Framing ErrorHVAC ProblemHumidity UnacceptableI/O Device ErrorInput Device ErrorPA	LAN ErrorNon-Toxic Leak DetectedLocal Node Transmission Error
Loss of FrameLoss of SignalMaterial Supply ExhaustedMultiplexer Problem
Out of MemoryOutput Device ErrorPerformance Degraded
Power ProblemPressure Unacceptable*Processor Problem (Internal Machine Error)Pump FailureQueue Size ExceededReceive FailureReceiver FailureRemote Node Transmission ErrorResource at or Nearing CapacityResponse Time ExcessiveRetransmission Rate Excessive&Software Program Abnormally Terminated*Software Program Error (Incorrect Results)Storage Capacity ProblemTemperature UnacceptableThreshold CrossedTiming ProblemToxic Leak DetectedTransmit FailureTransmitter FailureUnderlying Resource UnavailableVersion MismatchPAPrevious Alert ClearedLogin Attempts FailedSoftware Virus DetectedHardware Security BreachedDenial of Service DetectedSecurity Credential MismatchUnauthorized AccessAlarm ReceivedLoss of PointerPayload MismatchTransmission ErrorExcessive Error Rate
Trace ProblemElement UnavailableElement MissingLoss of Multi FrameBroadcast Channel FailureInvalid Message ReceivedRouting FailureBackplane FailureIdentifier DuplicationProtection Path FailureSync Loss or MismatchTerminal ProblemReal Time Clock FailureAntenna FailureBattery Charging FailureDisk FailureFrequency Hopping FailureLoss of RedundancyPower Supply FailureSignal Quality ProblemBattery DischargingBattery FailureCommercial Power ProblemFan FailureEngine FailureSensor FailureFuse FailureGenerator FailureLow BatteryLow Fuel	Low Water
Explosive Gas
High WindsIce BuildupSmokeMemory MismatchOut of CPU CyclesSoftware Environment ProblemSoftware Download FailureElement ReinitializedTimeoutLogging Problems
Leak DetectedProtection Mechanism FailureProtecting Resource FailureDatabase InconsistencyAuthentication FailureBreach of ConfidentialityCable TamperDelayed InformationDuplicate InformationInformation MissingInformation ModificationInformation Out of SequenceKey ExpiredNon-Repudiation FailureOut of Hours ActivityOut of ServiceProcedural ErrorUnexpected Information>A free-form string describing the probable cause of the error.OA free-form string describing recommended actions to take to resolve the error.�The identifying information of the entity (i.e., the instance) generating the error. If this entity is modeled in the CIM Schema, this property contains the path of the instance encoded as a string parameter. If not modeled, the property contains some identifying string that names the entity that generated the error. The path or identifying string is formatted per the ErrorSourceFormat property.�The format of the ErrorSource property is interpretable based on the value of this property. Values are defined as: 
0 - Unknown. The format is unknown or not meaningfully interpretable by a CIM client application. 
1 - Other. The format is defined by the value of the OtherErrorSourceFormat property.2 - CIMObjectPath. A CIM Object Path as defined in the CIM Infrastructure specification. Note: CIM 2.5 and earlier used the term object names.
CIMObjectPath�A string defining "Other" values for ErrorSourceFormat. This value MUST be set to a non NULL value when ErrorSourceFormat is set to a value of 1 ("Other"). For all other values of ErrorSourceFormat, the value of this string must be set to NULL.XThe CIM status code that characterizes this instance. 
This property defines the status codes that MAY be return by a conforming CIM Server or Listener. Note that not all status codes are valid for each operation. The specification for each operation SHOULD define the status codes that may be returned by that operation. 
The following values for CIM status code are defined: 
1 - CIM_ERR_FAILED. A general error occurred that is not covered by a more specific error code. 
2 - CIM_ERR_ACCESS_DENIED. Access to a CIM resource was not available to the client. 
3 - CIM_ERR_INVALID_NAMESPACE. The target namespace does not exist. 
4 - CIM_ERR_INVALID_PARAMETER. One or more parameter values passed to the method were invalid. 
5 - CIM_ERR_INVALID_CLASS. The specified Class does not exist. 
6 - CIM_ERR_NOT_FOUND. The requested object could not be found. 
7 - CIM_ERR_NOT_SUPPORTED. The requested operation is not supported. 
8 - CIM_ERR_CLASS_HAS_CHILDREN. Operation cannot be carried out on this class since it has instances. 
9 - CIM_ERR_CLASS_HAS_INSTANCES. Operation cannot be carried out on this class since it has instances. 
10 - CIM_ERR_INVALID_SUPERCLASS. Operation cannot be carried out since the specified superclass does not exist. 
11 - CIM_ERR_ALREADY_EXISTS. Operation cannot be carried out because an object already exists. 
12 - CIM_ERR_NO_SUCH_PROPERTY. The specified Property does not exist. 
13 - CIM_ERR_TYPE_MISMATCH. The value supplied is incompatible with the type. 
14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED. The query language is not recognized or supported. 
15 - CIM_ERR_INVALID_QUERY. The query is not valid for the specified query language. 
16 - CIM_ERR_METHOD_NOT_AVAILABLE. The extrinsic Method could not be executed. 
17 - CIM_ERR_METHOD_NOT_FOUND. The specified extrinsic Method does not exist. 
18 - CIM_ERR_UNEXPECTED_RESPONSE. The returned response to the asynchronous operation was not expected. 
19 - CIM_ERR_INVALID_RESPONSE_DESTINATION. The specified destination for the asynchronous response is not valid. 
20 - CIM_ERR_NAMESPACE_NOT_EMPTY. The specified Namespace is not empty.
21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT. The enumeration context supplied is not valid.
22 - CIM_ERR_INVALID_OPERATION_TIMEOUT. The specified Namespace is not empty.
23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED. The specified Namespace is not empty.
24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED. The attempt to abandon a pull operation has failed.
25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED. Filtered Enumeratrions are not supported.
26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED. Continue on error is not supported.
27 - CIM_ERR_SERVER_LIMITS_EXCEEDED. The WBEM Server limits have been exceeded (e.g. memory, connections, ...).
28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN. The WBEM Server is shutting down.
29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED. The specified Query Feature is not supported.CIM_ERR_FAILEDPACIM_ERR_ACCESS_DENIEDCIM_ERR_INVALID_NAMESPACECIM_ERR_INVALID_PARAMETERCIM_ERR_INVALID_CLASSCIM_ERR_NOT_FOUNDCIM_ERR_NOT_SUPPORTEDCIM_ERR_CLASS_HAS_CHILDRENCIM_ERR_CLASS_HAS_INSTANCESCIM_ERR_INVALID_SUPERCLASSCIM_ERR_ALREADY_EXISTSCIM_ERR_NO_SUCH_PROPERTYCIM_ERR_TYPE_MISMATCH$CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTEDCIM_ERR_INVALID_QUERYCIM_ERR_METHOD_NOT_AVAILABLECIM_ERR_METHOD_NOT_FOUNDPACIM_ERR_UNEXPECTED_RESPONSE$CIM_ERR_INVALID_RESPONSE_DESTINATIONCIM_ERR_NAMESPACE_NOT_EMPTY#CIM_ERR_INVALID_ENUMERATION_CONTEXT!CIM_ERR_INVALID_OPERATION_TIMEOUTCIM_ERR_PULL_HAS_BEEN_ABANDONED CIM_ERR_PULL_CANNOT_BE_ABANDONED*CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED+CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTEDCIM_ERR_SERVER_LIMITS_EXCEEDEDCIM_ERR_SERVER_IS_SHUTTING_DOWN#CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED�A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode.2.22.1�CIM_Error is a specialized class that contains information about the severity, cause, recommended actions and other data related to the failure of a CIM Operation. Instances of this type MAY be included as part of the response to a CIM Operation.Application-specific error codeMThe name of the error type, for example : 'HRESULT' or 'MI_RESULT' or 'Win32'6Enumeration corresponding to the category enum in MI.hMI_ERRORCATEGORY_NOT_SPECIFIEDMI_ERRORCATEGORY_OPEN_ERRORMI_ERRORCATEGORY_CLOSE_EERRORMI_ERRORCATEGORY_DEVICE_ERROR"MI_ERRORCATEGORY_DEADLOCK_DETECTED!MI_ERRORCATEGORY_INVALID_ARGUMENTMI_ERRORCATEGORY_INVALID_DATA"MI_ERRORCATEGORY_INVALID_OPERATIONMI_ERRORCATEGORY_INVALID_RESULTMI_ERRORCATEGORY_INVALID_TYPEMI_ERRORCATEGORY_METADATA_ERROR MI_ERRORCATEGORY_NOT_IMPLEMENTEDMI_ERRORCATEGORY_NOT_INSTALLED!MI_ERRORCATEGORY_OBJECT_NOT_FOUND"MI_ERRORCATEGORY_OPERATION_STOPPED"MI_ERRORCATEGORY_OPERATION_TIMEOUTMI_ERRORCATEGORY_SYNTAX_ERRORMI_ERRORCATEGORY_PARSER_ERRORMI_ERRORCATEGORY_ACCESS_DENIEDMI_ERRORCATEGORY_RESOURCE_BUSY MI_ERRORCATEGORY_RESOURCE_EXISTS%MI_ERRORCATEGORY_RESOURCE_UNAVAILABLEMI_ERRORCATEGORY_READ_ERRORMI_ERRORCATEGORY_WRITE_ERRORMI_ERRORCATEGORY_FROM_STDERRMI_ERRORCATEGORY_SECURITY_ERRORMI_ERRORCATEGORY_PROTOCOL_ERROR!MI_ERRORCATEGORY_CONNECTION_ERROR%MI_ERRORCATEGORY_AUTHENTICATION_ERROR MI_ERRORCATEGORY_LIMITS_EXCEEDEDMI_ERRORCATEGORY_QUOTA_EXCEEDEDMI_ERRORCATEGORY_NOT_ENABLEDqOMI_Error is a class used to report errors in the OMI infrastructure and components built on that infrastructure.ResourceScriptBreakAll+Credentials under which the resource runs. IdlePendingConfiguration,State detail of local configuration manager.NThe resource module repository source that this partial configuration will useEnable Debug DSC Configuration. Disable Debug DSC Configuration.<Registration Key with which to register with the Pull ServerARegistration Key with which to register with the Reporting Server!AgentId of the current Dsc Agent.HRegistration Key with which to register with the Resource Repository WebKThe set of configuration names with which to register with the Pull Server.LocalConfigurationManagerfThe path to the trusted publisher store used to validate the signature of the mof document or modules.
ConfigurationModuleThe signature validation type.$Current signature validation policy.-The signature validation options of the node.5The maximum module size in MB that can be downloaded.-Resources changed state in the configuration.8Field to display whether the resource changed its state.MonitorOnlyPA]Class for holding properties of a resource object that changed state during current interval.String URL of the proxy server%Credential to access the proxy serverMemory allocation failed.&MOF file size exceeded max size limit.Error opening file: %1!s!Reading file content failedError getting file size.StringCchCatW failed.$CreateProcess failed for mofcomp.exe�PowerShell Desired State Configuration failed to register MOF file%1!s! using Mofcomp.exe during discovery of %2!s! resource . Check the MOF file and try again.6Unable to generate checksum for current configuration.@LCM failed to move one or more resources to their desired state.,LCM failed to load PowerShell module loader.9LCM failed to start desired state configuration manually.=LCM failed to retrieve property values of meta configuration.JLCM failed to retrieve the property %1!s! from the object of class %2!s! .1LCM failed to write to resource state cache file.-LCM failed to serialize resource state cache./LCM failed to deserialize resource state cache.&Invalid index to resource state cache.PA-LCM failed to serialize configuration status./LCM failed to deserialize configuration status.gNo status information available for node %1!s!. Apply a configuration on the target node and try again.PA;The registration of Event Tracing for Windows (ETW) failed.0Could not initialize the agent critical section./Could not initialize the file critical section.&Could not expand the environment path.ETW unregistration failed.nThe validation of the Configuration directory did not succeed. Ensure that the directory exists and try again.?Could not delete the old file Get.mof before the get operation.]Could not save the Get.mof file. Delete Get.mof in the Configuration directory and try again.yCould not load the instance document from the specified location. Ensure that the instance document exists and try again.!GetConfiguration did not succeed.zCould not delete the file Get.mof after the get operation. Check the properties of the location of the file and try again.cThe creation of the configuration directory failed. Verify the directory permissions and try again.Memory allocation failed.Stprintf failed._A configuration is pending. If you are in Pull mode, please run Update-DscConfiguration to pull a new configuration and apply it. If you are in Push mode, please run Start-DscConfiguration command with -Force parameter to apply a new configuration or run Start-DscConfiguration command with -UseExisting parameter to finish the existing configuration.rCould not save the pending configuration MOF file. Check the properties of the destination location and try again.HLoading the instance document from the pending location did not succeed.4The SendConfigurationApply function did not succeed.:Deleting the pending file after moving it did not succeed.PACould not copy file.iUnable to create configuration MOF file because converting security descriptor for administrators failed.�Could not create the configuration MOF file. Check the Analytic event log to investigate why the MOF file could not be created at this path.ECould not construct MSFT_DSCMetaConfiguration using Mof_Instance_New.ModuleLoader is null.HLoading the Local Configuration Manager settings schema did not succeed.!Metaschema loading returned null. Could not create the serializer.=Could not serialize the Local Configuration Manager settings.?Could not delete the Local Configuration Manager settings file.Creating deserializer failed.GCloning the typed Local Configuration Manager settings did not succeed.CCould not create the parameters required for invoking the Task API.AAdding task path parameters to call the task API did not succeed.8Creating a session to call the task API did not succeed.6The ExpandEnvironmentStrings function did not succeed.?Getting the current thread impersonation token did not succeed.Could not revert to self.Could not resume impersonation.HCould not construct the output object for the GetConfiguration function.BWriting the output parameter for GetConfiguration did not succeed.aApplyConfiguration could not get the current Local Configuration Manager settings for the system.4Posting output for GetConfiguration did not succeed.qCould not construct the output object for the ApplyConfiguration function. Check the configuration and try again.9The Set function in ApplyConfiguration returned an error.=Could not post the output in the ApplyConfiguration function.)Could not update LCM version information.\A reboot is scheduled to progress further. Configuration will be continued after the reboot.Starting consistency engine.Consistency check completed.\A pending configuration exists. DSC will process a set request on the pending configuration./Checking consistency for current configuration.;Configuration document successfully saved to pending state.mThe instance document does not specify any resource. Add at least one resource to the document and try again.]The Local Configuration Manager could not read the ComputerName property context information.:Local Configuration Manager could not get token info size.CAn LCM method call arrived from computer %1!s! with user sid %2!s!.�Could not save the temporary Local Configuration Manager settings file. Check the properties of the destination location and try again.-Could not delete the temporary metadata file.Deletion of file%1!s!failed.CExecuting Get-Action returned success but didn't return any status.FGet-DSCAction returned success but did not return the expected status.JGetConfiguration ran successfully, but did not return the expected status.AGetConfiguration ran successfully, but did not return any status.iThe configurationData parameter is reserved for future use. The current configuration is used by default.9Could not construct the test configuration output object.TCould not set the resource ID in TestConfiguration. Try running the operation again.5Could not post the output for the test configuration.�Current configuration does not exist. Execute Start-DscConfiguration command with -Path parameter to specify a configuration file and create a current configuration first.:Completed processing test operation. The operation failed.5[%1!s!]: LCM:  [ %2!-16s!]   %3!s! in  %4!s! seconds.>The Force parameter accepts only boolean values True or False.<Could not retrieve the Local Configuration Manager settings.Update consistency task failed.RMachine reboot failed. Please reboot it manually to finish processing the request.DSC is restarting the computer.SA PUSH operation was requested without -Force while configured for PULL processing.fA previous configuration does not exist. DSC can rollback only when there is a previous configuration.lThe ConfigurationNumber parameter is reserved for future use. The previous configuration is used by default.PA�Cannot invoke the %1!s! cmdlet. The %2!s! cmdlet is in progress and must return before %3!s! can be invoked. Use -Force option if that is available to cancel the current operation.Unexpected task name received.OAn interval was specified outside of the acceptable range (maximum of 31 days).;An error was encountered while deleting the temporary file.GetTempPath failed.GetTempFileName failed.CreateFile failed.WriteFile failed.CloseHandle failed./Error attempting to get the length of a string.ACompleted processing test operation. The operation returned True.BCompleted processing test operation. The operation returned False.*Clear the cache of built-in DSC resources.4Failed to clear the cache of built-in DSC resources.�Could not create the pull run log file. Check the Analytic event log to investigate why the file could not be created at this path.+The moduleManager parameter cannot be null.!MI_Application_Initialize failed.)The moduleManager parameter is not valid.)The moduleManager parameter is not valid.QThe moduleManager, className, and registrationInstance parameters cannot be null.HRegistration instance not found. Class is not a DSC configuration class.5The class is not registered as a configuration class.IThe moduleManager, inInstance, and outInstance parameters cannot be null.GetFilteredResource failed.aCould not create a new object to store the operation options while initializing the deserializer.QSetting the Operation option while initializing the deserializer did not succeed.FindFirstFile Failed.FindNextFile Failed./The parameter for GetSystemSchema is not valid.1The parameter for GetSchemaFromMOFs is not valid.BNot all instances within the instance document contain ResourceId.LThe instance document contains multiple OMI_ConfigurationDocument instances.NInstance document must contain exactly one OMI_ConfigurationDocument instance.7ClassName property not found for registration instance.AThe miApp, inInstance, and outInstance parameters cannot be null.MI_Instance_GetElement failed.-An unexpected infrastructure class was found.5Found multiple classes registered with the same name.mThe mandatory ClassName property was not found in the registration. Use a registered classname and try again..Found a registration instance without a class.�A schema was found that does not contain registration. Check the Registration and Schema directories to find the registered schemas.#The class reference does not exist.$Class should not contain any method.!ClassVersion Qualifier not found.7A property or array of type reference is not supported.YCannot have the Read property with any of the following qualifiers: Write, Key, Required.PAoAt least one key property must be defined in the instance document. Update the instance document and try again.BYou must specify at least one configuration resource per MOF file.;All classes must have a reference to ConfigurationResource.>There must be exactly one configuration resource per MOF file.ICould not find mandatory property %1!s!. Add this property and try again. MI_Instance_GetClassName failed.qInstance should be of type MSFT_CimConfigurationProviderRegistration or MSFT_PSConfigurationProviderRegistration.'Mandatory property ClassName not found.4Mandatory property DSCEngineCompatVersion not found..Mandatory property DscModuleVersion not found.'Mandatory property Namespace not found.(Mandatory property ModuleName not found.Mandatory property not found.'Mandatory property type does not match.!MGet class property count failed.<The number of properties does not match the expected number.PA,Mandatory property qualifer type is missing.eMSFT_PSConfigurationProviderRegistration must derive from MSFT_BaseConfigurationProviderRegistration.PThe registration instance does not contain a namespace. A namespace is required.,GetTargetResource requires three parameters.-TestTargetResource doesn't have 4 parameters.,SetTargetResource doesn't have 3 parameters.rValidateDSCProviderMappingForWMIV2Provider did not succeed. One of the following was not found: Get, Test, or Set.fMSFT_CimConfigurationProviderRegistration must derive from MSFT_BaseConfigurationProviderRegistration.+GetEnvironmentVariable for %windir% failed.�The version number of the instance document is not any of the supported versions. Please change the version number in the OMI_Configuration document instance to either 1.0.0 or 2.0.0XFound more than one instance with the same ResourceId %1!s!. Correct that and try again.�The current document contains Local Configuration Manager settings, which is not supported. Send Local Configuration Manager settings seperately.�Local Configuration Manager settings were not found, or the current document contains other configurations. Correct that and try again.Starting reboot processing.iA pending configuration exists after reboot. DSC will process a set request on the pending configuration.<Checking consistency for current configuration after reboot.PAReboot processing completed.�LCM "%4!s!" does not recognize the property "%1!s!" with document "%2!s!" "%3!s!". Please recompile your configuration document, and then try again.�There is no document instance inside the metaconfiguration. Please create the configuration with an instance of OMI_ConfigurationDocument and try again.�DSC Local Configuration Manager only supports one instance of a configuration repository in version 2.0.0 of the metaconfiguration document when there are no partial configurations. Since there are multiple configuration repositories defined, LCM will use only the first repository for existing pull scenarios and will ignore the rest. To remove this warning, either use a single configuration repository, or use partial configurations to point to the configuration repositories.�The only allowed download manager names are DSCFileDownloadManager and WebDownloadManager. However the metaconfiguration contains %1!s! as the download manager name. Correct that and try again.�The property AllowUnsecureConnection can only take values of either true or false. Correct this in the metaconfiguration and try again.�A reboot is scheduled to progress further. Configuration will not be continued after the reboot. To continue configuration, use Start-DscConfiguration -UseExisting after reboot.�A reboot is required to progress further. Please reboot the system. Configuration will not be continued after the reboot. To continue configuration, use Start-DscConfiguration -UseExisting after reboot.eAn internal error occurred : Mandatory property ProviderPath for DSC provider registration not found.cAn internal error occurred : Mandatory property ModulePath for DSC provider registration not found.�The resource %1!s! from module %2!s! is imported twice using version %3!s! and version %4!s!. Using more than one version of a resource is not supported. Remove one of the versions to correct the problem.ZThe current refresh mode is PULL but there are no configuration download managers defined.dDependency cannot be resolved with null instance parameters. Verify that the instances are not null.�A circular dependency was found in the resources specified in the instance document. Check and correct the Requires property of instance %1!s!, then try again.Index is out of bounds.0MI_Instance_GetElement failed to get ResourceId.�ResourceId %1!s! could not be found in any of the resources specified in the instance document. The ResourceId specified in the Requires property may be incorrect. Correct the instance %2!s!, then try again.+Index out of range for dependency resolver.OutInstances cannot be null.!MI_Application_NewSession failed.Unknown registration type.FMI_Instance_GetElement failed to get Namespace for WMIv2 DSC resource."MI_Application_NewInstance failed.PAHMI_Instance_AddElement returned an error on the inputResource parameter. MI_Operation_GetInstance failed..MI_Instance_GetElement failed for ReturnValue.AMI_Instance_GetElement returned an error on the Result parameter.CMI_Instance_GetElement failed for ProviderContext method parameter.UMI_Instance_GetElement did not succeed for the Method parameter of the configuration.MI_Instance_Clone failed."Could not process the get request.CMI_Instance_GetElement failed to get Message from MSFT_LogResource.Test did not succeed.�A circular dependency was found in the resources specified in instance document. Check and correct the Requires property of instance %1!s! defined in %2!s!, then try again.�ResourceId %1!s! could not be found in any of the resources specified in the instance document. The ResourceId specified in the Requires property may be incorrect. Correct the instance %2!s! defined in %3!s!", then try again.&%1!s! The related ResourceID is %2!s!. in %1!s! seconds. in %1!s! seconds. in %1!s! seconds.8The local machine certificate store could not be opened.GThe certificate cannot be found in the local machine certificate store.:Could not acquire a handle to the key context for the CSP.%The public key could not be acquired.&The private key could not be acquired.5Memory could not be allocated for the encrypted data.Encryption did not succeed.1Could not allocate memory for the decrypted data.Decryption failed.6Updating the password element after decription failed.~Could not retrieve the current Local Configuration Manager settings. Apply Local Configuration Manager settings and try again.(The current configuration was cancelled.&Could not wait for the stopping event.'Could not cancel the current operation.PA, ,Could not initialize a new operation option.7MI_OperationOptions_SetCustomOptions returned an error.6The Confirm parameter is not supported in this cmdlet.[Credential objects are only supported up to 4 levels of nesting from the schema class root.�The resources ('%1!s!' and '%2!s!') have conflicting values of the following properties: '%3!s!'. Ensure that their values match.5Circular dependency exists in configuration instance.�The Local Configuration Manager is not configured with a certificate. Resource '%1!s!' in configuration '%2!s!' cannot be processed.(The Certificate ID is not valid: '%1!s!'%2!s! in %1!s! seconds.PA)[%1!s!]: LCM:  [ %2!-16s!]  [%3!s!] %4!s!)[%1!s!]:         %2!-16s!   [%3!s!] %4!s!StartEnd*FAILED*TestGetPASetResourceRollback Skip)[%1!s!]: LCM:  [ %2!-16s!]   %3!s!  %4!s!CompareRemove	GetStatusStopTrueFalseCA reboot is required to progress further. Please reboot the system.{The specified RefreshFrequencyMins was over-written to %1!s! since it was outside the range of acceptable values (30-44640)�The specified ConfigurationModeFrequencyMins was over-written to %1!s! since it was outside the range of acceptable values (15-44640)PA�Falling back to the previous MOF file or system defaults because the meta configuration mof does not exist or has either been corrupted or an invalid mof property has been set.=GetLcmUpdate ran successfully, but did not return any status.BCould not install module dependencies needed by the configuration.[Force operation is terminated due to other incoming force configuration or stop operations.=Could not delete the existing compare configuration MOF file.rCould not save the compare configuration MOF file. Check the properties of the destination location and try again.DCompleted processing compare operation. The operation returned True.ECompleted processing compare operation. The operation returned False.:Could not rename BuiltInProvCache to BuiltInProvCache.Old.3GetResourceState is called with invalid parameters.=Could not publish the partial configuration in location %1!s!;The only way DSC Partial Configurations can be used in Push mode is if the Publish-DscConfiguration Cmdlet is used. No other push cmdlet is supported. To avoid this error, either set a metaconfiguration without partial configurations, or use the Publish-DscConfiguration cmdlet to deploy your partial configuration.�Name property of the OMI_ConfigurationDocument instance has not been set. To use partial configurations, this property must be set in the configurationAThere was an error while merging the partial configuration files.3There was an error while serializing the instance. 5There was an error while writing into the file %1!s!.At least one of the resources present in the configuration document contains configuration name that is not equivalent to the partial configuration name %1!s!. Correct that and try again. All resources present in a partial configuration document must contain the same configuration name.�The partial configuration name %1!s! present in the configuration document is invalid. Define a partial configuration inside the metaconfiguration with this partial configuration name in order to use it.�There is no partial configuration defined inside the metaconfiguration document. Create partial configuration instances and try again.rThe configuration provided contains an invalid resource instance of class name %1!s! because it doesn't have a field with the name ConfigurationName inside it. In order to use this configuration as a partial configuration, the configuration name field is mandatory inside each resource and it's name should match the name field of the OMI_ConfigurationDocument instance.* Merging of partial configurations failed.�The WMIv2 DSC resource %1!s! threw one or more non-terminating errors while running the %2!s! functionality. These errors are logged to the ETW channel Microsoft-Windows-DSC/Operational. Refer to this channel for more details.�Found a conflict in definition of exclusive resource %1!s!. The field Exclusive resource can have values of resource names that cannot be reused by any other partial configuration. Correct this duplicate occurence and try again.GThe download manager %1!s! mentioned in the partial configuration is undefined in the meta configuration or assigned incorrectly. Check the download manager and assign ResourceRepositoryWeb or ResourceRepositoryShare to ResourceModuleSource and ConfigurationRepositoryWeb or ConfigurationRepositoryShare to ConfigurationSource.�The partial configuration %1!s! cannot use %2!s! resource, which is exclusively reserved by another partial configuration. Either correct the metaconfiguration to remove this, or do not use this exclusive resource in this partial configuration.BSaved configuration document into the partial configuration store.�The partial configuration %1!s! depends on another partial configuration that does not exist. This partial configuration will not be set until it finds the partial configuration that it depends on._An error occured while applying the partial configuration %1!s!. The error message is : 
%2!s!.None of the partial configurations defined in the metaconfiguration was found in the store. Either these configurations have not been pulled from the server (in the case of pull refresh mode) , or they have not been published to the store (in the case of push refresh mode). WOne or more partial configurations failed to apply. No configuration could be created. NThe resource instance is not formed correctly. Error in finding the classname.�The module name property inside the resource %1!s! is undefined. Please regenerate the mof using a corresponding powershell file or add the module name property inside the instance of the resource.�The exclusive resource string %1!s! for the partial configuration %2!s! is not written in any of the allowed formats. Exclusive resources can be written as ModuleName\ResourceName , or ModuleName\* or ResourceName DDeleting the invalid partial configuration file %1!s!. Reason: %2!s!CThe partial configuration file %1!s! will be skipped. Reason: %2!s!The partial configuration directory is absent at the location $env:windir/system32/configuration/partialconfigurations. LCM failed to recreate this directory. Suspend all DSC operations or recreate this directory to allow partial configurations feature to work. The configuration status directory is absent at the location $env:windir/system32/configuration/configurationstatus. LCM failed to recreate this directory. Suspend all DSC operations or recreate this directory to allow configuration status feature to work. BLCM failed to record the configuration status for operation: %1!s!?LCM failed to retrieve the configuration status for file: %1!s!:The request cannot continue until the machine is rebooted.�To manually receive the remaining output, execute: Connect-DscConfiguration -InstanceId '%1!s!' -Bookmark '%2!s!' -ComputerName %3!s! -Verbose -Wait�An error occured while deleting the old partial configuration with the same name. Run Stop-DSCConfiguration with the -Force option to stop executing any pending DSC operations and try again. �There was an error while saving the partial configuration file into the pending store. Run Stop-DSCConfiguration with the -Force option to stop executing any pending DSC operations and try again. -Could not initialize the Meta Configuration. NCould not construct the output object for the GetConfigurationStatus function.9Could not set return for GetConfigurationStatus function.PA:Posting output for GetConfigurationStatus did not succeed.BSetting the thread priority for consistency check did not succeed.�Updated configuration not found on pull server so no action taken. Ensure that a configuration with a different checksum exists on the pull server for target node.qNo attempt was made to get a configuration from the pull server because LCM RefreshMode is currently set to Push.�Applying the configuration after reboot is stopped because the meta configuration mof setting ActionAfterReboot is set to StopConfiguration.WConfiguration and refresh intervals could not be initialized. Using the default values.U%1!s! cmdlet is not supported in %2!s! mode. Please set the LCM RefreshMode to %3!s!.wThe GET operation will be carried against a pending configuration since the latest configuration has not converged yet.xThe TEST operation will be carried against a pending configuration since the latest configuration has not converged yet.;Configuration document is being published to pending state.�LCM state is changed by non-DSC operations. If you wish to change the state of LCM, please use Remove-DscConfigurationDocument cmdlet.Failed to encrypt file '%1!s!'Failed to decrypt file '%1!s!'HLCM is running in MonitorOnly mode and will only test the configuration.GAn error was encountered while deleting the current configuration file.GAn error was encountered while deleting the pending configuration file.HAn error was encountered while deleting the previous configuration file.sThe -Force option was specified with the Stop operation. The current configuration has been successfully cancelled.*Configuration document Current was removed*Configuration document Pending was removed+Configuration document Previous was removedQThe Local Configuration Manager did not find any current configuration to remove.QThe Local Configuration Manager did not find any pending configuration to remove.RThe Local Configuration Manager did not find any previous configuration to remove.MThere is no operation running currently. Stop will return without any action.+The configuration was successfully stopped.Stop-DscConfiguration is attempting to stop the current configuration after the current resource completes execution. The configuration will be cancelled once the console returns. To stop it immediately, use the -Force option with Stop-DscConfiguration cmdlet.DAn error was encountered while deleting partial configuration files.,Partial configuration documents were removedRThe Local Configuration Manager did not find any partial configurations to remove.HAn error was encountered while deleting the configuration checksum file.'Configuration checksum file was removedSThe Local Configuration Manager did not find configuration checksum file to remove.;The previous configuration will be restored on target node.,The Enable-DscDebug need BreakAll parameter.KAn error was encountered while deleting the configuration state cache file.&Configuration state cache was removed.UThe Local Configuration Manager did not find any configuration state cache to remove.PA�The configuration document with version %1!s! cannot be processed by LCM version %2!s! because the MinimumCompatibleVersion value is %3!s!. For the document to be compatible with this LCM, the property minimumCompatibleVersion should be set to %2!s! in the OMI_ConfigurationDocument instance. Regenerate the configuration document to update the MinimumCompatibleVersion property, or upgrade the version of DSC that is running on this computer.�The configuration document with version %1!s! cannot be processed by LCM version %2!s! because the MinimumCompatibleVersion property is undefined. For the document to be compatible with this LCM, the property minimumCompatibleVersion should be set to %2!s! in the OMI_ConfigurationDocument instance. Regenerate the configuration document to include the MinimumCompatibleVersion property, or upgrade the version of DSC that is running on this computer.�LCM cannot process the CompatibleVersionAdditionalProperties value in the OMI_ConfigurationDocument instance. Regenerate the configuration document, and then try again.MThe property CompatibleVersionAdditionalProperties in the OMI_ConfigurationDocument instance can only accept values of the type String Array. Because the configuration document contains an invalid value for this property, LCM cannot process the OMI_ConfigurationDocument instance. Regenerate the configuration document and try again.PA"LCM is publishing a configuration.$LCM is applying a new configuration.,LCM is a applying an existing configuration.*LCM is restoring a previous configuration..LCM is testing node against the configuration.LCM is getting a configuration.&LCM is performing a consistency check.;LCM is continuing applying configuration after last reboot.HLCM is checking and applying new available configuration on pull server.1LCM is applying a new meta configuration setting..LCM is retriving configuration status history.LCM is removing configurations./LCM is enabling DSC resource scripts debugging.0LCM is disabling DSC resource scripts debugging.%LCM is executing DSC resource method.FPowerShell Desired State Configuration failed to register MOF classes.@Executing Get-Action with configuration %1!s!'s checksum: %2!s!.WExecuting Get-Action with configuration %1!s!'s checksum returned result status: %2!s!.UChecksum is different. LCM will execute GetConfiguration to pull configuration %1!s!.QExecuting GetConfiguration succeeded. Configuration %1!s! was pulled from server.EExecuting GetConfiguration failed. Configuration %1!s! is not pulled.)Applying the new configuration(s) pulled.PAnExecuting Get-Action with configuration %1!s!'s checksum failed. Please check the availability of pull server.nPull Configuration(s) from the pull server if checksum do not match and apply configuration(s) on target node./Registering Dsc Agent didn't return any status.9Registering Dsc Agent did not return the expected status.9Unable to generate AgentId for Registration of Dsc Agent.|The properties ConfigurationNames and ConfigurationID cannot be specified together. Please remove one of them and try again.OA ServerUrl is required in the metaconfiguration for Registration of Dsc Agent.CRegistration of the Dsc Agent with the server %1!s! was successful.\Registration of the Dsc Agent with the server %1!s! failed. The underlying error is: %2!s! .�Executing Get-Action on partial configuration '%1!s!' Failed. Please ensure the parital configuration and its checksum exist on the server. Check the DSC event logs for further details.x4VS_VERSION_INFO��
!|O
!|O?�StringFileInfo�040904B0LCompanyNameMicrosoft Corporation0FileDescriptionDSCn'FileVersion10.0.20348.2849 (WinBuild.160101.0800)8InternalNameDscCore.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.HOriginalFilenameDscCore.dll.muij%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.20348.2849DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDING