Sectors - SharePoint

Microsoft SharePoint has seen massive adoption and it is a powerful enabler for collaborative working.  With its totally customizable appearance, extensibility, rich security model and support for workflow, documents and records management, it’s the natural choice for a Microsoft-centric enterprise.  But a SharePoint deployment can only succeed if the users embrace it, and the main barrier to adoption is the user experience for remote workers.  SharePoint collaboration is ultimately founded on users sharing and updating documents and that will only happen if the sharing doesn’t get in the way of their day jobs. SharePoint works very well in a LAN environment but over a WAN users can experience long upload and download times and then choose to abandon sharing in favour of keeping their own local, and outdated, copies of documents, and fail to add their new or updated versions to the common pool.  Replify Accelerator can remove this performance barrier.

The users would not have accepted SharePoint without Replify.

Mark Baxter of Mivan

Microsoft’s Business Productivity On-line Suite (BPOS) is a very attractive and cost-effective alternative to in-house deployment of Exchange and SharePoint, but putting SharePoint “in the cloud” does introduce WAN performance challenges.  We’ve demonstrated that Replify Accelerator can be deployed alongside BPOS to reduce or eliminate the problems. Combined with Replify Syncstor, to provide seamless off-line working while on the move, Replify delivers the best possible SharePoint experience.

Features and Benefits

• Tight integration with SharePoint – add document libraries to your Syncstor offline repositories with one click.
• Acceleration for HTTP,  HTTPS and File transfer – all interactions with SharePoint are accelerated and enhanced by Replify Accelerator.
• Resume interrupted downloads – because content is learned as it passes, even if the network fails and your file transfer is broken, it will quickly recover and pick up from where it left off if you try again.
• Offline working – even when the network isn’t there, your document libraries still are. Work on them locally but maintain synchronization with the central repositories and other users with minimal bandwidth demands.