• Added the ability to designate Time Machine backup storage quotas on a per-user or per-group basis.
• Time Machine volumes are now configured with file permissions allowing only the backup user or administrators to access the Time Machine backup file. In addition, Time Machine backup files owned by other users are now hidden when browsing the volume.
• Implemented functionality to automatically generate and configure a Time Machine volume when running on Windows Home Server.
• Implemented functionality to prompt the user for a username and password during remote administration if the logged-in username and password cannot be used to access the remote server.
• ExtremeZ-IP will now disallow guest logins by default. Guest access can be enabled through the ExtremeZ-IP Administrator.
• Fixed a problem where ExtremeZ-IP could hang on servers using DFS. The problem would occur if a Mac client with a DFS home directory path attempted to login to a server that had profile home directories enabled, but was not the target machine of the user's DFS home directory path.
• Fixed a compatibility problem between ExtremeZ-IP and CommVault Simpana. Previously, offline files could sometimes fail to be recalled when opening from a Mac client. To work around this issue, the Refreshable registry setting "ServerUsesRelativeHandles" should be set to 0. Please see the Online Help for more information.
• ExtremeZ-IP will now hide inaccessible volumes by default. This avoids a bug in the Mac client where the presence of inaccessible volumes in the volume list can cause other volumes to not appear properly.

• ExtremeZ-IP now supports volumes that are at or within a junction or mount point. The mount point can target a drive with or without an assigned drive letter.
• Fixed a problem where ExtremeZ-IP could leak file handles when encountering deeply nested folders during a non-indexed search.
• Fixed a problem where volumes containing a space in their names would not mount properly from the Zidget.
• Fixed a problem where 10.4 clients could fail to open files containing Cyrillic characters in the filename.
• Fixed a problem where the ExtremeZ-IP DFS client Launch Daemon could be installed with incorrect permissions.
• Fixed a problem where ExtremeZ-IP could fail to start in a timely manner after a system restart if both the ExtremeZ-IP and Windows Search services were configured to start automatically.
• Fixed a problem where ExtremeZ-IP would incorrectly advertise the Kerberos authentication mechanism when Kerberos was not in fact available (e.g. on servers not bound to a domain). This could lead to a crash of the NetAuthAgent process on Snow Leopard clients.
• Fixed a problem where aliases would lose their targets when copied to an ExtremeZ-IP volume by a Snow Leopard client.
• Changing the ArchiveConnect offline color label will now take effect for clients after the next mount of an ExtremeZ-IP volume. Previously, the old color label would remain even after remounting the volume.
• Fixed a problem where ExtremeZ-IP could crash when receiving an unexpected SetACL AFP command.

• ExtremeZ-IP debug log now outputs Pool Paged Bytes and Pool Nonpaged Bytes among other stats (such as handle and thread count).
• ExtremeZ-IP now outputs volume path and search index size information to the debug log at startup.
• File modification times are no longer updated when dot underscore migration occurs. Previously, files would have their modifications times set to the time the migration occurred.
• Fixed a problem where ExtremeZ-IP would not properly preserve ShowInaccessibleFiles and ShowInaccessibleFolders settings after an upgrade.
• ExtremeZ-IP now properly handles CREATOR_OWNER and CREATOR_GROUP ACEs. Previous versions of ExtremeZ-IP would not properly add in ACEs for the owner or group as a result of these inherit only ACEs.
• With ACL support enabled, performing a Get Info operation from Finder will now display CREATOR_OWNER and CREATOR_GROUP ACEs as "owner" and "group" respectively. They would previously display as "unknown".

• This release has been certified as Snow Leopard compatible.
• Added new UNIX permissions settings that can be configured in the registry.
• Added support for the HTTPDiscoveryMinimumZidgetVersion registry setting, which lets customers override the default minimum Zidget version.
• The filename policy to restrict characters illegal in Windows file or folder names now prevents names that begin with a space.
• Added UI for existing settings that control whether or not inaccessible files and folders are visible to Mac clients.
• ExtremeZ-IP and ArchiveConnect are now compatible with Symantec Enterprise Vault volumes that have pass-through recall enabled.
• Fixed a problem where ExtremeZ-IP 's internal HTTP server would be enabled at startup even if all HTTP checkboxes were unchecked in the ExtremeZ-IP Administrator.
• Fixed a problem where ExtremeZ-IP could crash when attempting to index a very deeply nested folder hierarchy (~190 levels or more).
• Fixed a problem where ExtremeZ-IP could crash when performing a non-indexed search of a volume containing a folder hierarchy at least 10 levels deep.
• Fixed a problem where ExtremeZ-IP could crash when processing a search request if it encountered a folder whose path is exactly 1020 characters long.
• Fixed a problem where ExtremeZ-IP could fail to add entries to its search index for changes that occurred while ExtremeZ-IP was not running.
• Fixed a problem where users that originally connected to the ExtremeZ-IP server using a username and password could fail to reconnect if their entered username did not match the exact case of the username as stored in Active Directory (e.g. "administrator" vs. "Administrator").
• ExtremeZ-IP will no longer allow files or folders to be given names that are reserved in Windows, such as "CON" or "LPT1"
• Fixed a problem where 10.6 clients would fail to mount a volume containing Unicode characters.
• Fixed a problem where the ExtremeZ-IP Administrator running on Windows Vista or 2008 could hang when connected to a server running Windows 2003 or XP.
• The filename policy to restrict specific extensions will now apply to folders as well as files.
• Fixed a problem where ExtremeZ-IP could fail to properly uninstall if Active Directory contains a very large number of groups.
• Fixed a problem where ExtremeZ-IP could fail to properly uninstall if the Service Connection Point (SCP) could not be removed.
• Fixed a problem where ExtremeZ-IP would fail to install a Service Connection Point (SCP) when ExtremeZ-IP was installed on a domain controller.
• Fixed a problem where ExtremeZ-IP would fail to install a Service Connection Point (SCP) if computer objects were not stored in the "Computers" container in Active Directory.

This upgrade is recommended for any customers currently engaged with the ExtremeZ-IP technical support team.

This is a hot fix release. Testing of this release was focused on the areas of ExtremeZ-IP that have changed since the 6.0.1 release. Full testing and general release status should be completed within the next 2-4 weeks.

The changes in this release include:

• Added the ability to customize the specific UNIX permissions that clients can set. For example, ExtremeZ-IP can be configured to allow Macs to change permissions for the owner, but not for the group.
• Fixed a problem where ExtremeZ-IP could incorrectly report file/folder UNIX permissions as 000 (no access) if the user did not have access to read permissions on the file/folder.
• When the "Allow Mac clients to change folder permissions" feature is disable, ExtremeZ-IP will ignore any UNIX permissions previously set to files and folders, and compute based on the file/folder ACL.
• When the "Reset Permissions on Move" feature is enabled, ExtremeZ-IP will now remove any explicit ACEs from the moved file, including any UNIX permissions.

• Added support for Group Logic ArchiveConnect.
• ExtremeZ-IP will now automatically create separate log files each time the service is run. Old log files will now be automatically compressed and the oldest archived logs will be automatically deleted as needed to conserve disk space.
• Added the ability to completely disable the Print Server via a registry setting.
• ExtremeZ-IP can now broadcast DFS targets to the Zidget without enabling the broadcasting of all its AFP shares.
• ExtremeZ-IP Spotlight now supports the following search terms: Author, Subject, Title and Keyword. These terms can be used to search PDF files if the PDF iFilter is installed on the server.
• Fixed a problem where Tiger 10.4.11 clients could get disconnected from the server when copying Adobe Creative Suite files containing comments.
• Fixed a problem where the ExtremeZ-IP service could crash at startup if the ExtremeZ-IP Startup Log (as opposed to the Debug Log) exceeded 200 MB.
• Fixed a problem where the ExtremeZ-IP service could crash at shutdown if logging of the AfpSession module was set to DEBUG.
• Fixed a problem where the ExtremeZ-IP service could crash if indexed search was enabled or disabled for a specific volume while clients were actively searching that volume.
• The ExtremeZ-IP internal HTTP server can now be disabled by unchecking all three options in the Service Discovery Settings tab for Zidget/HTTP (print, file and DFS).
• When the "Reset Permissions on Move" feature is enabled, ExtremeZ-IP will now set the owner of the moved file to the user performing the move.
• When an invalid DFS namespace is entered, the ExtremeZ-IP Administrator will now allow user to edit the field rather than tossing them back to the DFS tab.
• Fixed a problem in the case where ExtremeZ-IP fails to contact the intersite topology generator (ISTG) to determine DFS site costing.

• This is the initial 6.0 release.

• This is the initial 5.4 release.
• ExtremeZ-IP 5.4 is the last generation of ExtremeZ-IP to support Windows 2000. If you are running Windows 2003, 2008, XP, or Vista, Group Logic recommends you install ExtremeZ-IP 6.0.

• Fixed a problem where Windows 2008 could blue screen if Mac clients saved files to an ExtremeZ-IP volume. The problem would occur when the client application used the AFP ExchangeFiles command. This command is used by a number of applications, including Microsoft Word. ExtremeZ-IP works around the problem by opening folders by full path rather than ID during ExchangeFile processing, which incurs a minor performance hit. Microsoft is aware of the issue and will be issuing a fix at an unspecified date.
• Fixed a problem where files could not be opened using their Windows 8.3 filename. While ExtremeZ-IP does not communicate these 8.3 filenames to Mac clients, workflows such as Prinergy that involve Windows and Mac components can result in Mac clients making requests for files and folders by these names. Support for 8.3 names can be enabled via the 'ServerAllows8Dot3Names' registry value. See the Online Help for more details.
• Fixed a problem where files containing extended attributes could fail to be duplicated using the 'ditto' command. As of 10.5.6, the ditto command fails in the case due to an error on the client side. Enabling the 'ServerAllowsLargeEABuffers' setting allows ExtremeZ-IP to work around this bug. See the Online Help for more details.
• Fixed a problem where some files, including GarageBand projects, could fail to sync when using Portable Home Directories.

• Fixed a problem where a folder could incorrectly be assigned a blank ACL after a move if ACLs and 'reset permissions on move' were both enabled for the volume.
• Fixed a problem where files whose names contain a '#' followed by a number (e.g. #231500.txt) could fail to display in the Finder.

• ExtremeZ-IP file and print servers are now certified to run on Windows Server 2008. Note that ExtremeZ-IP does not support Windows Server 2008 clusters at this time.
• The ExtremeZ-IP Installer now installs the Group Logic AppleTalk Protocol. This protocol is designed for versions of Windows that do not include a native AppleTalk Protocol. These include Windows Server 2008, Windows Vista, and Windows XP. For more information, see the "AppleTalk Installation.doc" file within the "AppleTalk" subfolder if the ExtremeZ-IP application directory.
• Fixed a problem where ExtremeZ-IP could crash if it encountered a folder with an empty ACL.
• Fixed a problem where ExtremeZ-IP could incorrectly report itself as being blocked by Windows Firewall when running on Windows 2008 Server.
• ExtremeZ-IP now properly decodes print job title information from print jobs created by Adobe Creative Suite 3 (CS3). When the document name contains Unicode characters, CS3 encodes the PostScript job name in a hexadecimal format not previously understood by ExtremeZ-IP.
• Fixed the EZIPUTIL SERVER /FILES command.
• Fixed a problem where ExtremeZ-IP could crash when a client attempted to reconnect to the server. This could occur if the client's reconnect credential was encrypted with an expired key.
• The ExtremeZ-IP Administrator can now remotely administer an instance of the ExtremeZ-IP service when the Administrator is running on Windows Server 2008.
• ExtremeZ-IP performance counters are now available on servers running Windows 2008 Server.
• Fixed a problem that could occur when a OS X Tiger 10.4.11 client attempts to copy a file from the server to the desktop, and the file contains an extended attribute.

• Improved support for locked folders by controlling access to them in a "Macintosh-like" manner. Windows does not by default restrict access to folders marked as read-only, so ExtremeZ-IP modifies the folder's Access Control List (ACL) to perform the lock.
• Fixed a problem where files and folders could fail to be returned in search results. If a user that did not have access to the file or folder performed a search that included that file/folder in the results, ExtremeZ-IP would incorrectly remove that file/folder from all later search results, even for users that did have access to that file/folder.
• Directory Services lookups are now performed against the global catalog rather than a single domain by default. This resolves problems with complex domain structures: for example, long name logins for users who accounts are stored in non-default OUs.
• Fixed a problem where files with extended attributes could fail to be copied from ExtremeZ-IP to a Tiger (10.4.11) client.
• Fixed a problem where files compressed on an ExtremeZ-IP volume would incorrectly appear as UNIX executables in the Finder.
• Fixed a problem where the ExtremeZ-IP Administrator would fail to save the setting "Allow workstation to save password".

• The ExtremeZ-IP Administrator will now present a "Check for Updates" button on the main window when running a release version of ExtremeZ-IP.
• The ExtremeZ-IP service will now honor the "IPAddress" registry setting on a clustered server. This allows a particular service to listen on some, but not all, IP addresses in a given cluster group.
• The EZIPUTIL command-line utility now contains a command to edit an existing ExtremeZ-IP volume. Run "EZIPUTIL VOLUME" from the command-line for details.
• The EZIPUTIL command-line utility now lists all volume properties when performing a "VOLUME LIST" command.
• The EZIPUTIL command-line utility now contains a command that tells the ExtremeZ-IP service to refresh its registry settings.
• Fixed a problem where ExtremeZ-IP could fail to start if Directory Services had been enabled and the network containing the ExtremeZ-IP server contained a trust with a NetBIOS name but not a fully qualified domain name.
• Fixed a problem where files and folders copied between ExtremeZ-IP volumes from OS 9 could fail to be displayed by the Finder in the destination volume.
• Fixed a problem where sessions listed as "Waiting for Reconnect" in the ExtremeZ-IP Administrator could fail to be automatically disconnected after the configured timeout (default 5 minutes).
• Fixed a problem where ExtremeZ-IP would fail to support extended attributes whose names contained characters illegal in Windows filenames (e.g. colon, question mark and backslash).
• Fixed a problem where ExtremeZ-IP would incorrectly operate in a case sensitive manner in its support of Apple's "special" extended attributes: com.apple.ResourceFork and com.apple.FinderInfo.
• Fixed a problem where Microsoft Office 2008 SP1 for Mac could fail to open documents when those documents were double-clicked in the Finder.
• Fixed a problem where the ExtremeZ-IP would fail to find user information in Active Directory if the credentials entered in the Directory Services area of the ExtremeZ-IP Administrator contained an incomplete domain (e.g. "example" instead of "example.com").
• Fixed a problem where the ExtremeZ-IP Administrator would warn the user about "invalid Directory Services credentials" even when credentials had not been entered.
• Fixed a problem where the ExtremeZ-IP File Server fails to start if the system's perflib counters could not be found.
• Fixed a problem where ExtremeZ-IP would report an incorrect number of offline volumes through its performance counters.
• Fixed a problem where the ExtremeZ-IP File Server could hang after a file system delay. This could occur if ExtremeZ-IP's thread pool manager mistakenly reduced the size of the thread pool to zero, leaving no threads available to satisfy client requests.

• ExtremeZ-IP now saves column widths in dialogs within the ExtremeZ-IP Administrator. These column widths are restored each time the ExtremeZ-IP Administrator is launched.
• Fixed a potential crash that could occur after saving files in applications such as Microsoft Excel. This issue was most likely to occur if the user saving the file did not have the "Take Ownership" permission in the folder containing the data file.
• Fixed a problem where applications such as Microsoft Word could fail to save changes to an existing file due to permissions problems. This issue was most likely to occur if the user saving the file was not the file's owner.
• Fixed a problem where files and folders within a volume could become inaccessible to users logging in to ExtremeZ-IP with the guest account. This could appear to cause the user to be disconnected.
• Fixed a problem where two sessions from the same client machine - one logged in with the display name (e.g. "John Doe") and one using the username (e.g. "johndoe") - would incorrectly use two user licenses rather than one.
• The ExtremeZ-IP Administrator will now display all user names in the Users dialog as "domain\username" or "computer\username", even if the user logs in using their display name (e.g. "John Doe" rather than "johndoe").
• Fixed a problem where guest users would see the incorrect list of volumes if Windows' "Guest Account Status" feature was enabled.
• Fixed a problem where guest users would appear with the wrong username in the ExtremeZ-IP Administrator if Windows' "Guest Account Status" feature was enabled.
• Fixed a problem in the ExtremeZ-IP installer where the installer would incorrectly process the serial number in a case sensitive manner. For example, if the entered serial number began with 'z' rather than 'Z', the installer would reject that serial number.
• Fixed a problem where the Macintosh command-line "xattr" program would fail to list the extended attributes on a file located within an ExtremeZ-IP volume.
• ExtremeZ-IP now properly sorts numerical columns in the Print Processing Log of the ExtremeZ-IP Administrator. Previously, ExtremeZ-IP would sort those columns alphabetically, resulting in a sort order such as "1, 29, 3, 444, 5".
• Fixed a problem in the ExtremeZ-IP Administrator's "Type and Creator" dialog where new extensions could not be associated with the "text/dosa" type and creator.

• Fixed a problem where ExtremeZ-IP could crash (and fail to produce a crash dump) when receiving a request involving a filename greater than 255 characters.
• Updated Mac OS X printing components for Mac OS X 10.5.2 compatibility. Attempting to add printers through 'Print & Fax' preferences panel in Leopard 10.5.2 and greater will fail with all earlier versions of the Mac OS X printing components.
• ExtremeZ-IP will now allow broadcast of print queues over the Appletalk protocol in the MacJapanese character set if the queue name cannot be fully converted into the MacRoman set.

• Fixed a problem where a Mac OS 10.5.2 client could fail to connect to ExtremeZ-IP with a Kerberos ticket.
• Fixed a problem where the ExtremeZ-IP service could return local files that were not located in the "HTML Files" folder, but in any location on the NTFS volume containing the application directory. The problem was limited to files with the following extensions: html, xml, zip, gif, png, jpg and ico.
• Fixed a problem where the ExtremeZ-IP service could crash when receiving a malformed AFP packet.
• Fixed a problem where the ExtremeZ-IP service could crash when receiving a malformed SLP packet.

• Fixed a problem where the ExtremeZ-IP service could crash when clients attempted to reconnect to the server.
• Fixed a problem where users could disconnect from ExtremeZ-IP due to "too many I/O requests".
• ExtremeZ-IP now logs specific error information to the Windows Event Log when the service fails to start.
• ExtremeZ-IP will now allow administrators to automatically add an exception to the Windows Firewall.
• ExtremeZ-IP will now place warnings into the Windows Event Log when client logins are rejected because there are no available licenses.
• ExtremeZ-IP will now output crash dumps directly into the application folder.
• Fixed a problem where Leopard clients could see folders appear as empty through the Finder.
• Fixed a problem where the service could fail to start because teamed NICs had yet to initialize.
• Fixed a problem where ExtremeZ-IP could return the wrong error code when it refused to change a client password due to a violation of a password policy.
• Fixed a problem where sending a message to a reconnected client could cause the client to receive the logon message rather than the intended message.
• Improved performance of the Zidget in environments with hundreds of print queues.
• Fixed a problem where upgrading from a print trial to a licensed version of the print server can fail to automatically restart the print server.
• Print Processing Log now sorts jobs in a case-insensitive manner.
• Direct (non-spooling) print queues now automatically reject jobs received over LPR.
• ExtremeZ-IP print queues using the LPR output method now support sending jobs over LPR to a remote queue whose name contains Unicode characters.

• Fixed a problem where volumes could appear empty after an upgrade to 5.1.
• Fixed a problem where files copied into an ExtremeZ-IP volume from a Windows-side Rampage workflow could incorrectly appear as aliases.
• Fixed a problem where certain messages would fail to be written to the Windows Event Log (for example, violations of the filename policy).
• Fixed a problem where the server would enforce an incorrect license count on cluster machines with multiple virtual servers.
• Fixed a problem where the server would return an incorrect error code when the Mac client failed to authenticate due to an incorrect username or password.
• Fixed a problem where the server would return an incorrect error code when the Mac client attempted to change their password in cleartext and the "old" and "new" passwords matched.
• Fixed a problem where the server could fail to process requests do to a negative refcount error.
• Fixed a problem where Windows Event Log messages could get truncated if the log message contained Unicode characters.
• Fixed a problem where Windows Event Log messages containing IPv6 addresses could appear malformed.
• Fixed a problem where the "Show Only Accessible Volumes" setting in the ExtremeZ-IP Administrator could fail to display the correct value.
• Added complete support for queue names containing Unicode characters. ExtremeZ-IP print queues containing these characters can now be properly discovered and added using all discovery methods (Bonjour, Appletalk, HTTP/Zidget), and these queues can have their PPDs downloaded and be printed to properly without error.
• Fixed a problem where ExtremeZ-IP could crash at startup if the print queue registry settings were invalid.
• Fixed a problem where queues added via the Zidget would be automatically reshared over Bonjour on Leopard clients.

• This is the initial 5.1 release.

• Fixed a problem where the license count could exceed the number of active users, preventing new users from logging in.
• Fixed a problem where the "Disconnect Waiting" button in the Users window of the ExtremeZ-IP Administrator would fail to disconnect users that were waiting for reconnect.
• Fixed a problem where the Finder could fail to show the correct number of items in a folder. This could occur if files were added or removed from the folder while a user without permission to view that folder was enumerating the parent folder.
• Fixed a problem where users could not login to the server with DHX encryption if their passwords contained characters that are illegal in Windows filenames (* < > " / | \ ?).
• Fixed a problem where Mac users could get disconnected when reading or writing files to the server when the network was under load but the thread pool was shrinking.
• Fixed a problem where ExtremeZ-IP could fail to display files and folders containing the Ohm symbol (Ω - unicode character U+2126).
• Fixed a problem where users could fail to login via Kerberos if their Kerberos ticket was large (e.g. 4000 bytes).
• Fixed a problem where the ExtremeZ-IP could crash at startup after an upgrade from ExtremeZ-IP 3.2.2 or earlier.
• Fixed a crash that could occur when placing information about performance statistics into the ExtremeZ-IP debug log.
• Fixed a problem where ExtremeZ-IP could not startup after an upgrade because its performance counter DLL was still in use.
• Fixed a problem where messages about ExtremeZ-IP running in trial mode continued to be sent to clients after a serial number was entered in the ExtremeZ-IP Administrator.
• Fixed a problem where enabling the (optional) "CreatePrecomposedMacRoman" registry setting could cause problems copying files via the Finder.
• Added additional logging information to alert administrators if the ExtremeZ-IP service cannot start after an upgrade.
• Fixed a problem where sessions waiting for reconnect would not be automatically disconnected if the user reconnected but used a username with a different case than with the original session (e.g. "Bob" and "bob").
• Fixed a problem where the "jobs offline" counter of a print queue could become invalid if jobs were automatically deleted after being offline for too long.
• Improved handling of print jobs that do not succesfully print. Failed jobs can no longer take the entire queue offline. These failed jobs will be automatically retried at a configurable interval, and optionally deleted after a certain amount of time.

• 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.
• 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.
• Fixed problem where applications such as Photoshop, InDesign and Quark could give errors when saving to an existing file.
• 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.
• 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.
• Fixed problem where idle OS 9 clients could be disconnected from the server. This issue was present in ExtremeZ-IP 5.0 only.
• 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.
• Fixed problem where ExtremeZ-IP Server name would not match the Network Name dependency on a cluster, but would have "IP" appended to it.
• 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.
• 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.
• 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.
• Changed behavior so that modifications to .DS_Store files do not cause the volume's modification time to be updated.
• Added code to gracefully handle situation when client asks for deprecated "launch limit" parameter.
• Fixed problem where clients could fail to mount a volume containing an 8-character volume password.
• 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.
• Added support for performance counters that are specific to individual ExtremeZ-IP print queues.
• Added the ability for administrators to automatically replicate shared Windows printers as ExtremeZ-IP print queues by clicking a single button in the Print Queues Window.
• Fixed a problem where printing jobs whose name contained question marks could cause a crash.
• Fixed a problem where print jobs whose names contained characters that are illegal in Windows filenames (e.g. '?' and ':') would fail to display properly in the ExtremeZ-IP Administrator.

• This is the initial 5.0 release.

• 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.
• Fixed a potential crash in home directory support. The crash could occur if a client machine attempted to access another user's home directory.
• 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.
• Enabled ServerCombinesLPRPackets feature by default.

• Fixed a problem where the system statistics that are output every minute stopped being output.
• Added ServerIgnoresReadOnlyFolders registry key. If enabled, the server will not display any folders as locked, even if they are marked "read-only" in Windows.
• 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.
• Fixed a problem where files could fail to show up in indexed searches after being saved in applications such as Microsoft Word.
• Fixed a problem PictroMatch would fail to delete files from a watched folder within an ExtremeZ-IP volume. This problem was to do a bug in the support for the AFP Move command.
• Added ServerCombinesLPRPackets registry key to fix a problems where jobs would fail to spool to certain LPR printers.