| File name: | DscCore.dll.mui |
| Size: | 49152 byte |
| MD5: | 413a501392518da26f688d657c73fe94 |
| SHA1: | 2c435ec980f3e3c845c108b6f728f6049a3f5e26 |
| SHA256: | 8b134b0229a773a6238f314dae1a86d648a7c7eb662d05439bd314dd6b17aa6c |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Chinese (Simplified) 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 | Chinese (Simplified) | English |
|---|---|---|
| 19 | 所有本机配置提供程序的基础架构。 | Base schema for all native configuration providers. |
| 30 | 回退到以前的配置。 | Rollback to previous configuration. |
| 265 | 这表示键值对。 | This represents a key-value pair. |
| 281 | 开始进行一致性检查。 | Starts the consistency check. |
| 308 | 将配置文档发送到托管节点并另存为挂起。 | Send the configuration document to the managed node and save it as pending. |
| 309 | 将配置文档发送到托管节点并使用配置代理来应用配置。 | Send the configuration document to the managed node and use Configuration Agent to apply the configuration. |
| 312 | 将配置文档发送到托管节点并使用配置代理通过 Get 方法来应用配置。 | Send the configuration document to the managed node and use Configuration Agent to apply the configuration using the Get method. |
| 314 | 将配置文档发送到托管节点并根据当前配置对其进行测试。 | Send the configuration document to the managed node and test it against the current configuration. |
| 317 | 设置用于控制配置代理的本地配置管理器设置。 | Set Local Configuration Manager settings that are used to control Configuration Agent. |
| 318 | 获取用于控制配置代理的本地配置管理器设置。 | Get Local Configuration Manager settings that are used to control Configuration Agent. |
| 319 | 正在停止进行中的配置。 | Stopping the configuration in progress. |
| 320 | 本地配置管理器，用于控制配置文件的状态并使用配置代理来应用配置。 | Local Configuration Manager that controls the states of configuration files and uses Configuration Agent to apply the configurations. |
| 341 | 用于重新应用配置以达到所需状态的连续运行之间的时间间隔。 | The time interval between consecutive runs for reapplying the configuration to get to the desired state. |
| 344 | 用于查找证书的证书 ID。 | The certificate ID used to locate the certificate. |
| 346 | 用于从“拉”服务器获取配置的配置 ID。 | The configuration ID used to get the configuration from the pull server. |
| 347 | 配置和模块下载管理器的名称。 | Name of the configuration and module Download Manager. |
| 348 | 特定于下载管理器的自定义数据。 | Custom data that is specific to Download Manager. |
| 349 | 用于从服务器获取操作的连续运行之间的时间间隔。 | The time interval between consecutive runs to get the action from the server. |
| 350 | 本地配置管理器设置。 | Local Configuration Manager settings. |
| 351 | UserName 是授权服务映射到某个标识的用户名。 | UserName is the name of the user that an authorization service maps to an identity. |
| 352 | UserPassword 属性可能包含用于访问资源的密码。 | The UserPassword property may contain a password used to access resources. |
| 353 | 要用于 DSC 配置提供程序的凭据。 | Credential to use for DSC configuration providers. |
| 354 | 用于访问资源的默认凭据。 | Default credential to access resources. |
| 355 | 重新启动节点(如果需要)。 | Reboot node if needed. |
| 356 | 服务器的配置应用模式。 | The configuration apply mode for the server. |
| 358 | ApplyOnly | ApplyOnly |
| 359 | ApplyAndMonitor | ApplyAndMonitor |
| 360 | ApplyAndAutoCorrect | ApplyAndAutoCorrect |
| 366 | 服务器的刷新模式。有效值为“拉”和“推”和“已禁用”。 | The refresh mode for the server. Valid values are Pull, Push and Disabled. |
| 389 | 从“拉”服务器下载时覆盖模块。 | Overwrite modules when downloading from Pull Server. |
| 411 | 推 | Push |
| 412 | 拉 | Pull |
| 413 | 已禁用 | Disabled |
| 422 | 忙碌 | Busy |
| 423 | 本地配置管理器的当前状态。 | Current state of local configuration manager. |
| 425 | PendingReboot | PendingReboot |
| 430 | 使用配置代理来应用配置。 | Use Configuration Agent to apply the configuration. |
| 450 | 客户端的唯一标识符。 | An unique identifier of client. |
| 458 | 当前本地配置管理器的兼容版本。 | Compatible versions of current local configuration manager. |
| 459 | 本地配置管理器的当前版本。 | Current version of local configuration manager. |
| 462 | 下载管理器位置的字符串 URL | String URL of the download manager location |
| 468 | 从 OMI_ReportManager 类继承的 Web 报告管理器类 | Web report manager class inheriting from OMI_ReportManager class |
| 471 | 定义配置下载管理器的类 | Class defining the configuration download manager |
| 473 | 定义资源模块管理器结构的类 | Class defining the structure of resource module managers |
| 475 | 定义报告管理器的类 | Class defining a report manager |
| 476 | 从 OMI_ConfigurationDownloadManager 继承的 Web 下载管理器类 | Web download manager class inheriting from OMI_ConfigurationDownloadManager |
| 478 | 从 OMI_ConfigurationDownloadManager 继承的文件配置下载管理器类 | File configuration download manager class inheriting from OMI_ConfigurationDownloadManager |
| 479 | 资源模块管理器位置的字符串 URL | String URL of the resource module manager location |
| 480 | 从 OMI_ResourceModuleManager 继承的 Web 资源模块管理器类 | Web resource module manager class inheriting from OMI_ResourceModuleManager |
| 481 | 文件资源管理器的字符串 UNC 路径 | String UNC path of the File resource manager |
| 482 | 从 OMI_ResourceModuleManager 类继承的文件资源模块管理器类 | File resource module manager class inheriting from OMI_ResourceModuleManager class |
| 492 | 用于下载配置的、包含位置信息的配置下载管理器对象的数组 | Array of configuration download manager objects that contain location information to download configurations |
| 493 | 用于下载所缺少 DSCResources 的、指向某个位置的资源模块管理器的数组 | Array of resource module managers pointing to a location to download missing DSCResources |
| 495 | 用于保存资源对象属性的类。 | Class for holding properties of a resource object. |
| 496 | 帮助生成 DSC 报告的、指向某个位置的报告管理器的数组 | Array of report managers pointing to a location that would help generate reports for DSC |
| 506 | 用于访问文件位置的默认凭据 | Default credential to access the file location |
| 509 | 用于允许建立不安全连接的布尔变量 | Boolean variable to allow unsecure connections |
| 510 | 下载管理器位置的字符串 UNC 源路径 | String UNC source path of the download manager location |
| 515 | 用于显示资源是否处于所需状态的字段。 | Field to display whether the resource is in desired state. |
| 517 | 部分配置的说明 | Description of the partial configuration |
| 518 | 定义此特定部分配置独占的资源 | Defines the resources that are exclusive to this particular partial configuration |
| 519 | 此部分配置将要使用的配置存储库源 | The configuration repository source that this partial configuration will use |
| 521 | 一个依赖关系变量，用于指示必须在此项之前应用哪个部分配置 | A dependency variable indicating which partial configuration must be applied prior to this |
| 522 | 这表示一个部分配置类。 | This represents a Partial Configuration class. |
| 523 | 指定要应用的部分配置的数组 | Array of partial configurations that are specified to be applied |
| 525 | 报告管理器使用的服务器的 URL。 | URL of the server used by report manager. |
| 526 | 用于查找建立安全连接所用的证书的证书 ID。 | The certificate ID used to locate the certificate for secure connections. |
| 527 | 指定报告管理器是否可以通过 HTTP 使用不安全的连接。 | Specifies whether report manager can use unsecure connection over http. |
| 533 | 资源实例的唯一 ID。 | Unique Id for a resource instance. |
| 534 | 用于将其关联回 powershell 配置脚本的源信息。 | Source Info to correlate it back to powershell configuration script. |
| 535 | 此资源所依赖的资源的列表。 | List of resources this resource depends on. |
| 536 | 支持此资源的模块的名称。 | Name of the module that supports this resource. |
| 537 | 支持此资源的模块的版本。 | Version of the module that supports this resource. |
| 538 | 所属的配置的名称 | Name of the configuration this is a part of |
| 539 | 所有 Metaconfiguration 资源的基础架构。 | Base schema for all Metaconfiguration resources. |
| 540 | 用于保存处于所需状态的资源对象的属性的类。 | Class for holding properties of a resource object in desired state. |
| 542 | 用于保存不处于所需状态的资源对象的属性的类。 | Class for holding properties of a resource object not in desired state. |
| 543 | 启动资源的日期和时间。 | Date and time when the resource was started. |
| 544 | 处理整个配置花费的时间。 | Time taken to process entire configuration. |
| 545 | 针对资源请求了重新启动。 | Reboot was requested for resource. |
| 546 | 资源在被代理之前的初始属性值。 | Initial property values of the resource before it is enacted. |
| 547 | 资源在被代理之后的最终属性值。 | Final property values of the resource after it is enacted. |
| 548 | 配置的状态。 | Status of configuration. |
| 549 | 成功 | Success |
| 550 | 失败 | Failure |
| 551 | 已中止 | Aborted |
| 552 | InProgress | InProgress |
| 554 | 启动配置的日期和时间。 | Date and time when the configuration was started. |
| 555 | 在配置期间请求了重新启动。 | Reboot was requested during configuration. |
| 556 | 配置的类型。 | Type of Configuration. |
| 557 | 初始 | Initial |
| 558 | 一致性 | Consistency |
| 559 | 重新启动 | Reboot |
| 560 | ReadOnly | ReadOnly |
| 561 | 与配置关联的作业 ID。 | Job ID associated with configuration. |
| 562 | 配置的元数据。 | Meta data of configuration. |
| 563 | 配置中的资源总数。 | Total number of resources in configuration. |
| 564 | 配置的模式。 | Mode of configuration. |
| 565 | 配置时的 LCM 版本。 | Version of LCM at time of configuration. |
| 566 | 配置时节点的 NetBIOS 名称。 | NetBIOS name of node at time of configuration. |
| 567 | 配置时节点的 IP 地址。 | IP Address of node at time of configuration. |
| 568 | 配置时节点的 MAC 地址。 | MAC address of node at time of configuration. |
| 569 | 配置时的元配置信息。 | Meta-Configuration information at time of configuration. |
| 570 | 已在配置中成功配置资源。 | Resources successfully configured in the configuration. |
| 571 | 配置中的资源失败。 | Resources failed in the configuration. |
| 572 | 用于保存配置状态对象属性的类。 | Class for holding propertis of configuration status object. |
| 573 | 获取配置状态历史记录。 | Get the configuration status history. |
| 574 | 类似于 File 的资源名称。 | The resource name like File. |
| 575 | 类似于 file1 的实例名称。 | The instance name like file1. |
| 577 | 从 GetConfigurationResultOutput 方法得到的流式处理输出。 | Resulting streamed output from GetConfigurationResultOutput method. |
| 578 | 将配置文档发送到托管节点并开始使用配置代理来应用配置。使用 GetConfigurationResultOutput 检索结果输出。 | Send the configuration document to the managed node and start using the Configuration Agent to apply the configuration. Use GetConfigurationResultOutput to retrieve result output. |
| 579 | 检索与特定作业相关的配置代理输出。 | Retrieve the Configuration Agent output relating to a specific job. |
| 580 | 处理资源花费的时间。 | Time taken to process resource. |
| 595 | 运行配置的节点的区域设置。 | Locale of the node running the configuration. |
| 596 | 配置状态历史记录的保留天数。 | Number of days to retain configuration status history. |
| 597 | 提供程序返回的错误。 | Error returned by the provider. |
| 598 | 配置期间本地配置管理器中遇到错误。 | Error encountered in local configuration manager during configuration. |
| 599 | 正在删除配置文件。 | Removing the configuration files. |
| 607 | 有关 DSC 的传入请求的消息。 | Message for incoming requests to DSC. |
| 609 | DebugMode 的枚举。 | The enumeration for DebugMode. |
| 610 | 无 | None |
| 611 | ForceModuleImport | ForceModuleImport |
| 612 | 全部 | All |
| 613 | 直接对提供程序执行 Get 操作 | Execute Get on a provider directly |
| 614 | 直接对提供程序执行 Set 操作 | Execute Set on a provider directly |
| 615 | 直接对提供程序执行 Test 操作 | Execute Test on a provider directly |
| 619 | 重新启动服务器后的操作。 | The action after reboot the server. |
| 620 | ContinueConfiguration | ContinueConfiguration |
| 621 | StopConfiguration | StopConfiguration |
| 622 | 错误的主要分类。定义了以下值: 2 - 通信错误。此类错误主要与在两点之间传输信息所需要的过程和/或进程有关。 3 - 服务质量错误。此类错误主要与导致功能或性能下降的故障有关。 4 - 软件错误。此类错误主要与软件或处理故障有关。 5 - 硬件错误。此类错误主要与设备或硬件故障有关。 6 - 环境错误。此类错误主要与以下内容有关: 与设备或其他环境考虑事项相关的故障条件。 7 - 安全错误。此类错误与违反安全规则、检测到病毒，以及类似的问题有关。 8 -“过度订阅”错误。此类错误主要与分配充足的资源以完成操作时发生的故障有关。 9 -“资源不可用”错误。此类错误主要与访问所需资源时发生的故障有关。 10 -不受支持的操作错误。此类错误主要与不受支持的请求有关。 |
Primary 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. |
| 623 | 未知 | Unknown |
| 624 | 其他 | Other |
| 625 | 通信错误 | Communications Error |
| 626 | 服务质量错误 | Quality of Service Error |
| 627 | 软件错误 | Software Error |
| 628 | 硬件错误 | Hardware Error |
| 629 | 环境错误 | Environmental Error |
| 630 | 安全错误 | Security Error |
| 631 | “过度订阅”错误 | Oversubscription Error |
| 632 | “资源不可用”错误 | Unavailable Resource Error |
| 633 | 不受支持的操作错误 | Unsupported Operation Error |
| 634 | DMTF 保留 | DMTF Reserved |
| 635 | 自由格式的字符串，用于在将 1 (“其他”)指定为错误类型时描述该错误类型。 | A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType. |
| 636 | 唯一标识实体(拥有该实例中所述消息格式的定义)的字符串。OwningEntity 必须包含由定义该格式的商业实体或标准机构所拥有的版权化、商标化或其他形式的唯一名称。 | 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. |
| 637 | 在 OwningEntity 的作用域中唯一标识消息格式的不透明字符串。 | An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message. |
| 638 | 已设置格式的消息。此消息通过组合 MessageArguments 属性中指定的某些或所有动态元素构造而成，其中，静态元素由消息注册表中的 MessageID 或与 OwningEntity 关联的其他目录唯一标识。 | 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. |
| 639 | 包含此消息的动态内容的数组。 | An array containing the dynamic content of the message. |
| 640 | 一个枚举值，该值从通知程序的视角描述“指示”的严重性: 0 - 指示的“感知严重性”未知或不确定。 1 - 按 CIM 惯例，“其他”用于指示可以在 OtherSeverity 属性中找到的严重性值。 2 - 当提供信息性响应时，应该使用“信息”。 3 - 当适合让用户决定是否需要采取措施时，应该使用“降级/警告”。 4 - 应该使用“次要”来指示需要采取相应措施，但此时情况不严重。 5 - 应该使用“主要”来指示需要立即采取相应措施。 6 - 应该使用“严重”来指示需要立即采取相应措施，而且影响范围广泛(可能会很快导致关键资源无法提供)。 7 - 应该使用“致命/无法恢复”来指示发生了错误，但为时已晚，无法采取补救措施。 2 和 0 - 对于“信息”和“未知”，应当(分别)遵循其常见用法。确切地说，这些错误是纯信息性错误或者其严重性未知。 |
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. |
| 641 | 信息 | Information |
| 642 | 已降级/警告 | Degraded/Warning |
| 643 | 次要 | Minor |
| 644 | 主要 | Major |
| 645 | 严重 | Critical |
| 646 | 致命/无法恢复 | Fatal/NonRecoverable |
| 647 | 用于描述引发错误的可能原因的枚举值。 | An enumerated value that describes the probable cause of the error. |
| 648 | 适配器/卡错误 | Adapter/Card Error |
| 649 | 应用程序子系统故障 | Application Subsystem Failure |
| 650 | 带宽减少 | Bandwidth Reduced |
| 651 | 连接建立错误 | Connection Establishment Error |
| 652 | 通信协议错误 | Communications Protocol Error |
| 653 | 通信子系统故障 | Communications Subsystem Failure |
| 654 | 配置/自定义错误 | Configuration/Customization Error |
| 655 | 拥塞 | Congestion |
| 656 | 数据已损坏 | Corrupt Data |
| 657 | 超出 CPU 周期限制 | CPU Cycles Limit Exceeded |
| 658 | 数据集/调制解调器错误 | Dataset/Modem Error |
| 659 | 信号降级 | Degraded Signal |
| 660 | DTE-DCE 接口错误 | DTE-DCE Interface Error |
| 661 | 封闭门打开 | Enclosure Door Open |
| 662 | 设备故障 | Equipment Malfunction |
| 663 | 振动过度 | Excessive Vibration |
| 664 | 文件格式错误 | File Format Error |
| 665 | 检测到火灾 | Fire Detected |
| 666 | 检测到洪水 | Flood Detected |
| 667 | 帧错误 | Framing Error |
| 668 | HVAC 问题 | HVAC Problem |
| 669 | 湿度无法接受 | Humidity Unacceptable |
| 670 | I/O 设备错误 | I/O Device Error |
| 671 | 输入设备错误 | Input Device Error |
| 672 | LAN 错误 | LAN Error |
| 673 | 检测到无毒物质泄露 | Non-Toxic Leak Detected |
| 674 | 本地节点传输错误 | Local Node Transmission Error |
| 675 | 帧丢失 | Loss of Frame |
| 676 | 信号缺失 | Loss of Signal |
| 677 | 材料供应耗竭 | Material Supply Exhausted |
| 678 | 多路复用器问题 | Multiplexer Problem |
| 679 | 内存不足 | Out of Memory |
| 680 | 输出设备错误 | Output Device Error |
| 681 | 性能降低 | Performance Degraded |
| 682 | 电源问题 | Power Problem |
| 683 | 压力不可接受 | Pressure Unacceptable |
| 684 | 处理器问题(内部计算机错误) | Processor Problem (Internal Machine Error) |
| 685 | 泵故障 | Pump Failure |
| 686 | 超出队列大小 | Queue Size Exceeded |
| 687 | 接收故障 | Receive Failure |
| 688 | 接收器故障 | Receiver Failure |
| 689 | 远程节点传输错误 | Remote Node Transmission Error |
| 690 | 资源达到或接近容量 | Resource at or Nearing Capacity |
| 691 | 响应时间过长 | Response Time Excessive |
| 692 | 重新传输率过高 | Retransmission Rate Excessive |
| 693 | 软件程序异常终止 | Software Program Abnormally Terminated |
| 694 | 软件程序错误(结果不正确) | Software Program Error (Incorrect Results) |
| 695 | 存储容量问题 | Storage Capacity Problem |
| 696 | 温度不可接受 | Temperature Unacceptable |
| 697 | 已超过阈值 | Threshold Crossed |
| 698 | 计时问题 | Timing Problem |
| 699 | 检测到有毒物质泄露 | Toxic Leak Detected |
| 700 | 传输故障 | Transmit Failure |
| 701 | 发送器故障 | Transmitter Failure |
| 702 | 基础资源无法使用 | Underlying Resource Unavailable |
| 703 | 版本不匹配 | Version Mismatch |
| 704 | 之前的警报已清除 | Previous Alert Cleared |
| 705 | 登录尝试失败 | Login Attempts Failed |
| 706 | 检测到软件病毒 | Software Virus Detected |
| 707 | 违反硬件安全 | Hardware Security Breached |
| 708 | 检测到拒绝服务 | Denial of Service Detected |
| 709 | 安全凭据不匹配 | Security Credential Mismatch |
| 710 | 访问未经授权 | Unauthorized Access |
| 711 | 收到警报 | Alarm Received |
| 712 | 指针缺失 | Loss of Pointer |
| 713 | 负载不匹配 | Payload Mismatch |
| 714 | 传输错误 | Transmission Error |
| 715 | 错误率过高 | Excessive Error Rate |
| 716 | 跟踪问题 | Trace Problem |
| 717 | 元素无法使用 | Element Unavailable |
| 718 | 缺少元素 | Element Missing |
| 719 | 多个帧缺失 | Loss of Multi Frame |
| 720 | 广播通道故障 | Broadcast Channel Failure |
| 721 | 收到的消息无效 | Invalid Message Received |
| 722 | 路由故障 | Routing Failure |
| 723 | 底板故障 | Backplane Failure |
| 724 | 标识符重复 | Identifier Duplication |
| 725 | 保护路径故障 | Protection Path Failure |
| 726 | 失去同步或同步不匹配 | Sync Loss or Mismatch |
| 727 | 终端问题 | Terminal Problem |
| 728 | 实时时钟故障 | Real Time Clock Failure |
| 729 | 天线故障 | Antenna Failure |
| 730 | 电池充电故障 | Battery Charging Failure |
| 731 | 磁盘故障 | Disk Failure |
| 732 | 频率跳转故障 | Frequency Hopping Failure |
| 733 | 冗余缺失 | Loss of Redundancy |
| 734 | 电源故障 | Power Supply Failure |
| 735 | 信号质量问题 | Signal Quality Problem |
| 736 | 电池正在放电 | Battery Discharging |
| 737 | 电池故障 | Battery Failure |
| 738 | 商业用电问题 | Commercial Power Problem |
| 739 | 风扇故障 | Fan Failure |
| 740 | 引擎故障 | Engine Failure |
| 741 | 传感器故障 | Sensor Failure |
| 742 | 保险丝故障 | Fuse Failure |
| 743 | 生成器故障 | Generator Failure |
| 744 | 电池电量不足 | Low Battery |
| 745 | 燃料不足 | Low Fuel |
| 746 | 水不足 | Low Water |
| 747 | 爆炸性气体 | Explosive Gas |
| 748 | 大风 | High Winds |
| 749 | 结冰 | Ice Buildup |
| 750 | 冒烟 | Smoke |
| 751 | 内存不匹配 | Memory Mismatch |
| 752 | 超出 CPU 周期 | Out of CPU Cycles |
| 753 | 软件环境问题 | Software Environment Problem |
| 754 | 软件下载故障 | Software Download Failure |
| 755 | 元素已重新初始化 | Element Reinitialized |
| 756 | 超时 | Timeout |
| 757 | 日志记录问题 | Logging Problems |
| 758 | 检测到泄露 | Leak Detected |
| 759 | 保护机制故障 | Protection Mechanism Failure |
| 760 | 保护资源故障 | Protecting Resource Failure |
| 761 | 数据库不一致 | Database Inconsistency |
| 762 | 身份验证失败 | Authentication Failure |
| 763 | 违反保密性 | Breach of Confidentiality |
| 764 | 电缆篡改 | Cable Tamper |
| 765 | 信息延迟 | Delayed Information |
| 766 | 信息重复 | Duplicate Information |
| 767 | 缺少信息 | Information Missing |
| 768 | 信息被修改 | Information Modification |
| 769 | 信息无序 | Information Out of Sequence |
| 770 | 密钥到期 | Key Expired |
| 771 | 不可否认的故障 | Non-Repudiation Failure |
| 772 | 活动超时 | Out of Hours Activity |
| 773 | 停止服务 | Out of Service |
| 774 | 过程错误 | Procedural Error |
| 775 | 意外信息 | Unexpected Information |
| 776 | 描述引发错误的可能原因的自由格式字符串。 | A free-form string describing the probable cause of the error. |
| 777 | 描述解决错误应采取的建议操作的自由格式字符串。 | A free-form string describing recommended actions to take to resolve the error. |
| 778 | 生成错误的实体(即，实例)的标识信息。如果已在 CIM 架构中为该实体建模，则此属性包含编码为字符串参数的实例路径。如果未建模，则此属性包含某个标识字符串(用于命名生成错误的实体)。路径或标识字符串的格式是根据 ErrorSourceFormat 属性设置的。 | 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. |
| 779 | 可以根据此属性的值来解释 ErrorSource 属性的格式。这些值的定义如下所示: 0 - 未知。格式未知或者无法由 CIM 客户端应用程序提供有意义的解释。 1 - 其他。此格式由 OtherErrorSourceFormat 属性的值定义。2 - CIMObjectPath。根据 CIM 基础结构规范定义的 CIM 对象路径。注意: CIM 2.5 以及更早版本使用术语“对象名称”。 |
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. |
| 780 | CIMObjectPath | CIMObjectPath |
| 781 | 为 ErrorSourceFormat 定义“其他”值的字符串。当 ErrorSourceFormat 设置为值 1 (“其他”)时，此值必须设置为一个非 NULL 值。对于 ErrorSourceFormat 的所有其他值，必须将此字符串的值设置为 NULL。 | 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. |
| 782 | 表示该实例特征的 CIM 状态代码。 此属性定义符合相应特征的 CIM 服务器或侦听器可能返回的状态代码。请注意，并非所有状态代码对于每个操作都有效。每个操作的规范都应该定义该操作可能返回的状态代码。 为 CIM 状态代码定义的值如下: 1 - CIM_ERR_FAILED。发生了更具体错误代码未包括的常规错误。 2 - CIM_ERR_ACCESS_DENIED。客户端无法访问 CIM 资源。 3 - CIM_ERR_INVALID_NAMESPACE。目标命名空间不存在。 4 - CIM_ERR_INVALID_PARAMETER。传递给方法的一个或多个参数值无效。 5 - CIM_ERR_INVALID_CLASS。指定的类不存在。 6 - CIM_ERR_NOT_FOUND。找不到请求的对象。 7 - CIM_ERR_NOT_SUPPORTED。不支持请求的操作。 8 - CIM_ERR_CLASS_HAS_CHILDREN。无法对该类执行操作，因为该类具有实例。 9 - CIM_ERR_CLASS_HAS_INSTANCES。无法对该类执行操作，因为该类具有实例。 10 - CIM_ERR_INVALID_SUPERCLASS。无法执行操作，因为指定的超类不存在。 11 - CIM_ERR_ALREADY_EXISTS。无法执行操作，因为已存在一个对象。 12 - CIM_ERR_NO_SUCH_PROPERTY。指定的属性不存在。 13 - CIM_ERR_TYPE_MISMATCH。提供的值与类型不符。 14 - CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED。无法识别或不支持查询语言。 15 - CIM_ERR_INVALID_QUERY。查询对于指定的查询语言无效。 16 - CIM_ERR_METHOD_NOT_AVAILABLE。无法执行外部方法。 17 - CIM_ERR_METHOD_NOT_FOUND。指定的外部方法不存在。 18 - CIM_ERR_UNEXPECTED_RESPONSE。返回的异步操作响应不是预期响应。 19 - CIM_ERR_INVALID_RESPONSE_DESTINATION。异步响应的指定目标无效。 20 - CIM_ERR_NAMESPACE_NOT_EMPTY。指定的命名空间不为空。 21 - CIM_ERR_INVALID_ENUMERATION_CONTEXT。提供的枚举上下文无效。 22 - CIM_ERR_INVALID_OPERATION_TIMEOUT。指定的命名空间不为空。 23 - CIM_ERR_PULL_HAS_BEEN_ABANDONED。指定的命名空间不为空。 24 - CIM_ERR_PULL_CANNOT_BE_ABANDONED。尝试放弃拉操作失败。 25 - CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED。不支持筛选的枚举。 26 - CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED。不支持发生错误时继续操作。 27 - CIM_ERR_SERVER_LIMITS_EXCEEDED。已超过 WBEM 服务器限制(例如，内存、连接数等)。 28 - CIM_ERR_SERVER_IS_SHUTTING_DOWN。WBEM 服务器正在关闭。 29 - CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED。不支持指定的查询功能。 |
The 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. |
| 783 | CIM_ERR_FAILED | CIM_ERR_FAILED |
| 784 | CIM_ERR_ACCESS_DENIED | CIM_ERR_ACCESS_DENIED |
| 785 | CIM_ERR_INVALID_NAMESPACE | CIM_ERR_INVALID_NAMESPACE |
| 786 | CIM_ERR_INVALID_PARAMETER | CIM_ERR_INVALID_PARAMETER |
| 787 | CIM_ERR_INVALID_CLASS | CIM_ERR_INVALID_CLASS |
| 788 | CIM_ERR_NOT_FOUND | CIM_ERR_NOT_FOUND |
| 789 | CIM_ERR_NOT_SUPPORTED | CIM_ERR_NOT_SUPPORTED |
| 790 | CIM_ERR_CLASS_HAS_CHILDREN | CIM_ERR_CLASS_HAS_CHILDREN |
| 791 | CIM_ERR_CLASS_HAS_INSTANCES | CIM_ERR_CLASS_HAS_INSTANCES |
| 792 | CIM_ERR_INVALID_SUPERCLASS | CIM_ERR_INVALID_SUPERCLASS |
| 793 | CIM_ERR_ALREADY_EXISTS | CIM_ERR_ALREADY_EXISTS |
| 794 | CIM_ERR_NO_SUCH_PROPERTY | CIM_ERR_NO_SUCH_PROPERTY |
| 795 | CIM_ERR_TYPE_MISMATCH | CIM_ERR_TYPE_MISMATCH |
| 796 | CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED | CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED |
| 797 | CIM_ERR_INVALID_QUERY | CIM_ERR_INVALID_QUERY |
| 798 | CIM_ERR_METHOD_NOT_AVAILABLE | CIM_ERR_METHOD_NOT_AVAILABLE |
| 799 | CIM_ERR_METHOD_NOT_FOUND | CIM_ERR_METHOD_NOT_FOUND |
| 800 | CIM_ERR_UNEXPECTED_RESPONSE | CIM_ERR_UNEXPECTED_RESPONSE |
| 801 | CIM_ERR_INVALID_RESPONSE_DESTINATION | CIM_ERR_INVALID_RESPONSE_DESTINATION |
| 802 | CIM_ERR_NAMESPACE_NOT_EMPTY | CIM_ERR_NAMESPACE_NOT_EMPTY |
| 803 | CIM_ERR_INVALID_ENUMERATION_CONTEXT | CIM_ERR_INVALID_ENUMERATION_CONTEXT |
| 804 | CIM_ERR_INVALID_OPERATION_TIMEOUT | CIM_ERR_INVALID_OPERATION_TIMEOUT |
| 805 | CIM_ERR_PULL_HAS_BEEN_ABANDONED | CIM_ERR_PULL_HAS_BEEN_ABANDONED |
| 806 | CIM_ERR_PULL_CANNOT_BE_ABANDONED | CIM_ERR_PULL_CANNOT_BE_ABANDONED |
| 807 | CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED | CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED |
| 808 | CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED | CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED |
| 809 | CIM_ERR_SERVER_LIMITS_EXCEEDED | CIM_ERR_SERVER_LIMITS_EXCEEDED |
| 810 | CIM_ERR_SERVER_IS_SHUTTING_DOWN | CIM_ERR_SERVER_IS_SHUTTING_DOWN |
| 811 | CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED | CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED |
| 812 | 自由格式的字符串，包含用户可读的 CIMStatusCode 描述。该描述可以扩展，但必须与 CIMStatusCode 的定义一致。 | A free-form string containing a human-readable description of CIMStatusCode. This description MAY extend, but MUST be consistent with, the definition of CIMStatusCode. |
| 813 | 2.22.1 | 2.22.1 |
| 814 | CIM_Error 是一个特殊类，包含与某个 CIM 操作失败有关的严重性、原因、建议操作以及其他数据的相关信息。这种类型的实例可以作为某个 CIM 操作的响应的一部分。 | 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. |
| 815 | 应用程序特定错误代码 | Application-specific error code |
| 816 | 错误类型名称，例如:“HRESULT”或“MI_RESULT”或“Win32” | The name of the error type, for example : 'HRESULT' or 'MI_RESULT' or 'Win32' |
| 817 | 对应于 MI.h 中类别枚举的枚举 | Enumeration corresponding to the category enum in MI.h |
| 818 | MI_ERRORCATEGORY_NOT_SPECIFIED | MI_ERRORCATEGORY_NOT_SPECIFIED |
| 819 | MI_ERRORCATEGORY_OPEN_ERROR | MI_ERRORCATEGORY_OPEN_ERROR |
| 820 | MI_ERRORCATEGORY_CLOSE_EERROR | MI_ERRORCATEGORY_CLOSE_EERROR |
| 821 | MI_ERRORCATEGORY_DEVICE_ERROR | MI_ERRORCATEGORY_DEVICE_ERROR |
| 822 | MI_ERRORCATEGORY_DEADLOCK_DETECTED | MI_ERRORCATEGORY_DEADLOCK_DETECTED |
| 823 | MI_ERRORCATEGORY_INVALID_ARGUMENT | MI_ERRORCATEGORY_INVALID_ARGUMENT |
| 824 | MI_ERRORCATEGORY_INVALID_DATA | MI_ERRORCATEGORY_INVALID_DATA |
| 825 | MI_ERRORCATEGORY_INVALID_OPERATION | MI_ERRORCATEGORY_INVALID_OPERATION |
| 826 | MI_ERRORCATEGORY_INVALID_RESULT | MI_ERRORCATEGORY_INVALID_RESULT |
| 827 | MI_ERRORCATEGORY_INVALID_TYPE | MI_ERRORCATEGORY_INVALID_TYPE |
| 828 | MI_ERRORCATEGORY_METADATA_ERROR | MI_ERRORCATEGORY_METADATA_ERROR |
| 829 | MI_ERRORCATEGORY_NOT_IMPLEMENTED | MI_ERRORCATEGORY_NOT_IMPLEMENTED |
| 830 | MI_ERRORCATEGORY_NOT_INSTALLED | MI_ERRORCATEGORY_NOT_INSTALLED |
| 831 | MI_ERRORCATEGORY_OBJECT_NOT_FOUND | MI_ERRORCATEGORY_OBJECT_NOT_FOUND |
| 832 | MI_ERRORCATEGORY_OPERATION_STOPPED | MI_ERRORCATEGORY_OPERATION_STOPPED |
| 833 | MI_ERRORCATEGORY_OPERATION_TIMEOUT | MI_ERRORCATEGORY_OPERATION_TIMEOUT |
| 834 | MI_ERRORCATEGORY_SYNTAX_ERROR | MI_ERRORCATEGORY_SYNTAX_ERROR |
| 835 | MI_ERRORCATEGORY_PARSER_ERROR | MI_ERRORCATEGORY_PARSER_ERROR |
| 836 | MI_ERRORCATEGORY_ACCESS_DENIED | MI_ERRORCATEGORY_ACCESS_DENIED |
| 837 | MI_ERRORCATEGORY_RESOURCE_BUSY | MI_ERRORCATEGORY_RESOURCE_BUSY |
| 838 | MI_ERRORCATEGORY_RESOURCE_EXISTS | MI_ERRORCATEGORY_RESOURCE_EXISTS |
| 839 | MI_ERRORCATEGORY_RESOURCE_UNAVAILABLE | MI_ERRORCATEGORY_RESOURCE_UNAVAILABLE |
| 840 | MI_ERRORCATEGORY_READ_ERROR | MI_ERRORCATEGORY_READ_ERROR |
| 841 | MI_ERRORCATEGORY_WRITE_ERROR | MI_ERRORCATEGORY_WRITE_ERROR |
| 842 | MI_ERRORCATEGORY_FROM_STDERR | MI_ERRORCATEGORY_FROM_STDERR |
| 843 | MI_ERRORCATEGORY_SECURITY_ERROR | MI_ERRORCATEGORY_SECURITY_ERROR |
| 844 | MI_ERRORCATEGORY_PROTOCOL_ERROR | MI_ERRORCATEGORY_PROTOCOL_ERROR |
| 845 | MI_ERRORCATEGORY_CONNECTION_ERROR | MI_ERRORCATEGORY_CONNECTION_ERROR |
| 846 | MI_ERRORCATEGORY_AUTHENTICATION_ERROR | MI_ERRORCATEGORY_AUTHENTICATION_ERROR |
| 847 | MI_ERRORCATEGORY_LIMITS_EXCEEDED | MI_ERRORCATEGORY_LIMITS_EXCEEDED |
| 848 | MI_ERRORCATEGORY_QUOTA_EXCEEDED | MI_ERRORCATEGORY_QUOTA_EXCEEDED |
| 849 | MI_ERRORCATEGORY_NOT_ENABLED | MI_ERRORCATEGORY_NOT_ENABLED |
| 850 | OMI_Error 是一个类，用于报告 OMI 基础结构以及基于该基础结构组件中的错误。 | OMI_Error is a class used to report errors in the OMI infrastructure and components built on that infrastructure. |
| 851 | ResourceScriptBreakAll | ResourceScriptBreakAll |
| 852 | 资源运行时所依据的凭据。 | Credentials under which the resource runs. |
| 853 | 空闲 | Idle |
| 854 | PendingConfiguration | PendingConfiguration |
| 855 | 本地配置管理器的状态详细信息。 | State detail of local configuration manager. |
| 856 | 此部分配置将要使用的资源模块存储库源 | The resource module repository source that this partial configuration will use |
| 857 | 启用“调试 DSC 配置”。 | Enable Debug DSC Configuration. |
| 858 | 禁用“调试 DSC 配置”。 | Disable Debug DSC Configuration. |
| 859 | 用于注册到“拉”服务器的注册密钥 | Registration Key with which to register with the Pull Server |
| 860 | 用于注册到报告服务器的注册密钥 | Registration Key with which to register with the Reporting Server |
| 861 | 当前 Dsc 代理的 AgentId。 | AgentId of the current Dsc Agent. |
| 863 | 用于注册到资源存储库 Web 的注册密钥 | Registration Key with which to register with the Resource Repository Web |
| 864 | 用于注册到“拉”服务器的一组配置名称。 | The set of configuration names with which to register with the Pull Server. |
| 865 | LocalConfigurationManager | LocalConfigurationManager |
| 868 | 用于验证 mof 文档或模块签名的受信任发布者存储的路径。 | The path to the trusted publisher store used to validate the signature of the mof document or modules. |
| 869 | 配置 | Configuration |
| 870 | 模块 | Module |
| 871 | 签名验证类型。 | The signature validation type. |
| 873 | 当前的签名验证策略。 | Current signature validation policy. |
| 874 | 节点的签名验证选项。 | The signature validation options of the node. |
| 875 | 可下载的最大模块大小(以 MB 为单位)。 | The maximum module size in MB that can be downloaded. |
| 1001 | 内存分配失败。 | Memory allocation failed. |
| 1002 | MOF 文件的大小超过最大大小限制。 | MOF file size exceeded max size limit. |
| 1003 | 打开文件时出错: %1!s! | Error opening file: %1!s! |
| 1004 | 读取文件内容失败 | Reading file content failed |
| 1005 | 获取文件大小时出错。 | Error getting file size. |
| 1006 | StringCchCatW 失败。 | StringCchCatW failed. |
| 1007 | 为 mofcomp.exe 执行 CreateProcess 失败 | CreateProcess failed for mofcomp.exe |
| 1008 | PowerShell Desired State Configuration 在发现 %2!s! 资源的过程中无法使用 Mofcomp.exe 注册 MOF 文件 %1!s!。请检查 MOF 文件，然后重试。 | 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. |
| 1009 | 无法生成当前配置的校验和。 | Unable to generate checksum for current configuration. |
| 1010 | LCM 无法将一个或多个资源转换成其所需的状态。 | LCM failed to move one or more resources to their desired state. |
| 1011 | LCM 无法加载 PowerShell 模块加载程序。 | LCM failed to load PowerShell module loader. |
| 1012 | LCM 无法让你手动启动所需的状态配置。 | LCM failed to start desired state configuration manually. |
| 1013 | LCM 无法检索元配置的属性值。 | LCM failed to retrieve property values of meta configuration. |
| 1014 | LCM 无法从类 %2!s! 的对象中检索属性 %1!s!。 | LCM failed to retrieve the property %1!s! from the object of class %2!s! . |
| 1020 | LCM 无法写入到资源状态缓存文件。 | LCM failed to write to resource state cache file. |
| 1021 | LCM 无法序列化资源状态缓存。 | LCM failed to serialize resource state cache. |
| 1022 | LCM 无法反序列化资源状态缓存。 | LCM failed to deserialize resource state cache. |
| 1023 | 资源状态缓存的索引无效。 | Invalid index to resource state cache. |
| 1024 | LCM 无法序列化配置状态。 | LCM failed to serialize configuration status. |
| 1025 | LCM 无法反序列化配置状态。 | LCM failed to deserialize configuration status. |
| 1026 | 节点 %1!s! 没有状态信息。请在目标节点上应用某个配置，然后重试。 | No status information available for node %1!s!. Apply a configuration on the target node and try again. |
| 1101 | 注册 Windows 事件跟踪(ETW)失败。 | The registration of Event Tracing for Windows (ETW) failed. |
| 1102 | 无法初始化代理关键部分。 | Could not initialize the agent critical section. |
| 1103 | 无法初始化文件关键部分。 | Could not initialize the file critical section. |
| 1104 | 无法展开环境路径。 | Could not expand the environment path. |
| 1105 | ETW 注销失败。 | ETW unregistration failed. |
| 1106 | 验证配置目录未成功。请确保该目录存在，然后重试。 | The validation of the Configuration directory did not succeed. Ensure that the directory exists and try again. |
| 1107 | 无法在执行 get 操作之前删除旧文件 Get.mof。 | Could not delete the old file Get.mof before the get operation. |
| 1108 | 无法保存 Get.mof 文件。请删除配置目录中的 Get.mof，然后重试。 | Could not save the Get.mof file. Delete Get.mof in the Configuration directory and try again. |
| 1109 | 无法从指定位置加载实例文档。请确保该实例文档存在，然后重试。 | Could not load the instance document from the specified location. Ensure that the instance document exists and try again. |
| 1110 | GetConfiguration 未成功。 | GetConfiguration did not succeed. |
| 1111 | 无法在执行 get 操作后删除 Get.mof 文件。请检查文件所在位置的属性，然后重试。 | Could not delete the file Get.mof after the get operation. Check the properties of the location of the file and try again. |
| 1112 | 配置目录创建失败。请验证目录权限，然后重试。 | The creation of the configuration directory failed. Verify the directory permissions and try again. |
| 1114 | Stprintf 失败。 | Stprintf failed. |
| 1115 | 某个配置处于挂起状态。在“拉”模式下，请运行 Update-DscConfiguration 以拉取并应用新配置。在“推”模式下，请运行带 -Force 参数的 Start-DscConfiguration 命令以应用新配置，或运行带 -UseExisting 参数的 Start-DscConfiguration 命令以完成现有的配置。 | 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. |
| 1116 | 无法保存挂起的配置 MOF 文件。请检查目标位置的属性，然后重试。 | Could not save the pending configuration MOF file. Check the properties of the destination location and try again. |
| 1117 | 从挂起的位置加载该实例文档未成功。 | Loading the instance document from the pending location did not succeed. |
| 1118 | SendConfigurationApply 函数未成功。 | The SendConfigurationApply function did not succeed. |
| 1119 | 移动挂起的文件后进行删除未成功。 | Deleting the pending file after moving it did not succeed. |
| 1120 | 无法复制文件。 | Could not copy file. |
| 1121 | 由于为管理员转换安全描述符失败，无法创建配置 MOF 文件。 | Unable to create configuration MOF file because converting security descriptor for administrators failed. |
| 1122 | 无法创建配置 MOF 文件。请查看分析事件日志，以调查无法在此路径上创建 MOF 文件的原因。 | 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. |
| 1123 | 无法使用 Mof_Instance_New 构造 MSFT_DSCMetaConfiguration。 | Could not construct MSFT_DSCMetaConfiguration using Mof_Instance_New. |
| 1124 | ModuleLoader 为 Null。 | ModuleLoader is null. |
| 1125 | 加载本地配置管理器设置架构未成功。 | Loading the Local Configuration Manager settings schema did not succeed. |
| 1126 | 加载元架构时返回了 Null。 | Metaschema loading returned null. |
| 1127 | 无法创建序列化程序。 | Could not create the serializer. |
| 1128 | 无法序列化本地配置管理器设置。 | Could not serialize the Local Configuration Manager settings. |
| 1129 | 无法删除本地配置管理器设置文件。 | Could not delete the Local Configuration Manager settings file. |
| 1130 | 创建反序列化程序失败。 | Creating deserializer failed. |
| 1131 | 克隆类型化本地配置管理器设置未成功。 | Cloning the typed Local Configuration Manager settings did not succeed. |
| 1132 | 无法创建调用任务 API 所需的参数。 | Could not create the parameters required for invoking the Task API. |
| 1133 | 添加任务路径参数来调用任务 API 未成功。 | Adding task path parameters to call the task API did not succeed. |
| 1134 | 创建一个会话来调用任务 API 未成功。 | Creating a session to call the task API did not succeed. |
| 1135 | ExpandEnvironmentStrings 函数未成功。 | The ExpandEnvironmentStrings function did not succeed. |
| 1136 | 获取当前的线程模拟令牌未成功。 | Getting the current thread impersonation token did not succeed. |
| 1137 | 无法还原为其自身。 | Could not revert to self. |
| 1138 | 无法继续模拟。 | Could not resume impersonation. |
| 1139 | 无法构造 GetConfiguration 函数的输出对象。 | Could not construct the output object for the GetConfiguration function. |
| 1140 | 写入 GetConfiguration 的输出参数未成功。 | Writing the output parameter for GetConfiguration did not succeed. |
| 1141 | ApplyConfiguration 无法获取系统当前的本地配置管理器设置。 | ApplyConfiguration could not get the current Local Configuration Manager settings for the system. |
| 1142 | 发布 GetConfiguration 的输出未成功。 | Posting output for GetConfiguration did not succeed. |
| 1143 | 无法构造 ApplyConfiguration 函数的输出对象。请检查配置，然后重试。 | Could not construct the output object for the ApplyConfiguration function. Check the configuration and try again. |
| 1144 | ApplyConfiguration 中的 Set 函数返回了错误。 | The Set function in ApplyConfiguration returned an error. |
| 1145 | 无法发布 ApplyConfiguration 函数中的输出。 | Could not post the output in the ApplyConfiguration function. |
| 1146 | 无法更新 LCM 版本信息。 | Could not update LCM version information. |
| 1150 | 已计划重新启动以继续操作。重新启动后，将继续进行配置。 | A reboot is scheduled to progress further. Configuration will be continued after the reboot. |
| 1151 | 正在启动一致性引擎。 | Starting consistency engine. |
| 1152 | 一致性检查已完成。 | Consistency check completed. |
| 1153 | 存在挂起的配置。DSC 会处理针对挂起的配置的 set 请求。 | A pending configuration exists. DSC will process a set request on the pending configuration. |
| 1154 | 正在检查当前配置的一致性。 | Checking consistency for current configuration. |
| 1155 | 配置文档已成功保存为挂起状态。 | Configuration document successfully saved to pending state. |
| 1156 | 此实例文档没有指定任何资源。请向文档至少添加一个资源，然后重试。 | The instance document does not specify any resource. Add at least one resource to the document and try again. |
| 1157 | 本地配置管理器无法读取 ComputerName 属性的上下文信息。 | The Local Configuration Manager could not read the ComputerName property context information. |
| 1158 | 本地配置管理器无法获取令牌信息大小。 | Local Configuration Manager could not get token info size. |
| 1159 | 收到了来自用户 SID 为 %2!s! 的计算机 %1!s! 的 LCM 方法调用。 | An LCM method call arrived from computer %1!s! with user sid %2!s!. |
| 1160 | 无法保存临时的本地配置管理器设置文件。请检查目标位置的属性，然后重试。 | Could not save the temporary Local Configuration Manager settings file. Check the properties of the destination location and try again. |
| 1161 | 无法删除临时元数据文件。 | Could not delete the temporary metadata file. |
| 1162 | 删除文件 %1!s! 失败。 | Deletion of file%1!s!failed. |
| 1163 | 执行 Get-Action 返回成功，但未返回任何状态。 | Executing Get-Action returned success but didn't return any status. |
| 1164 | Get-DSCAction 返回成功，但未返回预期的状态。 | Get-DSCAction returned success but did not return the expected status. |
| 1165 | GetConfiguration 运行成功，但未返回预期的状态。 | GetConfiguration ran successfully, but did not return the expected status. |
| 1166 | GetConfiguration 运行成功，但未返回任何状态。 | GetConfiguration ran successfully, but did not return any status. |
| 1167 | configurationData 参数已保留供将来使用。默认情况下使用当前配置。 | The configurationData parameter is reserved for future use. The current configuration is used by default. |
| 1168 | 无法构造测试配置输出对象。 | Could not construct the test configuration output object. |
| 1169 | 无法在 TestConfiguration 中设置资源 ID。请重新尝试运行该操作。 | Could not set the resource ID in TestConfiguration. Try running the operation again. |
| 1170 | 无法发布测试配置的输出。 | Could not post the output for the test configuration. |
| 1171 | 当前配置不存在。请先执行带有 -Path 参数的 Start-DscConfiguration 命令，以指定一个配置文件并创建当前配置。 | Current configuration does not exist. Execute Start-DscConfiguration command with -Path parameter to specify a configuration file and create a current configuration first. |
| 1173 | 已完成处理测试操作。该操作失败。 | Completed processing test operation. The operation failed. |
| 1174 | [%1!s!]: LCM: [ %2!-16s!] %3!s! (在 %4!s! 秒内)。 | [%1!s!]: LCM: [ %2!-16s!] %3!s! in %4!s! seconds. |
| 1175 | Force 参数仅接受布尔值 True 或 False。 | The Force parameter accepts only boolean values True or False. |
| 1176 | 无法检索本地配置管理器设置。 | Could not retrieve the Local Configuration Manager settings. |
| 1177 | 更新一致性任务失败。 | Update consistency task failed. |
| 1179 | 计算机重新启动失败。请手动重新启动以完成对请求的处理。 | Machine reboot failed. Please reboot it manually to finish processing the request. |
| 1180 | DSC 正在重新启动计算机。 | DSC is restarting the computer. |
| 1181 | 针对 PULL 处理进行配置时，在未使用 -Force 的情况下请求了 PUSH 操作。 | A PUSH operation was requested without -Force while configured for PULL processing. |
| 1182 | 以前的配置不存在。仅当存在以前的配置时，DSC 才能回退。 | A previous configuration does not exist. DSC can rollback only when there is a previous configuration. |
| 1183 | ConfigurationNumber 参数已保留供将来使用。默认情况下使用以前的配置。 | The ConfigurationNumber parameter is reserved for future use. The previous configuration is used by default. |
| 1186 | 无法调用 %1!s! cmdlet。%2!s! cmdlet 正在运行中，必须返回后才能调用 %3!s!。如果可以使用 -Force 选项取消当前操作，请使用该选项。 | 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. |
| 1187 | 收到意外的任务名称。 | Unexpected task name received. |
| 1188 | 指定的时间间隔超出了可接受的范围(最多 31 天)。 | An interval was specified outside of the acceptable range (maximum of 31 days). |
| 1189 | 删除临时文件时遇到错误。 | An error was encountered while deleting the temporary file. |
| 1190 | GetTempPath 失败。 | GetTempPath failed. |
| 1191 | GetTempFileName 失败。 | GetTempFileName failed. |
| 1192 | CreateFile 失败。 | CreateFile failed. |
| 1193 | WriteFile 失败。 | WriteFile failed. |
| 1194 | CloseHandle 失败。 | CloseHandle failed. |
| 1195 | 尝试获取字符串长度时出错。 | Error attempting to get the length of a string. |
| 1196 | 已完成处理测试操作。该操作返回 True。 | Completed processing test operation. The operation returned True. |
| 1197 | 已完成处理测试操作。该操作返回 False。 | Completed processing test operation. The operation returned False. |
| 1198 | 清除内置 DSC 资源的缓存。 | Clear the cache of built-in DSC resources. |
| 1199 | 无法清除内置 DSC 资源的缓存。 | Failed to clear the cache of built-in DSC resources. |
| 1200 | 无法创建“拉”运行日志文件。请查看分析事件日志，以调查无法在此路径上创建该文件的原因。 | 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. |
| 1201 | moduleManager 参数不能为 Null。 | The moduleManager parameter cannot be null. |
| 1202 | MI_Application_Initialize 失败。 | MI_Application_Initialize failed. |
| 1203 | moduleManager 参数无效。 | The moduleManager parameter is not valid. |
| 1205 | moduleManager、className 和 registrationInstance 参数不能为 Null。 | The moduleManager, className, and registrationInstance parameters cannot be null. |
| 1206 | 找不到注册实例。该类不是 DSC 配置类。 | Registration instance not found. Class is not a DSC configuration class. |
| 1207 | 该类未注册为配置类。 | The class is not registered as a configuration class. |
| 1208 | moduleManager、inInstance 和 outInstance 参数不能为 Null。 | The moduleManager, inInstance, and outInstance parameters cannot be null. |
| 1209 | GetFilteredResource 失败。 | GetFilteredResource failed. |
| 1210 | 在初始化反序列化程序时，无法创建新对象来存储操作选项。 | Could not create a new object to store the operation options while initializing the deserializer. |
| 1211 | 在初始化反序列化程序时，设置“操作”选项未成功。 | Setting the Operation option while initializing the deserializer did not succeed. |
| 1212 | FindFirstFile 失败。 | FindFirstFile Failed. |
| 1213 | FindNextFile 失败。 | FindNextFile Failed. |
| 1214 | GetSystemSchema 的参数无效。 | The parameter for GetSystemSchema is not valid. |
| 1215 | GetSchemaFromMOFs 的参数无效。 | The parameter for GetSchemaFromMOFs is not valid. |
| 1216 | 实例文档中并非所有实例都包含 ResourceId。 | Not all instances within the instance document contain ResourceId. |
| 1217 | 此实例文档包含多个 OMI_ConfigurationDocument 实例。 | The instance document contains multiple OMI_ConfigurationDocument instances. |
| 1218 | 实例文档必须正好包含一个 OMI_ConfigurationDocument 实例。 | Instance document must contain exactly one OMI_ConfigurationDocument instance. |
| 1219 | 找不到注册实例的 ClassName 属性。 | ClassName property not found for registration instance. |
| 1220 | miApp、inInstance 和 outInstance 参数不能为 Null。 | The miApp, inInstance, and outInstance parameters cannot be null. |
| 1221 | MI_Instance_GetElement 失败。 | MI_Instance_GetElement failed. |
| 1222 | 找到意外的基础结构类。 | An unexpected infrastructure class was found. |
| 1223 | 发现使用同一名称注册了多个类。 | Found multiple classes registered with the same name. |
| 1224 | 在注册中找不到必需的 ClassName 属性。请使用已注册的类名，然后重试。 | The mandatory ClassName property was not found in the registration. Use a registered classname and try again. |
| 1225 | 找到一个没有类的注册实例。 | Found a registration instance without a class. |
| 1226 | 发现一个架构不包含注册。请检查“注册”目录和“架构”目录以查找注册的架构。 | A schema was found that does not contain registration. Check the Registration and Schema directories to find the registered schemas. |
| 1227 | 类引用不存在。 | The class reference does not exist. |
| 1228 | 类不应包含任何方法。 | Class should not contain any method. |
| 1229 | 找不到 ClassVersion 限定符。 | ClassVersion Qualifier not found. |
| 1230 | 属性或类型引用数组不受支持。 | A property or array of type reference is not supported. |
| 1231 | 不能具有带以下任何限定符的 Read 属性: Write、Key、Required。 | Cannot have the Read property with any of the following qualifiers: Write, Key, Required. |
| 1232 | 在实例文档中必须至少定义一个键属性。请更新实例文档，然后重试。 | At least one key property must be defined in the instance document. Update the instance document and try again. |
| 1233 | 你必须为每个 MOF 文件至少指定一个配置资源。 | You must specify at least one configuration resource per MOF file. |
| 1234 | 所有的类必须具有对 ConfigurationResource 的引用。 | All classes must have a reference to ConfigurationResource. |
| 1235 | 每个 MOF 文件必须有且只有一个配置资源。 | There must be exactly one configuration resource per MOF file. |
| 1236 | 找不到强制属性 %1!s!。请添加此属性，然后重试。 | Could not find mandatory property %1!s!. Add this property and try again. |
| 1237 | MI_Instance_GetClassName 失败。 | MI_Instance_GetClassName failed. |
| 1238 | 实例的类型应为 MSFT_CimConfigurationProviderRegistration 或 MSFT_PSConfigurationProviderRegistration。 | Instance should be of type MSFT_CimConfigurationProviderRegistration or MSFT_PSConfigurationProviderRegistration. |
| 1239 | 找不到强制属性 ClassName。 | Mandatory property ClassName not found. |
| 1240 | 找不到强制属性 DSCEngineCompatVersion。 | Mandatory property DSCEngineCompatVersion not found. |
| 1241 | 找不到强制属性 DscModuleVersion。 | Mandatory property DscModuleVersion not found. |
| 1242 | 找不到强制属性 Namespace。 | Mandatory property Namespace not found. |
| 1243 | 找不到强制属性 ModuleName。 | Mandatory property ModuleName not found. |
| 1244 | 找不到强制属性。 | Mandatory property not found. |
| 1245 | 强制属性类型不匹配。 | Mandatory property type does not match. |
| 1246 | MGet 类属性计数失败。 | MGet class property count failed. |
| 1247 | 属性的数目与预期的数目不匹配。 | The number of properties does not match the expected number. |
| 1248 | 缺少强制属性限定符类型。 | Mandatory property qualifer type is missing. |
| 1249 | MSFT_PSConfigurationProviderRegistration 必须从 MSFT_BaseConfigurationProviderRegistration 派生。 | MSFT_PSConfigurationProviderRegistration must derive from MSFT_BaseConfigurationProviderRegistration. |
| 1250 | 注册实例不包含命名空间。命名空间是必需的。 | The registration instance does not contain a namespace. A namespace is required. |
| 1251 | GetTargetResource 需要三个参数。 | GetTargetResource requires three parameters. |
| 1252 | TestTargetResource 没有 4 个参数。 | TestTargetResource doesn't have 4 parameters. |
| 1253 | SetTargetResource 没有 3 个参数。 | SetTargetResource doesn't have 3 parameters. |
| 1254 | ValidateDSCProviderMappingForWMIV2Provider 未成功。找不到以下三个项中的某一个: Get、Test 或 Set。 | ValidateDSCProviderMappingForWMIV2Provider did not succeed. One of the following was not found: Get, Test, or Set. |
| 1255 | MSFT_CimConfigurationProviderRegistration 必须从 MSFT_BaseConfigurationProviderRegistration 派生。 | MSFT_CimConfigurationProviderRegistration must derive from MSFT_BaseConfigurationProviderRegistration. |
| 1256 | 为 %windir% 执行 GetEnvironmentVariable 失败。 | GetEnvironmentVariable for %windir% failed. |
| 1257 | 实例文档的版本号不是任何受支持版本。请将 OMI_Configuration 文档实例中的版本号更改为 1.0.0 或 2.0.0 | 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.0 |
| 1258 | 找到了多个具有同一 ResourceId %1!s! 的实例。请更正该错误，然后重试。 | Found more than one instance with the same ResourceId %1!s!. Correct that and try again. |
| 1259 | 当前文档包含本地配置管理器设置，而这是不受支持的。请单独发送本地配置管理器设置。 | The current document contains Local Configuration Manager settings, which is not supported. Send Local Configuration Manager settings seperately. |
| 1260 | 找不到本地配置管理器设置，或者当前文档包含的是其他配置。请进行更正，然后重试。 | Local Configuration Manager settings were not found, or the current document contains other configurations. Correct that and try again. |
| 1261 | 正在启动重新启动处理。 | Starting reboot processing. |
| 1262 | 重新启动后存在挂起的配置。DSC 会处理针对挂起的配置的 Set 请求。 | A pending configuration exists after reboot. DSC will process a set request on the pending configuration. |
| 1263 | 正在检查当前配置在重新启动后的一致性。 | Checking consistency for current configuration after reboot. |
| 1264 | 已完成重新启动处理。 | Reboot processing completed. |
| 1265 | LCM“%4!s!”无法识别文档“%2!s!”“%3!s!”的属性“%1!s!”。请重新编译你的配置文档，然后重试。 | 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. |
| 1266 | 元配置中没有文档实例。请使用 OMI_ConfigurationDocument 的实例创建配置，然后重试。 | There is no document instance inside the metaconfiguration. Please create the configuration with an instance of OMI_ConfigurationDocument and try again. |
| 1268 | 如果不存在任何部分配置，DSC 本地配置管理器将仅支持元配置文档版本 2.0.0 中某个配置存储库的一个实例。由于定义了多个配置存储库，因此 LCM 只会将第一个存储库用于现有提取方案，并忽略其他存储库。若要删除此警告，请使用单个配置存储库，或者使用部分配置指向配置存储库。 | 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. |
| 1269 | 允许的下载管理器名称只能是 DSCFileDownloadManager 和 WebDownloadManager。但是，元配置包含 %1!s! 作为下载管理器名称。请更正该错误，然后重试。 | 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. |
| 1270 | 属性 AllowUnsecureConnection 只能取值 true 或 false。请在元配置中更正此错误，然后重试。 | The property AllowUnsecureConnection can only take values of either true or false. Correct this in the metaconfiguration and try again. |
| 1271 | 已计划重新启动以继续操作。在重新启动后将不会继续进行配置。若要继续配置，请在重新启动后使用 Start-DscConfiguration -UseExisting。 | A reboot is scheduled to progress further. Configuration will not be continued after the reboot. To continue configuration, use Start-DscConfiguration -UseExisting after reboot. |
| 1272 | 需要重新启动才能继续操作。请重新启动系统。在重新启动后将不会继续进行配置。若要继续配置，请在重新启动后使用 Start-DscConfiguration -UseExisting。 | 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. |
| 1273 | 发生内部错误: 找不到 DSC 提供程序注册的强制属性 ProviderPath。 | An internal error occurred : Mandatory property ProviderPath for DSC provider registration not found. |
| 1274 | 发生内部错误: 找不到 DSC 提供程序注册的强制属性 ModulePath。 | An internal error occurred : Mandatory property ModulePath for DSC provider registration not found. |
| 1275 | 模块 %2!s! 中的资源 %1!s! 已使用版本 %3!s! 和版本 %4!s! 导入两次。不支持使用资源的多个版本。请删除其中一个版本以更正问题。 | 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. |
| 1276 | 当前的刷新模式是“拉”，但没有定义任何配置下载管理器。 | The current refresh mode is PULL but there are no configuration download managers defined. |
| 1301 | 无法使用 null 实例参数解析依赖关系。请确保实例不为 null。 | Dependency cannot be resolved with null instance parameters. Verify that the instances are not null. |
| 1302 | 在实例文档的指定资源中发现循环依赖关系。请检查并更正实例 %1!s! 的 Requires 属性，然后重试。 | 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. |
| 1303 | 索引超出范围。 | Index is out of bounds. |
| 1304 | MI_Instance_GetElement 无法获取 ResourceId。 | MI_Instance_GetElement failed to get ResourceId. |
| 1305 | 在实例文档的任何指定资源中都找不到 ResourceId %1!s!。Requires 属性中指定的 ResourceId 可能不正确。请更正实例 %2!s!，然后重试。 | 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. |
| 1306 | 依赖关系解析程序的索引超出范围。 | Index out of range for dependency resolver. |
| 1307 | OutInstances 不能为 Null。 | OutInstances cannot be null. |
| 1308 | MI_Application_NewSession 失败。 | MI_Application_NewSession failed. |
| 1309 | 注册类型未知。 | Unknown registration type. |
| 1310 | MI_Instance_GetElement 无法获取 WMIv2 DSC 资源的命名空间。 | MI_Instance_GetElement failed to get Namespace for WMIv2 DSC resource. |
| 1311 | MI_Application_NewInstance 失败。 | MI_Application_NewInstance failed. |
| 1312 | MI_Instance_AddElement 在 inputResource 参数中返回了错误。 | MI_Instance_AddElement returned an error on the inputResource parameter. |
| 1313 | MI_Operation_GetInstance 失败。 | MI_Operation_GetInstance failed. |
| 1314 | 为 ReturnValue 执行 MI_Instance_GetElement 失败。 | MI_Instance_GetElement failed for ReturnValue. |
| 1315 | MI_Instance_GetElement 在 Result 参数中返回了错误。 | MI_Instance_GetElement returned an error on the Result parameter. |
| 1316 | 为 ProviderContext 方法参数执行 MI_Instance_GetElement 失败。 | MI_Instance_GetElement failed for ProviderContext method parameter. |
| 1317 | 为该配置的 Method 参数执行 MI_Instance_GetElement 未成功。 | MI_Instance_GetElement did not succeed for the Method parameter of the configuration. |
| 1318 | MI_Instance_Clone 失败。 | MI_Instance_Clone failed. |
| 1319 | 无法处理 get 请求。 | Could not process the get request. |
| 1320 | MI_Instance_GetElement 无法从 MSFT_LogResource 中获取消息。 | MI_Instance_GetElement failed to get Message from MSFT_LogResource. |
| 1321 | 测试未成功。 | Test did not succeed. |
| 1328 | 在实例文档的指定资源中发现循环依赖关系。请检查并更正 %2!s! 中定义的实例 %1!s! 的 Requires 属性，然后重试。 | 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. |
| 1329 | 在实例文档的任何指定资源中都找不到 ResourceId %1!s!。Requires 属性中指定的 ResourceId 可能不正确。请更正 %3!s!" 中定义的实例 %2!s!，然后重试。 | 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. |
| 1330 | %1!s!相关的 ResourceID 为 %2!s!。 | %1!s! The related ResourceID is %2!s!. |
| 1332 | (在 %1!s! 秒内)。 | in %1!s! seconds. |
| 1335 | 无法打开本地计算机证书存储。 | The local machine certificate store could not be opened. |
| 1336 | 在本地计算机证书存储中找不到证书。 | The certificate cannot be found in the local machine certificate store. |
| 1337 | 无法获取 CSP 密钥上下文的句柄。 | Could not acquire a handle to the key context for the CSP. |
| 1338 | 无法获取公钥。 | The public key could not be acquired. |
| 1339 | 无法获取私钥。 | The private key could not be acquired. |
| 1340 | 无法为加密的数据分配内存。 | Memory could not be allocated for the encrypted data. |
| 1341 | 加密未成功。 | Encryption did not succeed. |
| 1342 | 无法为解密的数据分配内存。 | Could not allocate memory for the decrypted data. |
| 1343 | 解密失败。 | Decryption failed. |
| 1344 | 解密后更新密码元素失败。 | Updating the password element after decription failed. |
| 1355 | 无法检索当前的本地配置管理器设置。请应用本地配置管理器设置，然后重试。 | Could not retrieve the current Local Configuration Manager settings. Apply Local Configuration Manager settings and try again. |
| 1356 | 当前配置已取消。 | The current configuration was cancelled. |
| 1357 | 无法等待停止事件。 | Could not wait for the stopping event. |
| 1358 | 无法取消当前操作。 | Could not cancel the current operation. |
| 1360 | ， | , |
| 1361 | 无法初始化新的操作选项。 | Could not initialize a new operation option. |
| 1362 | MI_OperationOptions_SetCustomOptions 返回了错误。 | MI_OperationOptions_SetCustomOptions returned an error. |
| 1363 | 此 cmdlet 不支持 Confirm 参数。 | The Confirm parameter is not supported in this cmdlet. |
| 1364 | 最多只有 4 个嵌套级别(从架构类根开始算起)才支持凭据对象。 | Credential objects are only supported up to 4 levels of nesting from the schema class root. |
| 1365 | 资源(“%1!s!”和“%2!s!”)具有以下属性的冲突值:“%3!s!”。请确保其值匹配。 | The resources ('%1!s!' and '%2!s!') have conflicting values of the following properties: '%3!s!'. Ensure that their values match. |
| 1366 | 配置实例中存在循环依赖关系。 | Circular dependency exists in configuration instance. |
| 1368 | 未使用证书配置本地配置管理器。无法处理配置“%2!s!”中的资源“%1!s!”。 | The Local Configuration Manager is not configured with a certificate. Resource '%1!s!' in configuration '%2!s!' cannot be processed. |
| 1369 | 证书 ID 无效:“%1!s!” | The Certificate ID is not valid: '%1!s!' |
| 1370 | %1!s! 秒中 %2!s!。 | %2!s! in %1!s! seconds. |
| 1401 | [%1!s!]: LCM: [ %2!-16s!] [%3!s!] %4!s! | [%1!s!]: LCM: [ %2!-16s!] [%3!s!] %4!s! |
| 1402 | [%1!s!]: %2!-16s! [%3!s!] %4!s! | [%1!s!]: %2!-16s! [%3!s!] %4!s! |
| 1403 | 启动 | Start |
| 1404 | 结束 | End |
| 1405 | *失败* | *FAILED* |
| 1406 | 测试 | Test |
| 1407 | 获取 | Get |
| 1408 | 设置 | Set |
| 1409 | 资源 | Resource |
| 1410 | 回退 | Rollback |
| 1411 | 1412 跳过 | 1412 Skip |
| 1413 | [%1!s!]: LCM: [ %2!-16s!] %3!s! %4!s! | [%1!s!]: LCM: [ %2!-16s!] %3!s! %4!s! |
| 1414 | 比较 | Compare |
| 1415 | 删除 | Remove |
| 1416 | GetStatus | GetStatus |
| 1417 | 停止 | Stop |
| 1418 | True | True |
| 1419 | False | False |
| 1501 | 需要重新启动才能继续操作。请重新启动系统。 | A reboot is required to progress further. Please reboot the system. |
| 1502 | 指定的 RefreshFrequencyMins 已覆盖为 %1!s!，因为它超出了可接受值的范围(30-44640) | The specified RefreshFrequencyMins was over-written to %1!s! since it was outside the range of acceptable values (30-44640) |
| 1503 | 指定的 ConfigurationModeFrequencyMins 已覆盖为 %1!s!，因为它超出了可接受值的范围(15-44640) | The specified ConfigurationModeFrequencyMins was over-written to %1!s! since it was outside the range of acceptable values (15-44640) |
| 1504 | 正在回退到系统默认值，因为元配置 mof 已损坏，或者设置了无效的 mof 属性。 | Falling back to system defaults because the meta configuration mof has either been corrupted or an invalid mof property has been set. |
| 1505 | GetLcmUpdate 已成功运行，但未返回任何状态。 | GetLcmUpdate ran successfully, but did not return any status. |
| 1506 | 无法安装配置所需的模块依赖项。 | Could not install module dependencies needed by the configuration. |
| 1507 | 由于其他传入强制配置或停止操作方面的原因，强制操作已终止。 | Force operation is terminated due to other incoming force configuration or stop operations. |
| 1508 | 无法删除现有的比较配置 MOF 文件。 | Could not delete the existing compare configuration MOF file. |
| 1509 | 无法保存比较配置 MOF 文件。请检查目标位置的属性，然后重试。 | Could not save the compare configuration MOF file. Check the properties of the destination location and try again. |
| 1511 | 已完成处理比较操作。操作返回了 True。 | Completed processing compare operation. The operation returned True. |
| 1512 | 已完成处理比较操作。操作返回了 False。 | Completed processing compare operation. The operation returned False. |
| 1513 | 无法将 BuiltInProvCache 重命名为 BuiltInProvCache.Old。 | Could not rename BuiltInProvCache to BuiltInProvCache.Old. |
| 1514 | 使用无效的参数调用了 GetResourceState。 | GetResourceState is called with invalid parameters. |
| 1515 | 无法在位置 %1!s! 中发布部分配置 | Could not publish the partial configuration in location %1!s! |
| 1516 | 只有使用 Publish-DscConfiguration Cmdlet 才能在推送模式下使用 DSC 部分配置。不支持其他推送 cmdlet。若要避免此错误，请设置不带部分配置的元配置，或者使用 Publish-DscConfiguration cmdlet 来部署部分配置。 | 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. |
| 1517 | 尚未设置 OMI_ConfigurationDocument 实例的 Name 属性。若要使用部分配置，必须在配置中设置此属性 | Name property of the OMI_ConfigurationDocument instance has not been set. To use partial configurations, this property must be set in the configuration |
| 1518 | 合并部分配置文件时出错。 | There was an error while merging the partial configuration files. |
| 1519 | 序列化实例时出错。 | There was an error while serializing the instance. |
| 1520 | 写入到文件 %1!s! 时出错。 | There was an error while writing into the file %1!s!. |
| 1521 | 在配置文档中，至少有一个资源所包含的配置名称不等同于部分配置名称 %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. |
| 1522 | 配置文档中的部分配置名称 %1!s! 无效。请在元配置中定义一个采用此部分配置名称的部分配置，以便能够使用该名称。 | 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. |
| 1523 | 元配置文档中未定义任何部分配置。请创建部分配置实例，然后重试。 | There is no partial configuration defined inside the metaconfiguration document. Create partial configuration instances and try again. |
| 1524 | 提供的配置包含类名称 %1!s! 的无效资源实例，因为该实例中没有名为 ConfigurationName 的字段。若要将此配置用作部分配置，必须在每个资源中定义配置名称字段，并且该资源的名称应该与 OMI_ConfigurationDocument 实例的名称字段匹配。 | The 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. |
| 1525 | 合并部分配置失败。 | Merging of partial configurations failed. |
| 1526 | 在运行 %2!s! 功能时，WMIv2 DSC 资源 %1!s! 引发了一个或多个非终止错误。这些错误已记录到 ETW 通道 Microsoft-Windows-DSC/Operational。请参阅此通道以了解更多详细信息。 | 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. |
| 1527 | 发现独占资源 %1!s! 的定义有冲突。“独占资源”字段的值可以是无法由其他任何部分配置重复使用的资源名称。请更正此名称重复错误，然后重试。 | 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. |
| 1528 | 部分配置中提到的下载管理器 %1!s! 未在元配置中定义或未正确分配。请检查下载管理器并将 ResourceRepositoryWeb 或 ResourceRepositoryShare 分配到 ResourceModuleSource 和 ConfigurationRepositoryWeb，或者将 ConfigurationRepositoryShare 分配到 ConfigurationSource。 | The 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. |
| 1529 | 部分配置 %1!s! 无法使用 %2!s! 资源，该资源由其他部分配置以独占方式保留。请要么更正元配置以删除此资源，要么不在此部分配置中使用此独占资源。 | 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. |
| 1530 | 已将配置文档保存到部分配置存储中。 | Saved configuration document into the partial configuration store. |
| 1531 | 部分配置 %1!s! 依赖于另外某个不存在的部分配置。在找到此部分配置所依赖的部分配置之前，将不会设置此部分配置。 | 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. |
| 1532 | 应用部分配置 %1!s! 时出错。错误消息为: %2!s!。 |
An error occured while applying the partial configuration %1!s!. The error message is : %2!s!. |
| 1533 | 在存储中找不到元配置中定义的任何部分配置。要么是尚未从服务器中提取这些配置(对于提取刷新模式)，要么是尚未将这些配置发布到存储(对于推送刷新模式)。 | 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). |
| 1534 | 无法应用一个或多个部分配置。无法创建任何配置。 | One or more partial configurations failed to apply. No configuration could be created. |
| 1535 | 资源实例的格式不正确。查找类名称时出错。 | The resource instance is not formed correctly. Error in finding the classname. |
| 1536 | 资源 %1!s! 中的模块名称属性未定义。请使用相应的 powershell 文件重新生成 MOF，或者在资源实例中添加模块名称属性。 | 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. |
| 1537 | 未使用任何允许的格式编写部分配置 %2!s! 的独占资源字符串 %1!s!。可以使用 ModuleName\ResourceName、ModuleName\* 或 ResourceName 格式编写独占资源 | 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 |
| 1538 | 正在删除无效的部分配置文件 %1!s!。原因: %2!s! | Deleting the invalid partial configuration file %1!s!. Reason: %2!s! |
| 1539 | 将跳过部分配置文件 %1!s!。原因: %2!s! | The partial configuration file %1!s! will be skipped. Reason: %2!s! |
| 1540 | 位置 $env:windir/system32/configuration/partialconfigurations 处不存在该部分配置目录。LCM 无法重新创建此目录。请暂停所有 DSC 操作或重新创建此目录，使部分配置功能正常工作。 | 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. |
| 1541 | 位置 $env:windir/system32/configuration/configurationstatus 处不存在该配置状态目录。LCM 无法重新创建此目录。请暂停所有 DSC 操作或重新创建此目录，使配置状态功能正常工作。 | 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. |
| 1542 | LCM 无法记录操作的配置状态: %1!s! | LCM failed to record the configuration status for operation: %1!s! |
| 1543 | LCM 无法检索文件的配置状态: %1!s! | LCM failed to retrieve the configuration status for file: %1!s! |
| 1544 | 在重新启动计算机之前，请求将无法继续。 | The request cannot continue until the machine is rebooted. |
| 1545 | 若要手动接收剩余的输出，请执行: Connect-DscConfiguration -InstanceId '%1!s!' -Bookmark '%2!s!' -ComputerName %3!s! -Verbose -Wait | To manually receive the remaining output, execute: Connect-DscConfiguration -InstanceId '%1!s!' -Bookmark '%2!s!' -ComputerName %3!s! -Verbose -Wait |
| 1546 | 删除同名的旧部分配置时出错。请运行带有 -Force 选项的 Stop-DSCConfiguration 以停止执行所有挂起的 DSC 操作，然后重试。 | 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. |
| 1547 | 在挂起的存储中保存部分配置文件时出错。请运行带有 -Force 选项的 Stop-DSCConfiguration 以停止执行所有挂起的 DSC 操作，然后重试。 | 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. |
| 1549 | 无法初始化元配置。 | Could not initialize the Meta Configuration. |
| 1550 | 无法构造 GetConfigurationStatus 函数的输出对象。 | Could not construct the output object for the GetConfigurationStatus function. |
| 1551 | 无法设置 GetConfigurationStatus 函数的返回结果。 | Could not set return for GetConfigurationStatus function. |
| 1552 | 发布 GetConfigurationStatus 的输出未成功。 | Posting output for GetConfigurationStatus did not succeed. |
| 1553 | 设置一致性检查的线程优先级未成功。 | Setting the thread priority for consistency check did not succeed. |
| 1554 | 在“拉”服务器上找不到更新的配置，因此不执行任何操作。请确保目标节点的“拉”服务器上存在具有不同校验和的配置。 | 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. |
| 1555 | 未尝试从“拉”服务器获取配置，因为 LCM RefreshMode 当前设置为“推”。 | No attempt was made to get a configuration from the pull server because LCM RefreshMode is currently set to Push. |
| 1556 | 在重新启动后应用配置已停止，因为元配置 MOF 设置 ActionAfterReboot 设置为 StopConfiguration。 | Applying the configuration after reboot is stopped because the meta configuration mof setting ActionAfterReboot is set to StopConfiguration. |
| 1557 | 无法初始化配置和刷新间隔。请使用默认值。 | Configuration and refresh intervals could not be initialized. Using the default values. |
| 1558 | %2!s! 模式中不支持 %1!s! cmdlet。请将 LCM RefreshMode 设置为 %3!s!。 | %1!s! cmdlet is not supported in %2!s! mode. Please set the LCM RefreshMode to %3!s!. |
| 1559 | 将针对挂起的配置执行 GET 操作，因为最新的配置尚未聚合。 | The GET operation will be carried against a pending configuration since the latest configuration has not converged yet. |
| 1560 | 将针对挂起的配置执行 TEST 操作，因为最新的配置尚未聚合。 | The TEST operation will be carried against a pending configuration since the latest configuration has not converged yet. |
| 1561 | 配置文档正在发布为挂起状态。 | Configuration document is being published to pending state. |
| 1562 | LCM 状态由非 DSC 操作进行更改。如果你想要更改 LCM 的状态，请使用 Remove-DscConfigurationDocument cmdlet。 | LCM state is changed by non-DSC operations. If you wish to change the state of LCM, please use Remove-DscConfigurationDocument cmdlet. |
| 1563 | 无法加密文件“%1!s!” | Failed to encrypt file '%1!s!' |
| 1564 | 无法解密文件“%1!s!” | Failed to decrypt file '%1!s!' |
| 1601 | 删除当前配置文件时遇到错误。 | An error was encountered while deleting the current configuration file. |
| 1602 | 删除挂起的配置文件时遇到错误。 | An error was encountered while deleting the pending configuration file. |
| 1603 | 删除以前的配置文件时遇到错误。 | An error was encountered while deleting the previous configuration file. |
| 1604 | -Force 选项与 Stop 操作一起指定。当前配置已成功取消。 | The -Force option was specified with the Stop operation. The current configuration has been successfully cancelled. |
| 1613 | 当前的配置文档已删除 | Configuration document Current was removed |
| 1614 | 挂起的配置文档已删除 | Configuration document Pending was removed |
| 1615 | 以前的配置文档已删除 | Configuration document Previous was removed |
| 1616 | 本地配置管理器未找到任何要删除的当前配置。 | The Local Configuration Manager did not find any current configuration to remove. |
| 1617 | 本地配置管理器未找到任何要删除的挂起配置。 | The Local Configuration Manager did not find any pending configuration to remove. |
| 1618 | 本地配置管理器未找到任何要删除的以前的配置。 | The Local Configuration Manager did not find any previous configuration to remove. |
| 1619 | 当前没有运行的操作。停止操作将返回而不执行任何操作。 | There is no operation running currently. Stop will return without any action. |
| 1620 | 该配置已成功停止。 | The configuration was successfully stopped. |
| 1621 | Stop-DscConfiguration 正在尝试在当前资源执行完毕后停止当前配置。在控制台返回后，就会取消配置。若要立即停止，请将 -Force 选项与 Stop-DscConfiguration cmdlet 一起使用。 | 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. |
| 1622 | 删除部分配置文件时遇到错误。 | An error was encountered while deleting partial configuration files. |
| 1623 | 部分配置文档已删除 | Partial configuration documents were removed |
| 1624 | 本地配置管理器找不到任何要删除的部分配置。 | The Local Configuration Manager did not find any partial configurations to remove. |
| 1625 | 删除配置校验和文件时遇到错误。 | An error was encountered while deleting the configuration checksum file. |
| 1626 | 已删除配置校验和文件 | Configuration checksum file was removed |
| 1627 | 本地配置管理器找不到要删除的配置校验和文件。 | The Local Configuration Manager did not find configuration checksum file to remove. |
| 1628 | 将在目标节点上还原以前的配置。 | The previous configuration will be restored on target node. |
| 1629 | Enable-DscDebug 需要 BreakAll 参数。 | The Enable-DscDebug need BreakAll parameter. |
| 1630 | 删除配置状态缓存文件时遇到错误。 | An error was encountered while deleting the configuration state cache file. |
| 1631 | 已删除配置状态缓存。 | Configuration state cache was removed. |
| 1632 | 本地配置管理器未找到任何可删除的配置状态缓存。 | The Local Configuration Manager did not find any configuration state cache to remove. |
| 1701 | LCM 版本 %2!s! 无法处理版本为 %1!s! 的配置文档，因为 MinimumCompatibleVersion 值为 %3!s!。要使文档与此 LCM 兼容，应将 OMI_ConfigurationDocument 实例的属性 minimumCompatibleVersion 设为 %2!s!。请重新生成配置文档以更新 MinimumCompatibleVersion 属性，或者升级这台计算机上运行的 DSC 版本。 | 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. |
| 1702 | LCM 版本 %2!s! 无法处理版本为 %1!s! 的配置文档，因为 MinimumCompatibleVersion 属性未定义。要使文档与此 LCM 兼容，应将 OMI_ConfigurationDocument 实例的属性 minimumCompatibleVersion 设为 %2!s!。请重新生成配置文档以包括 MinimumCompatibleVersion 属性，或者升级这台计算机上运行的 DSC 版本。 | 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. |
| 1703 | LCM 无法处理 OMI_ConfigurationDocument 实例中的 CompatibleVersionAdditionalProperties 值。请重新生成配置文档，然后重试。 | LCM cannot process the CompatibleVersionAdditionalProperties value in the OMI_ConfigurationDocument instance. Regenerate the configuration document, and then try again. |
| 1704 | OMI_ConfigurationDocument 实例的属性 CompatibleVersionAdditionalProperties 只能接受字符串数组类型的值。由于配置文档包含的此属性的值无效，LCM 无法处理 OMI_ConfigurationDocument 实例。请重新生成配置文档，然后重试。 | The 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. |
| 1751 | LCM 将发布配置。 | LCM is publishing a configuration. |
| 1752 | LCM 将应用新配置。 | LCM is applying a new configuration. |
| 1753 | LCM 将应用现有配置。 | LCM is a applying an existing configuration. |
| 1754 | LCM 将还原以前的配置。 | LCM is restoring a previous configuration. |
| 1755 | LCM 将针对配置测试节点。 | LCM is testing node against the configuration. |
| 1756 | LCM 将获取配置。 | LCM is getting a configuration. |
| 1757 | LCM 将执行一致性检查。 | LCM is performing a consistency check. |
| 1758 | LCM 将在上次重新启动后继续应用配置。 | LCM is continuing applying configuration after last reboot. |
| 1759 | LCM 将在“拉”服务器上检查并应用新的可用配置。 | LCM is checking and applying new available configuration on pull server. |
| 1760 | LCM 将应用新的元配置设置。 | LCM is applying a new meta configuration setting. |
| 1761 | LCM 将检索配置状态历史记录。 | LCM is retriving configuration status history. |
| 1762 | LCM 将删除配置。 | LCM is removing configurations. |
| 1763 | LCM 正在启用 DSC 资源脚本调试。 | LCM is enabling DSC resource scripts debugging. |
| 1764 | LCM 正在禁用 DSC 资源脚本调试。 | LCM is disabling DSC resource scripts debugging. |
| 1765 | LCM 正在执行 DSC 资源方法。 | LCM is executing DSC resource method. |
| 1801 | 正在执行 Get-Action，配置 %1!s! 的校验和为 %2!s!。 | Executing Get-Action with configuration %1!s!'s checksum: %2!s!. |
| 1802 | 正在执行 Get-Action，配置 %1!s! 的校验和返回结果状态 %2!s!。 | Executing Get-Action with configuration %1!s!'s checksum returned result status: %2!s!. |
| 1803 | 校验和不同。LCM 将执行 GetConfiguration 以拉取配置 %1!s!。 | Checksum is different. LCM will execute GetConfiguration to pull configuration %1!s!. |
| 1805 | 执行 GetConfiguration 成功。已从服务器拉取配置 %1!s!。 | Executing GetConfiguration succeeded. Configuration %1!s! was pulled from server. |
| 1806 | 执行 GetConfiguration 失败。未拉取配置 %1!s!。 | Executing GetConfiguration failed. Configuration %1!s! is not pulled. |
| 1807 | 正在应用已拉取的新配置。 | Applying the new configuration(s) pulled. |
| 1808 | 执行具有配置 %1!s! 的校验和的 Get-Action 失败。请检查“拉”服务器的可用性。 | Executing Get-Action with configuration %1!s!'s checksum failed. Please check the availability of pull server. |
| 1809 | 如果校验和不匹配则从“拉”服务器上“拉”配置，并在目标节点上应用配置。 | Pull Configuration(s) from the pull server if checksum do not match and apply configuration(s) on target node. |
| 1810 | 注册 Dsc 代理未返回任何状态。 | Registering Dsc Agent didn't return any status. |
| 1811 | 注册 Dsc 代理未返回预期的状态。 | Registering Dsc Agent did not return the expected status. |
| 1812 | 无法为 Dsc 代理注册生成 AgentId。 | Unable to generate AgentId for Registration of Dsc Agent. |
| 1813 | 不能同时指定属性 ConfigurationNames 和 ConfigurationID。请删除其中之一，然后重试。 | The properties ConfigurationNames and ConfigurationID cannot be specified together. Please remove one of them and try again. |
| 1814 | ServerUrl 是 Dsc 代理注册元配置中的必需项。 | A ServerUrl is required in the metaconfiguration for Registration of Dsc Agent. |
| 1815 | 将 Dsc 代理注册到服务器 %1!s! 成功。 | Registration of the Dsc Agent with the server %1!s! was successful. |
| 1816 | 将 Dsc 代理注册到服务器 %1!s! 失败。基础错误为: %2!s!。 | Registration of the Dsc Agent with the server %1!s! failed. The underlying error is: %2!s! . |
| 1817 | 对部分配置“%1!s!”执行 Get-Action 失败。请确保部分配置及其校验和在服务器上存在。请查看 DSC 事件日志，了解更多详细信息。 | 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. |
| File Description: | DSC |
| File Version: | 10.0.15063.0 (WinBuild.160101.0800) |
| Company Name: | Microsoft Corporation |
| Internal Name: | DscCore.dll |
| Legal Copyright: | © Microsoft Corporation. All rights reserved. |
| Original Filename: | DscCore.dll.mui |
| Product Name: | Microsoft® Windows® Operating System |
| Product Version: | 10.0.15063.0 |
| Translation: | 0x804, 1200 |