Intel® vPro™ Platform
Intel Manageability Forum (Intel® EMA, AMT, SCS & Manageability Commander)
Announcements
Intel® Endpoint Management Assistant (Intel® EMA) Cloud Start Tool for Azure* 2.0 is now available for download here.

The Intel® Manageability Commander 2.2 has been released! Learn more here.

The Intel® Endpoint Management Assistant, version 1.5.1 is now available for download here.

The Intel® Setup and Configuration Software tool will End of Life (EOL) on 12/31/2022. The Intel® Setup and Configuration Software Download will be available until March 31, 2021. For details, Please click here.
2562 Discussions

Upgraded Dell Optiplex BIOS from A03 to A05 - now getting CimException whilst setting up IDE-R session!?

idata
Community Manager
1,117 Views

Hi all,

Today I upgraded my Intel i3 based system Dell Optiplex 990 from BIOS revision A03 to A05. This included a firmware update for Intel ME.

Unfortunately, when I now run my project to engage with this system using the Intel SDK components for an IDE-R session, the following exception is returned:

Intel.Manageability.Exceptions.CimException: Logic error: Received an unknown class - IPS_BootConfigSetting

...

...

...

at

IntelSDK.RemoteControlApi.GetCurrentBootDeviceName

The line of code, within RemoteControlTypedApi.cs, which generates this exception, is:

public string GetCurrentBootDeviceName(bool verbose)

{

//Get the CIM_BootSourceSetting all CIM_BootSources are connected to

CIM_BootSourceSetting bootSource = new CIM_BootSourceSetting(wsmanClient); <-----------</span>

Please could someone advise me why doing an upgrade seems to have disabled functionality? The logic of my application checks the currently set boot device on the system and if necessary, sets it back to IDE-R or Hard Disk, dependent on the current mode of operation. Has this function been superceded? If so, how could I best implement it?

Help would be very much appreciated,

Thanks,

Alex

0 Kudos
1 Reply
idata
Community Manager
210 Views

Hi Alex,

The problem you are seeing has to do with a feature that is included in the A05 BIOS and ME firmware upgrade (the "Additional vPro support" mentioned in the Fixes and Enhancements on Dell's site). This feature adds some objects to the firmware that the SDK sample does not recognize (the object of type IPS_BootConfigSetting is an example). I will try find out if there is a workaround that you can use to deal with your problem.

Best Regards,

Dick

Reply