ExtremeZ-IP Hot Fix Release History - Version 5.4
All version 5.4 releases are downloaded as full installer packages that contain the File Server, Print Server, and Print Accounting components. After unzipping the downloaded file, you will be presented with a ReadMe file and an executable installer. Simply run the installer and your ExtremeZ-IP installation will be updated and all settings will be retained. Every installer is cumulative and includes all updates from previous versions.
For detailed installation and upgrade instructions please see the ExtremeZ-IP Quick Start Guide. For Cluster Installations please see our Cluster Installation knowledge base article
ExtremeZ-IP 5.4x04 (released 5/12/2009) - Download Now - [ZIP - 17.6 MB]
- Added a set of commonly-used debugging files to the "Debug Logging" subfolder of the application directory.
- Fixed a problem where users could experience slow browsing with UNIX permissions and ACLs enabled.
- Fixed a problem where permissions were not reset properly if "reset permissions on move" was enabled but UNIX permissions/ACLs were disabled. This problem would only occur on Windows Vista and Windows Server 2008.
- Fixed a problem where legacy OS 9 applications could fail to move a file in an ExtremeZ-IP volume if the source or destination path ended in a null character.
- Fixed a problem where the service, Administrator, or installer could crash if the system contained a non-ExtremeZ-IP service containing "ExtremeZ-IP" in its display name.
- Fixed a problem where search index files could grow to very large sizes without automatically pruning themselves.
- Fixed a problem where indexed search could fail to return all results for volumes whose index file exceeds 4 MB.
- Fixed a problem where search index files could consume more than the allowable maximum amount of memory (20 MB, by default).
- Fixed a problem where folder modification dates could improperly get updated to "now" after duplication.
- Fixed a problem where ExtremeZ-IP could crash when the service was stopped or restarted. This crash was more likely to occur on Windows 2008 Server.