Using FSLogix Office 365 Container for Outlook Search in Non-Persistent RDS Environments
When Outlook is running in cached Exchange mode, Outlook data is stored in user-specific .OST files. These .OST files must follow the users as they roam from host to host. Windows Search Service indexes locally stored .OST files and creates an index catalog for each user to enable search functionality in Outlook. In non-persistent and load-balanced Remote Desktop Service environments, the index catalog doesn’t roam with user data. As a consequence, the index catalog must be rebuilt every time the user logs in and the Connection Broker send him or her to a new pooled desktop or a different RD Session Host within a Collection. FSLogix’s Office 365 Container was designed to solve this issue by roaming a user’s Outlook data as well as their search index catalog in such a way that it is compatible to the Windows Search Service. This enables users to search in Outlook while they are accessing their emails. But how good is this solution?
RDS Gurus has written about FSLogix before, for example here. Now RDS Gurus has cranked up their benchmarking lab and conducted a thorough test with the goal to illustrate the user experience of remote desktop users while they are searching their Outlook mailboxes in an RDS environment. Two different settings were configured, one using FSLogix Office 365 Containers and another using native RDS User Profile Disk (UPD) technology. The primary focus was to measure how performance degrades when multiple users are simultaneously searching Outlook (“noisy neighbor effect”). Here is a summary of the results:User experience is similar if Outlook is indexed. While there are some differences in the resource consumption between UPD and FSLogix technologies (this is more evident through performance counter logs and graphing), the user experience for users using UPD and using FSLogix is very similar if the user’s Outlook is indexed.
Read the entire article here, Using FSLogix Office 365 Container for Outlook Search in Non-Persistent RDS Environments
via Dr. Benny Tritsch at drtritsch.com