MSFTSM_RegisteredProfile class

Describes a
set of Common Information Model (CIM) classes, properties, and methods, required to manage a real-world entity or usage scenario. Registered profiles can be named and defined by the Distributed Management Task Force (DMTF) or other
standards organizations. The uses for a registered profile or sub-profile must be specified in the document that defines
the profile.

The MSFTSM_RegisteredProfile class is unrelated to the CIM_Profile class, which serves a completely different purpose. A registered profile is a named specification for
CIM-based management of a particular system, subsystem, service, or other entity, for a specified set of uses. It can be used as a standalone specification and it can proved the context for one or more MSFTSM_RegisteredSubProfile instances, which can only be used in the scope of a registered profile.

The following syntax is simplified from Managed Object Format (MOF) code and includes all of the inherited
properties.

Properties

The MSFTSM_RegisteredProfile class has these properties.

AdvertiseTypeDescriptions

Data type: string array

Access type: Read-only

Qualifiers: ArrayType
(Indexed)

Lists additional information related to the AdvertiseType property values. Entries in the array are correlated with those in the AdvertiseType property. An entry is required for every entry in the AdvertiseType array that is set to Other. Otherwise, an entry is typically not needed.

Indicates the advertisement for this access point. It is used by the advertising services of the Web-Based Enterprise Management (WBEM) infrastructure to determine what should be advertised and by what mechanisms.

Setting this property to NULL is equivalent to setting it to Not Advertised.

Uniquely and opaquely identifies an instance of this class within the scope of the containing namespace.

Important
To ensure uniqueness within the namespace, the value of InstanceID should be
constructed in the following pattern:

OrgID:LocalID

OrgID must include a copyrighted, trademarked, or
otherwise unique name that is owned by the business entity that defines
the InstanceID, or be a registered ID that is assigned by a recognized global authority. This is similar to the structure of Schema
class names. In addition, to ensure uniqueness, the first colon in InstanceID must be between the OrgID andLocalID. Therefore the OrgID must not contain a colon (':').

LocalID is chosen by the business entity and should not be re-used to
identify different underlying real-world elements.

If the above pattern is not used, the defining entity must assure that the resultant
InstanceID is not re-used across any InstanceIDs produced by this or other
providers for this namespace. LocalID must include either a vendor-specified unique identifier, or if it is mapped from an ITU M.3100 environment, the trailID, connectionID or subNetworkConnectionID property of the instance.

For Distributed Management Task Force (DMTF) defined instances, the
pattern must be used with the OrgID set to "CIM".

Indicates the name of this registered profile. The combination of the RegisteredName, RegisteredOrganization, and RegisteredVersion properties must uniquely identify the registered profile within the scope of the organization.