Introduction
Power budget tool for use on Intel® Server Board S5500WB family
Available Downloads
- Windows Server 2008 family*, Windows Server 2003 family*
- Size: 272 KB
- SHA1: 481F2E1BAFA852EE681534126AD8DD9F778C60A3
- Windows Server 2008 family*, Windows Server 2003 family*
- Size: 264 KB
- SHA1: A77DBF0314FFA99A41D1BF30E2517E175F2E3E2C
- Windows Server 2008 family*, Windows Server 2003 family*
- Size: 276.5 KB
- SHA1: 9319CCF618338D8CD3BC50DB3C6D5E67A642308C
- Windows Server 2008 family*, Windows Server 2003 family*
- Size: 269 KB
- SHA1: 0CEFD6555C5C4571CC9A4749690C836B3741AB71
Detailed Description
There are four Excel* spreadsheets available. Each one is for a different member of the Intel® S5500WB Server Board family.
If you have the SS5500WB motherboard with a standard "off the shelf" power supply, in a non-Intel chassis, download S5500WB_SSI_powerbudget_tool_v04.xls
If you have the SS5500WB in an non-Intel chassis with a 12V "single rail" power supply, use S5500WB_12Vonly_powerbudget_tool_v05.xls
If you purchased the integrated SKU, the S5500WB board in the SR1690 chassis, use SR1690WB_SSI_powerbudget_tool_R02.xls
If you purchased the SKU that comes with the S5500WB in the 12V SR1695 chassis, use SR1695WB_12Vonly_powerbudget_tool_v4.xls
If you have the SS5500WB motherboard with a standard "off the shelf" power supply, in a non-Intel chassis, download S5500WB_SSI_powerbudget_tool_v04.xls
If you have the SS5500WB in an non-Intel chassis with a 12V "single rail" power supply, use S5500WB_12Vonly_powerbudget_tool_v05.xls
If you purchased the integrated SKU, the S5500WB board in the SR1690 chassis, use SR1690WB_SSI_powerbudget_tool_R02.xls
If you purchased the SKU that comes with the S5500WB in the 12V SR1695 chassis, use SR1695WB_12Vonly_powerbudget_tool_v4.xls
This download is valid for the product(s) listed below.
Disclaimers1
Product and Performance Information
1
Intel is in the process of removing non-inclusive language from our current documentation, user interfaces, and code. Please note that retroactive changes are not always possible, and some non-inclusive language may remain in older documentation, user interfaces, and code.