The updates you are trying to apply are not Dell-authorized updates

If you try to use the F10 Platform Updates option in System Services to update firmware, but get the following error:  “The updates you are trying to apply are not Dell-authorized updates”

Make sure your server is running a minimum firmware revision for the following two items:

  • iDRAC – at least revision 1.85 or newer
  • Lifecycle Controller – at least revision 1.5.2 or newer

***The current Lifecycle Controller Repair package will NOT resolve the  issue, as it only updates the LFC to version 1.5.1, which is too old

The iDRAC is easily updated by using the “Update” option in the iDRAC webpage interface.

The Lifecycle Controller can (as of 11/9/12) only be updated in a Windows or Linux environment.  For  ESXi users, you can boot to OMSA Live and apply the LFC .bin update via command line.
This is #FAIL dear DELL

18 thoughts on “The updates you are trying to apply are not Dell-authorized updates

  1. I got caught with this yesterday. you would have thought dell would have considered this when they expired or changed their certificate signing on their packages to at least GIVE you the choice to permit installing the lifecycle firmware even if it considers that it’s incorrect.

    or alternatively provide a download that is signed using the old method so we could easily update via USB.

    having to download OMSA live and do the whole thing there was just a time wasting show stopper for me.

    past that point everything went well. i hope dell doesn’t make the same mistake again in the future.

    cheers, Wiz!!

  2. Epic fail for Dell. One of our customers cannot update one of their fresh R910 server. They are very angry because these servers work under esxi environment and update bios from live cd is not easy task. Thank you guys for you post, it is really helpful.
    I found good FAQ about using OMSA live-CD here:
    Last OMSA DVD (7.1) can be found here:

  3. I had the same problem and I called Dell. Turns out you can do both updates via the iDRAC, here is the response from Dell:

    To further correct this issue I will need you to do the following steps:

    You will need to update the iDRAC and LCC manually to regain the update functionality of the LCC and Repo ISO. You can run both of these updates from the iDRAC GUI using the packages below in the ORDER LISTED:

    1. iDRAC 1.92 (run the executable to extract the firming.d6 file and browse to that file from the update tab in the iDRAC GUI)

    2. LCC Repair

    They each take about 30 minutes each.

    Worked for me and I was able to proceed with updating the servers.

    • Another way : create a live USB stick and copy also the content of dell suu on it. Linux can run the suu and patch everything it takes 1+ hour per server so still a big #fail. Same has allowing an http proxy to contact dell FTP …. I love my Cisco UCS 😉

      Seems dell want to sell the esx plugin

  4. Simply amazes me that Dell can’t manage to make a single boot DVD ISO that can handle hardware updates like every other major vendor does. We’ve all fought this for years now. This is what makes IT people hate Dell Hardware – especially at 4am. I’ve had a horrible time getting the vCenter Plug-in to even talk to Dell hosts even after putting on the latest OMSA and iDRAC firmware updates. This is presumably because I don’t have the latest hardware updates in place. What a catch-22. Yep on Cisco UCS.

  5. I also ran into this issue, I tried to upload both the iDrac firmware and the Repair Pack for the LCC.
    iDrac upgrade went smoothly while the repair pack kept on crashing.

    I realized that the server must be out of the UEFI in order to be able to upgrade the LCC.
    I tough I should share this in case someone waste too much time like I did.

      • You need to update manually the 2 involved software using manual download and a USB key. After it will be smooth

        happy new year 😉

    • Thanks! I wish I had stumbled upon this earlier though. Updating the LCC would fail at 10% continually. Finally after reading this I rebooted and did not proceed into the UEFI/USC. I was then able to update both the LCC and iDRAC using the iDRAC update. I was then able to finish the rest of the updates using the USC. Wasted the better part of a day.

  6. Just spent a totally un-necessary all-nighter over this. The solution wasn’t that hard but given Dell’s glacial boot times, experimenting to find it was excruciating. This page is the best documentation I could find in a night of searching. Thank you so much, I never would have cracked it without the iDRAC tip. Some additional notes:

    Just to re-iterate; iDRAC can update itself and the Lifecycle Controller to get the new certificates. Then USM (F10) will work again and update the rest of the firmware. This is the easiest way.

    Use the link above to get the iDRAC6 image exe. On linux unpack it with unzip. It will give you a file “firmimg.d6”. Log into the iDRAC Firmware Update and browse to this file. Say Yes, Yes ,Yes.

    While iDRAC reloads, download the other link to get BDF_1.5.5_BIN-12.usc
    Re-run the Firmware Update feeding it the raw .usc file.

    You can now boot the machine and F10 into a functioning* USC.


    * Barely, painfully, glacially functioning*, but it can be cajoled to work.

    Tip: Use external DNS resolution[TM].
    Get an IP for “” and feed it that.
    For me it was incapable of using DNS servers.

    • Good to know the order doesn’t matter.
      Thanks for testing that rcmtech. (even if it was accidental)

  7. Had another late night getting another server patched up to date. Followed the procedure above and used iDRAC to update itself and LCC, rebooted into LCC (F10 boot option) expecting it to just do its thing and update all the rest of the firmware. Couldn’t get LCC to see the network at all. Spent hours fighting with it. If I told it to DHCP it would report a network fault (no DHCP answer) if I fed it a static address it would fail all the ping tests and fail to download the catalog. Tantalisingly, from outside I could ping the IP (DHCP or static), just LCC couldn’t use the network.
    A very helpful Dell tech advised me to use LCC to update the BIOS, but work around its network blindness by feeding it the update on a USB stick. Download the windows version on your PC and copy it to a USB stick. Use a simple filename or write the Dell one down, once you launch “Platform Update” and choose USB (not FTP) you will have to type it into the LCC letter perfect.
    Once the BIOS was updated the rebooted LCC still failed all its pings in the network test but did download the catalog and subsequent updates successfully. (Hey, at 2am I take my wins how they come, even wrapped in glitches.)
    Must have been some incompatibility between the updated LCC and my old BIOS. Props to the Dell tech for homing in on that possibility and finding an easy way round it.

    • PS: The incompatible old BIOS was 1.2.1 then updated to 2.9.0, big jump.
      The LCC was, and iDRAC 1.54.15

  8. Pingback: HOWTO: Fix Dell Lifecycle Controller Update issues | vNetWise

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s