Posts Tagged ‘ExtremeZ-IP’

GroupLogic product compatibility with Windows 8

Wednesday, April 3rd, 2013

activEcho
Client: Windows 8 is supported by activEcho client 2.7 or later.
Server: Windows 8 is not supported.

ArchiveConnect
AFP-based Servers: ExtremeZ-IP 8.0.3 or later is supported on Windows 8 for use with ArchiveConnect (see below).
SMB-based Servers: Windows 8 has not yet been certified for compatibility with ArchiveConnect

ExtremeZ-IP
Server: Windows 8 is supported by ExtremeZ-IP 8.0.3 or later.

MassTransit
Server: Windows 8 is not supported.
Windows Web Client: Windows 8 is supported when using the MassTransit 7.2.7 or later web client.

mobilEcho
Server: Windows 8 is supported by mobilEcho 4.3 or later.

Configuring Kerberos for ExtremeZ-IP Network Reshare

Wednesday, November 7th, 2012

In order for Mac users using Kerberos to access SMB/CIFS reshares through ExtremeZ-IP delegation must be enabled in Active Directory. If your environment requires Kerberos authentication, you will need to update the Active Directory computer object for any Windows servers that are running ExtremeZ-IP. The ExtremeZ-IP server must be given permission to present delegated credentials to the SMB server on behalf of your users.

NOTE: When you set up a user’s profile Home folder in Windows Active Directory and Users, you need to use the server’s domain name (of the EZ-IP server domain) instead of its ip address in order for the network Home directories to work with Kerberos for Mac OS 10.6 clients.

  1. In Active Directory Users and Computers, locate the Windows server or servers that you have ExtremeZ-IP installed on. They are commonly in the Computers folder.
  2. Open the Properties window for the ExtremeZ-IP server and select the Delegation tab.
  3. Select “Trust this computer for delegation to specified services only”.
  4. Select “Use any authentication protocol”, this is required for negotiation with the SMB server.
  5. You must now add any Windows servers or NAS devices that you would like your users to be able to access through reshare. Click Add… to search for these Windows computers in AD and add them. For each, you will need to select the “cifs” service type only.

Note: It may take 15 to 20 minutes for these changes to propagate through the Active Directory forest.

ExtremeZ-IP has detected an incompatible version of the Bonjour Service

Tuesday, September 11th, 2012

Cause:

ExtremeZ-IP uses Bonjour service advertisements to allow OS X client computers to see ExtremeZ-IP volumes in the Connect to Server dialog and print queues in the Print Center.

As of ExtremeZ-IP 8.0.1, version 3.0.0.10 of the Windows Bonjour Service is required, so this error will occur if an old version of the service is already installed on the server.

Resolution:

Option A: If Bonjour service advertisements are not required, you can set ExtremeZ-IP not to register with the Bonjour service. In the ExtremeZ-IP Administrator utility, click the Settings button. Select the Service Discovery tab and uncheck both the File and Print checkboxes for Bonjour.

Option B: If Bonjour service advertisements are required and you have an older version of Bonjour already installed on your server, perhaps by another software package that also uses Bonjour service advertisement, you will first need to upgrade to ExtremeZ-IP 8.0.5, then determine if your other software package is compatible with Bonjour version 3.0.0.10.

To switch to using Bonjour 3.0.0.10, open a command prompt and navigate to

“C:\Program Files (x86)\Bonjour” (This is where Bonjour is installed by default)

Then enter the command

mdnsresponder -remove

This will remove the installed service for the legacy Bonjour installation. Within a few minutes ExtremeZ-IP will automatically install a new Bonjour service for our included Bonjour 3.0.0.10 installation.

If the ExtremeZ-IP service advertisements do not begin within a few minutes, a reboot of the server may be required.

If these steps do not resolve any issues, please open a new support case here.

Using ArchiveConnect with ExtremeZ-IP Network Reshare

Wednesday, June 6th, 2012

Introduction

ArchiveConnect is fully compatible with ExtremeZ-IP 8.0’s new Network Reshare capability. This feature expands the options for giving Macs access to archive volumes on SMB accessible storage and also provides an excellent workaround for known issues with Mac clients running OS X 10.6.7 and later accessing SMB/CIFS archive volumes.

Network Reshare and ArchiveConnect provide a solution for accessing file archives on NAS storage

Due to an issue in Mac OS X 10.6.7 and later, Macs connecting to SMB accessible archive volumes on file servers or NAS storage are not able to properly recall files. This issue is fully detailed in this related knowledge base article.

By utilizing ExtremeZ-IP Network Reshare to make file archives, previously only available through SMB/CIFS connections, available to Macs using the standard AFP file sharing protocol, this issue can be avoided and Mac file recall behavior is properly managed by ArchiveConnect over the AFP connection.

Additional ArchiveConnct features included in ExtremeZ-IP also provide advantages to using AFP Network Reshare vs. using direct SMB access from Mac clients. An example is a configurable color label that indicates which files shown in the Finder are currently offline.

NetApp specific benefits to using ArchiveConnect with Network Reshare volumes

Before ExtremeZ-IP 8.0 with Network Reshare, Mac SMB access to NetApp archive volumes required the “Assume all SMB files are offline” setting to be configured in ArchiveConnect. This is not necessary when they are reshared through ExtremeZ-IP, so Mac users retain the ability to see thumbnail icons and quick look previews for files that are already online.

Accessing DFS files using ExtremeZ-IP Network Reshare

Wednesday, June 6th, 2012

Introduction

Prior to the release of version 8.0, ExtremeZ-IP supported Mac AFP access to Microsoft Distributed File System (DFS) file shares in several ways. Traditional ExtremeZ-IP DFS support requires one or more DFS namespaces to be added to the DFS tab in the ExtremeZ-IP Administrator’s Settings window. Then, Mac clients must be set up with one of the following options:

  • - The “Zidget” Dashboard widget – Used to browse DFS namespaces and mount specific resources within them.
  • - The ExtremeZ-IP “DFS Client” application – Used to allow mounting of DFS volumes in the Finder and browsing of the related DFS namespace, similar to the experience Windows presents to users.
  • - Manual modification of the Mac’s “auto_master” file – Provides the same experience as the DFS Client option, but requires editing a standard Mac config file rather than installing client software.

All of these options require client side software or changes on each Mac that requires access to DFS.

ExtremeZ-IP 8.0’s Network Reshare feature introduces an additional option for providing Macs with access to DFS resources. Network Reshare allows ExtremeZ-IP AFP file volumes to give access to folders located on other servers and NAS devices on your network. Macintosh clients continue to connect to ExtremeZ-IP using the standard AFP file sharing protocol, while ExtremeZ-IP utilizes the SMB/CIFS file sharing protocol to access files that are requested by Mac users from remote servers and NAS systems. By doing so, Mac users retain all the benefits of AFP file sharing while gaining access to resources that have traditionally only been available through SMB/Windows file sharing.

DFS shares can be configured as ExtremeZ-IP Network Reshare volumes. DFS target resolution simply occurs in the SMB reshare communication layer and Macs are able to seamlessly browse and access the reshared DFS resources presented in a standard AFP volume. No Mac client-side software or changes are required. Macs simply connect to ExtremeZ-IP AFP Network Reshare volumes in the Finder and can immediately browse the DFS namespace.

For more details on Network Reshare, see our Configuring Network Reshare support in ExtremeZ-IP knowledge base article.

Limitations

ExtremeZ-IP Server acts as DFS client
When hosting a Network Reshare DFS volume, the ExtremeZ-IP Windows server makes requests for resources located in DFS namespaces on behalf of the the Mac client. From the perspective of DFS, the Windows server itself is the client, not the actual Mac user making the request. For this reason, all DFS target selection and site costing will be negotiated for the Windows server, rather than the Mac client.

All Network Reshare communication is routed through the ExtremeZ-IP Windows server
Network Reshare routes all communication between your Mac clients and your DFS namespaces through the Windows server where ExtremeZ-IP is installed. This requires an extra network hop compared to the Mac client accessing DFS targets directly. For the best possible performance, it is recommended that ExtremeZ-IP is installed on a server with the fastest available NICs, and ideally this server has one or more NICs dedicated to communicating with the servers, NAS, or DFS namespaces being reshared.

ExtremeZ-IP Network Reshare feature and Network Reshare DFS volume configuration

For full details on configuring your ExtremeZ-IP server for Network Reshare and instructions on setting up a Network Reshare DFS volume, please see our Configuring Network Reshare support in ExtremeZ-IP knowledge base article.

GroupLogic Product Compatibility with Apple’s OS X 10.8 Mountain Lion

Friday, June 1st, 2012

We have tested the latest versions of the following products and found that they are compatible with OS X Mountain Lion:

activEcho (tested 2.5)
ArchiveConnect (test 1.2.5)
ExtremeZ-IP (tested 8.0.1)
MassTransit (tested 7.2.7 Web Client)

mobilEcho is unaffected since it consists of server and mobile device components.

If you have any questions or find any issues with our products, please contact us at http://support.grouplogic.com/request.

For information on compatibility with the OS X 10.7 Lion release, please see http://support.grouplogic.com/?p=3538

Registry settings for CommVault support with ExtremeZ-IP and ArchiveConnect

Monday, October 3rd, 2011

When configuring ExtremeZ-IP and ArchiveConnect to work with CommVault archives, there are 2 specific registry configurations that need to be made.

1) In the ExtremeZ-IP registry: “ServerUsesRelativeHandles” should be set to 0.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ExtremeZ-IP\Parameters4\Refreshable\ServerUsesRelativeHandles

After making this registry change, go to the ExtremeZ-IP Administrator, click the Settings button, and click the “Refresh Registry” button to have this change take effect.

2) In the CommVault registry: “GXHSM_IGNORE_ALT_STREAM_RECALLS” needs to be set to ‘Y’.
HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance001\WinFSDataMigrator\ GXHSM_IGNORE_ALT_STREAM_RECALLS

This change requires that you restart the CommVault services to take effect.

Files fail to come online when connecting to file system archives using SMB on Mac OS X 10.6.7, 10.6.8 and 10.7

Tuesday, June 28th, 2011

A change Apple introduced starting with Mac OS X 10.6.7 has led to questions about file system archiving support for Macs. The bug was finally fixed in Mac OS X 10.8.2. This article explains the options for previous version of Mac OS X.

What changed in Mac OS X 10.6.7?

Apple made a change in the Mac OS X 10.6.7 update that prevents Macs from using the SMB/CIFS network protocol to recall files that are stored offline with a file system archiving solution. The problem remains in 10.6.8 and 10.7.x Lion.

Is it still possible to use file system archiving from Macs?

Yes if a Mac uses Apple’s native AFP network protocol to connect to the server, instead of the Windows SMB protocol, recalls will continue to work properly.

How can I use AFP with a Windows server?

The AFP protocol can be easily supported on a Windows 2003 or 2008 server by using GroupLogic’s ExtremeZ-IP software on the server. A trial version of ExtremeZ-IP is available on GroupLogic’s web site. Using AFP also offers many other compatibility and performance advantages for Macs.

Do I still need ArchiveConnect?

Yes, if you have Macs accessing file system archiving solutions. ArchiveConnect is designed to allows Macs to browse archived files without triggering unintended mass recalls of offline files. A Mac running ArchiveConnect will work properly if the AFP protocol is used, regardless of the OS X version. However, please note that a Mac using an SMB connection with 10.6.7 or later will not recall files, whether intentional or not, with or without ArchiveConnect. A trial version of ArchiveConnect is available on GroupLogic’s web site.

Will the Mac bug be fixed?

We reported the bug to Apple as Bug ID # 10836961 and it was fixed in Mac OS X 10.8.2.

Where do I go from here?

We recommend that organizations using Macs with file system archiving use ExtremeZ-IP and ArchiveConnect together to give Macs the benefit of AFP along with user-initiated file recalls that work as expected.

ShadowConnect registry settings for non-english language support

Friday, May 27th, 2011

In order to function properly on Windows servers with non-english languages configured, ShadowConnect requires the modification of three registry values.

This is required so that ExtremeZ-IP can properly parse the EZShadowsFor{x}.txt file when determining if there are any shadow copies available for the volume. (The “{x}” in this file name is substituted for the drive letter being used).

These three parameters are in the registry at the following location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ExtremeZ-IP\Parameters4\VSS\Refreshable

and they are called:

VSSLocalStringContentsOf (default value is “Contents of”)
VSSLocalStringCreationTime (default value is “creation time:”)
VSSLocalStringShadowCopyVolume (default value is “Shadow Copy Volume:”)

These keys are automatically created at run time if they don’t exist. You can change these values to their non-english language equivalents to get Shadow Connect to work right in their environment.

You should run the following command once to determine the values for these keys:

vssadmin list shadows /for=c:

This will display the current shadow copy “sets”, which look like this:

Contents of shadow copy set ID: {4717beb4-f5d6-4055-9c00-62e040a09565}
Contained 1 shadow copies at creation time: 2/3/2011 3:28:57 PM
Shadow Copy ID: {72dae7b2-b9c8-4b49-9713-03177fad9523}
Original Volume: (C:)\\?\Volume{ac2a0daf-99cf-11dd-b5ff-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy31
Originating Machine: demerara.grouplogic.com
Service Machine: demerara.grouplogic.com
Provider: ‘Microsoft Software Shadow Copy provider 1.0′
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

ExtremeZ-IP looks in this output for those key words above in bold. These can be in a language other than english, and these are the values that you need to put in these registry keys for this to work. Note that the colons are needed. They help narrow the parse so that ExtremeZ-IP finds the right stuff, so these colons should be included in the registry key values.

For example, an Italian customer has this for the EZShadowsForG.txt file:

Contenuto dell’ID gruppo di copie shadow: {ac872192-d8ee-4c25-8a9b-a04f2267f979}
Conteneva 1 copie shadow al momento della creazione: 26/01/2011 14:27:44
ID copia shadow: {cfa00e4a-25f0-4a8c-b9e4-943670104575}
Volume originale: (G:)\\?\Volume{69f7e22d-fe3c-11df-a59b-005056830423}\
Volume copia shadow: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Computer di origine: SRV1.ArtiGraficheAlpine.local
Computer di servizio: SRV1.ArtiGraficheAlpine.local
Provider: ‘Microsoft Software Shadow Copy provider 1.0′
Tipo: ClientAccessible
Attributi: Permanente, Accessibile dal client, Senza rilascio automatico, Nessun autore, Differenziale

They would need to add the bold values to the keys to allow ShadowConnect to function properly.

GroupLogic Product Compatibility with Mac OS X 10.7 Lion

Tuesday, March 8th, 2011

We have tested the public release of Mac OS X 10.7 Lion and have updated our products for compatibility with this latest Mac OS release.

If you have any questions or find any issues with our products, please contact us at http://support.grouplogic.com/request

activEcho: The Mac activEcho client is fully compatibile with Mac OS X 10.7.

ArchiveConnect: Users of Mac OS X 10.7 will need to upgrade to the ArchiveConnect 1.2.1 or later Mac client software for Lion compatibility.

ExtremeZ-IP: Users of Mac OS X 10.7 will need to upgrade to ExtremeZ-IP 7.2 or later. ExtremeZ-IP 7.2 addresses all known issues with Lion, except for DFS-based home directory support.

If you require support for network home directories that reside in DFS namespaces, we recommend you do not move to Lion yet. Support for DFS home directories on Lion is in progress, but will require an upgrade to a later update release of ExtremeZ-IP and/or Mac OS 10.7.

MassTransit: If you have Web Client users on Mac OS 10.7 Lion and/or using Safari 5.1, you will need to upgrade your MassTransit Server and their Web Clients to version 7.2.4 or later.

Please note that as previously announced, MassTransit Server 6.0.2×28 is expected to be the last server version that runs on Mac OS X and we will not be testing it or updating it for 10.7 compatibility. The migration path for MassTransit Server is to upgrade to MassTransit 7.x on Windows 2003 or 2008.

ShadowConnect: Users of ShadowConnect will need to upgrade to ExtremeZ-IP 7.2 for ShadowConnect compatibility with Lion. The existing ShadowConnect 1.0.2 Mac client software is compatible with Lion.