You are on page 1of 48

Hitachi Content Platform Anywhere

HCP Anywhere 3.0 Release Notes


HCP Anywhere Software Version 3.0.0.20
HCP Anywhere Operating System Version 24.0.0.28
Desktop Application (for Windows) Version 3.0.0.18
Desktop Application (for Mac) Version 3.0.0.8
Microsoft Outlook Add-in 3.0.0.3
Mobile Application (for iOS) Version 3.0.0.5
Mobile Application (for Android) Version 3.0.0.4
Mobile Application for (Windows Phone) Version 3.0.0.3

RN-HCPAW003-15
March 30, 2017
2017 Hitachi Data Systems Corporation. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or
mechanical, including photocopying and recording, or stored in a database or retrieval system for
commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data Systems
Corporation (collectively, Hitachi). Licensee may make copies of the Materials provided that any such
copy is: (i) created as an essential step in utilization of the Software as licensed and is used in no other
manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials.
"Materials" mean text, data, photographs, graphics, audio, video and documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumes no
responsibility for its use. The Materials contain the most current information available at the time of
publication.

Some of the features described in the Materials might not be currently available. Refer to the most recent
product announcement for information about feature and product availability, or contact Hitachi Data
Systems Corporation at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable
Hitachi agreements. The use of Hitachi products is governed by the terms of your agreements with Hitachi
Data Systems Corporation.

By using this software, you agree that you are responsible for:

1) Acquiring the relevant consents as may be required under local privacy laws or otherwise from
authorized employees and other individuals to access relevant data; and

2) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with
relevant laws.

Notice on Export Controls. The technical data and technology inherent in this Document may be
subject to U.S. export control laws, including the U.S. Export Administration Act and its associated
regulations, and may be subject to export or import regulations in other countries. Reader agrees to
comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain
licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries.

AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eServer, FICON, FlashCopy,
IBM, Lotus, MVS, OS/390, PowerPC, RS6000, S/390, System z9, System z10, Tivoli, z/OS, z9, z10, z13,
z/VM, and z/VSE are registered trademarks or trademarks of International Business Machines Corporation.

Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft,
the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL
Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo, Windows Azure, Windows
PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or
trademarks of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from
Microsoft Corporation.

All other trademarks, service marks, and company names in this document or web site are properties of
their respective owners.
Contents

About this document 1


Release highlights for HCP Anywhere 3.0 1
Related documents 5
Upgrade notes 6
Impacts of upgrading 7
Brief interruption of services 7
TLS1.2 and its effects 7
Recovery (TLS 1.2) 8
Changes to User Portal URL 10
Recovery (URL) 10
Supported limits 11
Requirements for Active Directory authentication support 13
Requirements for SAML authentication support 14
Supported HCP releases 15
Consideration for connecting HCP Anywhere to HCP 15
Supported virtualization infrastructures 15
Supported ESXi hosts 15
Supported VMware products 16
Virtual machine requirements 16
Supported VMware features 16
Unsupported VMware features 17
Supported HDI devices 17
Supported NAS servers 17
Supported browsers 18
Supported languages 18
Supported platforms for file synchronization and sharing applications 19
Supported desktop operating systems 19
Supported mobile phones 20

Contents iii
HCP Anywhere 3.0 Release Notes
Supported Microsoft Outlook versions 21
Supported desktop application distribution platforms 21
Supported Citrix applications for VDI 22
Supported virus-scanning servers 22
Issues resolved in release 3.0 23
Issues with workarounds 27
Other known issues 36
Getting help 42
Comments 42

iv Contents
HCP Anywhere 3.0 Release Notes
About this document
This document contains the release notes for release 3.0 of Hitachi Content
Platform Anywhere (HCP Anywhere). This document describes the new
features, product documentation, and known issues for HCP Anywhere. It
also provides other useful information about this release of the product.

Release highlights for HCP Anywhere 3.0


This section describes the new new features, enhancements, and security
fixes in release 3.0 of HCP Anywhere.

Security fixes and enhancements


Release 3.0 of HCP Anywhere contains a number of security fixes and
enhancements, including updates to Apache Struts, Apache Tomcat,
Kernel, and OpenSSL.

For more information, see "Issues resolved in release 3.0".

HCP Anywhere enforcement of TLS1.2


Release 3.0 of HCP Anywhere enhances security by enforcing Transport
Security Layer (TLS) version 1.2 connections to the HCP Anywhere nodes by
default. TLS 1.2 is more secure than TLS1.0 and 1.1.

For more information on TLS1.2 and its effects on the HCP Anywhere
system, see "Impacts of upgrading".

Control sharing privileges using profile settings


Administrators can now limit sharing between different groups in their
organization using profile settings. Administrators can prevent certain
profiles from sharing with one another, prevent profiles from sharing with
anyone but those in the profile, or prevent profiles from sharing at all.

For more information, see the HCP Anywhere Administrator Help.

1
HCP Anywhere 3.0 Release Notes
Release highlights for HCP Anywhere 3.0

Administrator defined backup


In release 3.0, HCP Anywhere boasts several enhancements to backup and
data security. Previously, HCP Anywhere users could back up files and
folders located on their computers but outside their desktop application
folders. This offered users increased data security. Now, in addition to user
backup, administrators can back up files and folders for their users by
specifying:

Paths to back up for their users.

File types to back up for their users.

File types to be ignored during the back up process.

For more information, see the HCP Anywhere Administrator Help.

Seamless integration with the HCP Anywhere platform


Release 3.0 of HCP Anywhere contains an enhanced File Sync and Share
API. With the enhanced File Sync and Share API, administrators can create
custom apps, integrate third-party apps, and automate tasks using scripts
and programs. The File Sync and ShareAPI contains every endpoint HCP
Anywhere uses in their own User Portal. For help using this API, HCP
Anywhere offers a Java software developers kit (SDK) on the Maven Central
Repository and a sample program that uses the SDK on GitHub.

To access GitHub, which contains information on all the File Sync and Share
API resources, see https://github.com/Hitachi-Data-Systems/anywhere-
fss-sdk.

Mobilize NAS shares to HCP Anywhere using sAMAccountName


Administrators can now use the sAMAccountName to add their users'
personal NAS shares to HCP Anywhere. Previously, administrators could
only do this with the User Principle Name.

For more information, see the HCP Anywhere Administrator Help.

Increased backup limits


The HCP Anywhere system now allows users to back up a maximum of
300,000 files and folders per computer. Previously, users could back up a
maximum of 200,000 files and folders per computer.

For more information, see "Supported limits".

2
HCP Anywhere 3.0 Release Notes
Release highlights for HCP Anywhere 3.0

Modernresponsive User Portal


Release 3.0 of HCP Anywhere includes an entirely redesigned User Portal.
The new User Portal has a sleek, modern design with a focus on usability
and enhanced back-end processing for increased operating speeds. The new
User Portal can even be accessed in a mobile browser.

For more information, see the HCP Anywhere User Help.

Next generation Android application


The new Android application includes a number of enhancements and
features:

Completely redesigned UI with new navigation menu, more intuitive


workflows, and dynamic search

Direct upload to HCP Anywhere from within the app

Take photos and save to HCP Anywhere from within the app

Rename files and folders within the app

Sorting based on name or date last modified

For more information, see the HCP Anywhere User Help.

Next generation Windows desktop application


Version 3.0 of the Windows desktop application can be deployed and used in
both persistent and non-persistent virtual desktop infrastructure
environments. With this new functionality, administrators can configure
desktop application properties such as support for roaming user profiles,
the number of users that can access the desktop application on a single
Windows terminal, and the size of the desktop application cache.

For more information, see the HCP AnywhereAdministrator Help.

Intelligent storage management for the desktop application


The new Windows desktop application gives users complete control over
which files in their desktop application folders are saved locally to their
computers and which remain remotely in HCP Anywhere. This is the perfect
way for each user to manage the space their desktop application folder
occupies on their computer.

For more information, see the HCP Anywhere User Help.

3
HCP Anywhere 3.0 Release Notes
Release highlights for HCP Anywhere 3.0

New desktop application folder


When registering the desktop application, users can now choose an existing
folder to be their desktop application folder. This automatically adds any
files in that folder to HCP Anywhere. Users can even select their entire
Documents folder. Prior to release 3.0, users could only select an empty
folder when registering the desktop application.

For more information, see the HCP Anywhere User Help.

Desktop app dashboard


The desktop application boasts a new dashboard. The new dashboard
contains each user's usage, synchronization, and backup information in one
central location.

For more information, see the HCP Anywhere User Help.

Customized links from the desktop application


In release 3.0, users can create completely customized links using the
desktop application. Previously, users could create quick links in their
desktop application folder, which had the default link settings configured by
the HCP Anywhere administrator, but could not customize the links in any
way.

For more information, see the HCP Anywhere User Help.

Links that never expire


With links that never expire, users no longer have to worry about renewing
the expiration date for their links. Previously, all links remained active for a
limited number of days. Links that never expire can be enabled or disabled
in the HCP Anywhere Management Console.

For more information, see the HCP AnywhereAdministrator Help.

Dynamic group sharing


When users invite a group to a collaborative folder, HCP Anywhere now
manages the membership of that group for them. When a person is added
to a group in Active Directory, that person is automatically invited to the all
the collaborative folders in which the group is a member. Similarly, when a
person is deleted from a group in Active Directory, that person is
automatically removed from all the collaborative folders in which the group
is a member.

For more information, see the HCP Anywhere User Help.

4
HCP Anywhere 3.0 Release Notes
Related documents

New online help


HCP Anywhere has a new online help which contains only the essential,
need-to-know information about HCP Anywhere.

Updated Fedora operating system


The HCP Anywhere operating system is now based on the open source
operating system, Fedora 24, from the Fedora Project. Previously, the HCP
Anywhere operating system was based on Fedora 21.

For more information, see Third-Party Copyrights and Licenses.

Additional language support


The German language is now supported.

Related documents
These following documents contain additional information about HCP
Anywhere:

HCP Anywhere Administrator Help MK-HCPAW000 This help


contains the instructions you need to use the HCP Anywhere
Management Console to configure and monitor an HCP Anywhere
system and its hardware. This set of help topics also includes
instructions on administering the file synchronization and sharing and
HDI device management features.

This help is accessible from the HCPAnywhere Management Console.

HCP Anywhere User Help MK-HCPAW001 This help explains how to


use HCP Anywhere for file storage and synchronization. These topics
discuss the file synchronization interfaces that HCP Anywhere provides,
which include desktop and mobile applications and a web application
called the User Portal.

This help is accessible from the HCP Anywhere User Portal.

Deploying an HCP Anywhere VM System MK-HCPAW011 This book


provides the information you need to install HCP Anywhere in virtual
machines. The book explains what you need to know to successfully
configure your VM environment and contains step-by-step instructions
for the installation procedure.

Installing an HCP Anywhere System Final On-site Setup MK-


HCPAW005 This book contains instructions for deploying an

5
HCP Anywhere 3.0 Release Notes
Upgrade notes

assembled and configured physical HCP Anywhere system at a customer


site. The book explains how to make the necessary physical connections
and reconfigure the system for the customer computing environment.
The book also contains instructions for configuring Hi-Track Monitor to
monitor an HCP Anywhere system.

Third-party Copyrights and Licenses MK-HCPAW002 This book


contains copyright and license information for third-party software
distributed with or embedded in the HCP Anywhere operating system,
core software, and file synchronization and sharing applications.

HCP Anywhere File Sync andShareAPI Reference Guide MK-


HCPAW012 This help provides information on the set of
HTTPendpoints that make up the HCP Anywhere File Sync and Share
API.TheFile Sync and ShareAPI is a programmatic interface for
integrating custom and third-party applications with HCP Anywhere. For
each endpoint, the help explains which operations the endpoint
performs and how to make a request with that endpoint.

Upgrade notes
You can upgrade an HCP Anywhere system to release 3.0 only from release
1.1 or later. To upgrade from a release earlier than 1.1, you first need to
upgrade to release 1.1. You cannot downgrade HCP Anywhere to a previous
release.

Important: If, after an upgrade to version 2.0 or 2.0.1, your users are
unable to register 2.0.x applications, you need to resolve these registration
failures before you can upgrade to version 3.0. Contact your HCP Anywhere
service provider for help.

The AW004_<version-number>.bin.zip file is used for upgrading an HCP


Anywhere system.

Before upgrading
Before upgrading, ensure that all SSL server certificates for the HCP
Anywhere system are valid. If any certificates are invalid, desktop and
mobile applications will be unable to connect to the system.

If a user identified the HCP Anywhere system by IP address or by only the


first part of the fully qualified domain name when registering the desktop
application, the desktop application will be unable to connect to HCP

6
HCP Anywhere 3.0 Release Notes
Impacts of upgrading

Anywhere after the upgrade. In this case, the user needs to reconfigure the
application to use the fully qualified domain name for the HCP Anywhere
system.

Impacts of upgrading
Each release of HCP Anywhere contains a number of new features,
enhancements, and security fixes. Before upgrading, you should be aware
of the changes in the release as they can impact both your HCP Anywhere
system and your HCP Anywhere users. In this section, the major impacts of
upgrading to release 3.0 of HCP Anywhere are described.

Brief interruption of services


Upgrading to version 3.0 of HCP Anywhere causes a brief interruption of
services. For example:

The User Portal and Management Console are temporarily unavailable.

The HCP Anywhere applications are temporarily unable to connect to the


HCP Anywhere system.

Typically, services resume after 5 to 10 minutes.

TLS1.2 and its effects


Release 3.0 of HCP Anywhere enhances security by enforcing Transport
Security Layer (TLS) version 1.2 connections by default. TLS 1.2 is more
secure than TLS 1.0 and 1.1. However, enforcing TLS1.2 can prevent some
older applications from connecting to HCP Anywhere without some
additional configuration.

When TLS 1.2 is enforced, HCP Anywhere Windows desktop applications


and Outlook Add-ins older than version 3.0, Hitachi Data Ingestor (HDI)
devices older than version 6.1.1, and HCP Anywhere Android applications
on Android version 5.0 cannot connect to HCP Anywhere if all of the
following are true:

TLS 1.0 and 1.1 are disabled in the HCP Anywhere Management
Console. In release 3.0, TLS v1.0 and 1.1 can be enabled or disabled on

7
HCP Anywhere 3.0 Release Notes
Impacts of upgrading

the System > Security > Network page of the HCP Anywhere
Management Console.

SSL is not terminated at a network appliance that allows TLS 1.0 (for
example, a load balancer).

Additionally, for the Windows desktop application:

The desktop application is connecting to the HCP Anywhere system


from a Windows 7 machine that does not have the
DefaultSecureProtocols registry key configured to use TLS 1.2. On
Windows 8.1 and 10, the DefaultSecureProtocols registry key is
configured to use TLS 1.2 by default.

Additionally, for the Outlook Add-in:

The Outlook Add-in is connecting to the HCP Anywhere system from


a Windows machine that does not have the SchUseStrongCrypto
registry key configured to use TLS 1.2.

Recovery (TLS 1.2)


If the above conditions are true, you can allow older HCP Anywhere
applications and HDI devices to connect to HCP Anywhere by doing one of
the following:

Option 1 (less secure)

Enable TLS1.0 and 1.1 in the HCP Anywhere Management Console.


However, you are now using TLS 1.0 and 1.1 connections, which have
known security vulnerabilities.

Option 2 (less secure)

If you use a network appliance (for example, a load balancer) to direct


traffic to HCP Anywhere, you can:

1. Verify that Enable TLSv1.0 and v1.1 is disabled.

2. Verify that the network appliance supports TLS 1.0 and 1.1.

3. Terminate (unencrypt) SSL traffic at the network appliance.

Option 3 (more secure)

8
HCP Anywhere 3.0 Release Notes
Impacts of upgrading

This option only applies to the HCP Anywhere Windows desktop


application and Outlook Add-in.

1. Verify that Enable TLSv1.0 and v1.1 is disabled.

2. For the Windows desktop application, update your Window 7


machines to use TLS 1.2 connections for the desktop application by:

a. Applying update KB3140245 to your Windows 7 machines.

b. Setting the DefaultSecureProtocols registry key to 800 in the


following registry paths:

HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Int
ernet Settings\WinHttp

HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\Cu
rrentVersion\Internet Settings\WinHttp

c. Setting the SecureProtocols registry key to A80 in the following


registry paths:

HKEY_CURRENT_
USER\Software\Microsoft\Windows\CurrentVersion\Internet
Settings

HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Int
ernet Settings

An MSI for applying the DefaultSecureProtocols registry key and


further instructions are available from Microsoft:

https://support.microsoft.com/en-us/help/3140245/update-
to-enable-tls-1.1-and-tls-1.2-as-a-default-secure-protocols-
in-winhttp-in-windows

3. For the Windows OutlookAdd-in, update your Window machines to


use TLS 1.2 connections for the Add-in by setting the
SchUseStrongCrypto registry key to 1 in the following registry paths:

HKEY_LOCAL_
MACHINE\SOFTWARE\Microsoft\.NetFramework\v4.0.30319

9
HCP Anywhere 3.0 Release Notes
Impacts of upgrading

HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NetFramew
ork\v4.0.30319

Further instructions are available from Microsoft:

https://success.outsystems.com/Support/Enterprise_
Customers/Maintenance_and_Operations/(.NET)_Enable_SSL_
Protocols_for_your_Integrations_-_TLS_1.1_and_TLS_1.2

You can also prompt your users to upgrade their HCPAnywhere applications
to release 3.0 and upgrade your HDI devices yourself to a release that works
with TLS 1.2 (6.1.1 or later).

For more information, see the HCP Anywhere Administrator Help.

Changes to User Portal URL


In release 3.0 of HCP Anywhere, a number of aspects of the User Portal URL
have changed. Customers who use the User Portal URL for HTTP or
HTTPStraffic (typically in the form of load balancer rules) or who have
bookmarked User Portal pages are affected by this change.

Below are the changes to the User Portal URL:

The root of the User Portal URL has changed from portal to userportal.
Regardless of the User Portal page being accessed, the User Portal URL
always begins like this:

http://hcp-anywhere-system-name.domain-name/userportal

In addition to above change, most User Portal pages have an entirely


new URL structure. For example, the URL for the Files page used to end
/home/files while in the new User Portal it ends /#/files.

Recovery (URL)
For a network appliance, update the HTTP or HTTPS traffic rules to use the
new User Portal URL.

For bookmarks, simply re-bookmark pages in the new User Portal that
correspond to your old bookmarks.

10
HCP Anywhere 3.0 Release Notes
Supported limits

Supported limits
HCP Anywhere enforces the limits listed in the table below.

Item Limit

System management

Maximum number of profiles 400


(profile are used for allowing users to access to
HCPAnywhere)

File synchronization and sharing

Maximum number of users without a file 20


synchronization and sharing license

Maximum number of registered users 1 Entry Pod: 5,000

Standard Pods shipped with a


release earlier than 2.0:
20,000

Standard Pods shipped with


release 2.0 or later: 50,000

Maximum number of NAS servers 50

Maximum number of Windows desktop 1023


applications that can connect to a single Windows
Terminal Server at one time. This number is configured by the
HCP Anywhere administrator using
a registry entry.

Maximum number of devices for each user Can be configured from zero to 11

Maximum number of files and folders in a folder 20,000


for each user

Maximum total number of files and folders for 200,000


each user

Maximum number of folders that a user can 30


share with other users

Maximum file size 2 Can be configured from 1 GB to


2,043 GB

Default is 10 GB

11
HCP Anywhere 3.0 Release Notes
Supported limits

(continued)

Item Limit

Maximum path length 3 1,023 characters

However, Windows only supports


paths of up to 259 characters.

Maximum length of individual file or folder names 255 characters

Maximum number of files that can be added to Limited only by available space on
the list of favorites on a mobile application mobile device

Backup

Maximum number of files and folders that can be 300,000


backed up for each computer

Maximum number of files and folders that can be 20,000


backed up in a single folder

Multi-user systems support for the Windows desktop application

Maximum number of users who can use a single 1024


Windows Terminal Server at once to run the
desktop application (configurable using registry
entries)

For more information, see


Configuring desktop applications for
VDI.

HDI device management

Maximum number of in-service HDI devices 5


without an HDI device management license

Maximum number of HDI devices that HCP 10,000


Anywhere can manage

Maximum number of HDI devices in service at 5,000


one time 4

Maximum number of provisioning templates 50

Maximum number of HDI file systems (any type) 5


per HDI device

Maximum number of file system shares per HDI 50


file system

12
HCP Anywhere 3.0 Release Notes
Requirements for Active Directory authentication support

(continued)

Item Limit

Maximum number of tags that can be applied to 10


an HDI device

Maximum number of tags 500

1. The maximum number of registered users your HCP Anywhere system can
support is limited by your file synchronization and sharing license.

2. Check with your HCP administrator to ensure that the HCP system has enough
space to store files of the size you want.

3. For information on how path length limitations affect the desktop applications,
see the HCP Anywhere User Help.

4. The maximum number of in-service HDI devices is limited by your HDI device
management license.

Requirements for Active Directory authentication support


HCP Anywhere requires Windows Active Directoryfor user
authentication.For HCP Anywhere to work with AD:

All AD domain controllers must be running one of theseWindows server


versions:

Windows Server 2012 R2

Windows Server 2012

Windows Server 2008 R2

HCP Anywhere must have network connectivity to one or more domains


in the AD forest.

Note: By default, HCP Anywhere attempts to connect to every domain


in theforest, except for domains in the forest with international names.
HCP Anywhere does not support domains with international names. If
your AD infrastructure does not allow HCP Anywhere to connect to every
domain in the forest, you can use the domain whitelist in the HCP
Anywhere Management Console to specify the domains to which HCP
Anywhere can connect. For information on domain whitelists, see the
HCP Anywhere Administrator Help, which is available from the
Management Console.

13
HCP Anywhere 3.0 Release Notes
Requirements for SAML authentication support

HCP Anywhere must be able to contact at least one DNS server that can
resolve the AD domain name.

The AD time must be in sync with the HCP Anywhere system time. The
recommended configuration is for HCP Anywhere and AD to use the
same time server.

Additionally, to ensure that AD users have continuous access to HCP


Anywhere, the AD infrastructure should have a robust and fault-tolerant
configuration.

Requirements for SAML authentication support


HCP Anywhere is qualified for use with these SAML identity providers:

Active Directory Federation Services (AD FS) version 2.0

AD FS version 2.1

AD FS version 3.0

For HCP Anywhere to be able use AD FS for user authentication:

File synchronization and sharingusers must have network connectivity


to AD FS.

The AD FS time must be in sync with the Active Directory time. The
recommended configuration is for AD and ADFS to use the same time
server.

14
HCP Anywhere 3.0 Release Notes
Supported HCP releases

Supported HCP releases


HCP Anywhere requires an HCP system for:

Storing the contents of files added by file synchronization and sharing


users

Backing up essential HCP Anywhere system data

Storing data migrated from the HDI devices that HCP Anywhere
manages

The HCP system that HCP Anywhere uses must be at HCP release 6.0 or
later.

Consideration for connecting HCP Anywhere to HCP


HCP Anywhere accepts but does not verify all SSL server certificates from
the HCP system. Therefore, you should configure the connection between
HCP Anywhere and HCP to use only your organizations corporate network.

Supported virtualization infrastructures


The following sections list the supported virtualization infrastructures for
deploying HCP Anywhere in a VM.

Supported ESXi hosts


HCP Anywhere VM systems are qualified for use with ESXi versions:

5.5

6.0

6.5

Other ESXi versions may work but have not been formally tested.

15
HCP Anywhere 3.0 Release Notes
Supported virtualization infrastructures

Supported VMware products


These VMware products are qualified for the setup and management of an
HCP Anywhere VM system:

VMware vCenter Server version 5.5, 6.0, and 6.5

VMware vSphere WebClient version 5.5, 6.0, and 6.5

HCP Anywhere VM systems may work with other versions of VMware


vCenter or vSphere but have not been formally tested.

Virtual machine requirements


Each virtual machine requires a certain number of CPUs and a certain
amount of memory. These amounts are determined by both the number of
users the system can support and the number of nodes in the system:

Potential number of users

Single-node system Multi-node system CPUs Memory

1-100 1-100 4 4 GB

101-200 101200 4 6 GB

201-500 201500 4 8 GB

501-1,000 5011,000 4 10 GB

1,001-2,000 1,0012,000 4 16 GB

2,001-5,000 2,0015,000 6 32 GB

5,000-25,000 5,00120,000 16 128 GB

N/A 20,001-50,000 16 256 GB

Supported VMware features


These VMware vSphere features or tools have been qualified for use with an
HCP Anywhere VM system:

vMotion

Storage vMotion

Distributed Resource Scheduler (DRS)

16
HCP Anywhere 3.0 Release Notes
Supported HDI devices

Storage DRS

Distributed switch

VMware HA is supported on single-node systems

Unsupported VMware features


These VMware vSphere features or tools have not been tested and are not
supported with an HCP Anywhere system:

Fault Tolerance.

Snapshots. (Specifically, HCP Anywhere does not support rolling back to


a snapshot of an HCPAnywhere virtual machine.)

VMware HA is not supported on multi-node systems.

Supported HDI devices


HCP Anywhere is qualified for use with these types of HDIdevices:

Remote Server

Single Node

Virtual machine (VM)

To be managed by HCP Anywhere, a device must run one of these HDI


software versions:

5.0 or later for the Remote Server

5.1 or later for single node devices or VMs

Supported NAS servers


HCP Anywhere is qualified for mobilizing the contents of NAS shares from
these types of NAS servers:

Hitachi Data Ingestor 6.0.0 and 6.0.1

Hitachi NAS Platform (HNAS) 12.3 and 12.5

Hitachi Data Systems Unified NAS 13.0

17
HCP Anywhere 3.0 Release Notes
Supported browsers

NetApp ONTAP 8.1, 8.2, and 9.0

Microsoft Windows Server 2008R2, 2012R2, and 2016

EMC lsilon OneFS 7.2 and 8.0

EMC VNX

Supported browsers
Thetable below lists the browser and operating system combinations that
are recommended for accessing the HCP Anywhere Management Console
and User Portal. Other browsers or other versions of the browser may work
but have not been formally tested.

Browser Client operating system

Apple Safari 8, 9, and 10 Mac

Google Chrome 50 and later Windows and Mac OS X

Microsoft Internet Explorer 10 and 11 Windows

Mozilla Firefox 50 and later Windows and Mac OS X

Microsoft Edge Windows 10

BlackBerry Browser BlackBerry 10

* These considerations apply when you use Internet Explorer to view the Management Console or
User Portal:

The security level cannot be set to High.

The Management Console and User Portal do not function correctly when displayed in
Compatibility View .

Supported languages
For the User Portal, desktop applications, andOutlook Add-in, these
languages are supported:

English

Japanese

Korean

18
HCP Anywhere 3.0 Release Notes
Supported platforms for file synchronization and sharing applications

German

Simplified Chinese

French Canadian

Spanish (Latin America)

For the Android and iOS applications, these languages are supported:

All languages listed above, and

Portuguese

Turkish

For the Windows Phone application, English is the only supported language.

Supported platforms for file synchronization and sharing


applications
The following sections list the platforms qualified for running HCP Anywhere
file synchronization and sharing applications.

Supported desktop operating systems


Windows

The HCP AnywhereWindows desktop application is qualified for use with


these versions of Windows:

10

8.1 (Windows UCRT patch KB2999226 required)

7 (Windows UCRT patch KB2999226 and security patch KB3033929


required)

19
HCP Anywhere 3.0 Release Notes
Supported platforms for file synchronization and sharing applications

Notes:

The HCP Anywhere desktop application supports only 64-bit


versions of Windows.

The HCPAnywhere Windows desktop application supports only the


NTFS file system format. To find the file system format for a hard
disk drive on your computer:

a. In the My Computer window, right-click on the icon for the


hard disk drive that you want to check.

b. Click on the Properties button.

The file system type for the drive is displayed in the File system field.

Mac

The HCP AnywhereMac desktop application is qualified for use with these
versions of Mac OS X:

10.12 (Jaguar)

10.11 (El Capitan)

10.10 (Yosemite)

Note: The HCPAnywhere desktop application for Mac supports only the
HFS+ file system format. This is the default file system format for Mac OS X.
This file system format is case insensitive.

Supported mobile phones


iOS devices

The current version of the HCP Anywheremobile application (3.0 ) is


qualified for use with these versions of iOS:

10

Android devices

20
HCP Anywhere 3.0 Release Notes
Supported desktop application distribution platforms

The current version of the HCP Anywheremobile application (3.0 ) is


qualified for use with these versions of Android:

7.0 (Nougat)

6.0 (Marshmallow)

5.0 (Lollipop)

4.4 (Kit Kat)

4.2 and 4.3 (Jelly Bean)

Windows Phones

The current version of the HCP Anywheremobile application (3.0 ) is


qualified for use with these versions of Windows Phone:

10

8.1

Note: The HCP Anywhere mobile application runs only on Windows Phones,
not on Windows tablets or PCs.

Supported Microsoft Outlook versions


The HCPAnywhere Outlook Add-in is qualified for use with:

Microsoft Outlook versions 2010, 2013, and 2016

Microsoft Windows versions 7, 8.1, and 10

For the Outlook Add-in to be installed, these programs need to be installed


on the Windows machine:

.NET version 4.5 or greater

VSTO Visual Studio Tools for Office version 10.0.50903 or greater

Supported desktop application distribution platforms


HCP Anywhere is qualified for use these platforms for distributing the
desktop applications:

21
HCP Anywhere 3.0 Release Notes
Supported Citrix applications for VDI

For Windows, SCCM 2012

For Mac, Casper 9.61

Supported Citrix applications for VDI


For virtual desktop infrastructure (VDI) environments, the HCP Anywhere
Windows desktop application is qualified for use with:

Citrix XenServer 7.8, 7.9, and 7.11

Citrix XenDesktop 7.8, 7.9, and 7.11

Citrix XenApp 7.8, 7.9, and 7.11

Supported virus-scanning servers


HCPAnywhere can be configured to use the Internet Content Adaptation
Protocol (ICAP) to submit files added by file synchronization and sharing
users to servers that perform virus scanning. HCP Anywhere does not
synchronize files in which viruses are detected.

HCP Anywhere is qualified for use with these antivirus programs:

McAfee VirusScan Enterprise version 8.8 and McAfee VirusScan


Enterprise for Storage version 1.0.2 with hotfix HF726390 or version
1.1.0

Symantec Protection Engine for Cloud Services versions 7.0 and 7.5

Trend Micro InterScan Web Security Virtual Appliance versions 6.0 and
6.5

22
HCP Anywhere 3.0 Release Notes
Issues resolved in release 3.0

Issues resolved in release 3.0


The table below lists previously identified issues that have been resolved in
release 3.0. The issues are listed in order by reference number.

Ref.
number Description

AW-2486 Desktop application takes several minutes to alert that it cannot connect to the HCP
Anywhere system
When the HCP Anywhere desktop application loses connectivity to the HCP Anywhere
system, the application can take up to five minutes to alert that it cannot connect.
During this time, the application appears to be working normally.

Fix: The application now displays an alert immediately when it cannot connect to the
HCP Anywhere system.

AW-12337 Items displaying incorrectly in the User Portal


In version 11.0.23 of Internet Explorer, the following items are displayed incorrectly in
the User Portal:

The login screen is located at the top right-hand corner of the Internet Explorer
window instead of in the center of the Internet Explorer Window.

The Share Link window is stretched across the entire Internet Explorer window.

The Files, Collaboration, Activity, Account, and Help buttons are condensed into a
single Menu button regardless of window size.

Fix: In release 3.0, the User Portal has been entirely redesigned. The display issues listed
above do not exist in the new User Portal.

AW-12461 Known vulnerabilities in OpenSSL


The version of OpenSSL that HCP Anywhere uses was discovered to have some
vulnerabilities.

Fix: HCP Anywhere now uses OpenSSL version 1.0.2j. In OpenSSL version 1.0.2j, a
vulnerability to padding-oracle attack (CVE-2016-2107) is fixed.

AW-12894 Desktop applications deregisted during a network outage


Occasionally, the desktop application becomes deregistered during a network outage.

Fix: During a network outage, the desktop application no longer becomes deregistered.

23
HCP Anywhere 3.0 Release Notes
Issues resolved in release 3.0

Ref.
number Description

AW-13132 Outlook Add-in deregistered after changing language


When you change the display language of the Outlook Add-in, the add-in is incorrectly
deregistered.

Fix: When you change the display language of the Outlook Add-in, the add-in is no
longer deregistered.

AW-13133 Relying trust for SAML idP can only be set to use SHA-1 when joined to HCP
Anywhere
HCP Anywhere can only communicate with a SAML idP if the relying trust for the idP is
configured to use SHA-1.

Fix: HCP Anywhere can now communicate with SAML idPs who have their relying trust
configured to use SHA-1 or SHA-256.

AW-13409 Login errors are not all the same


Typically, login failures should all return the same response code.However, when a login
failure occurs in the following occasions, different response codes are returned:

Person does not have HCP Anywhere access.

Person has HCP Anywhere access but entered the wrong password.

Person has valid Active Directory credentials but does not have HCP Anywhere
access.

Fix: The same response code (401 (Unauthorized)) is now returned for each of the login
failures listed above.

AW-10605 HCP Anywhere desktop application not automatically added to Quick Access menu
On Windows 10, the HCP Anywhere desktop application is not automatically added to
the Quick Access menu when the application is installed and registered. To have the
desktop application appear in the Quick Access menu, you need to add it manually.

Fix: The desktop application is now added automatically to the Quick Accessmenu.

AW-13937 Unable to log into mobile applications after pod recovery


During an HCP Anywhere system recovery, the mobile applications can sometimes not
be logged into.

Fix: The mobile applications can now be logged into after the HCP Anywhere system
goes through a recovery.

24
HCP Anywhere 3.0 Release Notes
Issues resolved in release 3.0

Ref.
number Description

AW-13975 Known vulnerabilities in Apache Tomcat


The version of Apache Tomcat that HCP Anywhere uses was discovered to have some
and vulnerabilities.

AW-13996 Fix: HCP Anywhere now uses Apache Tomcat version 8.0.42. In Apache Apache Tomcat
version 8.0.42, the following commonly known vulnerabilities have been fixed:

JmxRemoteLifecycleListener vulnerability (CVE-2016-8735)

Block cipher vulnerability within SSL/TLSprotocol (CVE-2016-2183)

AW-14161 Logging into the User Portal takes a long time


For users with a lot of team folders, logging into the User Portal can take a long time.

Fix: In release 3.0, the User Portal has been entirely redesigned. For users with a lot of
team folders, logging into the User Portal no longer takes a long time.

AW-14615 Issues when team folder is nearing capacity and does not have a manager
When a team folder is nearing its storage capacity, the HCP Anywhere system sends an
email notification to the managers of the folder. If a team folder does not have a
manager, the HCP Anywhere system attempts to send an email notification but cannot.
As a result, the service JVM in the HCP Anywhere system is incorrectly restarted. This
can cause a number of issues, including the HCP Anywhere system being unable to
communicate with the ADaccount joined to the system.

Fix:The service JVM no longer restarts when a team folder does not have a manager and
is nearing its storage capacity.

AW-14770 Known vulnerabilities for TLS1.0 and 1.1


Prior to release 3.0, the HCP Anywhere system allowed applications to connect to the
system using TransportLayer Security (TLS) version 1.0 and 1.1. TLS1.0 and 1.1 have
a number of known vulnerabilities.

Fix: In release 3.0, TLS1.2 is enforced for all connections to the HCP Anywhere system.
For more information on this change and its effects, see "Impacts of upgrading" on
page7.

AW-13926 Outlook Add-in stuck in request loop after being deregistered


On rare occassions, the Outlook Add-in may get stuck in a request loop with the HCP
Anywhere server after being deregistered. Although the HCP Anywhere server always
returns a 401 (Invalid Token) to the Outlook Add-in requests, the request loop can
cause an unnecessary load on the system.

Fix: Deregistered Outlook Add-ins no longer get stuck in a request loop with the HCP
Anywhere server. Now, the HCP Anywhere server exits the request loop once it detects
that the add-in has been deregistered.

25
HCP Anywhere 3.0 Release Notes
Issues resolved in release 3.0

Ref.
number Description

AW-14280 Inviting group to collaborative folder fails


Inviting a group to a collaborative folder fails if the group contains a person who does not
have a corporate email configured.

Fix: Inviting a group to a collaborative folder no longer fails if the group contains a person
with a non-corporate email configured. Instead, the person with a non-corporate email
is not invited to the folder while the rest of the group is invited to the folder.

AW-15221 Known vulnerabilities in Apache Struts version 2.3.24


The version of Apache Struts that HCP Anywhere uses was discovered to have some
vulnerabilities.

Fix: HCP Anywhere now uses Apache Struts version 2.3.32. In Apache Struts version
2.3.32, the Remote Code Execution vulnerability (CVE-2017-5638) is fixed.

AW-15243 Known vulnerabilities in Kernel


The version of Kernel that HCP Anywhere uses was discovered to have some
vulnerabilities.

Fix: HCP Anywhere now uses Kernel version 4.8.16. In Kernel version 4.8.16, the
following commonly known vulnerabilities have been fixed:

TCP sessions vulnerability (CVE-2016-5696)

Copy-on-write vulnerability (CVE-2016-5195).

26
HCP Anywhere 3.0 Release Notes
Issues with workarounds

Issues with workarounds


The table below lists known HCP Anywhere issues for which workarounds
exist. The issues are listed in order by reference number.

Ref. number Description

AW-1055 With quota exceeded, moved file deleted from other devices
You can lower a user's storage quota to a size that's smaller than the amount of
data that the user has already stored in HCPAnywhere. This causes the user to be
over the user's storage quota. In this situation, the user cannot add any new files
to HCP Anywhere.

While over the storage quota, if the user moves a file from one folder in the desktop
application folder to another folder within the desktop application folder, the file is
deleted from the HCP Anywhere system and from the user's other devices but not
from the computer on which the file was moved. This happens because HCP
Anywhere synchronizes the removal of the file from the original location but does
not synchronize the addition of the file to its new location.

Workaround: To be able to move files, the user should do one of these:

Reduce the amount of storage used by deleting files from or moving files out of
the desktop application folder.

Ask the HCP Anywhere administrator to increase the user's storage quota.

AW-2766 File not downloaded when unsyncable file of same name is deleted
The following scenario describes what happens when a user adds two files with the
same name from two different HCPAnywhere applications, where one file can be
synced and the other cannot:

1. In the desktop application folder on the user's computer, the user adds a
file of a type that HCPAnywhere can sync .

2. On another device, the user adds a file that has the same name as the
unsyncable file. This second file is of a type that HCPAnywhere can
synchronize. The file is synchronized to the user's devices, except for the
computer that contains the unsyncable file.

3. The user deletes the unsyncable file from the desktop application folder.

The file from the second application is not automatically synchronized to the
computer from which the unsyncable file with the same name was deleted.

Workaround: Edit or rename the syncable file. This causes the file to be
synchronized to the computer from which the unsyncable file was deleted.

27
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-2949 A single failure when uploading multiple pictures or videos cancels all pending
uploads
With the HCP Anywhere mobile application, a user can select multiple pictures and
videos to add to HCP Anywhere. If a picture or video fails to be added (for example,
because the file is larger than the maximum file size for the mobile application), the
mobile application cancels the file uploads for all pictures and videos that have yet
to be added.

Workaround: Do one of these:

Resolve the problem that prevented the file from being uploaded. Then try to
upload the files again.

Try to upload the files again, excluding the one for which the previous operation
failed.

AW-3081 ICAP connection alert displayed by only one node


When the HCP Anywhere system cannot connect to the ICAP server that it uses to
scan files for viruses, the system displays an alert on the File Sync and Share
Overview page in the Management Console. However, this alert is generated by
only one node in the system. This means that depending on the node to which your
Management Console session is connected, you may or may not see the alert.

Workaround: Check the Overview page alerts for both nodes. To do this:

1. In a web browser, enter the URLfor the Management Console in this


format:

https://node-front-end-IP-address:8000/admin

2. To view the file synchronization and sharingOverview page, click on File


Sync and Share.

3. Log out of the Management Console.

4. Enter the URLfor the Management Console, this time by specifying the
front-end IPaddress for the other node in the system.

5. To view the file synchronization and sharing Overview page, click on File
Sync and Share.

AW-5021 File synchronization fails after HCP Anywhere system undergoes recovery
When an HCP Anywhere system is recovered after a serious hardware failure, a
user's desktop applications may be unable to synchronize files with the system.

Workaround: To resume file synchronization, restart the desktop application.

28
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-5576 Exported filesystems cannot be imported until data has been migrated to HCP
After creating an exported filesystem, if you import that filesystem before its data
has been has migrated to HCP, users will be unable to view any of the data in the
imported filesystem.

In this case, the Events tab for the device with the imported filesystem displays
these errors:

Event ID:3842 Device 'device-name' encountered error 'KAQX10020' :


'Provisioning failure (keyword: cifscreate, id: KAQM08165-E)'

Event ID:3842 Device 'device-name' encountered error 'KAQX10008' :


'Namespace-sharing synchronization failure (missing data)'

Workaround: Verify that the exported filesystem has migrated its data before
trying to import the filesystem. To do this, check Health Report tab for the device
on which you created the exported filesystem.

If you've already created the imported filesystem, delete it. Then import the
exported filesystem again after verifying that the data has been migrated.

AW-6179 Files are not synchronized after maximum file size limit is raised
The system does not synchronize files in a user's desktop application folder if those
files are larger than the maximum file size limit. When the administrator raises the
limit, some files may now be eligible to be synchronized, but the desktop application
does not automatically synchronize them.

Workaround: To synchronize the files, move them out of the desktop application
folder, wait for synchronization to complete, and then move them back in.

This information has been added to the HCP Anywhere User Help.

AW-7838 Invalid server name error when registering Android application


The Android application displays an error when a user attempts to register with an
HCP Anywhere system in the .local domain (for example, an HCP Anywhere system
named hcpanywhere.local).

Workaround: Change the HCP Anywhere system name to include a different


domain.

AW-9299 List of NAS servers in Management Console is unresponsive


Each NAS server added to HCP Anywhere needs to have a corresponding computer
account in Active Directory. After the NAS server is added to HCP Anywhere, if the
service principal name for its computer account is changed, the list of NAS servers
on the File Sync and Share >Collaboration page fails to load.

Workaround: Change the service principal name for the computer account back
to its original name.

29
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-9312 Sharing a link can open the wrong version of the application
On a Mac, a user can install a new version of the HCP Anywhere application
alongside an older version, rather than replacing the old version. While in this state,
if the user shuts down the HCP Anywhere application and then uses the Services
menu to attempt to share a file or folder, the old version of the application may be
opened.

Workaround: Delete the old version of HCP Anywhere application.

This information has been added to the HCP Anywhere User Help.

AW-9374 Incorrect app icon displayed after upgrade


The desktop application icon was updated for release 2.0:

Old: New:

When a user upgrades the Windows desktop application to release 2.0, the user
may see the old version of the icon in these places:

Start menu

Task bar

Favorites menu in Windows Explorer

Workaround: To manually update the icon:

1. Right-click on the icon.

2. From the menu, click on Properties.

3. Click on the Change Icon button.

4. Select the new icon and click on the OK button.

AW-9422 App stops when the user tries to return to the Settings screen
From the Settings screen in the Android app, a user can access a number of
subscreens (for example, the License Information or Help screens). If the Don't
keep activities developer option is enabled for the device, when the user accesses
one of these subscreens and then attempts to return to the Settings screen, the
app stops running and displays this error message:

"Unfortunately, HCP Anywhere has stopped."

Workaround: Disable the Don't keep activities developer option for the device.

30
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-9496 Management Console does not displayany NASshares for a NAS server
When you add a NAS server to the File Sync and Share >Configuration
>Mobilized Data page in the Management Console, the page automatically
displays the shares that the server exposes to anonymous users. If the server has
several hundred of these shares, the page may not display any shares at all for the
server.

Workaround: Use the Add Share (Manually) button to add the shares you want.

AW-9681 User Portal is sometimes inaccessible through Google Chrome


The User Portal may become inaccessible through Google Chrome if the
HCPAnywhere system uses a self-signed SSL certificate.

This happens because Chrome does not permanently store security exceptions for
websites. When a user returns to the Portal and Chrome no longer has a security
exception for it, Chrome assumes that the Portal violates HTTP Strict Transport
Security (HSTS) rules and prevents the user from accessing it.

Workaround: Delete the HSTSentry for the HCP Anywhere system from Chrome:

1. In Google Chrome, go to chrome://net-internals/#hsts.

2. In the Delete domain section, enter the domain name for your HCP
Anywhere system and click on the Delete button.

When the user returns to the Portal, he or she is prompted to accept a security
exception. Upon accepting, the user can again access the Portal.

AW-10144 No option for converting file attachments to links when reply to or forwarding
an email
When replying to or forwarding an email, the option for converting a file
attachment to a link does not appear in the Outlook ribbon.

Workaround: Configure Outlook to open replies and forwards in a new window.To


do this:

1. In Outlook, click on the File tab.

2. From the list that appears, click on options.

3. From the window that appears, click on the Mail tab.

4. In the Replies and forwards section, select Open replies and forwards in
a new window.

5. Click on OK.

31
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-11663 Files with prohibited extensions not uploading when no longer prohibited
In release 2.1, administrators can prevent certain files from being uploaded into
HCP Anywhere by specifying prohibited file extensions. When a user tries to upload
a file with a prohibited extension, the file fails to upload to the server. Instead, the
file remains in the user's desktop client folder as an unsynced file.

With an application running version 2.1 of HCP Anywhere, the file automatically
uploads to the server when the file extension is no longer prohibited. However, with
a pre-2.1 application, the file does not automatically upload. Instead, the file
remains unsynced.

Workaround: To upload the file, do one of these:

Pause and then resume synchronization of the file on the desktop application.

Restart the desktop application.

AW-12506 Custom service principal names removed after upgrade or system failure
When an upgrade is applied to HCP Anywhere or HCP Anywhere experiences a
system failure, the Active Directory computer account which is joined toHCP
Anywhere is reset on the HCP Anywhere system. When HCP Anywhere resets the
Active Directory computer account, any custom service principal names (SPNs) are
removed from that computer account. This can prevent users from being able to
authenticate with the HCP Anywhere system

Workaround: Reset the SPNs on the AD computer account which is joined to HCP
Anwyhere.

AW-12510 Performing node recovery from a physical node to a virtualnode leaves system
in a broken state
When you perform a node recovery from a physical node to a virtual node or from a
virtual node to a physical node, the node is unable to come back online.

Workaround: To convert a physical system to a virtual system or a virtual system to


a physical system, you need to convert the entire system together instead of
converting one node at a time. If you want to convert a physical system to a virtual
system or vice versa, contact technical support for help.

32
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-13523 On a Windows computer, the desktop application folder or an item in the


desktop application folder cannot be opened, edited, or deleted
The desktop application allows you to choose which files are saved locally to your
computer and which files remain remotely in HCP Anywhere. When certain file
types are remote files, Windows may prevent the file from being opened, edited, or
deleted. For example, .iso files cannot be opened or mounted when they are
remotely in HCP Anywhere.

Workaround: To open, edit, or delete the file, you need to first save the file locally.
To save the file locally, do these:

1. Right-click on the file.

2. In the menu, click on Save locally.

AW-13685 Cannot upload file from desktop application using Windows Edge browser
The desktop application allows you to choose which files are saved locally to your
computer and which files remain remotely in HCP Anywhere. If you attempt to
upload a remote file through a Windows Edge browser, the upload fails.

Workaround: To upload the file through a Windows Edge browser, you need to first
save the file locally. To save the file locally, do these:

1. Right-click on the file.

2. In the menu, click on Save locally.

AW-14818 Desktop cannot create secure SSL/TLS channel


Prior to release 3.0, the desktop application connected to the HCP Anywhere
system using the default TLSversion configured in the WinHTTP registry key on the
Windows machine in which it was installed. On Windows 7, the WinHTTP registry
key is configured to use TLS1.0 by default. In release 3.0 of HCP Anywhere,
applications can only connect to the HCP Anywhere system using TLS1.2
connections. If an application attempts to connect to the HCP Anywhere system
using a TLS1.0 or 1.1 connection, the application fails to connect and a "could not
created secure SSL/TLS channel" error is displayed.

Workaround: This issue has a number of workarounds.For more information, see


"Impacts of upgrading" on page7.

33
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-14823 Outlook Add-in cannot create secure SSL/TLS channel


Prior to release 3.0, the Outlook Add-in connected to the HCP Anywhere system
using the default TLSversion configured in the .NET registry key on the Windows
machine in which it was installed. By default, the .NET registry key is configured to
use TLS1.0 on all Windows machines. In release 3.0 of HCP Anywhere, applications
can only connect to the HCP Anywhere system using TLS1.2 connections. If an
application attempts to connect to the HCP Anywhere system using a TLS1.0 or
1.1 connection, the application fails to connect and a "could not created secure
SSL/TLS channel" error is displayed.

Workaround: This issue has a number of workaround.For more information, see


"Impacts of upgrading" on page7.

AW-14976 Corrupted .zip file when .zip file contains an item with non-ASCII characters in
the name
When you download multiple files or folders, they are combined into a single .zip
file. If one of the files or folders in the .zip file contains non-ASCII characters in its
name, the .zip becomes corrupted.

Workaround: Download the files or folders again, but without the item containing
non-ASCIIcharacters in its name. You can also download the item that contains
non-ASCII characters in its name so long as the file is not included in a .zip file.

AW-15016 A member of a collaborative folder is being tracked as an individual instead of


as part of a group
When you invite a group to a collaborative folder, HCP Anywhere tracks the
members of the group for you. If someone is added to the group in Active Directory,
that person is also invited to the collaborative folder.

When you invite a person to a collaborative folder, that person is tracked as an


individual even if that person is also a member of a group in the folder. When
someone is tracked individually, they have the icon of a single person next to their
name in the Manage Shared Folder window. When someone is tracked as part of a
group, they have the icon of three people next to their name in the Manage Shared
Folder window.

Workaround: If a person is being tracked as an individual in a folder and you want


to track them as part of a group, you need to:

1. Remove that person from the folder.

2. Invite the group to the folder.

34
HCP Anywhere 3.0 Release Notes
Issues with workarounds

(Continued)

Ref. number Description

AW-15222 Team folder displayed twice in desktop application


In the desktop application, when you move a team folder into another collaborative
folder (shared or team), the team folder is moved to the root of HCP Anywhere if
you are the last manager of that team folder. This behavior is expected since there
must always be at least one manager in each team folder. However, when the
team folder is moved to the root of HCP Anywhere, a duplicate of the team folder is
left within the collaborative folder in which the team folder was moved. In the
duplicate filesystem, the files appear to be real but do not contain any data.

Workaround: Delete the duplicate filesystem.

AW-15359 iOS application not automatically opening upon registration


When you register the iOS application using a SAML authentication provider, the
application does not open automatically as the success message describes.

Workaround: Close the success message and open the HCP Anywhere application
manually.

AW-15425 Unable to delete files in a Windows Phone application older than release 3.0
When using a HCP Anywhere Windows Phone application older than release 3.0,
you cannot delete files in the Windows Phone application if the HCP Anywhere
system is at release 3.0 or later.

Workaround: Upgrade the Windows Phone application to release 3.0

35
HCP Anywhere 3.0 Release Notes
Other known issues

Other known issues


The table below lists known issues in the current release of HCP Anywhere
for which no workarounds exist. The issues are listed in order by reference
number.

Ref.
number Description

AW-3282 Folder fails to be deleted if it contains files that are currently being uploaded to
the HCPAnywhere system
In the following scenario, when a user attempts to delete a folder, files in the folder are
deleted but the folder itself remains:

1. The user creates a folder within the desktop application folder.

2. The user adds files to the newly created folder.

3. Before the newly added files finish synchronizing, the user deletes the folder.

AW-4471 Passcode lock requirements not enforced after restoring to a different device
A user can use Apple iTunes to back up and restore the contents of an Apple device.
After restoring those contents to a different Apple device, when the user downloads and
registers the HCP Anywhere app on the device, the user may be able to use the app
regardless of whether the device uses a weak passcode or no passcode at all.

AW-4619 Lowering file size limit deletes favorite files from device
When a user lowers the Maximum File Size setting, any favorite files that are larger
than the new setting are removed from the list of favorites and the local copies of the
files are deleted from the device.

AW-4667 Many concurrent requests for a large file can significantly slow file synchronization
If several hundred users attempt to access a single large file at the same time, the HCP
Anywhere system immediately services requests for these users. Requests for other
files made by a second set of users are queued until the system has finished with the
requests for the first set of users. File synchronization for the second set of users is
essentially paused during this period of time.

AW-4746 User is prompted twice to reauthenticate


While using the HCP Anywhere app on an Android device, the user is occasionally
prompted to reenter his or her password. While this prompt is visible, the user can exit
and then return to the app. Upon returning to the app, when the user enters his or her
password in the prompt, the prompt is incorrectly displayed a second time. The user
needs to enter his or her password a second time in order to continue using the app.

36
HCP Anywhere 3.0 Release Notes
Other known issues

(Continued)

Ref.
number Description

AW-4853 Stopping the app stops all file transactions


On an Android device, a user can stop an app by opening the list of active apps and then
swiping the app off the screen. When a user stops the HCP Anywhere app in this way, all
file uploads and downloads for the app are canceled.

AW-5224 Incorrect error when trying to accept a shared folder invitation


If a user has any desktop or mobile applications older than release 1.1, the user cannot
accept invitations to shared folders. If the user receives and clicks on a link to join a
shared folder, the User Portal displays an error message saying that the user does not
have permission to access the Portal. This is incorrect; the user has permission to
access the Portal, but cannot view or accept shared folder invitations until the user
upgrades all of his or her devices.

AW-5396 Desktop applications do not indicate loss of connection after system recovery
When HCP Anywhere comes back online after undergoing a system recovery, the
system synchronizes any file changes that occurred on user's desktop applications while
the system was down. If the desktop application loses connectivity during this process,
the application does not display the appropriate alerts.

AW-5957 HCP Anywhere connects to domain controllers that are not in whitelisted domains
When using both AD domain whitelisting and domain controller overrides, HCP
Anywhere will attempt to contact the domain controllers specified as overrides for
Global Services even if those controllers belong to domains that are not in the whitelist.

AW-6191 Misleading column header when viewing the access history of a file
In the User Portal, users can view the access history of a file in the History for file
window by using the Read access (shared links) and Read access (other) filters.When
viewing the access history of a file, there is a column called Modified.

The Modified column does not actually display the times when the file was
modified.Instead, the Modified column displays the times when the file was accessed.

AW-6212 Incorrect filenames sent to virus scanning servers


HCP Anywhere may send incorrect filenames to virus scanning servers. For example,
the file example.txt may be sent as %2Fexample.txt. In this case, if the virus
scanning server is configured to block any file called example.txt, the virus scanning
server receives an unexpected filename and does not block the file.

AW-6832 Possible upload failure when sending a file from another app
When you send a file to HCP Anywhere from another app, a notification may appear in
the Notification Drawer that says the upload failed. The file may or may not have been
uploaded successfully to the HCP Anywhere system. Whether or not this issue occurs
depends on the app from which you sent the file.

37
HCP Anywhere 3.0 Release Notes
Other known issues

(Continued)

Ref.
number Description

AW-8676 Failed uploads to mobilized data shares appear to succeed


A user can continue to use pre-2.0 desktop and mobile applications with an HCP
Anywhere system that's at release 2.0 or later. In this case, if the user has access to
mobilized data shares, the user cannot view or work with those shares with the out-of-
date applications.

In a pre-2.0 application, a user can create a folder with the same name as a mobilized
data share. The operation appears to be successful, but the folder is not actually created
or synchronized. This also occurs for any files that the user adds to the folder.

This information has been added to the HCP Anywhere User Help.

AW-9059 Path length restriction on Windows Phone


A user can store a file in HCP Anywhere that exceeds the Windows Phone path length
limit but not the HCP Anywhere path length limit. This means that the user cannot
download and view the file on his or her Windows Phone.

This information has been added to the HCP Anywhere User Help.

AW-9165 Successful file upload incorrectly reported as a failure


In this situation, HCP Anywhere incorrectly reports a successful file upload to a
mobilized data share as having failed:

1. A user uploads a large file into a folder in the share.

2. While the file is uploading, another user renames the folder.

This information has been added to the HCP Anywhere User Help.

AW-9355 Japanese text not displayed correctly in registration wizard


While the app language is set to Japanese, the text on the Cancel button in the
registration wizard is incorrectly truncated. This issue occurs only on Mac OSX 10.9.4.

AW-9433 No search results during audit of mobilized data share


While auditing a mobilized data share, an administrator can view any files the user adds
to the share. However, searches for files in the mobilized data share return no results.

AW-9584 Default sharing option is always public onWindows Phone


On a Windows Phone, public link sharing is always selected by default even if internal
link sharing has been set as the default on the HCP Anywhere Management Console.

AW-10111 Calendar files incorrectly converting to links


When converting a calender file (.ics) attachment to a link, HCP Anywhere converts
each image in the calendar file to its own separate link, instead of converting the
calender file to a single link.

38
HCP Anywhere 3.0 Release Notes
Other known issues

(Continued)

Ref.
number Description

AW-10907 User Portal not loading when using SAML as an identity provider
On Internet Explorer 8 and 9, identity providers configured to use POST redirection fail
to load the HCP Anywhere User Portal.

AW-11411 Incorrect user reported as uploading files to a folder shared using a link
When an administrator runs an ownedModifications audit report, the report incorrectly
returns information on files uploaded to folders shared using links. Instead of returning
the actual user who uploaded the file to the folder, the report displays that the file was
uploaded by the owner of the folder.

AW-11412 Incorrect information displayed in Management Console when new users register
using a desktop or mobile application
In release 2.1, new users can register their HCP Anywhere accounts through the User
Portal or any of the HCP Anywhere applications (the desktop client, mobile application,
or Outlook Add-in). On the Registered Users page in the Management Console,
administrators can view a user's registered devices.

When a new user registers an HCP Anywhere account using one of the applications, the
Registered Users page incorrectly shows that the user registered using both the User
Portal and the application.

AW-11995 Unable to download a folder that was shared via a link and has a number in its
name
When a user accesses a folder that has a number in its name and was shared via a link,
the user is unable to:

Download the entire folder at once

Copy the entire folder to HCP Anywhere

Copy individual files in the folder to HCP Anywhere.

The user is only able to download individual files in the folder.

AW-13734 Folder in the desktop application has the backup icon


The desktop application allows you to store files on the desktop application or back up
folders outside the desktop application. When you move a backup folder into the
desktop application, the folder incorrectly remains badged with the backup icon
although it is no longer being backed up.

AW-14180 All images uploaded to theUser Portal using an iPad at version 9.x are named
image.jpeg
On an iPad at version 9.x, the iPad names each image file image.jpeg. Consequently,
every image file uploaded to the User Portal from an iPad at version 9.x is named
image.jpeg in the User Portal.

39
HCP Anywhere 3.0 Release Notes
Other known issues

(Continued)

Ref.
number Description

AW-14276 HDI device not encrypting data


If an HDI device is older than version 5.2, the HDI device cannot create encrypted
filesystems even when the Enable encryption at rest option is selected in the HCP
Anywhere Management Console. When an HDI device older than version 5.2 is put into
service with the Enable encryption at rest option selected, that HDI fails to apply any
configuration changes from the HCP Anywhere system once the HDI device is upgraded
to version 5.2 or later.

If you have already put an HDI device older than version 5.2 into service with the
Enable encryption at rest option selected, contact technical support for help.

AW-14277 Login fails on BlackBerry device


Typically, when you log into a website for the first time, the browser stores your
username and password.Consequently, the next time you access the website, your
username and password is pre-filled into the login page for you.

If you attempt to log into the User Portal on a BlackBerry device with a username and
password that has been pre-filled into the login page, the login fails. To log into the User
Portal on a BlackBerry device, you need to manually enter your username and
password.

AW-14699 Group membership is not being updated


You can update the membership of groups in a collaborative folder using the Sync
membership button in the Manage Shared Folder window. This queries Active
Directory for any changes to the group membership.If changes are detected (for
example, a user was added or deleted from the group), those changes are made in the
collaborative folder. The Sync membership button does not update the collaborative
folder with any changes that have occurred in Active Directory within the 60 seconds
prior to clicking the button.

AW-15049 Text no longer displayed in correct language


In release 3.0, a number of languages are no longer supported. When you upgrade an
application that is configured with a language that is no longer supported, the display
language is changed to English.

40
HCP Anywhere 3.0 Release Notes
Other known issues

(Continued)

Ref.
number Description

AW-15098 Unable to register iOS application using SAML


The iOS application cannot be registered if all of the following are true:

The phone or tablet is running iOSversion 9.2.1.

You are being authenticated by a SAML identity provider.

You do not have an email configured for HCP Anywhere.

In this case, to register the iOSapplication, you need to upgrade the iOS version on the
phone or tablet.

AW-15143 In a collaborative folder, member roles are not changed when a group role is
changed
When you invite a group to a collaborative folder, HCP Anywhere tracks the group for
you. If someone is added to the group in Active Directory, that person is also invited to
the collaborative folder.

When the role of a group in a collaborative folder is changed, the roles of any existing
folder members of the group are not changed.The group role only applies to folder
members who are invited to the folder after the role has been set.

AW-15234 Cannot install or upgrade to version 3.0 of the desktop application on 32-bit
Windows machine
Release 3.0 of the Windows desktop application does support 32-bit Windows machines.
If you attempt to install the desktop application on a 32-bit Windows machine, the
installation fails. If you attempt to upgrade an older desktop application to release 3.0
on a 32-bit machine:

The upgrade fails.

An upgrade prompt is displayed every time your authentication token for the
desktop application expires. By default, authentication tokens for the desktop
application expire every 7 days.However, this expiration time can be adjusted in
the HCP Anywhere Management Console.

In both the installation and upgrade scenarios, the failure message describes that 32-
bit machines are not supported.

AW-15441 Look UP option is still available when copy and paste is disabled for the MobileIron
wrapped iOS application
When you disabled copy and paste operations in the MobileIron administrator portal,
users can still use the Look UP option in the MobileIron wrapped iOS applicatioin. The
Look UP option copies any highlighted text into a web browser. This is a known
MobileIron issue, not an HCP Anywhere issue.

41
HCP Anywhere 3.0 Release Notes
Getting help

(Continued)

Ref.
number Description

AW-15521 Cannot register HCP Anywhere iOS application when iOSdevice is running version
10.3 and HCP Anywhere server is using a self-signed certificate
The HCP Anywhere iOSapplication cannot be registered if both of the following are true:

The iOSdevice on which the application is installed is running version 10.3

The HCP Anywhere server is using a self-signed certificate

Getting help
Hitachi Data Systems Support Portal is the destination for technical
support of products and solutions sold by Hitachi Data Systems. To contact
technical support, log on to Hitachi Data Systems Support Connect for
contact information: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDS


customers, partners, independent software vendors, employees, and
prospects. It is the destination to get answers, discover insights, and make
connections. Join the conversation today! Go to community.hds.com,
register, and complete your profile.

Comments
Please send us your comments on this document:

HCPAnywhereDocumentationFeedback@hds.com

Include the document title and part number, including the revision (for
example, -01), and refer to specific sections and paragraphs whenever
possible. All comments become the property of Hitachi Data Systems.

Thank you!

42
HCP Anywhere 3.0 Release Notes
HCP Anywhere 3.0 Release Notes
Hitachi Data Systems

Corporate Headquarters
2845 Lafayette Street
Santa Clara, California 95050-2627
U.S.A.
www.hds.com

Regional Contact Information

Americas
+1 408 970 1000
info@hds.com

Europe, Middle East, and Africa


+44 (0) 1753 618000
info.emea@hds.com

Asia Pacific
+852 3189 7900
hds.marketing.apac@hds.com

RN-HCPAW003-15