Skip to main content

Precautions when using Windows Server 2003 SP2

Windows | Windows Server 2003 SP | Precautions


Last Reviewed June 3, 2009

The following table lists items that must be checked when using PRIMEQUEST Series and Bundled Software.

Window Server 2003 SP2

Applies To Precautions OS Edition Last Review
PCI Express SAS card
[MC-08SS21]
SAS Expansion File Unit
[MC-03F121U/ MC-03F131U]
SAS Expansion File Unit (for China) [MC-03F121C]
PCI Express Fibre Channel cards
[MC-08FC51 / MC-08FC61 / MC-08FC81 / MC-08FC91]
To use PCI Express SAS cards and PCI Express Fibre Channel cards in a Windows Server 2003 , confirm that the drivere used is 2.10a7 or later. You can download this driver from here.

Apply the Fibre Channel cards driver of the number of the same versions to the driver of all Fibre Channel cards useing.

The matching EFI driver and Fibre Channel driver versions differ pending on the Fibre Channel card model being use.

To determine the correct matching version refer to: "How to update PRIMEQUEST Fibre Channel Card Firmware/EFI driver."
Enterprise Edition / Datacenter Edition Jun. 3, 2009
PRIMEQUEST 400Series/ 500Series / 500ASeries
Fibre Channel cards
MC-08FC11
MC-08FC31
MC-08FC41
MC-08FC51
MC-08FC61
MC-08FC71
MC-08FC81
MC-08FC91
To use these Fibre Channel cards in a Windows Server 2003 SP2 environment, the Microsoft Quick Fix Engineering Windows revision module (QFE) KB945119 must be applied and the Fibre channel card driver, firmware and EFI driver updated.

The matching Fibre Channel card driver, firmware and EFI driver versions differ pending on the Fibre Channel card model being use.

To determine the correct matching version refer to: "How to update PRIMEQUEST Fibre Channel Card Firmware/EFI driver."

Download Fibre Channel card drivers and QFE from here.
Enterprise Edition/Datacenter Edition Jun. 3, 2009
SAS Card
[MC-08SS11]
PCI Express SAS card
[MC-08SS21]
To use these SAS cards in a Windows Server 2008 environment, confirm that the driver used is 1.27.03.00 or later. You can download this driver from here.

NOTE: If using these SAS cards and the on-board SAS controller together, the driver must be installed twice. One for these SAS cards and again for on-board SAS controller.
Enterprise Edition / Datacenter Edition Dec. 4, 2008
PRIMEQEUST 400Series / 500Series / 500ASeries Symptoms
Windows firewall settings may need to be changed when you apply SP2.

Action
[Advanced] tab on [Windows Firewall] of [Start]-[Control Panel] , Confirm whether [Network Connection Settings] are set correctly.
Enterprise Edition/Datacenter Edition Jul. 15, 2008
PRIMEQEUST 400Series / 500Series / 500ASeries
Dual Channel Ultra320
SCSI cards:
MC-08SC21
MC-08SC11
Symptoms
Increased shutdown times or blue screen/halt error displayed.

Action
To use these SCSI cards in a Windows Server 2003 SP2 environment, update the drivers.

To confirm whether one of these SCSI cards is in use, see here.

If using these SCSI cards PRIMEQUEST 580/540 and 480/440, apply the revised drivers to any on-board SCSI in the same partition.

Use device manager, to apply them to all SCSI ports one by one. Refer to "PRIMEQUEST SCSI card Users Guide" bundled with revision drivers for the update method.

Driver versions V1.25.05.00
Download drivers form here.
Enterprise Edition/ Datacenter Edition Jul. 15, 2008

Bundled Software

Applies To Version Precautions Last Review
SystemcastWizard Lite V1.1
V1.1A
V1.2
V1.2A
V1.2B
V1.3
V1.4
V1.5
V1.6
V1.6A
V1.7
V1.8
V1.8A
V1.9
V2.0
V2.0A
A vulnerability exists in the PXE service, TFTP service and in the Registry Setting Tool.

1. Description of Vulnerability
A buffer overflow can occur in the PXE service and due to the Registry Setting Tool of this software.
In addition, a directory traversal occurs with the TFTP service of this software.

2. Vulnerability Threat
Can cause arbitrary code to be executed on the deployment server and can cause the PXE service to crash.
In addition it may allow users not authorised to use the deployment server to refer to files.

3. Update Patch
Download Patch from here.

credit:
Ruben Santamarta of R&D/Reverse Engineer in Wintercore, reported this vulnerability to us.
Jan. 29, 2009