White Papers

158 Lifecycle Controller Integration Best Practices Guide

32 OS Deployment Profile Use Cases

32.1 Discovery of OS Deployment Profile Support

Use the following procedure below to confirm the existence of OS Deployment profile support.

Applies to: LC1.3.0+

Prerequisites for script: none

Script: GetOSDProfile.win

A) The Lifecycle Controller remote service must be in a “ready” state before running 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= OS Deployment” 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.

Results for the InstanceID of DCIM:OSDeployment:1.1.0 shown below. If no instance is returned, the profile is not

supported.

DCIM_LCRegisteredProfile

AdvertiseTypeDescriptions = WS-Identify

AdvertiseTypeDescriptions = Interop Namespace

AdvertiseTypes = 1

InstanceID = DCIM:OSDeployment:1.1.0

OtherRegisteredOrganization = DCIM

ProfileRequireLicense = Remote Operating System Deployment

ProfileRequireLicenseStatus = LICENSED

RegisteredName = OS Deployment

RegisteredOrganization = 1

RegisteredVersion = 1.4.0