Reference Guide

Property Description
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identies an instance of this class. To ensure uniqueness within the NameSpace, the value
of InstanceID should be constructed using the following preferred algorithm:
<OrgID> : <LocalID>
Where <OrgID> and <LocalID> are separated by a colon (:), and where <OrgID> must
include a copyrighted, trademarked, or otherwise unique name that is owned by the
business entity that is creating or dening the InstanceID or that is a registered ID assigned
to the business entity by a recognized global authority. (This requirement is similar to the
<Schema Name>_<Class Name> structure of Schema class names.) In addition, to ensure
uniqueness, <OrgID> must not contain a colon (:). When using this algorithm, the rst colon
to appear in InstanceID must appear between <OrgID> and <LocalID> . <LocalID> is chosen
by the business entity and should not be reused to identify dierent underlying (real-world)
elements. If the above preferred algorithm is not used, the dening entity must assure that
the resulting InstanceID is not reused across any InstanceIDs produced by this or other
providers for the NameSpace of this instance. For DMTF-dened instances, the preferred
algorithm must be used with the <OrgID>set to CIM.
NumberOfHardwareThreads
Number of hardware threads available for the processor. May be obtained from SMBIOS
v2.5 4 oset 25h.
NumberOfProcessorCores
Number of processor cores available for processor. This number would not include cores
disabled by hardware and may be obtained from SMBIOS 2.5 Type 4 oset 23h.
DCIM_AccountManagementCapabilities
Property
Description
ElementNameEditSupported
Boolean indicating whether the ElementName can be modied.
InstanceID
Within the scope of the instantiating Namespace, InstanceID opaquely and uniquely
identies 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:
<OrgID>:<LocalID>
Where <OrgID> and <LocalID>are separated by a colon ':', and where MUST include a
copyrighted, trademarked or otherwise unique name that is owned by the business entity
creating/dening the InstanceID, or is a registered ID that is assigned to the business entity
by a recognized global authority (This is similar to the
<Schema_Name>_<Class_Name>structure of Schema class names.) In addition, to ensure
uniqueness MUST NOT contain a colon (':'). When using this algorithm, the rst colon to
appear in InstanceID MUST appear between <OrgID> and <LocalID>. <LocalID> is chosen
by the business entity and SHOULD not be re-used to identify dierent underlying (real-
world) elements. If the above preferred algorithm is not used, the dening entity MUST
assure that the resultant InstanceID is not re-used across any InstanceIDs produced by this
or other providers for this instance's NameSpace. For DMTF dened instances, the
preferred algorithm MUST be used with the <OrgID>set to 'CIM'.
OperationsSupported
OperationsSupported describes the type of operations that are supported for an Account
associated with the AccountManagementService.
Possible values are:
• 2 = Create — Indicates the AccountManagementService may be used to create new
accounts.
• 3 = Modify — Indicates that the associated Accounts may be modied.
• 4 = Delete — Indicates that associated Accounts may be deleted.
• .. = DMTF Reserved
Dell Command | Monitor10.1.0 classes and properties 209