Release Notes. CTERA Portal 4.1. July CTERA Portal 4.1 Release Notes 1

Transcription

1 Release Notes CTERA Portal 4.1 July 2014 CTERA Portal 4.1 Release Notes 1

2 1 Release Contents Copyright CTERA Networks Ltd. All rights reserved. No part of this document may be reproduced in any form or by any means without written permission from CTERA Network Ltd. Information in this document is subject to change without notice and does not represent a commitment on part of CTERA Networks Ltd. CTERA, C200, C400, C800, P1200, CloudPlug, NEXT3, Cloud Attached Storage, and Virtual Cloud Drive are trademarks, service marks, or registered trademarks of CTERA Networks Ltd. All other product names mentioned herein are trademarks or registered trademarks of their respective owners. The products described in this document are protected by U.S. patents, foreign patents, or pending applications. 2 CTERA Portal 4.1 Release Notes

3 1 Release Contents About This Release CTERA Portal 4.1 includes the following highlights: Personal and Project folders Multi-folder synchronization New notifications Storage pool monitoring on Linux Enhanced NFS-based seeding import and export Remote wiping of CTERA Mobile devices SMS-based authentication for invitations Support for UPN when working with Active Directory Disable HTTPS redirection for portal Web access Prevent portal administrators from accessing gateway files End User Portal displays last-viewed tab upon login Enhanced performance when using WebDAV Support for Portuguese in the Web interface Support for EMC ViPR backend storage node Personal and Project Folders In previous versions of CTERA Portal, cloud drive consisted of a single home folder per user and multiple project folders. In contrast, in CTERA Portal 4.1 there are multiple personal folders and multiple project folders. The home folder is a type of a personal folder that is automatically created along with the user. Personal folders can be shared with other users, like project folders. They can also be converted to project folders by users who have the Project management permission. CTERA Portal 4.1 Release Notes 3

4 1 Release Contents The differences between project folders and personal folders are: Personal folders appear under their owner s private namespace and can have any name. In contrast, each project folder must have a unique name, and they appear in the /projects namespace. Personal folders are intended for storing the personal files of a specific team member. The user can share their personal folders with others on an ad-hoc basis, but their personal folders appear under their own name in recipients shared with me subfolder (for example, \shared with me\joe Smith\expenses). In contrast, project folders are intended for storing team-wide projects that are not associated solely with a specific user (for example, \projects\marketing). Personal folders are supported in both reseller and team portals. In contrast, project folders are supported only in team portals. Here is an example of the Cloud Drive folder structure: \myfiles \myfolder9 4 CTERA Portal 4.1 Release Notes

5 Release Contents 1 \my-nice-folder \projects\public \projects\marketing \shared with me\joe Smith\expenses \shared with me\joe Smith\photos \users\joe Smith\myfiles \users\joe Smith\backups The first three folders are personal folders belonging to the user whose Cloud Drive this is. Folders starting with \projects are project folders. For example, \projects\public is a project folder. Folders starting with \shared with me\username are personal folders that were shared by username. For example, \shared with me\joe Smith\mypersonalfolder1 is a personal folder called mypersonalfolder1, and it was shared by Joe Smith. Folders starting with \users\username are personal folders that belong to team members. For example, \users\joe Smith\myfiles is a personal folder that belongs to Joe Smith. Only team administrators can see personal folders belonging to team members. Tip Note: Upon upgrading the CTERA Portal from 4.0 to 4.1, quick access folders are migrated to project folders. Quick access folders are no longer supported. Note: The folder names shared with me and projects are configurable in the virtual portal settings. The folder name myfiles, which is the default name for users home folders, is also configurable. CTERA Portal 4.1 Release Notes 5

6 1 Release Contents Multi-folder Synchronization Devices can now synchronize multiple folders to the CTERA Portal in parallel. Synced folders can be centrally managed via configuration templates on the CTERA Portal. If a folder is managed by a configuration template, the end user cannot override the folder s configuration locally. As part of configuration templates, the administrator can select any number of Cloud Drive folders to sync, as well as exclude specific subfolders if desired. 6 CTERA Portal 4.1 Release Notes

7 Release Contents 1 By default, all the folders are synced to the Cloud Drive folder on the device; however, this can be overridden on a per-folder basis, by clicking on the desired folder and choosing Sync to alternate local folder. The alternate local folder supports environment variables. For example, you can choose to sync a folder to $MYDOCUMENTS. CTERA Portal 4.1 Release Notes 7

8 1 Release Contents New Notifications CTERA Portal 4.1 includes a number of new notifications that can be sent to end users And to global administrators 8 CTERA Portal 4.1 Release Notes

9 Release Contents 1 Storage Pool Monitoring on Linux Storage pool monitoring is now supported also in Linux-based installations (in addition to Nexenta based installations). CTERA Portal 4.1 Release Notes 9

10 1 Release Contents Enhanced NFS-based Seeding Import and Export CTERA Portal 4.1 includes the following enhancements to NFS-based seeding import and export: Ability to specify which user roles can perform seeding import and export Allow the person performing seeding to use only authorized NFS servers (seeding stations) that are specified in a list configured by the global administrator. Remote Wipe CTERA Portal 4.1 supports the remote wiping of CTERA Mobile devices. Remote wipe causes the device to log out and to erase all locally synced files. In addition, the wiped device s key is invalidated. Once remote wipe has been activated through the CTERA Portal, wiping commences as soon as the device comes online. The console enables administrators to easily see how many devices are configured to be wiped and how many have completed the wipe procedure. An notification is sent to the administrator who initiated the wipe procedure, once remote wipe has completed. Only administrators with the Allow remote wipe for devices permission in their role may perform remote wipe. By default, this permission is selected for all the administrator roles except for the Read Only Administrator role. 10 CTERA Portal 4.1 Release Notes

11 Release Contents 1 CTERA Portal 4.1 Release Notes 11

12 1 Release Contents SMS-based Authentication for Guest Invitations The previous CTERA Portal version supported -based authentication for guest invitations. In addition to requiring recipients to authenticate to the CTERA Portal, it was possible to send them a random, 6-digit numeric passcode via , which they must enter in order to access the shared file/folder. CTERA Portal 4.1 supports sending the passcode via SMS, as well. To enable SMS-based authentication, a CTERA Portal global administrator visits the Global Administration View s Settings > Messaging page and selects Enable SMS Messaging. Support for UPN When Working with Active Directory When logging in, the user can now specify the Active Directory UPN attribute or the samaccountname attribute as their username. Previous versions allowed only logging in using the samaccountname attribute. 12 CTERA Portal 4.1 Release Notes

13 Release Contents 1 Disable HTTPS Redirection for Portal Web Access CTERA Portal now allows disabling the automatic redirection of users from HTTP to HTTPS. This is useful, for example, when running the CTERA Portal server behind an external SSLtermination device, such as a HTTPS load balancer. Prevent Portal Administrators from Accessing Gateway Files Portal administrators must now have "Access User Files" permissions, in order to access gateways files via SSO. End User Portal Displays Last-viewed Tab Upon Login The CTERA End User Portal now remembers the last tab that the user viewed. The next time the user logs in, the CTERA End User Portal will display the same tab, (whether the Cloud Drive, Backups, or Administration tab). Enhanced Performance When Using WebDAV The CTERA Portal now provides enhanced performance when using the WebDAV protocol to read or write files. Support for Portuguese in the Web Interface The CTERA Portal Web interface now supports Portuguese. Support for EMC ViPR Backend Storage Node The CTERA Portal now supports EMC ViPR software-defined storage as a backend storage node. CTERA Portal 4.1 Release Notes 13

14 1 Release Contents 14 CTERA Portal 4.1 Release Notes