Practices Guide

Lifecycle Controller Integration―Best Practices Specification
72
C) Search for “RegisteredName= Role Based Authorization” and note its instanceID to use in
step D)
D) GET the applicable instance using the InstanceID from C). See Section 2.3 for a definition
of
GET.
[LC1.5.0/LC1.5.1] GetCIMRegisteredProfile():
[LC2.0.0] GetLCRegisteredProfile():
Results for the InstanceID of DCIM:BaseMetrics:1.0.0 shown below. If no instance is returned,
the profile is not supported.
DCIM_LCRegisteredProfile
AdvertiseTypeDescriptions = WS-Identify
AdvertiseTypeDescriptions = Interop Namespace
AdvertiseTypes = 1
AdvertiseTypes = 1
InstanceID = DCIM:BaseMetrics:1.0.0
OtherRegisteredOrganization = DCIM
ProfileRequireLicense = Power Monitoring
ProfileRequireLicenseStatus = LICENSED
RegisteredName = Base Metrics
RegisteredOrganization = 1
RegisteredVersion = 1.0.0
6 BIOS and Boot Management Profile Use Cases
6.1 Discovery of BIOS and boot Profile Support
Use the following procedure below to confirm the existence of BIOS and boot profile support.
Applies to: LC1.5.0+
Prerequisites for script: none
Script: GetBIOSandBootProfile.win
A) The Lifecycle Controller remote service must be in a “ready” state before executing any
other WSMAN commands. The GetRSStatus() method or the GetRemoteServicesAPIStatus()
method may be used depending on the version of the LC Management registered profile.
B) GetLCRegisteredProfiles(): ENUMERATE the DCIM_LCRegisteredProfile class to view all
registered profiles. See section 2.2 for a definition of
ENUMERATE .
C) Search for “RegisteredName= BIOS and Boot Management” and note its instanceID to use in
step D)
D) GetLCRegisteredProfile(): GET the DCIM_LCRegisteredProfile instance using the
InstanceID from C). See Section 2.3 for a definition of
GET.