|
Extremez-ip 2 readme version 2x166 July 19, 2011
|
| bet | 17/96 | | Sana | 21.03.2017 | | Hajmi | 275,22 Kb. | | #971 |
| BUG FIXES:
* 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]
|
| |
