New Features

Storage Sync is better than ever! We’ve made some exciting changes based on your feedback and can’t wait for you to check out these new features.  

  • Storage Sync and Terminal Server 
    Storage Sync can be accessed from users logging in to a remote desktop session hosted in a Terminal Server environment.  One example that works well involves users logging into a remote desktop session that need to access a variety of applications and resources from their remote session including Storage Sync.  This release allows a Terminal Server, multi-user connection into Storage Sync where each user can map the Egnyte Storage Sync share.  As each user maps their own Storage Sync share, they can access the folders that they've been given permissions.

  • Multipipe sync enabled by default
    Multipipe sync will be enabled in 11.3.0 by default.

Key Issues Addressed

The following issues are addressed in the 11.3.0 release and include:

  • A fix for an SSL Certificate Renewal issue
  • An extension to an Active Directory Join Timeout 
  • A fix to strengthen SSH Security
  • A fix to retain a previous usermap during a user mapping exception
  • An update to samba libraries that addresses local file locks


How To Upgrade

From Storage Sync version 11.1.3, 11.1.4, 11.1.5, 11.2.x:

  • Orchestrator will automatically update the Storage Sync packages
  • If the manual upgrade is set for Storage Sync, please access the Storage Sync UI to perform the upgrade.  

From Storage Sync version 11.1.1: 

  • SSH to the device as egnyteservice and switch users via sudo.
  • Execute the command "yum upgrade orchestrator" 
  • This will upgrade Storage Sync orchestrator, which will then perform the upgrade to 11.3.0
  • If you have enabled Manual Upgrade for Storage Sync, please access the Storage Sync UI to perform the upgrade. 

Run "yum" only in this particular case (from 11.1.1)!

From Storage Sync versions 11.0.x and 10.3.3:

  • Download the Storage Sync 11.3.0 OVA from the helpdesk
  • Perform a sync on 10.x or 11.0 VM to ensure data on disk is up to date
  • Turn off the VM
  • If possible, take a VM snapshot of the production VM to ensure we have a backup copy of the data disk [optional]
  • Migrate data disk(s) to newly deployed 11.3.0 VM
  • Turn on the 11.3.0 VM and follow installation steps on UI