pcsvDevice.dll.mui 裝置的 PCSV Proxy 提供者 cf635f3ef31caa406b402f09be58f622

File name:	pcsvDevice.dll.mui
Size:	59904 byte
MD5:	cf635f3ef31caa406b402f09be58f622
SHA1:	911341b06fe20400f34d304ba34677d98b735aed
SHA256:	884d8fe8890f50a26b1cdfdc5eca82acba92bf50674ac8e22cdb4b86abee36db
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
1	InstanceID 是一個選擇性屬性，可在具現化命名空間的領域內，用來隱晦且唯一地識別此類別的執行個體。此類別的各種子類別可以覆寫此屬性以將它設為必要或設為機碼。這類子類別也可以修改偏好的演算法，以確保下面定義的唯一性。 為確保在命名空間中的唯一性，應該使用下列「偏好的」演算法來建構 InstanceID 的值: : 其中 和 是由冒號 (:) 分隔，而 必須包含建立或定義 InstanceID 之企業實體所擁有的著作權化、商標化或其他方面的唯一名稱，或此唯一名稱是由知名全球授權單位指派給企業實體的註冊識別碼。(此要求條件類似於結構描述類別名稱的 _ 結構)。此外，為確保唯一性， 不能包含冒號 (:)。使用此演算法時，InstanceID 中顯示的第一個冒號必須顯示在 與 之間。 是由企業實體所選擇，不應被重複用來識別不同的基礎 (真實世界) 元素。如果不是 Null 且未使用上述「偏好的」演算法，定義實體必須確保產生的 InstanceID 不會被重複用於此執行個體之命名空間的這個提供者或其他提供者所產生的任何 InstanceID。 如果未針對 DMTF 定義的執行個體設為 Null，則使用「偏好的」演算法時，必須將 設為 CIM。	InstanceID is an optional property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace. Various subclasses of this class may override this property to make it required, or a key. Such subclasses may also modify the preferred algorithms for ensuring uniqueness that are defined below. To ensure uniqueness within the NameSpace, the value of InstanceID should be constructed using the following "preferred" algorithm: : Where and are separated by a colon (:), and where must include a copyrighted, trademarked, or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID or that is a registered ID assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness, must not contain a colon (:). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be reused to identify different underlying (real-world) elements. If not null and the above "preferred" algorithm is not used, the defining entity must assure that the resulting InstanceID is not reused across any InstanceIDs produced by this or other providers for the NameSpace of this instance. If not set to null for DMTF-defined instances, the "preferred" algorithm must be used with the set to CIM.
2	Caption 屬性是物件的簡短文字描述 (單行字串)。	The Caption property is a short textual description (one- line string) of the object.
3	Description 屬性提供物件的文字描述。	The Description property provides a textual description of the object.
4	物件的使用者易記名稱。此屬性除了允許每個執行個體定義其機碼屬性、身分識別資料及描述資訊之外，還允許定義使用者易記名稱。 請注意，ManagedSystemElement 的 Name 屬性也被定義為使用者易記名稱。但是，它通常被細分成子類別而當作 Key。同一個屬性不太可能可以同時表達身分識別和使用者易記名稱，而又不產生矛盾。當 Name 存在且不是 Key (例如，LogicalDevice 的執行個體) 時，相同的資訊可同時存在於 Name 與 ElementName 屬性中。請注意，如果有關聯的 CIM_EnabledLogicalElementCapabilities 執行個體，此屬性可能會有限制 (如該類別中定義之 ElementNameMask 與 MaxElementNameLen 屬性所定義)。	A user-friendly name for the object. This property allows each instance to define a user-friendly name in addition to its key properties, identity data, and description information. Note that the Name property of ManagedSystemElement is also defined as a user-friendly name. But, it is often subclassed to be a Key. It is not reasonable that the same property can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and is not a Key (such as for instances of LogicalDevice), the same information can be present in both the Name and ElementName properties. Note that if there is an associated instance of CIM_EnabledLogicalElementCapabilities, restrictions on this properties may exist as defined in ElementNameMask and MaxElementNameLen properties defined in that class.
5	2.19.0	2.19.0
6	ManagedElement 是抽象類別，它為 CIM 架構中的非關聯類別提供通用 Superclass (或繼承樹狀結構的頂層)。	ManagedElement is an abstract class that provides a common superclass (or top of the inheritance tree) for the non-association classes in the CIM Schema.
7	View 是一個抽象類別，可為提供受管理資源之取消正規化、彙總表示法的類別提供一個一般 Superclasss。每個子類別的定義將包含從類別 (用來在正規化檢視中建立資源模型) 的圖形傳播的屬性。這些類別可以是資源類別或關聯。必須指定值傳播方式 (亦即資源類別和值的轉換) 的定義。 可以將子類別明確限制為唯讀。如果未將子類別限制為唯讀，設計人員就必須謹慎考慮可能會發生資料同步和一致性問題。ElementView 關聯可用來找出構成受管理資源之正規化檢視的執行個體。	View is an abstract class that provides a common superclass for classes providing de-normalized, aggregate representations of managed resources. The definition of each sub-class will include properties propagated from the the graph of classes that are used to model the resource in the normalized view. The classes may be resource classes or associations. The definition of how a value is propagated (i.e. source class and value transformations) is required to be specified. Sub-classes may be explicitly constrained to be read only. If a sub-class is not constrained as read only, the designers are strongly encouraged to carefully consider the data synchronization and consistencies issues that may result. The ElementView association may be used to find the instances that form the normalized view of the managed resource.
8	2.26.0	2.26.0
9	一個指示物件安裝時間的日期時間值。沒有值並不表示物件尚未安裝。	A datetime value that indicates when the object was installed. Lack of a value does not indicate that the object is not installed.
10	Name 屬性可定義用來識別物件的標籤。設定為子類別時，Name 屬性可被覆寫成 Key 屬性。	The Name property defines the label by which the object is known. When subclassed, the Name property can be overridden to be a Key property.
11	指示元素的目前狀態。已定義各種操作狀態。許多列舉值的意義都可透過其名稱得知。不過，一些列舉值並非如此，這裡提供這些列舉值的詳細描述。 「負荷過高」表示元素運作中，但需要注意。「負荷過高」狀態的範例包括多載、過熱等等。 「預期將失敗」表示元素名義上是運作中，但預期不久後將失敗。 「服務中」描述正在設定、維護、清除或管理元素。 「無法連絡」表示監控系統知道此元素，但是從未能夠與其建立通訊。 「通訊中斷」表示已知 ManagedSystem Element 存在，而且過去系統曾順利與其聯繫，但目前無法與其聯繫。 「 已停止」與「已中止」類似，但前者意味著徹底且循序的停止，而後者意味著意外停止 (可能需要更新元素的狀態與設定)。 「休眠」表示元素為非作用中或已靜止。 「支援實體發生錯誤」表示此元素可能「狀況良好」，但它所依存的另一個元素發生錯誤。例如，因為低層的網路問題而無法運作的網路服務或端點。 「已完成」表示元素已完成其操作。此值應該與「狀況良好」、「錯誤」或「已降級」結合，以便用戶端可以判斷整個操作的狀態是「已完成且狀況良好」(通過)、「已完成但發生錯誤」(失敗) 或「已完成但已降級」(操作完成，但狀態並非「狀況良好」或未回報錯誤)。 「電源模式」表示元素在 Associated PowerManagementService 關聯中包含額外的電源模式資訊。 OperationalStatus 會取代 ManagedSystemElement 的 Status 屬性以提供一致的方法給列舉、滿足陣列屬性的實作需求，以及提供一條從現今環境到未來環境的移轉途徑。因為此變更需要已過時的限定詞，所以先前未能進行。由於現有的 Status 屬性已在管理應用程式中廣泛使用，我們強烈建議提供者或檢測設備同時提供 Status 與 OperationalStatus 屬性。此外，OperationalStatus 的第一個值應該包含元素的主要狀態。檢測之後，Status (因為它是單一值屬性) 也應該提供元素的主要狀態。	Indicates the current statuses of the element. Various operational statuses are defined. Many of the enumeration\'s values are self-explanatory. However, a few are not and are described here in more detail. "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning nominally but predicting a failure in the near future. "In Service" describes an element being configured, maintained, cleaned, or otherwise administered. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the ManagedSystem Element is known to exist and has been contacted successfully in the past, but is currently unreachable. "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Power Mode" indicates that the element has additional power model information contained in the Associated PowerManagementService association. OperationalStatus replaces the Status property on ManagedSystemElement to provide a consistent approach to enumerations, to address implementation needs for an array property, and to provide a migration path from today\'s environment to the future. This change was not made earlier because it required the deprecated qualifier. Due to the widespread use of the existing Status property in management applications, it is strongly recommended that providers or instrumentation provide both the Status and OperationalStatus properties. Further, the first value of OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is single-valued) should also provide the primary status of the element.
12	不明	Unknown
13	其他	Other
14	良好	OK
15	已降級	Degraded
16	負荷過高	Stressed
17	預期將失敗	Predictive Failure
18	錯誤	Error
19	無法修復的錯誤	Non-Recoverable Error
20	正在啟動	Starting
21	正在停止	Stopping
22	已停止	Stopped
23	服務中	In Service
24	無法連絡	No Contact
25	通訊中斷	Lost Communication
26	已中止	Aborted
27	休眠	Dormant
28	支援實體發生錯誤	Supporting Entity in Error
29	已完成	Completed
30	電源模式	Power Mode
31	DMTF 保留	DMTF Reserved
32	廠商保留	Vendor Reserved
33	描述各種 OperationalStatus 陣列值的字串。例如，如果指派給 OperationalStatus 的值為「正在停止」，則此屬性可能包含有關為何將物件停止的解釋。請注意，此陣列中的項目與 OperationalStatus 中位於相同陣列索引的項目相互關聯。	Strings describing the various OperationalStatus array values. For example, if "Stopping" is the value assigned to OperationalStatus, then this property may contain an explanation as to why an object is being stopped. Note that entries in this array are correlated with those at the same array index in OperationalStatus.
34	指出物件之目前狀態的字串。已定義各種操作與非操作狀態。此屬性已過時而被 OperationalStatus 取代，OperationalStatus 在其列舉中包含相同的語意。做出此變更的原因有三: 1) 以陣列的形式可更為正確地定義狀態。當狀態實際為多重值屬性 (例如，元素狀態可能為「狀況良好」與「已停止」)，此定義可克服使用單一值來描述狀態的限制。 2) MaxLen 為 10 的限制太多，會導致列舉值不清楚。 3) 在定義 CIM V2.0 時已討論對 uint16 資料類型的變更。不過，現有的 V1.0 實作已使用該字串屬性，而且不想修改其程式碼。因此，Status 被加入到 Schema 中當作祖項。使用過時的限定詞不僅可以維護現有的屬性，還可以允許使用 OperationalStatus 來改進定義。	A string indicating the current status of the object. Various operational and non-operational statuses are defined. This property is deprecated in lieu of OperationalStatus, which includes the same semantics in its enumeration. This change is made for 3 reasons: 1) Status is more correctly defined as an array. This definition overcomes the limitation of describing status using a single value, when it is really a multi-valued property (for example, an element might be OK AND Stopped. 2) A MaxLen of 10 is too restrictive and leads to unclear enumerated values. 3) The change to a uint16 data type was discussed when CIM V2.0 was defined. However, existing V1.0 implementations used the string property and did not want to modify their code. Therefore, Status was grandfathered into the Schema. Use of the deprecated qualifier allows the maintenance of the existing property, but also permits an improved definition using OperationalStatus.
35	指示元素的目前健康情況。此屬性表示此元素的健康情況，但不一定表示其子元件的健康情況。可能的值介於 0 到 30 之間，其中 5 表示元素健康情況十分良好，而 30 表示元素完全無法運作。連續體定義如下: 「無法修復的錯誤」(30) - 元素完全失敗，而且無法修復。此元素提供的所有功能皆已喪失。 「嚴重失敗」(25) - 元素無法運作，而且可能無法修復。 「主要失敗」(20) - 元素失敗。此元件的部分或所有功能可能被降級或無法運作。 「次要失敗」(15) - 所有功能都能使用，但某些功能可能被降級。 「已降級/警告」(10) - 元素正常運作，並且提供所有功能。不過，元素未全力運作。例如，元素可能未以最佳效能運作，或可能回報可修復的錯誤。 「狀況良好」(5) - 元素完全發揮功能並且在正常操作參數內運作，而且沒有錯誤。 「不明」(0) - 實作目前無法回報健康情況。 DMTF 已保留連續體的未使用部分，以供未來額外的健康情況使用。	Indicates the current health of the element. This attribute expresses the health of this element but not necessarily that of its subcomponents. The possible values are 0 to 30, where 5 means the element is entirely healthy and 30 means the element is completely non-functional. The following continuum is defined: "Non-recoverable Error" (30) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost. "Critical Failure" (25) - The element is non-functional and recovery might not be possible. "Major Failure" (20) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working. "Minor Failure" (15) - All functionality is available but some might be degraded. "Degraded/Warning" (10) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors. "OK" (5) - The element is fully functional and is operating within normal operational parameters and without error. "Unknown" (0) - The implementation cannot report on HealthState at this time. DMTF has reserved the unused portion of the continuum for additional HealthStates in the future.
36	已降級/警告	Degraded/Warning
37	次要失敗	Minor failure
38	主要失敗	Major failure
39	嚴重失敗	Critical failure
41	CommunicationStatus 可指示檢測設備與基礎 ManagedElement 通訊的能力。CommunicationStatus 的可能值包括: 不明、無、通訊狀況良好、通訊中斷或無法連絡。 傳回 Null 值表示實作 (提供者) 未實作此屬性。 「不明」 表示實作一般可以傳回此屬性，但目前無法這樣做。 「無法使用」表示實作 (提供者) 可以傳回此屬性的值，但從未針對此特定硬體/軟體這樣做，或刻意不使用此屬性，因為它不會新增任何有意義的資訊 (就像刻意使用一個屬性來為另一個屬性新增額外資訊的情況)。 「通訊狀況良好」表示已與元素建立通訊，但無法提供任何服務品質。 「無法連絡」表示監控系統知道此元素，但從未能夠與其建立通訊。 「通訊中斷」表示已知 Managed Element 存在，而且過去系統曾順利與其聯繫，但目前無法與其聯繫。	CommunicationStatus indicates the ability of the instrumentation to communicate with the underlying ManagedElement. CommunicationStatus consists of one of the following values: Unknown, None, Communication OK, Lost Communication, or No Contact. A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Communication OK " indicates communication is established with the element, but does not convey any quality of service. "No Contact" indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it. "Lost Communication" indicates that the Managed Element is known to exist and has been contacted successfully in the past, but is currently unreachable.
42	無法使用	Not Available
43	通訊狀況良好	Communication OK
44	DetailedStatus 透過額外的狀態詳細資料彌補 PrimaryStatus 的不足。可能的值如下: 無法使用、沒有額外資訊、負荷過高、預期將失敗、錯誤、無法修復的錯誤、支援實體發生錯誤。詳細狀態是用來在元素的 PrimaryStatus 上展開。 傳回 Null 值表示實作 (提供者) 未實作此屬性。 「無法使用」表示實作 (提供者) 可以傳回此屬性的值，卻無法傳回此特定軟硬體的值，或者因為屬性會新增無意義的資訊 (例如刻意新增額外資訊至另一個屬性) 而刻意不使用此屬性。 「沒有額外資訊」表示元素正常運作中，如 PrimaryStatus = "狀況良好" 所指示。 「負荷過高」表示元素運作中，但需要注意。「負荷過高」狀態的範例包括多載與過熱等。 「預期將失敗」表示元素正常運作中，但預期不久後將失敗。 「無法修復的錯誤」表示此元素發生需要人為介入的錯誤情況。 「發生錯誤的支援實體」表示此元素的狀態可能是「狀況良好」，但它所依存的另一個元素發生錯誤。例如，因為低層的網路問題而無法運作的網路服務或端點。	DetailedStatus compliments PrimaryStatus with additional status detail. It consists of one of the following values: Not Available, No Additional Information, Stressed, Predictive Failure, Error, Non-Recoverable Error, SupportingEntityInError. Detailed status is used to expand upon the PrimaryStatus of the element. A Null return indicates the implementation (provider) does not implement this property. "Not Available" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "No Additional Information" indicates that the element is functioning normally as indicated by PrimaryStatus = "OK". "Stressed" indicates that the element is functioning, but needs attention. Examples of "Stressed" states are overload, overheated, and so on. "Predictive Failure" indicates that an element is functioning normally but a failure is predicted in the near future. "Non-Recoverable Error " indicates that this element is in an error condition that requires human intervention. "Supporting Entity in Error" indicates that this element might be "OK" but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems.
45	沒有額外資訊	No Additional Information
46	OperatingStatus 提供元素操作情況的目前狀態值，而且可以用來提供有關 EnabledState 值的詳細資訊。它也可以提供當元素從一個狀態轉換為另一個狀態時 (例如當元素在 EnabledState 與 RequestedState 以及其他轉換情況之間轉換時) 的轉換狀態。 OperatingStatus 的可能值包括: 不明、無法使用、服務中、正在啟動、正在停止、已停止、已中止、休眠、已完成、正在移轉、正在移出、正在移入、正在建立快照、正在關機、正在測試 傳回 Null 值表示實作 (提供者) 未實作此屬性。 「不明」 表示實作一般可以傳回此屬性，但目前無法這樣做。 「無」表示實作 (提供者) 可以傳回此屬性的值，但從未針對此特定硬體/軟體這樣做，或刻意不使用此屬性，因為它不會新增任何有意義的資訊 (就像刻意使用一個屬性來為另一個屬性新增額外資訊的情況)。 「正在服務」描述正在設定、維護、清除或管理元素。 「正在啟動」描述正在將元素初始化。 「正在停止」描述正在將元素循序停止。 「 已停止」與「已中止」類似，但前者意味著徹底且循序的停止，而後者意味著意外停止 (可能需要更新元素的狀態與設定)。 「休眠」表示元素為非作用中或已靜止。 「已完成」表示元素已完成其操作。此值應該與 PrimaryStatus 中的「狀況良好」、「錯誤」或「已降級」結合，以便用戶端可以判斷整個操作的狀態是「已完成且狀況良好」(通過)、「已完成但發生錯誤」(失敗) 或「已完成但已降級」(操作完成，但狀態並非「狀況良好」或未回報錯誤)。 「正在移轉」表示正在主機元素之間移動元素。 「正在移入」表示正在將元素移至新的主機元素。 「正在移出」表示正在將元素從主機元素移出。 「正在關機」描述元素正在進行未預期停止。 「正在測試」表示元素正在執行測試功能。 「轉換中」描述元素正處於狀態之間，亦即，元素既不完全處於其上一個狀態，也不完全處於其下一個狀態。當其他指示轉換到特定狀態的值皆不適用時，應該使用此值。 「服務中」描述元素正處於服務中且運作中的狀態。	OperatingStatus provides a current status value for the operational condition of the element and can be used for providing more detail with respect to the value of EnabledState. It can also provide the transitional states when an element is transitioning from one state to another, such as when an element is transitioning between EnabledState and RequestedState, as well as other transitional conditions. OperatingStatus consists of one of the following values: Unknown, Not Available, In Service, Starting, Stopping, Stopped, Aborted, Dormant, Completed, Migrating, Emmigrating, Immigrating, Snapshotting. Shutting Down, In Test A Null return indicates the implementation (provider) does not implement this property. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "None" indicates that the implementation (provider) is capable of returning a value for this property, but not ever for this particular piece of hardware/software or the property is intentionally not used because it adds no meaningful information (as in the case of a property that is intended to add additional info to another property). "Servicing" describes an element being configured, maintained, cleaned, or otherwise administered. "Starting" describes an element being initialized. "Stopping" describes an element being brought to an orderly stop. "Stopped" and "Aborted" are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated. "Dormant" indicates that the element is inactive or quiesced. "Completed" indicates that the element has completed its operation. This value should be combined with either OK, Error, or Degraded in the PrimaryStatus so that a client can tell if the complete operation Completed with OK (passed), Completed with Error (failed), or Completed with Degraded (the operation finished, but it did not complete OK or did not report an error). "Migrating" element is being moved between host elements. "Immigrating" element is being moved to new host element. "Emigrating" element is being moved away from host element. "Shutting Down" describes an element being brought to an abrupt stop. "In Test" element is performing test functions. "Transitioning" describes an element that is between states, that is, it is not fully available in either its previous state or its next state. This value should be used if other values indicating a transition to a specific state are not applicable. "In Service" describes an element that is in service and operational.
47	正在服務	Servicing
48	正在移轉	Migrating
49	正在移出	Emigrating
50	正在移入	Immigrating
51	正在建立快照	Snapshotting
52	正在關機	Shutting Down
53	正在測試	In Test
54	轉換中	Transitioning
55	PrimaryStatus 提供高階狀態值，目的是要對應紅色/黃色/綠色類型的狀態表示法。這應該與 DetailedStatus 搭配使用，以提供 ManagedElement 及其子元件的高階、詳細健康狀態。 PrimaryStatus 的可能值包括: 不明、狀況良好、已降級或錯誤。「不明」 表示實作一般可以傳回此屬性，但目前無法這樣做。 「狀況良好」表示 ManagedElement 正常運作中。 「已降級」表示 ManagedElement 在低於標準的狀況下運作。 「錯誤」表示 ManagedElement 發生錯誤情況。	PrimaryStatus provides a high level status value, intended to align with Red-Yellow-Green type representation of status. It should be used in conjunction with DetailedStatus to provide high level and detailed health status of the ManagedElement and its subcomponents. PrimaryStatus consists of one of the following values: Unknown, OK, Degraded or Error. "Unknown" indicates the implementation is in general capable of returning this property, but is unable to do so at this time. "OK" indicates the ManagedElement is functioning normally. "Degraded" indicates the ManagedElement is functioning below normal. "Error" indicates the ManagedElement is in an Error condition.
56	CIM_ManagedSystemElement 是系統元素階層的基底類別。系統的所有可辨別元件皆可納入此類別中。系統元件的範例包括: - 軟體元件 (例如，應用程式伺服器、資料庫及應用程式) - 作業系統元件 (例如，檔案、處理程序及執行緒) - 裝置元件 (例如，磁碟機、控制器、處理器及印表機) - 實體元件 (例如，晶片與介面卡)	CIM_ManagedSystemElement is the base class for the System Element hierarchy. Any distinguishable component of a System is a candidate for inclusion in this class. Examples of system components include: - software components such as application servers, databases, and applications - operating system components such as files, processes, and threads - device components such as disk drives, controllers, processors, and printers - physical components such as chips and cards.
57	2.22.0	2.22.0
58	CIM_LogicalElement 是代表抽象系統元件 (例如，Files、Processes 或 LogicalDevices) 之 System 的所有元件的基底類別。	CIM_LogicalElement is a base class for all the components of a System that represent abstract system components, such as Files, Processes, or LogicalDevices.
59	2.6.0	2.6.0
60	一個代表工作狀態的自由格式字串。繼承的 OperationalStatus 屬性中會反映主要狀態。JobStatus 則提供額外、實作特定的詳細資料。	A free-form string that represents the status of the job. The primary status is reflected in the inherited OperationalStatus property. JobStatus provides additional, implementation-specific details.
61	將工作提交以供執行的時間。當值為全部零值時，表示擁有元素無法回報日期和時間。因此，會將 ScheduledStartTime 和 StartTime 回報為間隔，而這些間隔是相對於要求這兩個屬性值的時間。	The time that the Job was submitted to execute. A value of all zeroes indicates that the owning element is not capable of reporting a date and time. Therefore, the ScheduledStartTime and StartTime are reported as intervals relative to the time their values are requested.
62	目前工作的排定開始時間。此時間可由實際的日期和時間來表示，或以間隔來表示，而此間隔是相對於要求此屬性的時間。當值為全部零值時，表示工作已經在執行。此屬性已過時，由更易懂的排程屬性 RunMonth、RunDay、RunDayOfWeek 及 RunStartInterval 取代它。	The time that the current Job is scheduled to start. This time can be represented by the actual date and time, or an interval relative to the time that this property is requested. A value of all zeroes indicates that the Job is already executing. The property is deprecated in lieu of the more expressive scheduling properties, RunMonth, RunDay, RunDayOfWeek, and RunStartInterval.
63	工作的實際開始時間。此時間可由實際的日期和時間來表示，或以間隔來表示，而此間隔是相對於要求此屬性的時間。請注意，JobProcessingStatistics 類別中也有此屬性。此類別是擷取週期性工作之處理資訊的必要類別，因為此單一值屬性中只能儲存「上次」執行時間。	The time that the Job was actually started. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
64	工作的持續執行時間間隔，或者如果工作已完成，則為總執行時間。請注意，JobProcessingStatistics 類別中也有此屬性。此類別是擷取週期性工作之處理資訊的必要類別，因為此單一值屬性中只能儲存「上次」執行時間。	The time interval that the Job has been executing or the total execution time if the Job is complete. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run time can be stored in this single-valued property.
65	工作的應執行次數。當值為 1 時，表示工作不是週期性，而零以外的任何值表示工作將重複發生的次數。零則表示沒有工作處理次數限制，但是工作會在 UntilTime 之後或由手動操作終止。預設的工作處理次數為一次。	The number of times that the Job should be run. A value of 1 indicates that the Job is not recurring, while any non-zero value indicates a limit to the number of times that the Job will recur. Zero indicates that there is no limit to the number of times that the Job can be processed, but that it is terminated either after the UntilTime or by manual intervention. By default, a Job is processed once.
66	工作的應執行月份。指定 0 代表一月，1 代表二月，以此類推。	The month during which the Job should be processed. Specify 0 for January, 1 for February, and so on.
67	一月	January
68	二月	February
69	三月	March
70	四月	April
71	五月	May
72	六月	June
73	七月	July
74	八月	August
75	九月	September
76	十月	October
77	十一月	November
78	十二月	December
79	月中應處理工作的日子。此屬性依據 DayOfWeek 的值會有兩種不同的解譯。其中一種情況是由 RunDay 定義月中處理工作的日子。當 DayOfWeek 為 0 時，會使用這種解譯。正整數或負整數則分別表示 RunDay 應該從月頭或月尾算起。例如，5 表示是 RunMonth 的第 5 天，而 -1 表示是 RunMonth 的最後一天。 當 RunDayOfWeek 不為 0 時，RunDay 為月中處理工作的日子，並與 RunDayOfWeek 一起定義。例如，如果 RunDay 為 15，而 RunDayOfWeek 為 Saturday，則處理工作的時間會在 RunMonth 第 15 天當天或之後的第一個星期六 (例如，該月的第三個星期六)。如果 RunDay 為 20，而 RunDayOfWeek 為 -Saturday，則表示是 RunMonth 第 20 天當天或之前的第一個星期六。如果 RunDay 為 -1，而 RunDayOfWeek 為 -Sunday，則表示是 RunMonth 的最後一個星期日。	The day in the month on which the Job should be processed. There are two different interpretations for this property, depending on the value of DayOfWeek. In one case, RunDay defines the day-in-month on which the Job is processed. This interpretation is used when the DayOfWeek is 0. A positive or negative integer indicates whether the RunDay should be calculated from the beginning or end of the month. For example, 5 indicates the fifth day in the RunMonth and -1 indicates the last day in the RunMonth. When RunDayOfWeek is not 0, RunDay is the day-in-month on which the Job is processed, defined in conjunction with RunDayOfWeek. For example, if RunDay is 15 and RunDayOfWeek is Saturday, then the Job is processed on the first Saturday on or after the 15th day in the RunMonth (for example, the third Saturday in the month). If RunDay is 20 and RunDayOfWeek is -Saturday, then this indicates the first Saturday on or before the 20th day in the RunMonth. If RunDay is -1 and RunDayOfWeek is -Sunday, then this indicates the last Sunday in the RunMonth.
80	一個與 RunDay 一起使用的正整數或負整數，用來表示一週中應處理工作的日子。將 RunDayOfWeek 設為 0 時，表示月中確切的某一天，例如 3 月 1 日。正整數 (以 Sunday、Monday... Saturday 來表示) 表示指定之 RunDay 當天或之後的星期幾。負整數 (以 -Sunday、-Monday... -Saturday 來表示) 表示 RunDay 當天或「之前」的星期幾。	A positive or negative integer used in conjunction with RunDay to indicate the day of the week on which the Job is processed. RunDayOfWeek is set to 0 to indicate an exact day of the month, such as March 1. A positive integer (representing Sunday, Monday, ..., Saturday) means that the day of week is found on or after the specified RunDay. A negative integer (representing -Sunday, -Monday, ..., -Saturday) means that the day of week is found on or BEFORE the RunDay.
81	-Saturday	-Saturday
82	-Friday	-Friday
83	-Thursday	-Thursday
84	-Wednesday	-Wednesday
85	-Tuesday	-Tuesday
86	-Monday	-Monday
87	-Sunday	-Sunday
88	ExactDayOfMonth	ExactDayOfMonth
89	Sunday	Sunday
90	Monday	Monday
91	Tuesday	Tuesday
92	Wednesday	Wednesday
93	Thursday	Thursday
94	Friday	Friday
95	Saturday	Saturday
96	午夜過後應處理工作的時間間隔。例如， 00000000020000.000000:000 表示應在本地時間或 UTC 時間 (使用 LocalOrUtcTime 屬性來辨別) 2 點或之後執行工作。	The time interval after midnight when the Job should be processed. For example, 00000000020000.000000:000 indicates that the Job should be run on or after two o\'clock, local time or UTC time (distinguished using the LocalOrUtcTime property.
97	此屬性指示 RunStartInterval 和 UntilTime 屬性中表示的值代表本地時間或 UTC 時間。使用列舉值 2「UTC 時間」，即可將時間值與全球同步。	This property indicates whether the times represented in the RunStartInterval and UntilTime properties represent local times or UTC times. Time values are synchronized worldwide by using the enumeration value 2, "UTC Time".
98	本地時間	Local Time
99	UTC 時間	UTC Time
100	工作在此時間之後即無效或應停止。此時間可由實際的日期和時間來表示，或以間隔來表示，而此間隔是相對於要求此屬性的時間。當值為全部 9 值時，表示工作可以無限地執行。	The time after which the Job is invalid or should be stopped. This time can be represented by an actual date and time, or by an interval relative to the time that this property is requested. A value of all nines indicates that the Job can run indefinitely.
101	當工作完成或失敗時要通知的使用者。	The User who is to be notified upon the Job completion or failure.
102	提交工作的使用者，或是導致建立工作的服務或方法名稱。	The User that submitted the Job, or the Service or method name that caused the job to be created.
103	指示執行工作的緊急性或重要性。數字越小，優先順序越高。請注意，JobProcessingStatistics 類別中也有此屬性。此類別是擷取會影響工作結果之設定資訊的必要類別。	Indicates the urgency or importance of execution of the Job. The lower the number, the higher the priority. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the setting information that would influence the results of a job.
104	要求此值時，已完成的工作百分比。請注意，JobProcessingStatistics 類別中也有此屬性。此類別是擷取週期性工作之處理資訊的必要類別，因為只有「上次」執行資料可以儲存在此單一值屬性中。 請注意，101 這個值是未定義的值，在此規格的下一個主要版本中將不允許使用。	The percentage of the job that has completed at the time that this value is requested. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run data can be stored in this single-valued property. Note that the value 101 is undefined and will be not be allowed in the next major revision of the specification.
105	百分比	Percent
106	指示當工作完成時，是否應自動刪除工作。請注意，週期性工作的「完成」是由它的 JobRunTimes 或 UntilTime 屬性來定義，或由手動操作來終止工作時即視為完成。如果將此屬性設為 false，而工作完成，就必須使用外來方法 DeleteInstance 來刪除工作，而不是更新此屬性。	Indicates whether or not the job should be automatically deleted upon completion. Note that the \'completion\' of a recurring job is defined by its JobRunTimes or UntilTime properties, or when the Job is terminated by manual intervention. If this property is set to false and the job completes, then the extrinsic method DeleteInstance must be used to delete the job instead of updating this property.
107	一個廠商特定錯誤碼。如果工作完成且沒有錯誤，此值必須設為零。請注意，JobProcessingStatistics 類別中也有此屬性。此類別是擷取週期性工作之處理資訊的必要類別，因為只有「上次」執行錯誤可以儲存在此單一值屬性中。	A vendor-specific error code. The value must be set to zero if the Job completed without error. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
108	一個包含廠商錯誤描述的自由格式字串。請注意，JobProcessingStatistics 類別中也有此屬性。此類別是擷取週期性工作之處理資訊的必要類別，因為只有「上次」執行錯誤可以儲存在此單一值屬性中。	A free-form string that contains the vendor error description. Note that this property is also present in the JobProcessingStatistics class. This class is necessary to capture the processing information for recurring Jobs, because only the \'last\' run error can be stored in this single-valued property.
109	描述要針對執行失敗的工作採取的復原動作。可能的值包括: 0 =「不明」，表示不知道要採取什麼復原動作 1 =「其他」，表示將在 OtherRecoveryAction 屬性中指定復原動作 2 =「不要繼續」，表示停止執行工作並適當地更新其狀態 3 =「繼續執行下一個工作」，表示繼續執行佇列中的下一個工作 4 =「重新執行工作」，表示應該重新執行工作 5 =「執行復原工作」，表示執行使用 RecoveryJob 關係建立關聯的工作。請注意，復原工作必須已經在要執行它的佇列中。	Describes the recovery action to be taken for an unsuccessfully run Job. The possible values are: 0 = "Unknown", meaning it is unknown as to what recovery action to take 1 = "Other", indicating that the recovery action will be specified in the OtherRecoveryAction property 2 = "Do Not Continue", meaning stop the execution of the job and appropriately update its status 3 = "Continue With Next Job", meaning continue with the next job in the queue 4 = "Re-run Job", indicating that the job should be re-run 5 = "Run Recovery Job", meaning run the Job associated using the RecoveryJob relationship. Note that the recovery Job must already be in the queue from which it will run.
110	不要繼續	Do Not Continue
111	繼續執行下一個工作	Continue With Next Job
112	重新執行工作	Re-run Job
113	執行復原工作	Run Recovery Job
114	一個字串，描述當執行個體的 RecoveryAction 屬性為 1 (「其他」) 時的復原動作。	A string describing the recovery action when the RecoveryAction property of the instance is 1 ("Other").
115	KillJob 即將過時，因為循序關閉和立即刪除並沒有區別。CIM_ConcreteJob.RequestStateChange() 提供 \'Terminate\' 和 \'Kill\' 選項來加以區別。 一種刪除此工作和任何基礎處理程序並移除任何「懸空」關聯的方法。	KillJob is being deprecated because there is no distinction made between an orderly shutdown and an immediate kill. CIM_ConcreteJob.RequestStateChange() provides \'Terminate\' and \'Kill\' options to allow this distinction. A method to kill this job and any underlying processes, and to remove any \'dangling\' associations.
116	成功	Success
117	不受支援	Not Supported
118	逾時	Timeout
119	失敗	Failed
120	存取遭拒	Access Denied
121	找不到	Not Found
122	廠商特定	Vendor Specific
123	指示當工作終止時，是否要自動刪除工作。此參數的修先順序高於 DeleteOnCompletion 屬性。	Indicates whether or not the Job should be automatically deleted upon termination. This parameter takes precedence over the property, DeleteOnCompletion.
124	工作是一個代表工作執行單位 (例如指令碼或列印工作) 的 LogicalElement。工作與處理程序的區別在於工作可被排程或排入佇列，並且其執行不受限於單一系統。	A Job is a LogicalElement that represents an executing unit of work, such as a script or a print job. A Job is distinct from a Process in that a Job can be scheduled or queued, and its execution is not limited to a single system.
125	2.10.0	2.10.0
126	錯誤的主要分類。已定義下列值: 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.
127	通訊錯誤	Communications Error
128	服務品質錯誤	Quality of Service Error
129	軟體錯誤	Software Error
130	硬體錯誤	Hardware Error
131	環境錯誤	Environmental Error
132	安全性錯誤	Security Error
133	過度訂閱錯誤	Oversubscription Error
134	無法使用資源錯誤	Unavailable Resource Error
135	不支援的操作錯誤	Unsupported Operation Error
136	一個當 ErrorType 為 1 (「其他」) 時用來描述 ErrorType 的自由格式字串。	A free-form string describing the ErrorType when 1, "Other", is specified as the ErrorType.
137	實體的唯一識別字串，此實體擁有此執行個體中所述訊息格式的定義。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.
138	一個在 OwningEntity 的領域內唯一識別訊息格式的隱晦字串。	An opaque string that uniquely identifies, within the scope of the OwningEntity, the format of the Message.
139	格式化的訊息。此訊息是透過將 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.
140	一個含有訊息動態內容的陣列。	An array containing the dynamic content of the message.
141	一個從通知程式的觀點描述跡象嚴重性的列舉值: 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.
142	資訊	Information
143	次要	Minor
144	主要	Major
145	重大	Critical
146	嚴重/無法復原	Fatal/NonRecoverable
147	一個描述錯誤可能原因的列舉值。	An enumerated value that describes the probable cause of the error.
148	介面卡/智慧卡錯誤	Adapter/Card Error
149	應用程式子系統失敗	Application Subsystem Failure
150	頻寬縮減	Bandwidth Reduced
151	連線建立錯誤	Connection Establishment Error
152	通訊協定錯誤	Communications Protocol Error
153	通訊子系統失敗	Communications Subsystem Failure
154	設定/自訂錯誤	Configuration/Customization Error
155	壅塞	Congestion
156	資料損毀	Corrupt Data
157	超過 CPU 週期限制	CPU Cycles Limit Exceeded
158	資料集/數據機錯誤	Dataset/Modem Error
159	訊號衰減	Degraded Signal
160	DTE-DCE 介面錯誤	DTE-DCE Interface Error
161	機殼門開著	Enclosure Door Open
162	設備故障	Equipment Malfunction
163	過度震動	Excessive Vibration
164	檔案格式錯誤	File Format Error
165	偵測到火災	Fire Detected
166	偵測到水災	Flood Detected
167	訊框處理錯誤	Framing Error
168	HVAC 問題	HVAC Problem
169	濕度無法接受	Humidity Unacceptable
170	I/O 裝置錯誤	I/O Device Error
171	輸入裝置錯誤	Input Device Error
172	LAN 錯誤	LAN Error
173	偵測到非有毒物質洩漏	Non-Toxic Leak Detected
174	本機節點傳輸錯誤	Local Node Transmission Error
175	訊框遺失	Loss of Frame
176	訊號遺失	Loss of Signal
177	材料供應已耗盡	Material Supply Exhausted
178	多工器問題	Multiplexer Problem
179	記憶體不足	Out of Memory
180	輸出裝置錯誤	Output Device Error
181	效能降低	Performance Degraded
182	電源問題	Power Problem
183	壓力無法接受	Pressure Unacceptable
184	處理器問題 (內部電腦錯誤)	Processor Problem (Internal Machine Error)
185	幫浦故障	Pump Failure
186	超過佇列大小	Queue Size Exceeded
187	接收失敗	Receive Failure
188	接收器失敗	Receiver Failure
189	遠端節點傳輸錯誤	Remote Node Transmission Error
190	資源達到或接近處理能力上限	Resource at or Nearing Capacity
191	回應時間過長	Response Time Excessive
192	重新傳輸率過高	Retransmission Rate Excessive
193	軟體程式異常終止	Software Program Abnormally Terminated
194	軟體程式錯誤 (結果不正確)	Software Program Error (Incorrect Results)
195	儲存容量問題	Storage Capacity Problem
196	溫度無法接受	Temperature Unacceptable
197	超過閾值	Threshold Crossed
198	計時問題	Timing Problem
199	偵測到有毒物質洩漏	Toxic Leak Detected
200	傳輸失敗	Transmit Failure
201	傳輸器失敗	Transmitter Failure
202	基礎資源無法使用	Underlying Resource Unavailable
203	版本不符	Version Mismatch
204	已清除前一個警示	Previous Alert Cleared
205	嘗試登入失敗	Login Attempts Failed
206	偵測到軟體病毒	Software Virus Detected
207	硬體安全性遭破壞	Hardware Security Breached
208	偵測到阻斷服務	Denial of Service Detected
209	安全性認證不符	Security Credential Mismatch
210	未經授權的存取	Unauthorized Access
211	接收到警示	Alarm Received
212	指標遺失	Loss of Pointer
213	承載不符	Payload Mismatch
214	傳輸錯誤	Transmission Error
215	錯誤率過高	Excessive Error Rate
216	追蹤問題	Trace Problem
217	元素無法使用	Element Unavailable
218	元素遺失	Element Missing
219	多個訊框遺失	Loss of Multi Frame
220	廣播通道失敗	Broadcast Channel Failure
221	接收到的訊息無效	Invalid Message Received
222	路由失敗	Routing Failure
223	後擋板故障	Backplane Failure
224	識別碼重複	Identifier Duplication
225	保護路徑失敗	Protection Path Failure
226	同步遺失或不符	Sync Loss or Mismatch
227	終端機問題	Terminal Problem
228	即時時鐘故障	Real Time Clock Failure
229	天線故障	Antenna Failure
230	電池充電失敗	Battery Charging Failure
231	磁碟失敗	Disk Failure
232	跳頻失敗	Frequency Hopping Failure
233	備援遺失	Loss of Redundancy
234	電源供應器故障	Power Supply Failure
235	訊號品質問題	Signal Quality Problem
236	電池放電中	Battery Discharging
237	電池故障	Battery Failure
238	商用電源問題	Commercial Power Problem
239	風扇故障	Fan Failure
240	引擎故障	Engine Failure
241	感應器故障	Sensor Failure
242	保險絲故障	Fuse Failure
243	發電機故障	Generator Failure
244	電力偏低	Low Battery
245	燃料不足	Low Fuel
246	水位不足	Low Water
247	爆炸性氣體	Explosive Gas
248	大風	High Winds
249	結冰	Ice Buildup
250	煙霧	Smoke
251	記憶體不符	Memory Mismatch
252	CPU 週期不足	Out of CPU Cycles
253	軟體環境問題	Software Environment Problem
254	軟體下載失敗	Software Download Failure
255	元素已重新初始化	Element Reinitialized
256	記錄問題	Logging Problems
257	偵測到洩漏	Leak Detected
258	保護機制失敗	Protection Mechanism Failure
259	保護資源失敗	Protecting Resource Failure
260	資料庫不一致	Database Inconsistency
261	驗證失敗	Authentication Failure
262	機密性缺口	Breach of Confidentiality
263	纜線盜接	Cable Tamper
264	資訊延遲	Delayed Information
265	資訊重複	Duplicate Information
266	資訊遺失	Information Missing
267	資訊修改	Information Modification
268	資訊失序	Information Out of Sequence
269	金鑰過期	Key Expired
270	不可否認性失敗	Non-Repudiation Failure
271	上班時間外的活動	Out of Hours Activity
272	無法服務	Out of Service
273	程序性錯誤	Procedural Error
274	意外的資訊	Unexpected Information
275	一個描述錯誤可能原因的自由格式字串。	A free-form string describing the probable cause of the error.
276	一個描述解決錯誤之建議採取動作的自由格式字串。	A free-form string describing recommended actions to take to resolve the error.
277	產生錯誤之實體 (即執行個體) 的識別資訊。如果 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.
278	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.
279	CIMObjectPath	CIMObjectPath
280	一個定義 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.
281	描述此執行個體之特徵的 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。無法執行操作，因為指定的 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.
282	CIM_ERR_FAILED	CIM_ERR_FAILED
283	CIM_ERR_ACCESS_DENIED	CIM_ERR_ACCESS_DENIED
284	CIM_ERR_INVALID_NAMESPACE	CIM_ERR_INVALID_NAMESPACE
285	CIM_ERR_INVALID_PARAMETER	CIM_ERR_INVALID_PARAMETER
286	CIM_ERR_INVALID_CLASS	CIM_ERR_INVALID_CLASS
287	CIM_ERR_NOT_FOUND	CIM_ERR_NOT_FOUND
288	CIM_ERR_NOT_SUPPORTED	CIM_ERR_NOT_SUPPORTED
289	CIM_ERR_CLASS_HAS_CHILDREN	CIM_ERR_CLASS_HAS_CHILDREN
290	CIM_ERR_CLASS_HAS_INSTANCES	CIM_ERR_CLASS_HAS_INSTANCES
291	CIM_ERR_INVALID_SUPERCLASS	CIM_ERR_INVALID_SUPERCLASS
292	CIM_ERR_ALREADY_EXISTS	CIM_ERR_ALREADY_EXISTS
293	CIM_ERR_NO_SUCH_PROPERTY	CIM_ERR_NO_SUCH_PROPERTY
294	CIM_ERR_TYPE_MISMATCH	CIM_ERR_TYPE_MISMATCH
295	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED	CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED
296	CIM_ERR_INVALID_QUERY	CIM_ERR_INVALID_QUERY
297	CIM_ERR_METHOD_NOT_AVAILABLE	CIM_ERR_METHOD_NOT_AVAILABLE
298	CIM_ERR_METHOD_NOT_FOUND	CIM_ERR_METHOD_NOT_FOUND
299	CIM_ERR_UNEXPECTED_RESPONSE	CIM_ERR_UNEXPECTED_RESPONSE
300	CIM_ERR_INVALID_RESPONSE_DESTINATION	CIM_ERR_INVALID_RESPONSE_DESTINATION
301	CIM_ERR_NAMESPACE_NOT_EMPTY	CIM_ERR_NAMESPACE_NOT_EMPTY
302	CIM_ERR_INVALID_ENUMERATION_CONTEXT	CIM_ERR_INVALID_ENUMERATION_CONTEXT
303	CIM_ERR_INVALID_OPERATION_TIMEOUT	CIM_ERR_INVALID_OPERATION_TIMEOUT
304	CIM_ERR_PULL_HAS_BEEN_ABANDONED	CIM_ERR_PULL_HAS_BEEN_ABANDONED
305	CIM_ERR_PULL_CANNOT_BE_ABANDONED	CIM_ERR_PULL_CANNOT_BE_ABANDONED
306	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED	CIM_ERR_FILTERED_ENUMERATION_NOT_SUPPORTED
307	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED	CIM_ERR_CONTINUATION_ON_ERROR_NOT_SUPPORTED
308	CIM_ERR_SERVER_LIMITS_EXCEEDED	CIM_ERR_SERVER_LIMITS_EXCEEDED
309	CIM_ERR_SERVER_IS_SHUTTING_DOWN	CIM_ERR_SERVER_IS_SHUTTING_DOWN
310	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED	CIM_ERR_QUERY_FEATURE_NOT_SUPPORTED
311	一個自由格式字串，包含一般人看得懂的 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.
312	2.22.1	2.22.1
313	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.
314	在具現化命名空間的領域內，InstanceID 可以隱晦且唯一地識別此類別的執行個體。為確保在命名空間中的唯一性，應該使用下列「偏好的」演算法來建構 InstanceID 的值: : 其中 和 是由冒號 \':\' 分隔，而 必須包含建立或定義 InstanceID 之企業實體所擁有的著作權化、商標化或其他方面的唯一名稱，或此唯一名稱是由知名全球授權單位指派給企業實體的註冊識別碼。(此要求條件類似於結構描述類別名稱的 _ 結構)。此外，為確保唯一性， 不能包含冒號 \':\'。使用此演算法時，InstanceID 中顯示的第一個冒號必須顯示在 與 之間。 是由企業實體所選擇，不應被重複用來識別不同的基礎 (真實世界) 元素。如果未使用上述「偏好的」演算法，定義實體必須確保產生的 InstanceID 不會被重複用於此執行個體之命名空間的這個提供者或其他提供者所產生的任何 InstanceID。 對於 DMTF 定義的執行個體，使用「偏好的」演算法時，必須將 設為 \'CIM\'。	Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely identifies an instance of this class. In order to ensure uniqueness within the NameSpace, the value of InstanceID SHOULD be constructed using the following \'preferred\' algorithm: : Where and are separated by a colon \':\', and where must include a copyrighted, trademarked or otherwise unique name that is owned by the business entity that is creating or defining the InstanceID, or that is a registered ID that is assigned to the business entity by a recognized global authority. (This requirement is similar to the _ structure of Schema class names.) In addition, to ensure uniqueness must not contain a colon (\':\'). When using this algorithm, the first colon to appear in InstanceID must appear between and . is chosen by the business entity and should not be re-used to identify different underlying (real-world) elements. If the above \'preferred\' algorithm is not used, the defining entity must assure that the resulting InstanceID is not re-used across any InstanceIDs produced by this or other providers for the NameSpace of this instance. For DMTF defined instances, the \'preferred\' algorithm must be used with the set to \'CIM\'.
315	此工作執行個體的使用者易記名稱。此外，使用者易記名稱也可用來做為搜尋或查詢的屬性。(注意: 名稱在命名空間中不一定要是唯一的。)	The user-friendly name for this instance of a Job. In addition, the user-friendly name can be used as a property for a search or query. (Note: Name does not have to be unique within a namespace.)
316	JobState 是一個指示工作操作狀態的整數列舉。它也可以指示這些狀態之間的轉換，例如「正在關閉」和「正在啟動」。下列是狀態的簡要描述: 新增 (2) 表示工作從未啟動。 正在啟動 (3) 表示工作正在從「新增」、「已暫停」或「服務」狀態移至「正在執行」狀態。 正在執行 (4) 表示工作正在執行。 已暫停 (5) 工作已停止，但可以順暢地重新啟動。 正在關閉 (6) 表示工作正在移至「已完成」、「已終止」或「已刪除」狀態。 已完成 (7) 表示工作已經正常地完成。 已終止 (8) 表示工作已經被「終止」狀態變更要求所停止。工作及其所有基礎處理程序皆已停止，而只能以新工作的形式重新啟動 (這是工作特定的)。 已刪除 (9) 表示工作已經被「刪除」狀態變更要求所停止。其基礎處理程序可能仍繼續在執行，而必須執行清理來釋出資源。 例外狀況 (10) 表示工作處於異常狀態，此狀態可能指示有錯誤發生。實際狀態可能會透過工作特定的物件來顯示 服務 (11) 表示工作處於廠商特定的狀態，此狀態支援問題探索、解析或兩者。 查詢擱置中 (12) 表示正在等待用戶端解析查詢	JobState is an integer enumeration that indicates the operational state of a Job. It can also indicate transitions between these states, for example, \'Shutting Down\' and \'Starting\'. Following is a brief description of the states: New (2) indicates that the job has never been started. Starting (3) indicates that the job is moving from the \'New\', \'Suspended\', or \'Service\' states into the \'Running\' state. Running (4) indicates that the Job is running. Suspended (5) indicates that the Job is stopped, but can be restarted in a seamless manner. Shutting Down (6) indicates that the job is moving to a \'Completed\', \'Terminated\', or \'Killed\' state. Completed (7) indicates that the job has completed normally. Terminated (8) indicates that the job has been stopped by a \'Terminate\' state change request. The job and all its underlying processes are ended and can be restarted (this is job-specific) only as a new job. Killed (9) indicates that the job has been stopped by a \'Kill\' state change request. Underlying processes might have been left running, and cleanup might be required to free up resources. Exception (10) indicates that the Job is in an abnormal state that might be indicative of an error condition. Actual status might be displayed though job-specific objects. Service (11) indicates that the Job is in a vendor-specific state that supports problem discovery, or resolution, or both. Query pending (12) waiting for a client to resolve a query
317	新增	New
318	執行中	Running
319	已暫停	Suspended
320	已終止	Terminated
321	已刪除	Killed
322	例外	Exception
323	服務	Service
324	查詢擱置中	Query Pending
325	工作狀態上次發生變更的日期或時間。如果工作狀態尚未變更，而已填入此屬性，則必須將它設為 0 間隔值。如果已要求狀態變更，但被拒絕或尚未處理，就不得更新此屬性。	The date or time when the state of the Job last changed. If the state of the Job has not changed and this property is populated, then it must be set to a 0 interval value. If a state change was requested, but rejected or not yet processed, the property must not be updated.
326	在工作執行完成後 (不論在該執行中是成功或失敗)，保留工作的時間長短。不論 DeleteOnCompletion 屬性的值為何，工作必須在某段時間內繼續保持存在。 預設值為 5 分鐘。	The amount of time that the Job is retained after it has finished executing, either succeeding or failing in that execution. The job must remain in existence for some period of time regardless of the value of the DeleteOnCompletion property. The default is five minutes.
327	要求將工作狀態變更為 RequestedState 參數中指定的值。多次叫用 RequestStateChange 方法可能會導致先前的要求被覆寫或遺失。 如果傳回 0，表示任務順利完成。任何其他傳回碼則表示發生錯誤狀況。	Requests that the state of the job be changed to the value specified in the RequestedState parameter. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost. If 0 is returned, then the task completed successfully. Any other return code indicates an error condition.
328	完成且沒有發生錯誤	Completed with No Error
329	不明/未指定的錯誤	Unknown/Unspecified Error
330	無法在逾時期間內完成	Can NOT complete within Timeout Period
331	參數無效	Invalid Parameter
332	使用中	In Use
333	已檢查方法參數 - 轉換已啟動	Method Parameters Checked - Transition Started
334	無效的狀態轉換	Invalid State Transition
335	不支援使用逾時參數	Use of Timeout Parameter Not Supported
336	忙碌	Busy
337	保留的方法	Method Reserved
338	RequestStateChange 會變更工作的狀態。可能的值如下: 啟動 (2) 會將狀態變更為「正在執行」。 暫停 (3) 會將工作暫時停止。目的是要在隨後以「啟動」來重新啟動工作。已暫停時，可能會進入「服務」狀態。(這是工作特定的。) 終止 (4) 會將工作井然有序地停止，這會依序儲存資料、保留狀態以及關閉所有基礎處理程序。 刪除 (5) 會將工作立即終止，而不要求儲存資料或保留狀態。 服務 (6) 會將工作置於廠商特定的服務狀態。有重新啟動工作的可能性。	RequestStateChange changes the state of a job. The possible values are as follows: Start (2) changes the state to \'Running\'. Suspend (3) stops the job temporarily. The intention is to subsequently restart the job with \'Start\'. It might be possible to enter the \'Service\' state while suspended. (This is job-specific.) Terminate (4) stops the job cleanly, saving data, preserving the state, and shutting down all underlying processes in an orderly manner. Kill (5) terminates the job immediately with no requirement to save data or preserve the state. Service (6) puts the job into a vendor-specific service state. It might be possible to restart the job.
339	啟動	Start
340	暫停	Suspend
341	終止	Terminate
342	刪除	Kill
343	一個逾時期間，用來指定用戶端預期轉換至新狀態時所需花費的時間上限。必須使用間隔格式來指定 TimeoutPeriod。當值為 0 或參數為 Null 時，表示用戶端對於轉換沒有時間上的要求。 如果此屬性不包含 0 或 Null，而實作不支援此參數，就必須傳回「不支援使用逾時參數」傳回碼。	A timeout period that specifies the maximum amount of time that the client expects the transition to the new state to take. The interval format must be used to specify the TimeoutPeriod. A value of 0 or a null parameter indicates that the client has no time requirements for the transition. If this property does not contain 0 or null and the implementation does not support this parameter, a return code of \'Use Of Timeout Parameter Not Supported\' must be returned.
344	當工作正在執行，或是已經被終止且沒有發生錯誤時，這個方法便不會傳回任何 CIM_Error 執行個體。不過，如果工作因為某個內部問題或因為被用戶端終止而失敗，則會傳回 CIM_Error 執行個體。	When the job is executing or has terminated without error, then this method returns no CIM_Error instance. However, if the job has failed because of some internal problem or because the job has been terminated by a client, then a CIM_Error instance is returned.
345	未指定的錯誤	Unspecified Error
346	如果工作的 OperationalStatus 不是「狀況良好」，這個方法會傳回 CIM 錯誤執行個體。否則，當工作為「狀況良好」時，則會傳回 Null。	If the OperationalStatus on the Job is not "OK", then this method will return a CIM Error instance. Otherwise, when the Job is "OK", null is returned.
347	工作的具體版本。此類別代表一般和可具現化的工作單位，例如批次或列印工作。	A concrete version of Job. This class represents a generic and instantiable unit of work, such as a batch or a print job.
348	InstanceID 是一個屬性，可在具現化命名空間的領域內，用來隱晦且唯一地識別此類別的執行個體。	InstanceID is the property that may be used to opaquely and uniquely identify an instance of this class within the scope of the instantiating Namespace.
349	此屬性與 CIM_ComputerSystem 所代表之邏輯電腦系統的 EnabledState 屬性對應。如需有關 EnabledState 的詳細資料，請參閱 CIM_EnabledLogicalElement.EnabledState。	This property corresponds to the EnabledState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.EnabledState for details on EnabledState.
350	已啟用	Enabled
351	已停用	Disabled
352	不適用	Not Applicable
353	已啟用但離線	Enabled but Offline
354	已延期	Deferred
355	靜止	Quiesce
356	此屬性與 CIM_ComputerSystem 所代表之邏輯電腦系統的 RequestedState 屬性對應。如需有關 RequestedState 的詳細資料，請參閱 CIM_EnabledLogicalElement.RequestedState。	This property corresponds to the RequestedState property of the logical computer system represented by CIM_ComputerSystem. See CIM_EnabledLogicalElement.RequestedState for details on RequestedState.
357	關機	Shut Down
358	沒有變更	No Change
359	離線	Offline
360	測試	Test
361	重新開機	Reboot
362	重設	Reset
363	此屬性與 CIM_ComputerSystem 所代表之邏輯電腦系統的 OperationalStatus 屬性對應。如需詳細資料，請參閱 CIM_ManagedSystemElement.OperationalStatus 描述。	This property corresponds to the OperationalStatus property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.OperationalStatus Description for details.
364	正在重新放置	Relocating
365	此屬性與 CIM_ComputerSystem 所代表之邏輯電腦系統的 HealthState 屬性對應。如需詳細資料，請參閱 CIM_ManagedSystemElement.HealthState。	This property corresponds to the HealthState property of the logical computer system represented by CIM_ComputerSystem. See CIM_ManagedSystemElement.HealthState for details.
366	此屬性指示此實體電腦系統上 FRU 資訊的可用性。如需詳細資料，請參閱 CIM_PhysicalAssetCapabilities.FRUInfoSupported。	This property indicates the availability of the FRU Information on this physical computer system. See CIM_PhysicalAssetCapabilities.FRUInfoSupported for details.
367	此屬性與 CIM_PhysicalFrame.Tag 對應。如需詳細資料，請參閱 CIM_PhysicalFrame.Tag。	This property corresponds to CIM_PhysicalFrame.Tag. See CIM_PhysicalFrame.Tag for details.
368	此屬性與 CIM_PhysicalFrame.Manufacturer 對應。如需詳細資料，請參閱 CIM_PhysicalFrame.Manufacturer。	This property corresponds to CIM_PhysicalFrame.Manufacturer. See CIM_PhysicalFrame.Manufacturer for details.
369	此屬性與 CIM_PhysicalFrame.Model 對應。如需詳細資料，請參閱 CIM_PhysicalFrame.Model。	This property corresponds to CIM_PhysicalFrame.Model. See CIM_PhysicalFrame.Model for details.
370	此屬性與 CIM_PhysicalFrame.SKU 對應。如需詳細資料，請參閱 CIM_PhysicalFrame.SKU。	This property corresponds to CIM_PhysicalFrame.SKU. See CIM_PhysicalFrame.SKU for details.
371	此屬性與 CIM_PhysicalFrame.SerialNumber 對應。如需詳細資料，請參閱 CIM_PhysicalFrame.SerialNumber。	This property corresponds to CIM_PhysicalFrame.SerialNumber. See CIM_PhysicalFrame.SerialNumber for details.
372	此屬性與 CIM_PhysicalFrame.Version 對應。如需詳細資料，請參閱 CIM_PhysicalFrame.Version。	This property corresponds to CIM_PhysicalFrame.Version. See CIM_PhysicalFrame.Version for details.
373	此屬性與 CIM_PhysicalFrame.PartNumber 對應。如需詳細資料，請參閱 CIM_PhysicalFrame.PartNumber。	This property corresponds to CIM_PhysicalFrame.PartNumber. See CIM_PhysicalFrame.PartNumber for details.
374	此屬性與 CIM_PowerUtilizationManagementCapabilities 的 PowerUtilizationModesSupported 屬性對應。如需詳細資料，請參閱 CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported。	This property corresponds to PowerUtilizationModesSupported property of CIM_PowerUtilizationManagementCapabilities. See CIM_PowerUtilizationManagementCapabilities.PowerUtilizationModesSupported for details.
375	動態	Dynamic
376	靜態	Static
377	此屬性與 CIM_PowerUtilizationManagementService 的 PowerUtilizationMode 屬性對應。如需詳細資料，請參閱 CIM_PowerUtilizationManagementService.PowerUtilizationMode。	This property corresponds to the PowerUtilizationMode of the CIM_PowerUtilizationManagementService. See CIM_PowerUtilizationManagementService.PowerUtilizationMode for details.
378	無	None
379	此屬性與 CIM_PowerAllocationSettingData.Limit 對應。如需詳細資料，請參閱 CIM_PowerAllocationSettingData.Limit。	This property corresponds to CIM_PowerAllocationSettingData.Limit. See CIM_PowerAllocationSettingData.Limit for details.
380	電腦系統上數值感應器的使用者易記名稱。如需詳細資料，請參閱 CIM_NumericSensor.ElementName。	User-friendly names of the numeric sensors on the computer system. See CIM_NumericSensor.ElementName for details.
381	數值感應器的狀態。如需詳細資料，請參閱 CIM_NumericSensor.EnabledState。	States of numeric sensors. See CIM_NumericSensor.EnabledState for details.
382	數值感應器的健康狀態。如需詳細資料，請參閱 CIM_NumericSensor.HealthState。	Health states of numeric sensors. See CIM_NumericSensor.HealthState for details.
383	數值感應器的目前狀態。如需詳細資料，請參閱 CIM_NumericSensor.CurrentState。	Current states of numeric sensors. See CIM_NumericSensor.CurrentState for details.
384	數值感應器的主要狀態。如需詳細資料，請參閱 CIM_NumericSensor.PrimaryStatus。	Primary statuses of numeric sensors. See CIM_NumericSensor.PrimaryStatus for details.
385	數值感應器所傳回之值的基礎單位。如需詳細資料，請參閱 CIM_NumericSensor.BaseUnits。	Base units of the values returned by the numeric sensors. See CIM_NumericSensor.BaseUnits for details.
386	攝氏 (C)	Degrees C
387	華氏 (F)	Degrees F
388	絕對溫度 (K)	Degrees K
389	伏特	Volts
390	安培	Amps
391	瓦	Watts
392	焦耳	Joules
393	庫侖	Coulombs
394	VA	VA
395	尼特	Nits
396	流明	Lumens
397	勒克斯	Lux
398	燭光	Candelas
399	千帕	kPa
400	PSI	PSI
401	牛頓	Newtons
402	CFM	CFM
403	RPM	RPM
404	赫茲	Hertz
405	秒	Seconds
406	分鐘	Minutes
407	小時	Hours
408	天	Days
409	週	Weeks
410	毫升	Mils
411	英吋	Inches
412	英呎	Feet
413	立方英吋	Cubic Inches
414	立方英呎	Cubic Feet
415	公尺	Meters
416	立方公分	Cubic Centimeters
417	立方公尺	Cubic Meters
418	公升	Liters
419	液盎司	Fluid Ounces
420	弧度	Radians
421	球面度	Steradians
422	轉數	Revolutions
423	週期	Cycles
424	重力	Gravities
425	盎司	Ounces
426	英磅	Pounds
427	英呎磅	Foot-Pounds
428	盎司英吋	Ounce-Inches
429	高斯	Gauss
430	吉伯	Gilberts
431	亨利	Henries
432	法拉	Farads
433	歐姆	Ohms
434	西門子	Siemens
435	莫耳	Moles
436	貝克	Becquerels
437	PPM (百萬分率)	PPM (parts/million)
438	分貝	Decibels
439	分貝 (DbA)	DbA
440	分貝 (DbC)	DbC
441	格雷	Grays
442	西弗	Sieverts
443	色溫絕對溫度 (K)	Color Temperature Degrees K
444	位元	Bits
445	位元組	Bytes
446	字組 (資料)	Words (data)
447	雙字組	DoubleWords
448	四字組	QuadWords
450	帕斯卡	Pascals
451	數值感應器所傳回之值的單位修飾元。如需詳細資料，請參閱 CIM_NumericSensor.UnitModifier。	Unit modifiers for the values returned by the numeric sensors. See CIM_NumericSensor.UnitModifier description for details.
452	如需詳細資料，請參閱 CIM_NumericSensor.RateUnits。	See CIM_NumericSensor.RateUnits for details.
453	每微秒	Per MicroSecond
454	每毫秒	Per MilliSecond
455	每秒	Per Second
456	每分鐘	Per Minute
457	每小時	Per Hour
458	每日	Per Day
459	每週	Per Week
460	每月	Per Month
461	每年	Per Year
462	如需詳細資料，請參閱 CIM_NumericSensor.CurrentReading。	See CIM_NumericSensor.CurrentReading for details.
463	如需詳細資料，請參閱 CIM_NumericSensor.SensorType。	See CIM_NumericSensor.SensorType for details.
464	溫度	Temperature
465	電壓	Voltage
466	電流	Current
467	轉速計	Tachometer
468	計數器	Counter
469	交換器	Switch
470	鎖定	Lock
471	溼度	Humidity
472	煙霧偵測	Smoke Detection
473	目前狀態	Presence
474	氣流	Air Flow
475	耗電量	Power Consumption
476	發電量	Power Production
477	壓力	Pressure
478	如需詳細資料，請參閱 CIM_NumericSensor.OtherSensorTypeDescription。	See CIM_NumericSensor.OtherSensorTypeDescription for details.
479	如需詳細資料，請參閱 CIM_NumericSensor.UpperThresholdNonCritical。	See CIM_NumericSensor.UpperThresholdNonCritical for details.
480	如需詳細資料，請參閱 CIM_NumericSensor.UpperThresholdCritical 描述。	See CIM_NumericSensor.UpperThresholdCritical description for details.
481	如需詳細資料，請參閱 CIM_NumericSensor.UpperThresholdFatal。	See CIM_NumericSensor.UpperThresholdFatal for details.
482	此屬性代表此實體電腦系統上之基礎記錄的識別碼。如需詳細資料，請參閱 CIM_RecordLog.InstanceID。	This property represents the identifiers for the underlying logs on this physical computer system. See CIM_RecordLog.InstanceID for details.
483	如需詳細資料，請參閱 CIM_RecordLog.MaxNumberOfRecords。	See CIM_RecordLog.MaxNumberOfRecords for details.
484	如需詳細資料，請參閱 CIM_RecordLog.CurrentNumberOfRecords。	See CIM_RecordLog.CurrentNumberOfRecords for details.
485	如需詳細資料，請參閱 CIM_RecordLog.OverWritePolicy。	See CIM_RecordLog.OverWritePolicy for details.
486	已滿時換行	Wraps When Full
487	永遠不覆寫	Never Overwrites
488	如需詳細資料，請參閱 CIM_RecordLog.LogState。	See CIM_RecordLog.LogState for details.
489	正常	Normal
490	正在清除	Erasing
491	識別此實體電腦系統上之開機來源的字串。如需詳細資料，請參閱 CIM_BootSourceSetting.StructuredBootString 描述。	Strings identifying the boot sources on this physical computer system. See CIM_BootSourceSetting.StructuredBootString description for details.
492	識別永續性開機設定之開機順序的元素陣列，除非為下次開機指定了 OneTimeBootSource，否則此開機順序會是電腦系統下次開機時要使用的順序。此陣列中每個元素的值都是一個參照 StructuredBootString 陣列中元素的索引。	An array of elements identifying the boot order of the persistent boot configuration that shall be used during the next boot of the computer system, unless the OneTimeBootSource for the next boot is specified. The value of each element in this array is an index referencing an element in the array of StructuredBootString.
493	此屬性識別用於下一個一次性開機的開機來源。此屬性的值是一個參照 StructuredBootString 陣列中元素的索引。	This property identifies the boot source that is used for the next one-time boot. The value of this property is an index referencing an element in the array of StructuredBootString.
494	此屬性會識別此實體電腦系統上的處理器數目。	This property identifies the number of processors on this physical computer system.
495	如需詳細資料，請參閱 CIM_ProcessorCapabilities.NumberOfProcessorCores。	See CIM_ProcessorCapabilities.NumberOfProcessorCores for details.
496	如需詳細資料，請參閱 CIM_ProcessorCapabilities.NumberOfProcessorThreads。	See CIM_ProcessorCapabilities.NumberOfProcessorThreads for details.
497	如需詳細資料，請參閱 CIM_Processor.Family。	See CIM_Processor.Family for details.
498	如需詳細資料，請參閱 CIM_Processor.MaxClockSpeed。	See CIM_Processor.MaxClockSpeed for details.
499	如需詳細資料，請參閱 CIM_Memory.BlockSize。	See CIM_Memory.BlockSize for details.
500	如需詳細資料，請參閱 CIM_Memory.NumberOfBlocks。	See CIM_Memory.NumberOfBlocks for details.
501	如需詳細資料，請參閱 CIM_Memory.ConsumableBlocks。	See CIM_Memory.ConsumableBlocks for details.
502	目前 BIOS 版本資訊的主版本數字元件。	The major number component of the current BIOS version information.
503	目前 BIOS 版本資訊的副版本數字元件。	The minor number component of the current BIOS version information.
504	目前 BIOS 版本資訊的修訂編號元件。	The revision number component of the current BIOS version information.
505	目前 BIOS 版本資訊的組建編號元件。	The build number component of the current BIOS version information.
506	此實體電腦系統上目前管理韌體之版本資訊的主版本數字元件。	The major number component of the version information for the current management firmware on this physical computer system.
507	此實體電腦系統上目前管理韌體之版本資訊的副版本數字元件。	The minor number component of the version information for the current management firmware on this physical computer system.
508	此實體電腦系統上目前管理韌體之版本資訊的修訂編號元件。	The revision number component of the version information for the current management firmware on this physical computer system.
509	此實體電腦系統上目前管理韌體之版本資訊的組建編號元件。	The build number component of the version information for the current management firmware on this physical computer system.
510	此實體電腦系統上目前管理韌體的使用者易記名稱。	The user-friendly name for the current management firmware on this physical computer system.
511	此實體電腦系統上目前管理韌體的版本字串。	The version string for the current management firmware on this physical computer system.
512	此實體電腦系統上目前或上次執行之作業系統的類型資訊。如需詳細資料，請參閱 CIM_OperatingSystem.OSType。	Type information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.OSType for details.
513	此實體電腦系統上目前或上次執行之作業系統的版本資訊。如需詳細資料，請參閱 CIM_OperatingSystem.Version。	Version information of the current or last running operating system on this physical computer system. See CIM_OperatingSystem.Version for details.
514	此實體電腦系統上目前或上次執行之作業系統的 EnabledState。	EnabledState of the current or last running operating system on this physcial computer system.
515	以字串格式表示的 BIOS 版本資訊。	The BIOS version information in string format.
516	如需詳細資料，請參閱 CIM_ComputerSystem.Dedicated。	See CIM_ComputerSystem.Dedicated for details.
517	非專用	Not Dedicated
518	存放裝置	Storage
519	路由器	Router
520	第 3 層交換器	Layer 3 Switch
521	中央機房交換器	Central Office Switch
522	集線器	Hub
523	存取伺服器	Access Server
524	防火牆	Firewall
525	列印	Print
526	I/O	I/O
527	Web 快取	Web Caching
528	管理	Management
529	區塊伺服器	Block Server
530	檔案伺服器	File Server
531	行動使用者裝置	Mobile User Device
532	中繼器	Repeater
533	橋接器/延伸器	Bridge/Extender
534	閘道	Gateway
535	存放裝置虛擬器	Storage Virtualizer
536	媒體櫃	Media Library
537	ExtenderNode	ExtenderNode
538	NAS 前端裝置	NAS Head
539	獨立性 NAS	Self-contained NAS
540	UPS	UPS
541	IP 電話	IP Phone
542	管理控制器	Management Controller
543	機箱管理員	Chassis Manager
544	主機型 RAID 控制器	Host-based RAID controller
545	存放裝置機箱	Storage Device Enclosure
546	桌上型電腦	Desktop
547	膝上型電腦	Laptop
548	虛擬磁帶媒體櫃	Virtual Tape Library
549	虛擬媒體櫃系統	Virtual Library System
550	網路電腦/精簡型用戶端	Network PC/Thin Client
551	FC 交換器	FC Switch
552	乙太網路交換器	Ethernet Switch
553	如需詳細資料，請參閱 CIM_System.IdentifyingDescriptions。	See CIM_System.IdentifyingDescriptions for details.
554	如需詳細資料，請參閱 CIM_ComputerSystem.OtherDedicatedDescriptions。	See CIM_ComputerSystem.OtherDedicatedDescriptions for details.
555	如需詳細資料，請參閱 CIM_System.OtherIdentifyingInfo。	See CIM_System.OtherIdentifyingInfo for details.
556	如需詳細資料，請參閱 CIM_Processor.CurrentClockSpeed。	See CIM_Processor.CurrentClockSpeed for details.
557	如需詳細資料，請參閱 CIM_Sensor.SensorContext。	See CIM_Sensor.SensorContext for details.
558	如需詳細資料，請參閱 CIM_NumericSensor.LowerThresholdNonCritical。	See CIM_NumericSensor.LowerThresholdNonCritical for details.
559	如需詳細資料，請參閱 CIM_NumericSensor.LowerThresholdCritical 描述。	See CIM_NumericSensor.LowerThresholdCritical description for details.
560	如需詳細資料，請參閱 CIM_NumericSensor.LowerThresholdFatal 描述。	See CIM_NumericSensor.LowerThresholdFatal description for details.
561	一個用來變更此實體電腦系統之狀態的外來方法。要求將元素的狀態變更為 RequestedState 參數中指定的值。當要求的狀態變更發生時，EnabledState 和 RequestedState 將會相同。多次叫用 RequestStateChange 方法可能會導致先前的要求被覆寫或遺失。 當傳回碼為 0 時，表示已順利起始狀態變更。 當傳回碼為 1 時，表示方法不受支援。當傳回碼為 2 時，表示方法失敗。 當傳回碼為 4096 時，表示已順利起始狀態變更、已經建立 ConcreteJob，並且輸出參數 Job 中傳回了它的參照。	An extrinsic method for changing the state of this physical computer system. Requests that the state of the element be changed to the value specified in the RequestedState parameter. When the requested state change takes place, the EnabledState and RequestedState will be the same. Invoking the RequestStateChange method multiple times could result in earlier requests being overwritten or lost. A return code of 0 shall indicate the state change was successfully initiated. A return code of 1 shall indicate that the method is not supported. A return code of 2 shall indicate that the method failed. A return code of 4096 shall indicate the state change was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
562	工作已啟動	Job Started
563	如需詳細資料，請參閱 CIM_ComputerSystem.RequestedStateChange.RequestedState。	See CIM_ComputerSystem.RequestedStateChange.RequestedState for details.
564	延期	Defer
565	可能包含 ConcreteJob 的參照，建立 ConcreteJob 是為了追蹤由方法叫用所起始的狀態轉換。	May contain a reference to the ConcreteJob created to track the state transition initiated by the method invocation.
566	如需詳細資料，請參閱 CIM_ComputerSystem.TimeoutPeriod。	See CIM_ComputerSystem.TimeoutPeriod for details.
567	一個用來清除此實體電腦系統上之記錄的外來方法。 要求將記錄的所有項目清除。 如果已順利執行要求，會傳回 0; 如果要求不受支援，會傳回 1; 如果發生錯誤，則會傳回 2。當傳回碼為 4096 時，表示已順利起始清除記錄的要求、已經建立 ConcreteJob，並且輸出參數 Job 中傳回了它的參照。	An extrinsic method for clearing a log on this physical computer system. Requests that the Log be cleared of all entries. The return value shall be 0 if the request was successfully executed, 1 if the request is not supported, and 2 if an error occurred. A return code of 4096 shall indicate the request to clear log was successfully initiated, a ConcreteJob has been created, and its reference returned in the output parameter Job.
568	被要求清除之記錄檔的識別碼。	Idenfier for the log that is requested to be cleared.
569	一個用來在此實體電腦系統上安裝軟體的外來方法。如果傳回 0，表示已順利完成函式且不需要任何 ConcreteJob 執行個體。如果要求不受支援，會傳回 1; 如果發生錯誤，則會傳回 2。如果傳回 4096，將會啟動一個 ConcreteJob 來執行安裝。輸出參數 Job 中會傳回工作的參照。	An extrinsic method for installing software on this physical computer system. If 0 is returned, the function completed successfully and no ConcreteJob instance was required. The return value shall be 1 if the request is not supported, and 2 if an error occurred. If 4096 is returned, a ConcreteJob will be started to to perform the install. The Job\'s reference will be returned in the output parameter Job.
570	工作的參照 (如果工作已完成，可能為 Null)。	Reference to the job (may be null if job completed).
571	如需詳細資料，請參閱 CIM_SoftwareIdentity.Classifications。	See CIM_SoftwareIdentity.Classifications for details.
572	韌體	Firmware
573	BIOS/FCode	BIOS/FCode
574	軟體套件組合	Software Bundle
575	管理韌體	Management Firmware
576	如需詳細資料，請參閱 CIM_SoftwareInstallationService.InstallFromURI.URI。	See CIM_SoftwareInstallationService.InstallFromURI.URI for details.
577	如需詳細資料，請參閱 CIM_SoftwareInstallationService.InstallFromURI.InstallOptions。	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptions for details.
578	延遲目標/系統重設	Defer target/system reset
579	強制安裝	Force installation
580	安裝	Install
581	更新	Update
582	修復	Repair
583	密碼	Password
584	解除安裝	Uninstall
585	記錄	Log
586	SilentMode	SilentMode
587	AdministrativeMode	AdministrativeMode
588	ScheduleInstallAt	ScheduleInstallAt
589	如需詳細資料，請參閱 CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues。	See CIM_SoftwareInstallationService.InstallFromURI.InstallOptionsValues for details.
590	此方法是用來變更 CIM_PhysicalComputerSystemView.PersistentBootConfigOrder 屬性所指定之永續性開機設定的開機來源順序。	This method is used to change the order of boot sources for the persistent boot configuration specified by the property CIM_PhysicalComputerSystemView.PersistentBootConfigOrder.
591	一個代表開機來源順序的已排序字串陣列。	An ordered array of strings representing the order of boot sources.
592	如果在方法傳回後繼續操作，會產生工作參照。(如果任務完成，可能為 Null)。	Reference to the job spawned if the operation continues after the method returns. (May be null if the task is completed).
593	此方法是用來設定此電腦系統上下次開機的一次性開機來源。	This method is used to set the one time boot source for the next boot on this computer system.
594	一個代表下次開機之開機來源的字串。	A string representing the boot source for next boot.
595	此類別定義實體電腦系統的檢視類別。	This class defines a view class for a physical computer system.
596	2.35.0	2.35.0
597	一個描述 RecordData 屬性中資訊之資料結構的字串。如果 RecordFormat 字串為 ，RecordData 應該就會解譯為自由格式字串。 若要描述 RecordData 的資料結構，RecordFormat 字串應該依下列方式建構: - 第一個字元是一個分隔字元，是用來將字串的剩餘部分剖析成子字串。 - 每個子字串皆由分隔字元分隔，並且應該採用 CIM 屬性宣告 (亦即資料類型和屬性名稱) 的形式。這組宣告可用來解譯以類似方式分隔的 RecordData 屬性。 例如，使用 \'*\' 分隔符號時，RecordFormat = "*string ThisDay*uint32 ThisYear*datetime SomeTime" 可以用來解譯: RecordData = "*This is Friday*2002*20020807141000.000000-300"。	A string describing the data structure of the information in the property, RecordData. If the RecordFormat string is , RecordData should be interpreted as a free-form string. To describe the data structure of RecordData, the RecordFormat string should be constructed as follows: - The first character is a delimiter character and is used to parse the remainder of the string into sub-strings. - Each sub-string is separated by the delimiter character and should be in the form of a CIM property declaration (i.e., datatype and property name). This set of declarations may be used to interpret the similarly delimited RecordData property. For example, using a \'*\' delimiter, RecordFormat = "*string ThisDay*uint32 ThisYear*datetime SomeTime" may be used to interpret: RecordData = "*This is Friday*2002*20020807141000.000000-300".
598	一個包含 LogRecord 資料的字串。 如果對應的 RecordFormat 屬性為 ，或無法根據建議的格式來加以剖析，RecordData 應該就會解譯為自由格式字串。如果 RecordFormat 屬性包含可剖析的格式資訊 (如 RecordFormat 描述限定詞中所建議)，就應該根據此格式來剖析 RecordData 字串。在此情況下，應該以分隔字元做為 RecordData 的開頭，並且應該依所述的方式使用此字元來分隔子字串。然後，RecordData 字串就能夠被資料取用者剖析並適當地分辨類型。	A string containing LogRecord data. If the corresponding RecordFormat property is , or cannot be parsed according to the recommended format, RecordData should be interpreted as a free-form string. If the RecordFormat property contains parseable format information (as recommended in the RecordFormat Description qualifier), the RecordData string SHOULD be parsed in accordance with this format. In this case, RecordData SHOULD begin with the delimiter character and this character SHOULD be used to separate substrings in the manner described. The RecordData string can then be parsed by the data consumer and appropriately typed.
599	一個指示特定地理、政治或文化區域的地區設定。地區設定指定建立 RecordForLog 資料時所使用的語言。如果 Locale 屬性空白，就會假設預設地區設定為 en_US (英文)。 地區設定字串是由 3 個以底線分隔的子字串組成: - 第一個子字串是語言代碼，如 ISO639 中所指定。 - 第二個子字串是國碼 (地區碼)，如 ISO3166 中所指定。 - 第三個子字串是變體，這是廠商特定的。 例如，US English 會顯示為: "en_US_WIN"，其中 "WIN" 變體會指定 Windows 瀏覽器特定的定序 (如果有的話)。由於變體並沒有標準化，因此並未廣泛使用，並且通常僅限於標準環境中使用的容易辨識值 ("WIN"、"UNIX"、"EURO" 等等。)。語言代碼和國家碼 (地區碼) 是必要的; 變體則可空白。	A locale indicates a particular geographical, political, or cultural region. The Locale specifies the language used in creating the RecordForLog data. If the Locale property is empty, it is assumed that the default locale is en_US (English). The locale string consists of three sub-strings, separated by underscores: - The first sub-string is the language code, as specified in ISO639. - The second sub-string is the country code, as specified in ISO3166. - The third sub-string is a variant, which is vendor specific. For example, US English appears as: "en_US_WIN", where the "WIN" variant would specify a Windows browser-specific collation (if one exists). Since the variant is not standardized, it is not commonly used and generally is limited to easily recognizable values ("WIN", "UNIX", "EURO", etc.) used in standard environments. The language and country codes are required; the variant may be empty.
600	一個從通知程式的觀點描述跡象嚴重性的列舉值: 1 -「其他」(依據 CIM 慣例) 是用來指示可以在 OtherSeverity 屬性中找到「嚴重性」的值。 3 -「降級/警告」應該在適合讓使用者決定是否需要採取動作時使用。 4 -「次要」應該用來指示需要採取動作，但是目前狀況還不嚴重。 5 -「主要」應該用來指示需要「立即」採取動作。 6 -「重大」應該用來指示需要「立即」採取動作並且範圍廣泛 (可能會導致重大資源即將中斷)。 7 -「嚴重/無法復原」應該用來指示發生錯誤，但是已經來不及採取補救動作。 2 和 0 - 分別為「資訊」和「不明」，是依照一般使用方式。就字面上的意思來說，就是跡象只是純粹提供資訊，或是它的嚴重性不明。	An enumerated value that describes the severity of the Indication from the notifier\'s point of view: 1 - Other, by CIM convention, is used to indicate that the Severity\'s value can be found in the OtherSeverity property. 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 Indication is purely informational or its severity is simply unknown.
601	RecordForLog 類別是用來將要彙總至記錄檔中的記錄具現化。	The RecordForLog class is used to instantiate records to be aggregated to a Log.
602	2.25.0	2.25.0
603	領域 Log 的 CreationClassName。	The scoping Log\'s CreationClassName.
604	領域 Log 的名稱。	The scoping Log\'s Name.
605	CreationClassName 指出在建立執行個體時所使用之類別或子類別的名稱。與此類別的其他機碼屬性一起使用時，此屬性可以讓此類別及其子類別的所有執行個體都能夠擁有唯一識別。	CreationClassName indicates the name of the class or the subclass used in the creation of an instance. When used with the other key properties of this class, this property allows all instances of this class and its subclasses to be uniquely identified.
606	RecordID 可和 MessageTimestamp 屬性搭配來唯一識別 MessageLog 中的 LogRecord。請注意，此屬性與 MessageLog 方法的 RecordNumber 參數不同。後者只是序數值，可在重複執行記錄檔時用來追蹤位置。另一方面，RecordID 則真的是 LogRecord 執行個體的識別碼。可以將它設定為記錄的序數位置，但並不是非得這樣做。	RecordID, with the MessageTimestamp property, serve to uniquely identify the LogRecord within a MessageLog. Note that this property is different than the RecordNumber parameters of the MessageLog methods. The latter are ordinal values only, useful to track position when iterating through a Log. On the other hand, RecordID is truly an identifier for an instance of LogRecord. It may be set to the record\'s ordinal position, but this is not required.
607	LogRecord 的主要結構包含項目的時間戳記。若項目的時間戳記未知，則應該使用值 99990101000000.000000+000。	A LogRecord\'s key structure includes a timestamp for the entry. If the timestamp for the entry is unknown, the value 99990101000000.000000+000 SHOULD be used.
608	自由格式字串，描述 LogRecord 的資料結構。	A free-form string describing the LogRecord\'s data structure.
609	LogRecord 物件可以描述 MessageLog 中項目的定義格式，或用來將記錄檔中的實際記錄具現化。以 MessageLog 中的個別項目來說，上述方式的後者比起執行 Log 類別的記錄操作方法，能夠提供多更多的語意定義與管理控制。建議您使用 LogRecord 的子類別為個別記錄檔項目中的資料建立模型，以避免以一個不帶有語意的屬性 (例如 RecordData) 建立 LogRecord。 透過建立 RecordID 與 Message Timestamp 機碼屬性的命名慣例，即可指定 LogRecord 的定義格式。	The LogRecord object can describe the definitional format for entries in a MessageLog, or can be used to instantiate the actual records in the Log. The latter approach provides a great deal more semantic definition and management control over the individual entries in a MessageLog, than do the record manipulation methods of the Log class. It is recommended that the data in individual Log entries be modeled using subclasses of LogRecord, to avoid the creation of LogRecords with one property (such as RecordData) without semantics. Definitional formats for LogRecords could be specified by establishing a naming convention for the RecordID and Message Timestamp key properties.
610	2.11.0	2.11.0
611	目標 PCSV 裝置的名稱	Name of the target PCSV device
612	目標 PCSV 裝置的 SMBios Guid	SMBios Guid of the target PCSV device
613	IPv4AddressOrigin 指出將「IPv4 位址」、 「子網路遮罩」及「閘道」指派給 NIC 時所使用的方法。	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.
614	DHCP	DHCP
615	BOOTP	BOOTP
616	目標 PCSV 裝置的「IPv4 位址」	IPv4 Address of the target PCSV device
617	目標 PCSV 裝置的「IPv4 子網路遮罩」	IPv4 Subnet Mask of the target PCSV device
618	目標 PCSV 裝置的「IPv4 預設閘道」	IPv4 Default Gateway of the target PCSV device
619	目標 PCSV 裝置的 LAN MAC 位址	LAN MAC Address of the target PCSV device
620	SEL 可用空間 (位元組)	SEL Free space in Bytes
621	這是用來設定一次性開機來源與持續性開機來源 (新增來支援 PCSVDevice Cmdlet) 的包裝函式方法。這只會在內部呼叫其他兩個方法。此類別的 API 使用者應該直接呼叫其他方法，而不要使用此方法。此方法一次只會變更一個設定，若傳遞值給兩個參數，則此方法會失敗。	This is a wrapper method used to set both the one time boot source and persistent boot source added to support the PCSVDevice cmdlets. This just calls the other two methods internally. The API users for this class should call the other methods directlly insted of this. This method will only change one setting at a time, if you pass values for both paramters, then this method will fail.
622	這是用來變更 BMC 之網路設定的包裝函式方法。	This is a wrapper method used to change the network configuration of the BMC.
623	IPv4AddressOrigin 指出將「IPv4 位址」、「子網路遮罩」及「閘道」指派給 NIC 時所使用的方法。	IPv4AddressOrigin identifies the method by which the IPv4 Address, Subnet Mask, and Gateway were assigned to the NIC.
624	這是用來變更 BMC 使用者密碼的包裝函式方法。	This is a wrapper method used to change the BMC user password.
625	CurrentCredential 是以冒號分隔的字串，其中包含目前的使用者名稱與密碼。	CurrentCredential is a delimited string containing both the current username and password, separated by a colon.
626	NewPassword 將儲存在 BMC 上，做為 CurrentCredential 參數所指定之使用者的新密碼。	NewPassword will be stored on the BMC as the new password for the user specified by the CurrentCredential parameter.
627	此包裝函式方法是用來讀取 BMC SEL 記錄檔。	This is a wrapper method used to read BMC SEL log.
628	傳回 BMC SEL 項目 (以 MSFT_PCSVLogRecord 執行個體陣列的形式)	Return BMC SEL entries as an array of MSFT_PCSVLogRecord instances
10001	此呼叫所用的作業選項必須包含一個下列名稱的選項: %1。%1 作業選項必須屬於類型: %2; 且必須是下列格式: 使用者名稱:密碼。	The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2; and in the following format: username:password.
10002	剖析認證時發生錯誤 %1!X!。%2 操作選項必須是下列格式: 使用者名稱:密碼。	An error %1!X! occurred while parsing the credentials. The %2 operation option must be in the following format: username:password.
10003	此呼叫所用的作業選項必須包含一個下列名稱的選項: %1。%1 作業選項必須屬於類型: %2。	The operation options for this call must contain an option with the following name: %1. The %1 operation option must be of type: %2.
10004	%1 操作選項必須是類型 %2。	The %1 operation option must be of type %2.
10005	不支援要求的管理通訊協定。支援的類型為 WSMAN (1) 和 IPMI (2)。	The requested management protocol type is not supported. Supported types are WSMAN (1) and IPMI (2).
10006	不支援要求的驗證類型。支援的驗證類型為: 預設、摘要和基本。	The requested authentication type is not supported. The supported authentication types are: Default, Digest, and Basic.
10007	不支援要求的電源狀態。支援的電源狀態包括: 已啟用(2)、已停用(3) 和重設(11)。	The requested power state is not supported. The supported power states are: Enabled(2), Disabled(3), and Reset(11).
10008	此裝置不支援要求的開機來源。要求的開機來源必須是 StructuredBootString 陣列中的其中一個值。	The requested boot source is not supported on this device. The requested boot source must be one of the values in the StructuredBootString array.
10009	裝置嘗試使用不支援的驗證演算法來啟動工作階段。支援的驗證演算法包括 HMAC_SHA1 和 NONE。	The device attempted to start a session using an unsupported authentication algorithm. The supported Authentication algorithms are HMAC_SHA1 and NONE.
10010	裝置嘗試使用不支援的完整性演算法來啟動工作階段。支援的完整性演算法包括 HMAC_SHA1_96 和 NONE。	The device attempted to start a session using an unsupported integrity algorithm. The supported integrity algorithms are HMAC_SHA1_96 and NONE.
10011	裝置嘗試使用不支援的機密性演算法來啟動工作階段。支援的機密性演算法包括 AES_CBC_128 和 NONE。	The device attempted to start a session using an unsupported confidentiality algorithm. The supported confidentiality algorithms are AES_CBC_128 and NONE.
10012	裝置未實作任何支援的基底設定檔。支援的基底設定檔包括: %1、%2 與 %3。	The device does not implement any of the supported base profiles. The supported base profiles are: %1, %2, and %3.
10013	處理要求時發生未預期的 %1 錯誤 %2!X!。	An unexpected %1 error %2!X! occurred while processing the request.
10014	從裝置接收到的回應不正確。	The response received from the device was not valid.
10015	操作並未成功地完成。回應包含下列 IPMI 完成碼: %1!x!。	The operation did not complete successfully. The response contained the following IPMI Completion Code: %1!x!.
10016	無法使用指定的認證連線到裝置。請確認認證是否正確，然後再試一次。	Cannot connect to device using the given credentials. Verify the credentials and try again.
10017	裝置未在指定的逾時期間內回應。	The device did not respond in the specified timeout period.
10018	DMTF %1 設定檔並未實作到裝置上，或不是以標準方式實作。	The DMTF %1 profile is not implemented on the device or it is not implemented in the standard way.
10019	正在使用 %1 重新啟動裝置	Restarting device using %1
10020	操作失敗。裝置傳回下列 RMCP+ 狀態碼: %1!x!。	The operation failed. The device returned the following RMCP+ status code: %1!x!.
10021	正在使用 %1 啟動裝置	Starting device using %1
10022	正在使用 %1 停止裝置	Stopping device using %1
10023	已使用 %1 將一次性開機來源設定為 %2	Set one time boot source to %2 using %1
10024	正在使用 %1 從裝置取得資訊	Getting information from device using %1
10025	某些功能或內容將無法使用，因為裝置未實作 DMTF %1 設定檔。	Some capabilities or properties will not be available since the device does not implement the DMTF %1 Profile.
10026	此裝置不支援此操作。此裝置僅支援為「永續性開機順序」設定一個開機來源。	The operation is not supported for this device. The device only supports setting one boot source for Persistent Boot Order.
10027	此裝置類型不支援此操作。只有 IPMI 裝置才支援此操作。	The operation is not supported for this device type. This operation is supported for IPMI devices only.
10028	使用 %1 來設定永續性開機順序	Set persistent boot order using %1
10029	傳遞的參數無效。不支援以單一操作變更「單次開機來源」和「永續性開機順序」。	The parameters passed are not valid. Changing One Time Boot Source and Persistent Boot Order in a single operation is not supported.
10030	傳遞的參數無效。請傳遞其中一個開機設定的有效值。	The parameters passed are not valid. Please pass a valid value for one of the boot settings.
10031	此系統不支援此操作。系統沒有 Microsoft IPMI 相容裝置。	The operation is not supported on this system. The system does not have a Microsoft IPMI compatible device.
10032	只有透過頻外通道管理的裝置才支援電源狀態管理操作。若要使用頻外通道管理裝置，請提供裝置連線資訊，例如 TargetAddress、Credentials 與 ManagementProtocol 等。	Power state management operations are only supported for devices managed via an out-of-band channel. To manage the device using an out-of-band channel please provide device connection information e.g. TargetAddress, Credentials, ManagementProtocol etc.
10034	操作未順利完成。IPv4AddressOrigin 無法在 IPv4Address、IPv4SubnetMask 或 IPv4DefaultGateway 具有靜態值的情況下設定為 DHCP。	The operation did not complete successfully. IPv4AddressOrigin cannot be set to DHCP with static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10035	操作未順利完成。IPv4AddressOrigin 無法在 IPv4Address、IPv4SubnetMask 或 IPv4DefaultGateway 沒有靜態值的情況下設定為 STATIC。	The operation did not complete successfully. IPv4AddressOrigin cannot be set to STATIC without static values for IPv4Address or IPv4SubnetMask or IPv4DefaultGateway.
10036	操作未順利完成。%1 不是 IPMI 通訊協定支援的 IPv4AddressOrigin 值。支援的值為: STATIC(3) 與 DHCP(4)	The operation did not complete successfully. %1 is not supported IPv4AddressOrigin value for IPMI protocol. The supported values are: STATIC(3) and DHCP(4)
10037	操作未順利完成。IPv4 位址 '%1' 不是有效的 IPv4 位址。	The operation did not complete successfully. The IPv4 address '%1' is not a valid IPv4 address.
10038	僅支援透過頻內通道變更 BMC 網路設定。若要變更網路設定，請直接在遠端主機上執行此命令。	BMC network configuration change are only supported via an in-band channel. To change the network configuration, please execute this command on the remote host directly.
10039	BMC 網路設定變更收到未預期的參數類型。IP 位址預期為字串。	BMC network configuration change receives an unexpected parameter type. A string is expected for IP address.
10040	BMC 密碼變更收到未預期的參數類型。目前的認證預期以冒號符號分隔的字串	BMC password change received an unexpected parameter type. A delimited string is expected for current credential
10041	BMC 密碼變更收到未預期的參數類型。新密碼預期字串。	BMC password change received an unexpected parameter type. A string is expected for new password.
10042	目前的認證不符合 BMC 上有效使用者的認證。	The current credential did not match those of a valid user on the BMC.
10044	必須提供 2 個參數 (CurrentCredential 與 NewPassword) 才能變更 BMC 使用者密碼。至少缺少其中一個參數。	2 parameters (CurrentCredential and NewPassword) are required to change BMC user password. At least one of them is missing.
10045	使用者名稱不能超過 16 個字元。	Username cannot be longer than 16 characters.
10046	密碼不能超過 20 個字元。	Password cannot be longer than 20 characters.
10048	無法讀取系統事件記錄檔，因為正在進行清除操作。	Cannot read System Event Log because erase operation is in progress.
10051	無法保留系統事件記錄檔，因為正在進行清除操作。	Failed to reserve the System Event Log because an erase operation is in progress.
10052	無法清除系統事件記錄檔，因為保留已由外部事件 (例如，新增項目、裝置已重設等) 取消。	Cannot clear the System Event Log because the reservation was cancelled by an external event (e.g. a new entry was added, the device was reset, etc.).
10053	使用 %1 變更網路設定	Change network configuration using %1
10054	使用 %1 變更使用者密碼	Change user password using %1
10055	使用 %1 清除系統事件記錄檔	Clear System Event Log using %1
10056	本機裝置	Local Device
10057	正在使用 %1 將裝置正常關機	Gracefully shutting down device using %1
10058	啟用 SOL 承載失敗。SOL 承載必須在相同的工作階段中啟動。	Activating SOL payload failed. SOL payload must be activated in the same session.
0x90000001	Microsoft-Windows-DAL-Provider	Microsoft-Windows-DAL-Provider
0xB0000001	IPMI 要求 %1 未加密的要求資料	The Unencrypted request data for IPMI request %1
0xB0000002	IPMI 要求 %1 加密的回應資料	The Decrypted response data for IPMI request %1
0xB0000003	開始 PCSVDevice 的列舉	Starts enumeration of PCSVDevice
0xB0000004	停止 PCSVDevice 的列舉	Stops enumeration of PCSVDevice
0xB0000005	開始取得 PCSVDevice 的執行個體	Starts getting instance of PCSVDevice
0xB0000006	停止取得 PCSVDevice 的執行個體	Stops getting instance of PCSVDevice
0xB0000007	開始 RequestStateChange	Start RequestStateChange
0xB0000008	停止 RequestStateChange	Stops RequestStateChange
0xB0000009	開始 SetOneTimeBootSource	Starts SetOneTimeBootSource
0xB000000A	停止 SetOneTimeBootSource	Stops SetOneTimeBootSource
0xB000000B	PCSVDevice 操作的結果	Result of PCSVDevice operation
0xB000000F	有關 IPMI 傳送資料的資訊	Information on IPMI Sent Data
0xB0000010	有關 IPMI 接收到資料的資訊	Information on IPMI Received Data
0xB0000011	取得操作選項	Get operations options
0xB0000012	開始 ModifyPersistentBootConfigOrder	Starts ModifyPersistentBootConfigOrder
0xB0000013	停止 ModifyPersistentBootConfigOrder	Stops ModifyPersistentBootConfigOrder
0xB0000014	開始 ChangeBootConfiguration	Starts ChangeBootConfiguration
0xB0000015	停止 ChangeBootConfiguration	Stops ChangeBootConfiguration
0xB0000016	開始 ChangeNetworkConfiguration	Starts ChangeNetworkConfiguration
0xB0000017	停止 ChangeNetworkConfiguration	Stops ChangeNetworkConfiguration
0xB0000018	開始 ChangeUserPassword	Starts ChangeUserPassword
0xB0000019	停止 ChangeUserPassword	Stops ChangeUserPassword
0xB000001A	開始取得 PCSV 裝置記錄檔	Starts getting PCSV device log
0xB000001B	停止取得 PCSV 裝置記錄檔	Stops getting PCSV device log
0xB000001C	開始清除 PCSV 裝置記錄檔	Starts clearing PCSV device log
0xB000001D	停止清除 PCSV 裝置記錄檔	Stops clearing PCSV device log
0xB000001E	頻內 IPMI 要求 %1 的要求資料	The request data for in-band IPMI request %1
0xB000001F	頻內 IPMI 要求 %1 的回應資料	The response data for in-band IPMI request %1

File Name:	pcsvDevice.dll.mui
Directory:	%WINDIR%\WinSxS\amd64_microsoft-devicepro..-provider.resources_31bf3856ad364e35_10.0.15063.0_zh-tw_51bb465b5eed91b5\
File Size:	58 kB
File Permissions:	rw-rw-rw-
File Type:	Win32 DLL
File Type Extension:	dll
MIME Type:	application/octet-stream
Machine Type:	Intel 386 or later, and compatibles
Time Stamp:	0000:00:00 00:00:00
PE Type:	PE32
Linker Version:	14.10
Code Size:	0
Initialized Data Size:	59392
Uninitialized Data Size:	0
Entry Point:	0x0000
OS Version:	10.0
Image Version:	10.0
Subsystem Version:	6.0
Subsystem:	Windows GUI
File Version Number:	10.0.15063.0
Product Version Number:	10.0.15063.0
File Flags Mask:	0x003f
File Flags:	(none)
File OS:	Windows NT 32-bit
Object File Type:	Dynamic link library
File Subtype:	0
Language Code:	Chinese (Traditional)
Character Set:	Unicode
Company Name:	Microsoft Corporation
File Description:	裝置的 PCSV Proxy 提供者
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Internal Name:	pcsvDevice.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original File Name:	pcsvDevice.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0

pcsvDevice.dll.mui is Multilingual User Interface resource file that contain Chinese (Traditional) language for file pcsvDevice.dll (裝置的 PCSV Proxy 提供者).

File Description:	裝置的 PCSV Proxy 提供者
File Version:	10.0.15063.0 (WinBuild.160101.0800)
Company Name:	Microsoft Corporation
Internal Name:	pcsvDevice.dll
Legal Copyright:	© Microsoft Corporation. All rights reserved.
Original Filename:	pcsvDevice.dll.mui
Product Name:	Microsoft® Windows® Operating System
Product Version:	10.0.15063.0
Translation:	0x404, 1200