Hello, I am running a Poweredge 1950 with SBS2003. I am going to update the server to Windows 2008 R2 very soon but I wanted to clear up a Perc firmware update that OMSA has pointed out.
My current firmware version is 5.1.1-0040. OMSA says the minimum version is 5.2.2-0072.
I found another thread that gave some links for updates but they are all dead now. I searched the Dell support pages for an update file that was a Windows Update Package instead of Hard Drive or Floppy and I cannot find one.
How do I update this firmware? Thanks in advance.
Here is a link for the Windows installer version of the update:
Daniel MysingerGet Support on Twitter @DellCaresPro
Download the Dell Quick Resource Locator app today to access PowerEdge support content on your mobile device! (iOS, Android, Windows)
Brandon_IFCAwesome thanks for the link. Are there any additional steps I need other than to run this update program?
No, you just need to restart afterward for the update to take affect. Here are the release notes with install instructions if you want to read through them:
Just a head's up ... you should really update the BIOS and ESM before updating the PERC firmware.
Same way as you did [will do] your PERC firmware:
Thanks for your help guys. This is my first Poweredge server and there's so much information on the Dell Support pages that it's easy to get lost in what needs to be done.
Last two questions and I'll stop pestering you guys:
1. Is there any particular order that should be followed when updating the BIOS and the ESM?
2. What is the risk level involved with applying these updates? My fear is that I'll update something (particularly the PERC) and the server may lose the RAID configuration or something like that.
Thanks again for all of your help.
1. Generally, you should always update the BIOS first (the exception with newer systems - 11G,12G systems - the iDRAC/LC should be updated before BIOS), then the ESM, then other devices, such as the PERC, DRAC, NIC's, HDD's, etc. When updating the PERC, you should always update the driver before the firmware (I did not bring it up here, as you said you were just going to install 2008R2 anyway).
2. Risk is VERY minimal. People who experience problems usually do so when trying to update a system in distress ... like trying to update firmware to fix a problem (updating PERC firmware when a drive is failed or loses its configuration, etc., updating BIOS when the system is experiencing stability problems, etc.). It is extremely unlikely that updating the PERC will result in a loss of the RAID configuration, but even if it did, there are ways to get it back - in particular, the PERC controllers would probably just tell you there is a foreign config (having seen the config stored on the drives), then you import it, and all is well again.
Many people "step" the updates to try to prevent problems when jumping too far with one update, but I have found this to be unnecessary in 99% of situations.
Thanks very much to both of you for your advice. I will be applying these updates tonight after the office is done for the day.
I intend to apply these updates remotely over RDP.
The BIOS update will require a reboot.
The ESM will not require a reboot, but it may take 10 minutes for it to complete. You won't be there to hear it, but the fans will speed up during the update.