Poor email client performance is one of several serious problems that has prevented enterprises from fully adopting non-persistent virtual desktop models. Performance issues in email include long lag times and hanging while downloading and opening emails, time-outs when opening calendar items, and extremely slow response while inbox searching. For administrators, the various workarounds to this problem can result in dramatically increased server utilization, increased cost, and ongoing poor and inconsistent performance for end users.
This FAQ addresses the use of Profile Containers to enable Cached Exchange Mode in non-persistent (pooled) VDI, RDSH and XenApp. In general, this approach covers both internally managed Exchange, as well as externally hosted Exchange through 3rd party providers and through Microsoft, via Office 365 subscriptions of hosted Exchange for Business.
FSLogix Apps Profile Containers move the entire User Profile, including the registry, to an in-guest container, which appears to be fully integrated with the local system. This approach completely eliminates the need for Folder Redirection or other network-share based workarounds which can generate saturated server work queues and network links during boot storms caused by large numbers of users simultaneously logging on during peak periods of a normal work day. User email performance is returned to ‘normal’, or indistinguishable from running Outlook in a well-optimized local computing environment.