This document contains additional information not found in the regular documentation.
ExtremeZ-IP gives Windows the ability to serve files to Macintosh clients using AppleTalk Filing Protocol (AFP) services over TCP/IP. This functionality allows for better performance than Appletalk (because TCP/IP is generally faster than AppleTalk) and enhanced remote access (because it is based on IP, which is generally easier to route than AppleTalk, and is routed over the Internet). In addition, ExtremeZ-IP Print Server allows a Windows server to receive print jobs from Macintosh clients over TCP/IP or AppleTalk.
For more information, consult the ExtremeZ-IP documentation on the Internet at http://support.grouplogic.com/?page_id=63, or consult our Knowledge Base at http://www.grouplogic.com/knowledge.
Our technical support group is always available via email at firstname.lastname@example.org and 703-527-7979, extension 5.
Group Logic greatly values your feedback. If you encounter any problems, please contact us using one of the above methods.
Server System Requirements
ExtremeZ-IP can be run on the following versions of Windows:
- 2003 SP2 or later (all editions, including R2)
- Windows 7
- Vista (all editions)
- XP Professional SP2 or later
- XP Embedded
Memory requirements can be significant, depending on your usage. We recommend that your Windows system have at least 512 MB of RAM installed for optimal performance. You may need substantially more depending on the number of volumes and users and other applications running on the server.
Macintosh Client Requirements
Macintosh clients must have Mac OS 9.0 or later and should run the latest Mac OS release. If Macintosh clients are using Mac OS X, they must have version 10.2.8 or later. ExtremeZ-IP supports the latest Macintosh client technologies, including Bonjour®, the Service Location Protocol (SLP), Kerberos®, and Apple’s built-in encrypted logon support for long passwords. Print Accounting requires Mac OS X 10.3.
Group Logic's Zidget software requires Mac OS X 10.4 or above.
ExtremeZ-IP's DFS and Network Spotlight support require Mac OS X 10.5.
Print Accounting is not compatible with applications running in 64-bit mode on Mac OS X 10.6.
ExtremeZ-IP is administered primarily through the use of the ExtremeZ-IP Administrator program. To administer an ExtremeZ-IP server running on a remote server, hold down the Ctrl key while launching the Administrator and then specify an IP address or server name. You must have administrator rights on the remote Windows server.
Upgrading from Previous Versions of ExtremeZ-IP
You can install this version of ExtremeZ-IP without uninstalling a previous version. You may receive an inadvertent error message indicating that the service could not be stopped or that a file could not be removed. If you receive these errors, the best strategy is to manually stop the ExtremeZ-IP service first, then re-run the installer. You should not need to uninstall the old version.
Migrating from MacServerIP
Information about migrating from MacServerIP 8.1 can be found at our Knowledge Base at http://www.grouplogic.com/knowledge/index.cfm/fuseaction/view/docID/189
ExtremeZ-IP can be optionally configured through the Windows Registry. Group Logic recommends that this configuration only be performed by advanced users. More information about configuring ExtremeZ-IP via the Registry can be found in the help file of the ExtremeZ-IP Administrator, under the subject "Registry Keys".
Printing Compatibility Recommendation
Some printers cannot correctly print binary PostScript data if the printer receives the data using TCP/IP. When printing using an LPR Printer Queue to certain Hewlett-Packard printers it may be necessary to set the printer queue name to BINPS in the LPR configuration dialog to properly handle print jobs that contain binary information. The queue name that ExtremeZ-IP publishes to Macintosh clients does not matter. If you still encounter problems, or you want to ensure maximum compatibility with your ExtremeZ-IP server's configured processing methods, you may need to choose to generate ASCII (or other application-specific format) data in selected applications. This recommendation applies generally to those applications that generate their own PostScript, such as Adobe Photoshop, Adobe Illustrator, QuarkXPress, Macromedia Freehand, and others.
Information on Binary vs. ASCII printer data formats can be found here:
Warning about Updating Status of IP Printers with Mac OS 9
If a Macintosh OS 9 user creates a desktop printer via the ExtremeZ-IP component Choose IP Printer, attempting to update its status will cause a crash. After installing Choose IP Printer, the Update Info button will be available on the Status & Configuration panel of the Get Info window. This panel should not be present for a desktop printer created this way and will be removed once the Macintosh is restarted.
Warning about Direct Print Queues and the Zidget
ExtremeZ-IP administrators can configure direct print queues. These are queues that receive job information for logging purposes, but not the print jobs themselves. The actual print jobs are sent to the remote printer by the Macintosh client. Prior to ExtremeZ-IP 5.1, these direct print queues did not contain any information about the location of this remote printer. In ExtremeZ-IP 5.1, the configuration was changed to require that new direct print queues have knowledge of the location of the remote printer. Doing so allows Zidget clients to discover direct print queues, and automatically receive information from ExtremeZ-IP about the location of the remote printer. Any direct print queues created in versions of ExtremeZ-IP prior to 5.1 do not have this information, and therefore clients adding these queues via the Zidget will not print to the remote printer. In order to remedy this problem, the direct print queues should be modified to contain information about the location of the remote printer.
Warning about Mac OS 9 Print Accounting
Due to a conflict between OS 9 Print Accounting support and support for the new ExtremeZ-IP Zidget, OS 9 Print Accounting support has been disabled by default in ExtremeZ-IP 5.1 and later versions. In order to enable OS 9 Print Accounting support, please set the following registry key to 0 and refresh the registry:
Note that doing this will prevent Zidget clients from properly accessing print accounting queues.
By default ExtremeZ-IP will accept inbound print jobs on port 515.
Under Mac OS X Panther (10.3.X) or earlier print jobs are sent to port 515 regardless of the port specified by the server when the printer is built. Printers built under Mac OS X Tiger (10.4.X) or using the Windows Bonjour client (http://www.apple.com/support/downloads/bonjourforwindows.html) will send jobs to the port specified by the server when the printer is built.
Keep in mind that changing any printer port configuration may break previously built printers.
ExtremeZ-IP Printing and Intel based Macintosh Computers
Starting with ExtremeZ-IP 4.2.1, the Mac client-side print components are compatible with PowerPC and Intel based Macintosh computers. The Print Component installer will install a single Universal Binary that is compatible with all Macintosh systems running OS X 10.2 or later.
Numbers such as "[DE1013, US552, #2717]" refer to Group Logic's internal change tracking system.
Numbers such as "[7.0.1x18]" indicate the specific build in which a change was introduced.
Group Logic periodically releases "hot fixes" to its products to provide customers with access to bug fixes and new features before a full public release is available. Typically, a version will go through a number of hot fix releases (e.g., 7.1.2x1, 7.1.2x2, etc.) before a full product release. Customers can use this information to evaluate whether to update to the latest hot fix.
Please Note: Prior to ExtremeZ-IP 5.2, ExtremeZ-IP File Server and ExtremeZ-IP Print Server contained separate release notes. In the version history below, file and print items are listed separately for versions 5.1.3 and earlier, and listed together for 5.2 and later.
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]
* 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]
ExtremeZ-IP 7.1.2 (Released: May 2011) ENHANCEMENTS:
* Mac client sessions that take longer than 5 minutes to finish any command will be disconnected and reconnected. [US1304][7.1.2x116]
* Improved performance for server-side copies. [US1500][7.1.2x111]
* DHX2 UAM is now supported for Mac client login. [US1435][7.1.2x95]
* Default registry setting for Refreshable 'ServerConvertsShortcutsToLinks' is now 0 [OFF]. This setting can be toggled in the ExtremeZ-IP Administrator settings dialog in the File Server tab.[US1335][7.1.2x75][US1308][7.1.2x79]
* If a volume is not available at startup, the server will periodically retry to bring the volume online. [US92][7.1.2x50]
* Added three registry keys in VSSRefreshableZIPService to support the localization of the Windows Volume Shadow Copy Service [VSS]. The three keys are 'VSSLocalStringContentsOf', 'VSSLocalStringCreationTime', and 'VSSLocalStringShadowCopyVolume'. See the Group Logic Knowledge Base article on how to configure these settings: http://support.grouplogic.com/?p=3600
* Fixed a crash where a sleeping Mac client could wake up and the volume(s) mounted were no longer available on the server. [US1051][7.1.2x40]
* Improved support for resolving Windows Shortcuts as links. [US868][7.1.1x69][US1366][7.1.2x83]
* Fixed a bug where using EZIPUTIL to add volumes to a remote server was broken. [US1685][7.1.2x131]
* Fixed a problem where default registry values for 'Extensions' and 'Type_Creators' were not being populated correctly. [DE1425][7.1.2x116]
* Fixed a bug where DFS site costing was not returning the optimal DFS server. [US1266][7.1.2x89]
* DFS site costing was not working on Cluster. [US1360][7.1.2x75]
* Fixed a problem where after dragging a folder to the Mac Client side bar, clicking on the folder to display its contents would show duplicate entries. [US1319][7.1.2x64]
* Fixed a linkage problem between EZIPUtil and EZIPApi.dll. As a result, the Microsoft runtime libraries are no longer statically linked; they are now dynamically linked. This implies that if you copy EZIPUtil.exe and EZIPApi.dll to a folder other than the original installation folder, you must also copy Microsoft's MSVCP70.DLL and MSVCR70.DLL runtime libraries to that folder before the EZIPUtil program will function. [DE1172][7.1.2x19]
* Fixed a hang at shutdown with Indexed Search enabled. Indexed search reader threads would wait infinitely if a search indexer thread did not signal at shutdown. [US838] [7.1.1x36]
ExtremeZ-IP 7.1.1 (Released: February 2011) ENHANCEMENTS:
* Added support for a new ExtremeZ-IP family product: Group Logic LAN Client for StorNext Software. Available from Quantum.
* Hidden SMB shares (shares that begin with a '$') can now be migrated by enabling the Refreshable 'MigrateHiddenSMBShares registry key. [US873] [7.1.1x26]
* Fixed a hang at shutdown with Indexed Search enabled. Indexed search reader threads would wait infinitely if a search indexer thread did not signal at shutdown. [US838] [7.1.1x36]
* Shortcut (.lnk) files whose target is encoded as a UNC path for the target will now be resolved if the target is on an ExtremeZ-IP volume on the same server as the shortcut. [US585][7.1.1x65]
* Improved performance when enumerating folders containing large numbers of Windows shortcut files. [US868][7.1.1x69]
* Fixed a crash at startup when DFS was trying to resolve a large number of DFS Namespaces. [DE1225][7.1.1x51]
* Fixed a bug where folders dragged to the Dock were displaying duplicate entries in their contents. [US1045][7.1.1x68]
* ShadowConnect is now compatible with international versions of Windows. See the Online Help for more information on "VSSLocalString" settings. [US1118][7.1.1x78]
ExtremeZ-IP 7.1 (Released: November 2010) ENHANCEMENTS:
* Added DFSConnect option. DFSConnect is an optional add-on for ExtremeZ-IP that adds DFS support to 10, 25, 50, or 100-client versions of ExtremeZ-IP. Unlimited-client licenses of ExtremeZ-IP include DFS support.
* Added additional filename policies that allow administrators to restrict the length of file and folder names (with separate settings for files and folders), as well as the length of the full path for files and folders. [US561 and US319]
* Fixed a problem where users could receive errors saving files in Microsoft Word when those files were saved to the user's home directory. [US822]
* Fixed a problem where Windows shortcuts would not resolve properly by Mac clients. [DE1053]
* Fixed a problem where users could fail to copy files or folders to the server if those files/folders contained extended attributes with reserved names (e.g. "AFP_AfpInfo" and "AFP_Resource"). [US678]
* Fixed a problem where users could fail to copy folders to the server if a filename length policy was set to a small value, such as 31 characters. The user would receive an error such as "File '.504dfd41-0720-4d33-a498-01ce76e114ae-74a2f-0-Spotlight' could not be created because the filename exceeds the maximum length of 31 characters." This Spotlight file would not be visible in the source folder. [US667]
* Fixed a problem where ExtremeZ-IP could crash if a Mac user encountered a folder containing a Windows shortcut and AfpVolume logging was set to DEBUG. [DE1054]
ExtremeZ-IP 7.0.1 (Released: September 2010) ENHANCEMENTS:
* ExtremeZ-IP will now display only the truncated, human-readable portion of its serial number in the ExtremeZ-IP Administrator when the 'Refreshable' registry key 'DisplaySerialInUI' is disabled. [US578] [7.0.1x37]
* Added 'Spotlight/Refreshable' registry key 'SpotlightDefaultSearchIsBeginsWith' which, when disabled, will change the default Finder initiated Spotlight search type from 'begins with' to 'contains'. [US565] [7.0.1x37]
* Fixed a possible hang at shutdown if ExtremeZ-IP previously experienced delays at startup or shutdown. [DE1050] [7.0.1x58]
* ExtremeZ-IP will now registry both the short and long afpserver Service Principal names for Kerberos support, previously it just registered the long name. [US569] [7.0.1x37]
* Fixed a problem where ExtremeZ-IP could fail to add a second namespace to a DFS volume if the pre-2000 domain name is not a Netbios name. For example, if ExtremeZ-IP expected "DOMAIN" but instead found "domain.com". [DE1017] [7.0.1x25]
* Fixed a problem where DFS autofs could fail to mount a namespace containing the percent character ('%'). [DE1013] [7.0.1x18]
* Fixed a problem where DFS autofs could fail to mount targets due to a "path too long" error. [US552] [7.0.1x17]
* Fixed a problem where DFS namespaces could fail to be added if the namespace and a link within it had the same name. [DE1011] [7.0.1x12]
* Fixed a problem where out-of-date site costs could be used for DFS. [DE1009] [7.0.1x10]
* Fixed a problem where DFS namespaces that had path parts that were identical (multi-level link) would fail and stop the enumeration of a namespace. [DE1008] [7.0.1x10]
ExtremeZ-IP 7.0 (Released: July 2010) ENHANCEMENTS:
* Added support for Group Logic ShadowConnect.
* The ExtremeZ-IP installer has been updated. The installer will no longer prompt for the user to choose between release mode (requiring a serial number) and trial mode. Instead, the installer will automatically install the trial version if an ExtremeZ-IP serial is not already present on the server. To enter a serial number after installation, the ExtremeZ-IP Administrator's licensing dialog should be used. This licensing dialog supports the entering of both ExtremeZ-IP and ShadowConnect serial numbers.
* ExtremeZ-IP now automatically creates all registry keys with their default values.
* ExtremeZ-IP now supports Windows Error Reporting, so that crash information voluntarily uploaded to Microsoft can be analyzed by Group Logic.
* ExtremeZ-IP now contains a new Logging tab in the Settings window, which allows for enabling and disabling of verbose logging options, as well as manual spooling of the ExtremeZ-IP log.
* The ExtremeZ-IP Administrator now contains a GUI for creating and removing services on clustered servers.
* Users with administrator access can now view all users' home directories. Previously, administrative users could only view their own home directory. Note that non-adminstrative users continue to only be able to view their own home directory. [#9737] [6.1x37]
* Added the ability to generate filename policy reports. ExtremeZ-IP can now go through its volumes and generate a report listing all files and folders that violate its current filename policy. This allows users to find existing files and folders that were created prior to enabling filename policy support in ExtremeZ-IP. [#13261] [6.1x37]
* ExtremeZ-IP’s search index can now be manually reindexed using the ExtremeZ-IP Administrator application. [#6255] [6.1x46]
* The ExtremeZ-IP Administrator will now warn users if they create a volume that is a subfolder of an existing DFS root emulator volume. [US153] [6.1x118]
* The ExtremeZ-IP debug log now outputs date and time for each line, as well as the username and IP address of the logged-in session, if available. In addition, information about each volume is written to the log at startup, and information about the disks being shared is written to the log every 30 minutes. [#11506] [6.1x33]
* Added a "remove all jobs" button to the Print Queues window of the ExtremeZ-IP Administrator application. [#11678] [6.1x33]
* Added a new filename policy to optionally prevent creation of .DS_STORE files. [#12184] [6.1x35]
* Added the ability to choose SSL in the Directory Services area of the ExtremeZ-IP Administrator. [#13455] [6.1x45]
* The ExtremeZ-IP Zidget now only reloads data every 15 minutes by default. [US258] [6.1x105]
* The ExtremeZ-IP Administrator now runs automatically with elevated privileges. [US191]
* Added support for AFP reconnect replay cache. This cache will resend replies to clients that may have missed the initial reply prior to the reconnect. [DE103] [6.1x66]
* EZIPUTIL can now force a pruning of the mapping streams of all volumes by running "EZIPUTIL SERVER /PRUNE". [US74] [6.1x62]
* The ExtremeZ-IP Administrator now displays a warning if a non-default AFP port is chosen that is found to already be in use. [US78] [6.1x62]
* Added the ability to send password expiration notification messages to users at a registry key defined interval, specified in minutes. Please see the Online Help for information about "PasswordExpirationReminderInterval". [US84] [6.1x71]
* Added registry setting "HSM\Refreshable\BringOnlineExplicitlyBlocksCopies". Setting this registry value to 0 will allow Mac OS 10.4 PPC clients to use ExtremeZ-IP volumes that force users to bring offline files "online explicitly" via ArchiveConnect. [DE973] [7.0x33]
* Fixed a problem where browsing of a DFS share using autofs could fail to connect to SMB targets whose name contains one or more spaces. [US469] [7.0x14]
* Fixed a problem where ExtremeZ-IP could crash if the .auto_dfs file exceeded 17 KB in size. [DE915] [7.0x05]
* Improved performance of enumerating a DFS namespace that contains many links to a non-existant server. [DE915] [7.0x04]
* Fixed a problem where ExtremeZ-IP could incorrectly add UNIX permission ACEs to the target file of a copy request, even if ExtremeZ-IP was configured to let allow Macintosh clients to change permissions. [DE909] [6.1x177]
* Fixed a problem where ExtremeZ-IP could crash if it receives a HTTP request with a very long URL. [DE899] [6.1x162]
* Fixed a crash that could occur when caching identity information. In the process of saving the mapping between a user's SID and its name, ExtremeZ-IP could access invalid memory. [US373] [6.1x151]
* Fixed a problem where ExtremeZ-IP could run out of memory. This condition could occur if UNIX permissions were enabled and more than 100 different security descriptors were in use by Mac clients. An example of this would be a home directory environment. [US213] [6.1x142]
* Fixed a problem where an improperly identified postscript print job file could crash the server [US322] [6.1x137]
* Fixed a problem where the ExtremeZ-IP Administrator would disallow certain characters in volume and print queue names. The characters incorrectly being rejected were all Unicode characters whose hexadecimal representation ended in "3A", e.g. "к" (U 43A). [DE719] [6.1x88]
* ExtremeZ-IP will no longer allow Mac clients to lock or unlock folders if ExtremeZ-IP is configured to disallow Macs from changing permissions. [US157] [6.1x70]
* Fixed a problem with ExtremeZ-IP DFS support when a "default first site" could not be found. [DE623] [6.1x73]
* ExtremeZ-IP will no longer replicate SMB shares at, above, or below DFS root folders. [US124] [6.1x83]
* Fixed a problem where DFS server name resolution could fail if DNS contained the same name in another domain. [DE624] [6.1x73]
* Fixed a problem where ExtremeZ-IP could crash due to an out of memory condition if an ExtremeZ-IP volume contained one or more folders with a very large number of files. [DE100] [6.1x72]
* ExtremeZ-IP now fully supports home directories that are not immediately subfolders of the root of the ExtremeZ-IP volume. For example, if the volume is named 'Homes', the home directory can now be 'Homes\Juniors\TestUser'. Previously, home directories of this type would function correctly, but ExtremeZ-IP was not optimized for this condition. [#9011] [6.1x37]
* Filename policies no longer apply to temporary items. This avoids problems where applications can fail if the temporary files they create do not conform to a filename policy (e.g. the filename is too long). [#13088] [6.1x36]
* Fixed a problem where an ExtremeZ-IP volume could fail to initialize its search index if that volume's root folder was created by copying another ExtremeZ-IP volume's root folder. [DE514] [6.1x105]
* Improved login times for home directory users when logging in to a server other than the one containing their home directory. [DE94] [6.1x57]
* ExtremeZ-IP now sends password expiration notification messages to clients logging in using the Kerberos UAM. [DE118] [6.1x71]
* ExtremeZ-IP will now recall files brought online via ArchiveConnect in the user's context, rather than the SYSTEM context. This will let the file system archiver properly log the event with the correct username, and allow for user-specific logic to be properly enforced, e.g. user recall limits. [DE510] [6.1x82]