Windows Integrity Enterprise Edition and Datacenter Edition Release Notes

NOTE: On rx1620, Windows Server 2003 supports 256 MB, 512 MB, 1 GB, and 2 GB DIMMS
only. 4 GB DIMMs are not supported. When migrating from another OS to Windows Server 2003
on servers where 4 GB DIMMs are installed, replace the 4 GB DIMMs with supported DIMMs.
BL860c Server Blade
Table 1-13
• Windows Server 2003, Enterprise Edition with SP1/SP2 for Itanium-based Systems
• Windows Server 2003, Datacenter Edition with SP1/SP2 for Itanium-based Systems
Operating System
• Dual Port 4Gbps FC Mezzanine Card (Q-Logic) (403619-B21)
• Direct Adaptor Mezzanine Card for connecting to the Direct Attached Storage
Blade (431643-B21)
I/O Mezzanine Support
Troubleshooting Common Issues
Read this section completely before installing or running Windows Server 2003 on HP Integrity
servers. This section includes workarounds that may save you valuable time and effort.
Array Configuration Utility (ACU)
verifer.exe causes ACU inaccuracies
Issue ACU reports incorrect results when the Windows Driver Verifier
(verifier.exe) is enabled and running in the background.
Servers All Integrity
Workaround There is no workaround at this time. To run the ACU, you must first end the
verifier.exe process using the Windows Task Manager, then launch ACU.
Do not run both simultaneously.
Array Diagnostic Utility (ADU)
Uninstall feature unfunctional
Issue The ADU uninstall feature is not working.
Servers All Integrity
Workaround There is no workaround at this time.
Clustering
Cluster notes unable to see messages
Issue Normally in a cluster, when an application in one node logs an event to the
Windows Event Log, the message is visible to all nodes in the cluster. However,
due to a Microsoft limitation, when events are logged with more than 900 bytes
in the “lpRawData” binary field (as reported by the Microsoft API
“ReportEvent”), only the node that issued the event can see it using the Windows
Event Viewer. Other nodes in the cluster are unable to see these messages.
Servers Superdome, rx8620, rx7620
Workaround There is no workaround at this time.
20 Release 5.1 Overview