ExtremeZ-IP 5.0.1 (Released: April 2007) ENHANCEMENTS:
* Added capability for volumes to be configured so that moved files and folders inherit permissions from their new parent folders, rather than retaining their previous permissions. By default, Windows will retain
file and folder permissions after a move, but enabling this optional feature will ensure that these "old" permissions do not carry over after the move. This feature can be enabled for specific volumes, or by a global setting. [#7386] [5.0.1x01]
* Added code to place a warning in the Windows Event Log if Kerberos clients fail to authenticate because the server time differs from the time on the domain controller. [#6894] [5.0.1x01]
* Fixed problem where applications such as Photoshop, InDesign and Quark could give errors when saving to an existing file. This problem could cause errors in the application itself, and could cause the file to disappear from the Finder. This issue was present in the ExtremeZ-IP 5.0.1x07 hotfix only. [#7923] [5.0.1x09]
* Fixed problem where server could become unresponsive and connected clients could disconnect, requiring a restart of the service. This issue was present in ExtremeZ-IP 5.0 only. [#7913] [5.0.1x08]
* Fixed problem where ExtremeZ-IP would fail to fully enumerate the contents of a folder, causing files and folders to be invisible to the Finder or other applications. This problem was most likely to occur on gigabit networks, and when using applications such as Rampage that enumerate items in large blocks (32 at a time) compared to the Finder (20 items at a time). This issue was present ExtremeZ-IP 5.0 only. [#7886] [5.0.1x05]
* Fixed problem where idle OS 9 clients could be disconnected from the server. This issue was present in ExtremeZ-IP 5.0 only. [#7905] [5.0.1x08]
* Fixed problem where ExtremeZ-IP would return the wrong error code when a client attempted to perform a byte-range lock on a section of a file that already contained a byte-range lock from that client. This could cause some applications (such as Microsoft Word running in Classic mode) to incorrectly open a file in read-only mode. This issue was present in all versions of ExtremeZ-IP through 5.0. [#7732] [5.0.1x01]
* Fixed problem where ExtremeZ-IP Server name would not match the Network Name dependency on a cluster, but would have "IP" appended to it. This issue was present in ExtremeZ-IP 5.0 only. [#7887] [5.0.1x05]
* Fixed problem where selecting an existing extension in the Type and Creator window of the Administrator would fail to cause the corresponding type/creator to become selected. This issue was present ExtremeZ-IP 5.0 only. [#7888] [5.0.1x06]
* Fixed problem where a "ghosted" session could be left in "Waiting For Reconnect" state after a client reconnected to the server. This issue was present in ExtremeZ-IP 5.0 only. [#7795] [5.0.1x08]
* Fixed problem certain files could fail to have their Finder information migrated from their corresponding dot underscore files. This issue was present in ExtremeZ-IP 5.0 only. [#7883] [5.0.1x08]
* Changed behavior so that modifications to .DS_Store files do not cause the volume's modification time to be updated. This issue was present in all versions of ExtremeZ-IP from 4.0 through 5.0. [#3437] [5.0.1x01]
* Added code to gracefully handle situation when client asks for deprecated "launch limit" parameter. This issue was present in all versions of ExtremeZ-IP 4.0 through 5.0. [#3281] [5.0.1x01]
* Fixed problem where clients could fail to mount a volume containing an 8-character volume password. This issue was present in all versions of ExtremeZ-IP through 5.0. [#7612] [5.0.1x01]
* Fixed problem where the ExtremeZ-IP Administrator would fail to refresh the display of the number of locks for an opened file in the Files Window. Previously, the window would have to be closed and reopened for the value to properly update. This issue was present in all versions of ExtremeZ-IP through 5.0. [#7740] [5.0.1x01]
ExtremeZ-IP 5.0 (Released: February 2007) ENHANCEMENTS:
* Added support for the migration of existing SFM shares and the replication of SMB shares.
* Added support for nested volumes.
* Added support for migrating SMB "dot underscore" data into data files so that resource and finder information are available through ExtremeZ-IP.
* Added support for performance counters. ExtremeZ-IP publishes counter data so that the status of ExtremeZ-IP can be tracked with tools such as Perfmon and Microsoft Operations Manager (MOM). Some examples of available counters are "Users (Total)" and "Bytes read/sec".
* Added support for client reconnect. Clients will now automatically reconnect to the server after a network outage, server crash or reboot or cluster failover. Files open by the client will remain available after reconnect. ExtremeZ-IP contains a number options to configure reconnect behavior - see the Online Help file for details.
* Introduced a new thread pool architecture within ExtremeZ-IP. ExtremeZ-IP uses a dynamically sized thread pool to manage server activity, which will scale as the server is under load. Prior versions of ExtremeZ-IP would use 2 threads per user session, which limited the total number of sessions that could be handled simultaneously on a fast machine to 700-800 users, with significant overhead for thread context switching and other housecleaning operations. The new thread pooling architecture allows significant more users to be connected while consuming less memory and CPU resources. The thread pool can be configured via the Registry.
* Significant performance enhancements have been made to common AFP commands such as enumerations and getting information about files and folders. These enhancements reduce the amount of time it takes to respond to commands significantly, especially when under stress, and also reduce the load on the server. ExtremeZ-IP now caches more information and spends less time accessing the disk.
* Added support for server notifications, which help notify the remote client that it should reenumerate the contents of open Finder windows. [#7418] [5.0x122]
* Added support for sharing the root of a volume.
* Added support for modifying the serial number without stopping the service - thus allowing upgrades from File to Print Server or an increase in client count without requiring a service restart.
* Improved online help, allowing for the automatic copy of registry value names in order to simplify the process of modifying registry settings.
* Added Unicode support to the ExtremeZ-IP Administrator. The Administrator now properly displays volumes, paths, print queues, files and usernames containing Unicode characters. Administrators can now send Unicode messages to connected users as well. [#2266] [5.0x41]
* Improved logic for saving search index files. Files are now automatically placed in a single, global folder. This global folder can be customized through the Administrator, and individual volumes can override this global setting.
* Added code to cache information about domain controllers to speed up logins for domain users. [#6722] [5.0x41]
* Expanded the number of new clients that can connect to the server at nearly the same time from 5 to 128. This will remove situations where when 100s of users attempt to login to the server within a short period of time, a number of them get an error that the server is not responding.
* Added additional diagnostic logging to the debug log, such as commands processed per second, statistics on the thread pool and its usage patterns, and the number of users connected among other things.
* Added support for UTF-8 (Unicode) server names. [#2552] [5.0x113]
* Added optional feature requiring clients to change their passwords prior to expiration. See online help for more information on enabling this feature using the ForcedPasswordChangePeriod registry value. [#4496] [5.0x122]
* Improved performance when dealing with new files by flushing id/index information to disk less often. [#4854] [5.0x113]
* Fixed AdjustMacPermissions so that it properly creates write-only (drop) folders. [#5224] [5.0x128]
* Added an additional column to the Administrator's Users window indicating the status of a user: "Active", "Idle", "Sleeping" or "Waiting for Reconnect". [#6953] [5.0x122]
* Added support for longer logon messages through the LogonMsgW registry value (see online help for more information). Note that while ExtremeZ-IP supports logon messages up to 1024 characters, current versions of Macintosh OS X will fail to display messages longer than 500 characters. [#7377] [5.0x122]
* Added a warning to the main window of the Administrator when the service is configured to use a non-standard AFP port. [#7471] [5.0x122]
* Improved support for Unicode strings in the EZIPUTIL command-line utility. [#7577] [5.0x129]
* Extended "default domain" code to allows administrators to provide a list of default domains to try (in order) when a user logs on. See the help file for more information on the DefaultDomainName registry value. [#6735] [5.0x132]
* Improved search indexing code to reduce the likelihood that the volume has to be reindexed, and added additional logging to help diagnose why a reindex was needed. [#7039] [5.0x132]
* Fixed a problem where the ExtremeZ-IP could crash if a client duplicated a very large file (e.g. 4GB) and the volume was then removed. [#5688] [5.0x26]
* Fixed a problem where a client could receive a -36 error when attempting to copy folders ending in "#XXXX" to the server, where "XXXX" is a number. [#5598] [5.0x26]
* Fixed a problem where changing the IP addresses of servers on the network could cause Macintosh clients to connect to the wrong server. This problem was fixed by modifying the way ExtremeZ-IP generates its "server signature", a unique identifier for each server on the network. This signature is now based on the MAC address of the server's network card, the server's IP address and the ExtremeZ-IP service name. Previous signatures were only based on the IP address, which could mean that swapping two server's IP addresses could cause a Macintosh client to connect to the wrong server. However, modifying the way ExtremeZ-IP generates its signature means that any credentials cached in client's keychains prior to upgrading to 5.0 will no longer be valid - these clients will need to reenter their credentials so that they can be associated with the new server signature. [#845] [5.0x26]
* Improved conformance with AFP specification by updating the modification time of a folder when the invisibility or finder information of one of its children is modified. [#2424] [5.0x116]
* Fixed a problem where ExtremeZ-IP could fail to notice changes to the permissions of the root of a volume. Changes to the root of the volume are now updated within 1 minute. [#6387] [5.0x113]
* Fixed a problem disconnecting an OS 9 user from the Administrator could fail if the user was in the middle of a large file copy. These clients will now be disconnected within 30 seconds even if the copy is not complete. [#7081] [5.0x113]
* Fixed a problem where saving documents in certain applications (such as TextEdit) could cause those files' color labels (and other finder information) to be lost. [#7144] [5.0x120]
* Fixed a problem where searches on file size could mistakenly return 0 results. [#7153] [5.0x114]
* Fixed a problem where the ExtremeZ-IP Operation Log could fail to show all event log messages on servers with a larger number of such messages. [#7488] [5.0x123]
ExtremeZ-IP 4.2.4 (Released: October 2006) BUG FIXES:
* Fixed an issue where ExtremeZ-IP could fail to release a file handle to a folder after a failed rename or move operation. This could cause the folder to not be fully removed from the file system after a deletion request from the client. [#7261] [4.2.4x03]
* Fixed a potential crash in home directory support. The crash could occur if a client machine attempted to access another user's home directory. [#7199] [4.2.4x01]
* Fixed a problem where ExtremeZ-IP could return the wrong resource or data fork size for an open file. This could cause file corruption or other application problems. [#7158] [4.2.4x01]
ExtremeZ-IP 4.2.3 (Released: August 2006) ENHANCEMENTS:
* Added ServerIgnoresReadOnlyFolders registry key. If enabled, the server will not display any folders as locked, even if they are marked "read-only" in Windows. See the help file for more details. [#6373] [4.2.3x02]
* Added ServerLogsPerformanceStats registry key. If disabled, the server will not attempt to load the performance data helper DLL and will not output performance stats into the log. This key addresses a problem where ExtremeZ-IP can hang at startup trying to load that DLL. See the help file for more details. [#6586] [4.2.3x03]
* Fixed a problem where files could fail to show up in indexed searches after being saved in applications such as Microsoft Word. [#6304] [#4.2.3x01]
* Fixed a problem PictroMatch would fail to delete files from a watched folder within an ExtremeZ-IP volume. This problem was due to a bug in the support for the AFP Move command. [#6376] [#4.2.3x01]
* Fixed a problem where the system statistics that are output every minute stopped being output. [#6811] [#4.2.3x05]
ExtremeZ-IP 4.2.2 (Released: April 2006) ENHANCEMENTS:
* Added a dialog that warns administrators about the risks of sharing out the root of a drive. [#4298] [#4.2.2x07]
* Made the "SleepInterval" registry key refreshable. [#6218] [4.2.2x01]
* Improved performance of opening the Log window of the Administrator. [#2119] [#4.2.2x01]
* Added a workaround for a problem where files saved in Adobe Photoshop CS2 would cause Photoshop to crash when running on OS 10.4.6. This crash is a result of OS 10.4.6’s support for file comments greater than 128 characters and Photoshop CS2’s lack of support for these long comments. To activate this workaround, enable the "ServerTruncatesOS9Comments" registry key. This will cause all files with long comments that are written to an ExtremeZ-IP network volume to have their file comments truncated to 128 characters. See the help file for more details. [#6355] [4.2.2x07]
* Fixed a problem where sleeping sessions would take 30 seconds to be disconnected from the Administrator. [#6335] [4.2.2x07]
* Fixed a problem where search index files from different volumes could collide if stored in the same folder. [#6323] [4.2.2x07]
* Fixed a problem where search indexing would not initialize properly on a volume that had previously failed to come online. [#6264] [4.2.2x06]
* Fixed a problem where the service could crash while reindexing a volume's search index. [#6268] [4.2.2x05]
* Fixed a problem where inaccessible files and/or folders could be displayed on the client machine even if the server was configured to hide inaccessible files or folders. [#6237] [4.2.2x01]
* Fixed a problem where the number of open forks listed in the main windows of the Administrator would sometimes not match the number of forks listed in the Administrator's Files window. [#5702] [4.2.2x01]
ExtremeZ-IP 4.2.1 (Released: February 2006) ENHANCEMENTS:
* When uploading a file with a blank creation date (Jan 1, 1970), the creation date will be set to match the modification date. Files transferred from a USB drive (FAT) to a Macintosh may not have creation dates. [#5549] [4.2.1x01]
* Fixed a problem where an empty file could be created at a volume location if the folder corresponding to that volume was not found. [#6260] [4.2.2x03]
* Fixed a problem where Library Pro databases could not be reindexed when the database file was on a remote ExtremeZ-IP volume. [#6174] [4.2.1x03]
* Fixed a problem where errors relating to "Perflib" would appear in the Windows Event Viewer when users connected to ExtremeZ-IP. This would occur if the users did not have access to the "Perflib" portion of the registry. [#6170] [4.2.1x03]
* Fixed a problem where clients could get disconnected after receiving an incorrect error message when attempting to read past the end of a file. [#6127] [4.2.1x01]
ExtremeZ-IP 4.2 (Released: February 2006) ENHANCEMENTS:
* Added ability to customize volumes as home directories through the ExtremeZ-IP Administrator. [#5478] [4.2x30]
* Added an optional feature (disabled by default) that allows administrators to prevent users from performing searches that do not contain "name" as one of the criteria. These searches are much slower than "name" searches and can cause ExtremeZ-IP to use a large amount of CPU for the length of the search. Users who attempt to perform non-name searches are sent a warning dialog. See the ExtremeZ-IP Help for more information on this feature. [#5969] [4.1.1x16]
* Fixed a problem where certain files (particularly Microsoft Word documents) could disappear from the Finder. [#5746] [4.2x34]
* Fixed a problem where the server could suddenly experience high CPU usage and hanging user sessions when performing an indexed search. [#6010] [4.1.1x22]
* Fixed a problem where OS 9 clients could fail to create folder names sent in a particular format (with null characters at the beginning and end of the folder name). This problem could cause applications like "4D thin client" to fail. [#5975] [4.1.1x16]
* Fixed a problem where files could be corrupted when saving to the server while another user was viewing the same folder. The corruptions could occur in a variety of applications, such as Microsoft Word and Adobe Illustrator. [#5944] [4.1.1x14]
ExtremeZ-IP 4.1.1 (Released: December 2005) ENHANCEMENTS:
* Added warning to administrators that attempt to create volumes that the service does not have full control over. A warning is now given when the volume is created, and each time the volume comes online. The user account under which the service runs (usually SYSTEM) should have full control over the entire volume, but particularly the root of the volume. Creating ExtremeZ-IP volumes without giving the service full control is strongly discouraged, as it can prevent Macintosh file IDs from being persisted across instances of the service. [#4375] [4.1.1x11]
* Added logging of ExtremeZ-IP CPU usage (as opposed to system-wide CPU usage). [#5765] [4.1.1x03]
* Added the ability to time out idle users. See the ExtremeZ-IP help file for more information. [#1674] [4.1.1x01]
* Fixed a problem where replies to the AFPByteRangeLockExt command were not properly formed. [#4582] [4.1.1x09]
* Fixed a problem where users could experience poor performance when using client-side applications (such as Prinergy) that dealt with folders containing large numbers of files (thousands or more). [#5826] [4.1.1x07]
* Fixed a problem where volumes could not be mounted using the Classic Chooser under Mac OS 10.4. [#5773] [4.1.1x06]
* Fixed a problem where clients could fail to reconnect after server failover. [#5788] [4.1.1x05]
* Fixed a problem where ExtremeZ-IP could report stale information about a file if the file was being modified simultaneously from multiple clients. [#5640] [4.1.1x03]
* Fixed a problem where the Administrator would hang when trying to display the Log window when running on Windows 2003, 64-bit Edition. [#5706] [4.1.1x02]
* Fixed a problem where the Administrator could not show paths for open files that the SYSTEM account did not have access to. Under these conditions, the Files window would show “Path not available - SYSTEM does not have access to this file”, and the file could not be closed. [#5442] [4.1.1x01]
ExtremeZ-IP 4.1 (Released: October 2005) ENHANCEMENTS:
* Changed the default node table cache size to 20 Mb for better performance under load. [#5431] [4.1x07]
* Modified pruning of old Macintosh file IDs to occur weekly, regardless of whether or not ExtremeZ-IP had been running continuously during that time. Previous versions of ExtremeZ-IP would prune only after a week of uptime. [#5228] [4.1x08]
* Added fast indexed file search feature. Further information, configuration instructions, and tips related to this feature can be found in the Group Logic knowledge base article located at: http://www.grouplogic.com/knowledge/index.cfm/fuseaction/view_Info/docID/198 [4.1x01]
* Fixed a problem where drop folders (write-only) could not be deleted from the Windows side. [#5637] [4.1x18]
* Fixed a potential crash that could occur when using any client application that utilizes the ExchangeFiles command (e.g. Microsoft Office). [#5624] [4.1x16]
* Migrated the ‘PruningInterval’ key from the ‘NonRefreshable’ portion of the ExtremeZ-IP registry to the ‘Refreshable’ portion. [#5522] [4.1x11]
* Fixed a problem where files could not be copied into drop folders (write-only). These copies could fail within a single volume, or from volume to volume. [#5411] [4.1x09]
* Fixed a problem where resource forks could be lost in certain workflows involving Output Manager. Output Manager creates resource forks that could not previously be read by ExtremeZ-IP. [#5067] [4.1x08]
* Fixed a problem where ExtremeZ-IP could incorrectly report a serial number conflict on machines with multiple NIC cards. [#5216] [4.1x03]
* Fixed a minor memory leak that could occur when users logged on and off using Kerberos authentication. [#5209] [4.1x03]
* Fixed a minor memory leak that could occur when users disconnected from the server. [#5210] [4.1x03]
* Fixed a file resize issue where an application would fail to read from the end of a file immediately after resizing the file. This issue could cause files to become corrupted from applications such as Linocolor 6.0. [#5196] [4.1x03]
The following search related issues may occur when searching an ExtremeZ-IP 4.1 server with search indexing enabled from a Mac OS X 10.4 – 10.4.3 client. These issues are seemingly caused by bugs in Mac OS 10.4 and should hopefully be addressed in an upcoming software update.
* A file search may become unresponsive when returning a large number of results (1000 ). The search should complete successfully if given a couple minutes to complete.
* A file search may become unresponsive when typing slowly in the Finder window search prompt. This is caused by 10.4 automatically initiating a search on a partial search term as you type. This will frequently return a large number of results and is a side effect of the previous problem.
ExtremeZ-IP 4.0.6 (Released: August 2005) ENHANCEMENTS:
* The EZIPUTIL command-line interface will output the number of open forks and locks (SERVER /INFO) and the connected and idle time (SERVER /USERS). [#5141] [4.0.6x06]
* Added support for automatic upgrade of active/passive 3.0 settings to an active/active 4.0 service. [#5101] [4.0.6x03]
* The EZIPUTIL command-line interface supports two additional options: the listing of open files, and logged-in users. Enter "EZIPUTIL SERVER" from the command-line for more information. [#5063] [4.0.6x01]
* Fixed a problem where files could fail to save properly within "munged" folders on OS 9 - folders with names over 32 characters. This was known to occur with Linocolor 6. [#5338] [4.0.6x12]
* Fixed a problem where opening a document could change the modification time of the file. This was known to occur with Quark 4 (OS 9) documents containing linked images. [#5120] [4.0.6x12]
* Fixed a problem where ExtremeZ-IP could incorrectly report a serial number conflict on machines with multiple NIC cards. [#5216] [4.0.6x11]
* Fixed a minor memory leak that could occur when users logged on and off using Kerberos authentication. [#5209] [4.0.6x11]
* Fixed a minor memory leak that could occur when users disconnected from the server. [#5210] [4.0.6x11]
* Fixed a file resize issue where an application would fail to read from the end of a file immediately after resizing the file. This issue could cause files to become corrupted from applications such as Linocolor 6.0. [#5196] [4.0.6x11]
* Fixed a problem where duplicating a folder with a custom icon would generate a folder without a custom icon, and with a visible "ICON" file. [#5109] [4.0.6x06]
* Fixed a problem adding or removing a volume while under load could cause connections to hang or disconnect. [#5185] [4.0.6x05]
* Fixed a problem where users could fail to log into Quark Publishing System when running under OS 10.4 Classic mode. [#4551] [4.0.6x05]
* Fixed a problem where saving under HyperStudio (or other applications) could unlock previously-locked files. [#5080] [4.0.6x02]
* Fixed a problem with service permissions that could cause delayed response from a cluster node. [#4896] [4.0.6x01]
* Fixed a problem where FreeHand MX 11 toolbar does not display properly if users' home directories are shared through ExtremeZ-IP. [#5080] [4.0.6x01]