What's new in globalSAN iSCSI Initiator 5.3.1.562
Sep 4, 2018
- Addressed an issue with activation key [GLO-424]
- Fixed an issue causing Xtarget's checkbox to be invisible in Sierra [GLO-446]
- Fixed a KP that could occur when using CHAP under Sierra [GLO-441]
New in globalSAN iSCSI Initiator 5.3.0.518 (Dec 28, 2015)
- New Features:
- Support for OS X El Capitan [GLO-413]
- Support for OS X Yosemite [GLO-386]
- Support for Amazon AWS Gateway Target [GLO-321]
- Fixes:
- Addressed issues with FreeBSD CTL target [GLO-359] [GLO-410]
- Improved iSCSI logout sequence [GLO-371]
- Improved user feedback in GUI and CLI for long-running operations [GLO-372]
New in globalSAN iSCSI Initiator 5.2.0.429 (Jan 23, 2014)
- New Features & Licensing Changes:
- Support for OS X Mavericks [GLO-342]
- Drivers are now digitally signed [GLO-349]
- Added capability to move full/paid initiator license from one computer to another [GLO-259]
- Initiator trial mode no longer requires manually entering a key to begin [GLO-319]
- Persistent connections no longer allowed in trial mode [GLO-324]
- Improved UX with initiator when connected to EVO [GLO-186]
- Fixes:
- Addressed initiator connectivity issue with Windows Server 2012 [GLO-327]
- Improved initiator performance when CRC enabled in 10GbE environment [GLO-333]
- Fixed issue that could cause System Preferences to hang when opening globalSAN [GLO-351]
- Fixed issue that could cause System Profiler to crash when opening [GLO-343]
- Fixed and addressed incompatibility between Xtarget and VMware ESXi iSCSI initiator [GLO-268]
- Addressed Xtarget issue that was only seen in 10.8 + Ivy Bridge where Finder stalled while writing to an iSCSI/FireWire device [GLO-335]
New in globalSAN iSCSI Initiator 4.1.0.247 Beta (Nov 24, 2010)
- New Features:
- Snow Leopard support (32-bit and 64-bit kernels).
New in globalSAN iSCSI Initiator 4.0.0.204 (Apr 19, 2010)
- New Features:
- Snow Leopard support (32-bit kernel)
- Supports sleep and hibernate
- Redesigned user interface
- Multipathing
- It is no longer necessary to log in before globalSAN will restore persistent connections
- Increased security (non-authenticated users cannot add/remove a target)
- Increased compatibility with some targets
- Asynchronous logout
- Recovery of redirected logins uses the original IP (per "Gilligan" spec.)