Overview of features and architecture of Syncplicity Panorama for accessing Network Shares, Home Drives, and SharePoint Libraries.
Next in Series:
About this presentation:
Syncplicity Panorama enables user to access content that lives in SharePoint, Network Shares, and Home Drives. The Syncplicity Mobile app allows you to toggle between content stored in Syncplicity, SharePoint Content, and content within Network Shares and Home drives. Content that is approved for mobile access is exposed through bookmarks. Content not approved for mobile access is not exposed.
Navigation through the site is the same experience you get in Syncplicity, and all of the content within the site is displayed and accessible. SharePoint content can be checked out which of course locks the content natively in SharePoint. Files can be modified using the native editors built into the Syncplicity mobile clients, and can then be checked back in. Files can also be favorited which means a local copy is stored on within the secure container on your mobile device for offline access. Files can be accessed outside of the secure container using the devices “open in” functionality if not disabled by Syncplicity policy. All Syncplicity policies are respected for SharePoint content and Network Access.
Authentication is managed through a token stored on the mobile device, AD credentials are not stored.
The Connector is installed on a Windows Server 2013 R2 and above, which should reside in your corporate network, either in the DMZ or semi-private tier.
The Connector has the following connections:
- Syncplicity mobile users access the Connector over HTTPS via a load balancer.
- The Connector accesses the SharePoint servers over HTTP or HTTPS.
- The Connector accesses Network Shares over SMB
- The Connector local administrators manage the Connector by accessing the administration portal over HTTPS.
There should be firewalls between the Connector and the various network boundaries.
The Connector itself does not require any special settings if using a load balancer. However, the load balancer should be configured to use sticky sessions, also known as session affinity.
Also, you should install only one instance of the Connector per server.