******************************************************************************* Release notes for Microsoft iSCSI Software Initiator version 2.01 (QFE 908935) ******************************************************************************* * 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 1748 Iscsiprt.sys version 1748 Iscsiexe.exe version 1748 Iscsiupd.dll version 1748 Iscsilog.dll version 1748 iscsidsc.dll version 1748 iscsium.dll version 1748 relnotes.txt version 1748 Mpio.sys (version 1.16 which is the version of the 1.16 Microsoft MPIO binaries) Mpdev.sys (version 1.16 which is the version of the 1.16 Microsoft MPIO binaries) Mpspfltr.sys (version 1.16 which is the version of the 1.16 Microsoft MPIO binaries) If Microsoft iSCSI Software Initiator 2.0 is not installed, it will install the full package. The result in both cases will be the exact same set of binaries with all binaries listed above having the updated version stamp. All other binaries remain at version 2.0 which is 5.2.3790.1653. * Please see the iSCSI Initiator User's Guide for more information on installation and troubleshooting. * The checked and retail versions of the Microsoft iSCSI Software Initiator will only install only on retail version builds of Windows. There is no package that installs on checked builds of Windows. * iSCSI Initiator 2.0 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. 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 applet 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 applet 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. ******************************************************************************* Changes since Microsoft iSCSI Software Initiator 2.0 release 1. Updated Microsoft MPIO binaries to version 1.16 2. Fix in command sequence to check for MaxSequence number correctly. 3. Fix to ensure the load balance policy for multiple connections per session is persisted correctly. 4. Fix for issue not handling spinlock correctly 5. Fix to correctly handle retries in case of Target Redirection. The MS iSCSI Initiator will now retry connection establishment in the case where connection attempt with redirected Target fails. 6. Fix to initiate session recovery in the case of an iSCSI target that does not respond for a long duration. 7. Fix to begin session recovery after 5 Lun resets in the case of an iSCSI target that does not respond Lun Reset due to different expectation on Command Sequence Number. 8. Fix for LUNs not showing up in the bound persistent volumes list when target reported a processor device for a target 9. Fix to not overwrite newer MS MPIO binaries 10. Change to logic for identifying if Lun identity has changed, initiator will map Luns in case identity of old Lun changes. 11. Fix for issue where valid R2T caused a protocol error at the initiator 12. Fix for issue where I/O queue would not be restarted under certain circumstances 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)