ExtremeZ-IP Version History
ExtremeZ-IP 7.2 (Released: July 2011)
ENHANCEMENTS:
* ExtremeZ-IP is now certified with Mac OS 10.7 Lion. However, DFS-based home directories are not yet supported for Mac OS X 10.7 Lion clients. Support for DFS-based home directories will require a follow-up release of ExtremeZ-IP and/or Mac OS 10.7.
* All copies of ExtremeZ-IP now include ShadowConnect, which allows Mac clients to browse and restore previous versions of documents.
* The default node table size has been increased from 20 to 200 MB to improve performance. [US1956][7.2x133]
BUG FIXES:
* Fixed a crash at session shutdown introduced in the 7.1.2x142 release. [US1823][7.2x117]
* Fixed a crash at service shutdown introduced in the 7.1.2x142 release. [US2042][7.2x117]
* Fixed a crash during the processing of Windows shortcuts. [US1973][7.2x135]
* Spotlight searches are now supported with Lion Mac OS X clients. [US1565] [7.2x115]
* Time Machine backups are now supported with Lion Mac OS X clients. [US1854] [7.2x125]
* Fixed a problem where clients could be disconnected because they were incorrectly determined to be idle. [US1700][7.2x121]
* Fixed a problem where DFS volumes would fail to initialize after being restarted via the ExtremeZ-IP Administrator. [US1739] [7.2x115]
* ExtremeZ-IP will now remove the volume mapping stream when volumes are removed via the ExtremeZ-IP Administrator. [US1738][7.2x135]
* Fixed a bug related to DFS and clusters. ExtremeZ-IP changed the way it determines the computer name on a cluster, when contacting remote servers to establish/enumerate DFS targets for initial use. Now, when it detects that a computer name is not valid (for any reason) when enumerating the DFS targets, it will attempt to enumerate the cluster names of the server using the Windows Cluster API with the DNS name of that server. If it gets back a valid cluster name, it will use that in place of the DNS name to enumerate the DFS targets on that server.
Fixed a problem with Shadow Connect and foreign language support. ExtremeZ-IP will now properly parse the output from the Windows VSSADMIN command regardless of the localized language on the machine, assuming the VSS registry keys in the VSSRefreshableZIPService section of the registry are set properly for the locale (see below). [US2044][7.2x165]
|
