| File name: | DscCore.dll.mui |
| Size: | 49664 byte |
| MD5: | 3b0d5f433f785a2fb4320c6bb5903749 |
| SHA1: | 617d3fa965d3b9f69f19b2db58bba5dfbb8fbc3c |
| SHA256: | 4df80673027c093839d310afcea17e4a2b7a8a992a464140f00b66278c4d218d |
| Operating systems: | Windows 10 |
| Extension: | MUI |
If an error occurred or the following message in Chinese (Traditional) 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 (Traditional) | 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 | 用來尋找憑證的憑證識別碼。 | The certificate ID used to locate the certificate. |
| 346 | 用來從提取伺服器取得設定的設定識別碼。 | 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 | 用來尋找安全連線憑證的憑證識別碼。 | The certificate ID used to locate the certificate for secure connections. |
| 527 | 指定報表管理員是否可以使用透過 http 的不安全連線。 | Specifies whether report manager can use unsecure connection over http. |
| 533 | 資源執行個體的唯一識別碼。 | 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 | 所有中繼設定資源的基本架構。 | 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 | 與設定關聯的「工作識別碼」。 | 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 | 自由格式字串，在 ErrorType 指定為 1 (「其他」) 時提供 ErrorType 的說明。 | 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 預期狀態設定」無法使用 Mofcomp.exe 登錄 MOF 檔案 %1!s! (於探索 %2!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 是空值。 | ModuleLoader is null. |
| 1125 | 載入「本機設定管理員」設定結構描述失敗。 | Loading the Local Configuration Manager settings schema did not succeed. |
| 1126 | Metaschema 載入傳回空值。 | 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 | 收到來自電腦 %1!s!，使用者 SID %2!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 中設定資源識別碼。請嘗試重新執行操作。 | 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 處理進行設定時，已要求 PUSH 操作 (未搭配 -Force)。 | 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 參數不能是空值。 | 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 參數不能是空值。 | 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 參數不能是空值。 | 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 參數不能是空值。 | 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 屬性。請使用已登錄的 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 | 當沒有部分設定時，在中繼設定文件的 2.0.0 版本中，DSC 本機設定管理員只支援一個設定存放庫的執行個體。因為已定義多個設定存放庫，因此 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 | 已使用版本 %3!s! 與版本 %4!s! 匯入兩次來自模組 %2!s! 的資源 %1!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 | 目前的重新整理模式是 PULL，但未定義設定下載管理員。 | The current refresh mode is PULL but there are no configuration download managers defined. |
| 1301 | 無法使用空值執行個體參數解析相依性。請確認執行個體不是空值。 | 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 不能是空值。 | 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 | MI_Instance_GetElement 的 ReturnValue 失敗。 | MI_Instance_GetElement failed for ReturnValue. |
| 1315 | MI_Instance_GetElement 在 Result 參數上傳回錯誤。 | MI_Instance_GetElement returned an error on the Result parameter. |
| 1316 | MI_Instance_GetElement 的 ProviderContext 方法參數失敗。 | MI_Instance_GetElement failed for ProviderContext method parameter. |
| 1317 | MI_Instance_GetElement 對於設定的 Method 參數不成功。 | 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 | 執行個體文件中指定的資源有循環相依性。請檢查並更正執行個體 %1!s! 的 Requires 屬性 (定義於 %2!s!)，然後再試一次。 | 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 可能不正確。請更正執行個體 %2!s! (定義於 %3!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 | 憑證識別碼無效: '%1!s!' | The Certificate ID is not valid: '%1!s!' |
| 1370 | %2!s! 於 %1!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 |
| 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 | 可在 Push 模式中使用 DSC 部分設定的唯一方式是使用 Publish-DscConfiguration Cmdlet。不支援其他 Push 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 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 | WMIv2 DSC 資源 %1!s! 在執行 %2!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 | 已移除設定文件 Current | Configuration document Current was removed |
| 1614 | 已移除設定文件 Pending | Configuration document Pending was removed |
| 1615 | 已移除設定文件 Previous | 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 | 目前沒有執行中的操作。Stop 將返回，而不會執行任何動作。 | 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 | 版本為 %1!s! 的設定文件無法由 LCM 版本 %2!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 | 版本為 %1!s! 的設定文件無法由 LCM 版本 %2!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 | 正在使用設定 %1!s! 的總和檢查碼執行 Get-Action: %2!s!。 | Executing Get-Action with configuration %1!s!'s checksum: %2!s!. |
| 1802 | 使用設定 %1!s! 的總和檢查碼執行 Get-Action 已傳回結果狀態: %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 | Dsc 代理程式之登錄的中繼設定中需要 ServerUrl。 | A ServerUrl is required in the metaconfiguration for Registration of Dsc Agent. |
| 1815 | 向伺服器 %1!s! 登錄 Dsc 代理程式的作業成功。 | Registration of the Dsc Agent with the server %1!s! was successful. |
| 1816 | 向伺服器 %1!s! 登錄 Dsc 代理程式的作業失敗。底層錯誤是: %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: | 0x404, 1200 |