1 Rookie

 • 

55 Posts

9968

April 16th, 2020 01:00

Failing to update iSM LC DUP v3.5.1

We have OpenManageEnterprise (New OME) and the firmware compliance reports show that some servers (PE 320 and PE 440) have a version of iSM LC DUP that is too low (3.4.0 compared to 3.5.0). I download the correct executable from the Dell website (Systems-Management_Application_C4NXJ_WN64_3.5.1_A00.exe) but when I try to upgrade it, it fails with a "Unable to complete the firmware update operation because the specified firmware image is for a component that is not in the target system inventory" error. Everything else is updated to the latest version. An older executable (Systems-Management_Application_2VJ25_WN64_3.4.1_A00.exe) installs fine. I know it is not critical but it would be good to get the firmware compliance report to be warning free. The host OS is Windows 2016 x64 core. Thanks

Moderator

 • 

3.9K Posts

July 12th, 2023 04:00

1 Message

July 20th, 2023 05:00

Hi,

I too am wanting to update to 5.1 to get Open Manger Ent to go "green" and stop the nag. the file above linked "GCXFN" will not update the iDRAC, with older versions there seems to be 2 variants of the file. please can you provide a link to correct one. Can i also suggest that a better naming convention is adopted to avoid confusion between the 2 variants.

Thanks

3 Posts

July 20th, 2023 07:00

Again this info is retrieved from catalog.xml that you download from here: https://downloads.dell.com/catalog/Catalog.xml.gz

 

Current 5.1 installer is here:

https://downloads.dell.com/FOLDER09468086M/1/Systems-Management_Application_07X5X_WN64_5.1.0.0_A00.EXE

 

1 Rookie

 • 

24 Posts

September 24th, 2025 18:12

And according to the cab's xml, the iSM LC DUP Firmware 5.4.2.0 should be at
https://downloads.dell.com/FOLDER13586012M/1/Systems-Management_Application_J9FG1_WN64_5.4.2.0_A00.EXE

But this results in a 404. What am I doing wrong?

1 Rookie

 • 

24 Posts

September 24th, 2025 20:22

https://downloads.dell.com/FOLDER13475057M/1/Systems-Management_Application_VPJFF_LN64_5.4.2.0_A00.BIN works for the linux binary, but iDRAC doesn't accept it as a valid update.

Ok! I finally found it at https://downloads.dell.com/FOLDER13475051M/1/Systems-Management_Application_VPJFF_WN64_5.4.2.0_A00.EXE

but...

iDRAC still doesn't like it and gives the same error as OME: "Unable to complete the firmware update operation because the specified firmware image is for a component that is not in the target system inventory or the component is disabled for performing the update."

ARGH!

After downloading and installing Dell's Repository Manager (DRM), I was able to create an R540 boot iso (which does NOT update the iSM LC firmware to 5.4.2.0 when booting from it) and boot into LC to browse for the optical:/drm_files/repository/Catalog.xml file which showed the update, which FINALLY allowed me to apply it.

This is a tedious minimum 15min manual process, but at least I was finally able to update and Dell's OME is finally happy.

(edited)

Moderator

 • 

2.9K Posts

September 25th, 2025 08:41

1 Rookie

 • 

24 Posts

September 25th, 2025 19:04

@DELL-Erman O​ That doesn't help, as that just links to the old version. Dell's OME shows 5.4.2.0 as the current, but it fails to install it automatically. That is where the issue lies. The iDRAC install fails, and I've only gotten it to succeed with the manual update as stated above.

Moderator

 • 

4.6K Posts

September 25th, 2025 20:04

Hello,

 

I see you have done a lot of troubleshooting and found a way that did work. I'll post a few thoughts and maybe you already did them.

OME relies on update metadata files (e.g., LexingtonUpdates.xml and LexingtonUpdates.xml.asc) to validate and parse available updates. If the metadata for 5.4.2.0 is malformed, missing, or improperly signed, the automatic update process may reject it—even though the manual install bypasses this validation.

This can happen due to:

  • Corrupted or incomplete download from Dell’s update repository.
  • Signature mismatch or expired certificate in the .asc file.
  • Improper folder structure in the update share.

 

 

Try these steps and see how it does:

  1. Re-download the update package from Dell’s support site and verify the folder structure.
  2. Check the update logs in OME under Jobs > Job History for any parsing or signature errors.
  3. Clear the update cache and retry the automatic update.
  1. If the issue persists, continue using manual installation for 5.4.2.0 and monitor future updates for normal behavior.

 

1 Rookie

 • 

24 Posts

October 9th, 2025 18:35

1. Redownloading does not change - iDRAC still fails to apply it

2. Same "Unable to complete the firmware update operation because the specified firmware image is for a component that is not in the target system inventory or the component is disabled for performing the update." message

3. Same "Unable to complete the firmware update operation because the specified firmware image is for a component that is not in the target system inventory or the component is disabled for performing the update." message

4. Applying from LC firmware update manually from a Dell RepoMan iso is the only method that I have gotten to work.

Moderator

 • 

9.6K Posts

October 9th, 2025 20:19

reukiodo_uw,

 

Would you confirm a couple of things for me?

 

Does that update file work if run from within the Lifecycle Controller?

Also, is the idrac currently up to date on the system you are trying the update from?

 

 

 

1 Rookie

 • 

24 Posts

November 4th, 2025 20:47

As stated previously, manually running the update from within LC is the ONLY way this update was successful to apply.

This was the last update to apply, so yes, everything else (including iDRAC) was already applied to latest updates available.

Moderator

 • 

5.3K Posts

November 5th, 2025 05:10

Hello,

There are 2 iSM files: one for iDRAC embedded installer and the other for OS.

The one for iDRAC is optional and doing updated for it does not achieve much, unless customer is using iDRAC to mount iSM image and run the installer from it under OS.

You are using OME and the whole conversation started that OME does not show correct info.

My advice would be that you kindly raise a case, I'm positive if you are using OME, you may have some servers in warranty.

Respectfully,

1 Rookie

 • 

24 Posts

November 6th, 2025 00:37

I am unaware of how to 'raise a case' as Dell's site isn't exactly the most intuitive to navigate. Is there a direct link?

Moderator

 • 

5.3K Posts

November 6th, 2025 00:51

Contact Technical Support | Dell US Sure, this is how you get in touch with tech support.

Respectfully,

1 Rookie

 • 

24 Posts

November 6th, 2025 01:10

This is frustrating, and is exactly what I mean.... that was a link to a very generic support walk-through, not the link to immediately open a support request, which I eventually found is actually:

https://www.dell.com/support/myservice360/en-us/incidentmngt/totalsrs/tabular

No Events found!

Top