Known Issues

After setting up the system for iSCSI Remote Boot with two ports connected to a target and successfully booting the system, if you later try to boot the system with only the secondary boot port connected to the target, Microsoft Initiator will continuously reboot the system.

To work around this limitation follow these steps:

1. Using Registry Editor, expand the following registry key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

2. Create a DWORD value called DisableDHCPMediaSense and set the value to 0.

If you are using two Intel® PRO/1000 PT Server Adapters in two PCI Express x8 slots of a rack mounted Xeon system, Windows installation can be done only via a local HDD procedure.

If an iSCSI Remote Boot port CHAP user name and secret do not match the target CHAP user name and secret, Windows Server 2008 may blue screen or reboot during installation or boot. Ensure that all CHAP settings match those set on the target(s).

If you are performing an F6 Windows without a Local Disk installation, do not use Standby Mode.

If you perform a WDS installation and attempt to manually update drivers during the installation, the drivers load but the iSCSI Target LUN does not display in the installation location list. This is a known WDS limitation with no current fix. You must therefore either perform the installation from a DVD or USB media or inject the drivers on the WDS WinPE image.

Microsoft has published a knowledge base case explaining the limitation in loading drivers when installing with iSCSI Boot via a WDS server.
http://support.microsoft.com/kb/960924

Teaming is not supported with iSCSI Remote Boot. Creating a team using the primary and secondary iSCSI adapters and selecting that team during the Microsoft initiator installation may fail with constant reboots. Do not select a team for iSCSI Remote Boot, even if it is available for selection during initiator installation.

For load balancing and failover support, you can use MSFT MPIO instead. Check the Microsoft Initiator User Guide on how to setup MPIO.

Performing an F6 diskless installation while a removable or temporary storage device (such as a USB flash drive or Firewire drive) is loaded may cause a change in the BIOS boot order. If this occurs, you must re-start the F6 diskless installation. For this reason we recommend not loading a removable or temporary storage device while performing an F6 diskless installation.

This is a known issue for Windows Server 2003 and cannot be rectified by Intel iSCSI Remote Boot. Additional information about this Windows Server 2003 issue can be found in Microsoft support article kb816793.