So here we are in February 2019.
I work for an MSP that quotes work hours. One of the things we always include is updating firmware etc.
To save time, we use the Dell Lifecycle controller, rather than identifying, downloading and manually installing.
On a brand new Dell R740 server, I configured the Lifecycle Controller network (after ignoring the repeated IPV6) errors and then finding this article.
Which says to ignore it, even though there is not ignore button. What it means was go back to the previous menu and continue, which it did.
Then presented with and option to update BIOS from
so continued, but failed more than once.
Tested using a FTP client and found I could not open this site.
Then searched and found this article.
And was able to identify and update the server.
So, instead of thousands of users having to waste an hour EVERY time they update their server, fix the above 2 problems. Either in the firmware of the server or by enabling the site you are pointing everyone to by default.
Or are you too busy?
But wait there's more.
The above FTP site (ftp1.us.dell.com) has not been fully updated.
This shows BIOS version 1.6.12
So tried to install this manually via SMB.
And tried using the SMB method to update.
But presented with
"use a valid Windows-Based Update Package with an .exe extension.
No EXE BIOS updates on the above site.
Let me get back to our sales team and see how competitive Dell servers are after we factor in hours of trying to install updates.
You just saved me a few (more) hours, THANKS!!
It pays to read an entire thread (in this case a short one). I'm happily updating after spending a few hours trying to "follow the directions" and exercising my Google-foo because I erroneously thought I didn't know what I was doing or had entered something wrong at some point. I'd set aside all of today to figure out why this batch of old servers was being such an issue; thanks for giving me some of my day back. *beer*
"HP servers and Dell desktops make a happy office" I've heard often enough...there's some truth to that I'm thinking. And as a consultant, I'll be keeping that in mind.
I posted a solution for this a while back. Not sure if it still works the same way but I keep getting kudos so I guess it does.
I know this is old, but thanks Technigogo!
What a pain that was. Docs said use https:// blah blah but it said everything I used was an invalid address. You can't use colons or slashes. Spent forever searching for an answer and yours worked.