Intel S1200SPOR Server Board OFU BIOS/Firmware 03.01.0049

Versions:

- BIOS: 03.01.0049
- ME: 04.01.04.109
- BMC: 01.18.12306
- FRUSDR: V0.28
 

Changes in BIOS 03.01.R0049:

- [HSD-ES][2103632646] The BMC Firmware Revision&SDR Revision not hidden in POST Information under KCS Deny All mode.
- [HSD-ES][2103633189] FDD always are attached to the end of boot options after F9 under UEFI mode.
- [HSD-ES][1507958726] Run command "chipsec_main.py" and find module "igd_config0" failed.
- [HSD-ES][1507966668] [S1200SP][Point Release]S1200SP Point release based on 03.01.R4042 +Fixed the Overclocking MSR lock issue.
- Update RC code to 4.1.1.3
- [HSD-ES][1508038822] [S1200SP]Failed to set BIOS Knobs using syscfg in OS level.
- [HSD-ES][2103632569] Most changed settings return default when online update BIOS from D03.01.0042 to D03.01.0046.
- [HSD-ES][1507959325] Add new KCS policy done_core flage in BT.
- [HSD-ES][2103632613] [KCS] “Set Fan Profile” and “Fan PWM Offset” options not be Suppressed under Deny All mode
- [HSD-ES][1507032908][S1200SP][D0040]System become unresponsive when flash the modified BIOS capsule that change offset 0x70 value from 00 to 4F
- [HSD-ES][1507197468] FW-UEFI-Vuln-2019-115 [BDBA] Intel Server Board S1200SP Family - System Firmware Update Package Bridge SFUP for Intel OFU - BIOS 03.01.2032, ME FW 04.01.04.054
- [HSD-ES][1507218688] Include PRT patch Intel Server and Workstation Processors Microcode Update Rev. Production SRV_P_285 to Silver Pass 2019 QSBR
- [HSD-ES][1507195984] [Security] Race conditions in VariableInterface() allow arbitrary writes inside of SMRAM
- [HSD-ES][1507238750] The copyright should be Copyright (c) 2010-2019 instead of Copyright(c)2010-2018
- [HSD-ES][1607385130] Update Security version to 8
- [HSD-ES][1607423701] Silver Pass debug BIOS will assert in DXE FwBlockService
- Update for IPU 2019.2.
- [HSD-ES][1507689912]The copyright should be Copyright (c) 2010-2020 instead of Copyright 2010-2019.

Changes in ME 04.01.04.109:

1. 111153 SPS ME FW sometimes stop send E2 get OEM power reading cmd to BMC
2. IPMI F5h - Get PMBus Readings command may result in non-zero Completion Code
3. 1808702257 Policy ID 0 disappear after OS restart when parameter Domain HW Protection Enabled is set to False
4. 1808695866 ME FW is non responsive on SMLink0 in S5 after G3 after SPI image flash followed by CMOS clear

Changes in BMC 01.18.12306:

- web page copyright date wrong problem.
- [BMC]The SSH connection will be closed automatically after issuing some commands.
- [BMC][H1 761356] buffer overflow in usbe.ko leads to remote code execution.
- always homepage by default.
- Similar fix with 2103632313:[Grantley][BMC]The SSH connection will be closed automatically after issuing some commands.
- RED team report 2 security issues (File upload and Authentication Bypass)
- It can not receive the DHCP IPv6 IP when update the BMC_1.17.12281 version
- KCS PSIRT enhancement that is for core-bios-done possible security attack
- Implement 2 features: one is Cipher suite 3 support option in web console, second one is RMCP enable/disable option in web console

Changes in FRUSDR 0.28:

- Display version 0.24 in flash interface when flash Frusdr version 0.25.

Please follow the below procedure to update ME using UEFI iFlash32 14.0 Build 11

1. Boot the system to EFI Shell
2. Download ME release package
3. Unzip the ME release package to HD or USB Flash Drive
4. Map the respective storage device in system with the command Shell> map -r
5. Change the Shell to mapped device file system Example: Shell> fs0: (or fs1:)
6. Run the IFlash32 utility on the prompt. Use ME_xx_xx_xx_xxx.cap file when ME operational Image update is required. Use MEComplete_xx_xx_xx_xxx.cap file when Only whole ME Image update is required. fs0:> IFlash32 [File Name] /u /ni
7. Reboot system after the update is completed.

Use OFU to update system firmware by the following steps:

- Install OFU on Windows or Linux system
- Download the latest firmware update package from homepage
- Unzip package to a folder
- Run the following command in Windows command line/Linux terminal window: :flashupdt -u flashupdt.cfg

To update from Windows Preboot Execution Environment (WinPE)

The System Firmware Update Package can be inserted to Windows PE customized image for creating a bootable Windows PE CD. User is able to update system firmware from customized WinPE CD by the following steps:
- Boot server with customized WinPE CD
- Run script "WinPE21_x64_Update.bat" or "WinPE20_x86_Update.bat" (name may be varied depends on your own customization)

About ME Firmware:

If you wish to apply this ME (Management Engine) Firmware version, you should first make sure that the version number matches your AMT (Active Management Technology) family, as each update is specifically developed for certain system configurations.

While this technology is mostly associated with enterprises, it can also be used by various IT administrators as well as regular users. However, bear in mind that even though other platforms might also be compatible, we do not recommend installing this release on OSes other than the specified ones.

About OS Independent BIOS:

Although installing a newer BIOS version might add new features, update various components, or improve the device’s usability, this process is very risky, so the upgrade is recommended to be performed only when it is really needed.

Regardless of the method used or whether the upgrade is performed by a regular or power user, it’s recommended that the new BIOS be applied in a steady power environment such as the one ensured by a UPS unit.

The Basic Input/Output System (BIOS) is a very important software that loads the currently installed OS, and tests all of the system’s hardware components – so make sure you flash it correctly.

Bear in mind that failing to perform a successful installation could seriously damage your device, and the faulty BIOS resulted from the process might even render it unusable.

About Firmware Updates:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device's functionality in the event of a software update either turning up faulty or causing the unit's overall performance to drop. However, bear in mind that applying an older firmware isn't recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it's best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device's firmware. Also make sure you constantly check with our website to ensure that you don't miss a single new release.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.