Using FSLogix Cloud Cache for Office 365 deployments

Posted by Brandon Lee on Sep 18, 2018 12:19:09 PM

Office 365 adoption is growing at an unprecedented rate. As organizations make the transition to Office 365, they inevitably encounter some pitfalls associated with enabling all of the functionality and performance of applications such as Outlook.

The below is an excerpt from Theresa Miller's, What FSLogix Cloud Cache can do for you Office 365 deployment:

The Problem with Outlook when used in VDI

We already know that Outlook can perform slowly in VDI virtual machines, and if your organization is like many others, this is unacceptable and must be fixed. However, the real problem is that the OST (aka – Cache Mode) file can’t roam with the user using traditional means like Folder Redirection or Roaming Profiles. We NEED cached Exchange mode when using Office 365 to deliver a good user experience, but there just isn’t a good way to get it to work without considering 3rd party applications.

Improving the User Experience with Cloud Cache

Cloud Cache is a new capability within FSLogix Profile and Office 365 Container that introduces high availability for containers and extends resiliency within the FSLogix toolset. Imagine that your Office 365 connection to Exchange online drops. The user experience would be that Outlook connectivity to real-time data can cease to function. Similar problems would be seen for network interruptions to Office 365 data for other Microsoft cloud offerings as well. So, how can Cloud Cache help here?

Cloud Cache adds two critical elements to your FSLogix deployment:

  1. A truly local copy of any Office 365 (or Profile) data users have accessed – As you access data from your remote container, that data is stored in a local cache. This happens at the block level, so it’s not caching the entire OST file, for example, only the blocks that have been requested. The cache can be configured to build over time, building towards a complete local cache over time, or to clear at logoff. Any desktop (physical, persistent or non-persistent VDI, or RDSH) can benefit from this because it ensures that, should that data be required during an outage, applications continue to function.
  2. The option to have a failover copy of the Office 365 or Profile containers in any location, even the cloud Cloud Cache also includes the ability to store users’ Office 365 or Profile Containers in multiple locations at the same time, even in the cloud via native storage APIs. Cloud Cache will write to all configured locations but will only read from a primary location. If that location becomes unavailable, Cloud Cache connects to another location. When the original location comes back online, Cloud Cache will ensure it is up to date and switch back to using it as the primary. Using native cloud storage APIs saves money when compared to cloud-based SMB storage offerings and being able to place user data in any location on-premises or in the cloud gives you the ability to deliver high availability and disaster recovery without having to deploy expensive or complex hardware-based solutions.

Read the full article from Theresa Miller at 24x7itconnection

Topics: Office 365, Outlook, Cloud Cache, VDI

Subscribe to Email Updates

Recent Posts

Posts by Topic

see all

Follow Me