Microsoft iSCSI Software Initiator Version 2.04

Posted by bink on April 27 2007, 1:35 PM. Posted in Storage Server (NAS).

This is the latest version of the Microsoft iSCSI Software Initiator. The Microsoft iSCSI Software Initiator enables connection of a Windows 2003, Windows Server 2003 or Windows XP host to an external iSCSI storage array.
(build 3273)Version 2.042.04 Changes (Changes since Microsoft iSCSI Software Initiator 2.03 release) 1. Update iSCSI Initiator MPIO binaries to MPIO 1.18  2. Fix for bugcheck resulting from having a extra session in ibft with incorrect target address 3. Fix to allow up to 8 MCS connections 4. Fix enabling x64 use of management dll on x86. This change causes allos the iSCSI installer for x64 platforms to install the x86 versions of the iSCSI dlls in the syswow64 directory. This allows x86 applications that use the iSCSI apis to run on x64 platforms.   5. Fix to ensure existing Microsoft MPIO binaries installed on the system are correctly upgraded to version 1.186.      Fix to ensure that the Microsoft iSCSI Software initiator does not overwrite newer versions of MPIO binaries Note: Newer MPIO binaries are typically distributed by 3rd party array vendors in their multipathing software packages MPIO binaries are able to upgrade MPIO binaries7. Fix for iSCSI Initiator immediate retries on Queue Full status 8. Fix to Handle page 0x83 > 0xFF, which caused an assert in MPIO 9. Fix for active/standby path assignment being lost after pull and then re-plug network cable when using MCS. After reestablishing a connection that was active under the failover load balance policy, in some scenarios the connection would not come back as active. The change fixes this so the connection will come back as active10.     Fix in WMI interface behavior in the msiscsi.sys driver so that if the RemoveConnection method is called for the last active MCS connection on a session, an error will be returned to the user.  11. Fix for iSCSI Initiator Service-registry entry ImagePath.  The iSCSI installer previously used a hardcoded path when setting the ImagePath registry value under the iSCSI service key. With this fix, the installer uses a path relative to %SystemRoot%Download At Source