******************************************************************************* Release notes for Microsoft iSCSI Software Initiator 2.04 Build version for files updated since version 2.0 is 5.2.3790.3273. Binaries that have not been changed since version 2.0 release are 5.2.3790.1653 2.0x Version history: version 2.0 5.2.3790.1653 version 2.01 5.2.3790.1748 version 2.02 5.2.3790.1895 version 2.03 5.2.3790.3099 version 2.04 5.2.3790.3273 ******************************************************************************* * This is a dual-mode package. If iSCSI 2.0 or higher is installed, it will update just the files that include fixes which are the following: msiscsi.sys version 5.2.3790.3273 iscsiprt.sys version 5.2.3790.3273 iscsiwmi.dll version 5.2.3790.3273 iscsiexe.exe version 5.2.3790.3273 iscsidsc.dll version 5.2.3790.3273 relnotes.txt version 5.2.3790.3273 mpdev.sys version 1.18.3790.1920 (version 1.18 is the most current version of the Microsoft MPIO binaries as of 4-9-07) mpdev.inf version 1.18.3790.1920 (version 1.18 is the most version of the Microsoft MPIO binaries as of 4-09-07) mpspfltr.sys version 1.18.3790.1920 (version 1.18 is the most version of the Microsoft MPIO binaries as of 4-09-07) Please note that the size and date of mpio binaries in the iSCSI initiator package may not appear to be exactly the same as the size of the files released as 1.18. The build date of the 1.18 binaries maps to the build date of the iSCSI initiator package. However, the 1.18 binaries included are the same as binaries released as MS MPIO 1.18. If a previous version of the 2.0x Microsoft iSCSI Software Initiator is not installed, this will install the full package. The result in both cases will be the same set of binaries with all binaries listed above having the updated version stamp for version 2.04. All other binaries remain at previous version levels or at 5.2.3790.1653 if the file has not been updated since the 2.0 release * Please see the iSCSI Initiator User's Guide (uguide.doc) in this package for more information on installation and troubleshooting. * The checked and retail versions of the Microsoft iSCSI Software Initiator will only install on retail version builds of Windows. There is no package that installs on checked builds of Windows. * iSCSI Initiator 2.0x is installed directly to the appropriate locations under the %windir% directory. Documentation is installed under %windir%\iscsi. * Dynamic disks on an iSCSI session are not supported for Windows XP, Windows 2000, and Windows Server 2003. Please see the iSCSI users guide for more information. * Both initiator and target CHAP secrets should be greater than or equal to 12 bytes, and less than or equal to 16 bytes if IPsec is not being used. It should be greater than 1 byte and less than or equal to 16 bytes if IPsec is being used. * Note that the default iSCSI node name is generated from the Windows computer name. If the Windows computer name contains a character that would be invalid within an iSCSI node name, such as '_', then the Microsoft iSCSI Initiator service will convert the invalid character to '-'. * If you have automatic start services that relies upon an iSCSI volume or device, please see the user's guide for information on configuring those devices. * If user requests CHAP for logon authentication, initiator will set AuthMethod to CHAP in logon request. If the target returns None for AuthMethod, initiator will fail the login with status "Authentication Failure". An event will be logged in system event log to indicate that the initiator required CHAP but target did not offer CHAP. If the target returns an authentication method other than CHAP, when the initiator requests CHAP, initiator will fail the login with status "Authentication Failure". An event will be logged in system event log to indicate that the target offered an auth method that the initiator did not understand. * If the target returns CHECK CONDITION for a scsi request, but does not provide sense data, initiator will complete the request with status target error. Initiator does not treat the target behavior as a protocol error. * The Microsoft iSCSI control panel configuration utility includes a Session Detils window that can be accessed by clicking the Details button in the Active Sessions tab. Note that the Path information displayed for each device is only available on Windows 2003 server. * The iSCSI control panel configuration utility does not create an icon in the system tray. If the applet is in the background, you can switch to it by using the ALT-TAB key combination or by double clicking on the icon that launches it. ******************************************************************************* 2.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.18 6. 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 binaries 7. 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 active 10. 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% For additional information, please see the Microsoft iSCSI Initiator users guide and the following industry specifications: * iSCSI spec - RFC3720 * String Profile for iSCSI Names (http://www.ietf.org/internet-drafts/draft-ietf-ips-iscsi-string-prep-04.txt) * Preparation of Internationalized Strings ("stringprep") (RFC 3454) * UTF-8, a transformation format of Unicode and ISO 10646 (RFC 2044) Note on boot support using the Microsoft iSCSI Software Initiator: ********************* Boot support using the Microsoft iSCSI Software is only available in a separate version of the MS iSCSI initiator: Microsoft iSCSI Software Initiator Boot Version. This version is only needed by customers who specifically need to boot a Windows Server 2003 system from an iSCSI target array located on their iSCSI SAN using the software initiator. Although the boot version can be used for access to both data and boot volumes, since the boot version changes the load order of network services and creates a slightly higher requirement for system memory, customers who don’t need to boot their Windows Server 2003 server from the iSCSI SAN specifically should not churn their existing configurations and should stay with the initiator version available from http://www.microsoft.com/downloads All fixes to standard iSCSI components and binaries including MPIO, session recovery, etc. are included in both packages.