The role of the FSLogix agent and the container is to be transparent to applications running in the user session. Additionally, we may have implementing specific configurations to keep profile sizes small, most of which involve redirecting folders to the network. Consider Citrix Profile Management where we attempt to manage the smallest profile possible to strive for consistent login speeds by redirecting user folders to the network and set a complex set of include and exclude locations to simulate a persistent desktop experience. This is a different approach to traditional profile management. Simplifies administration because we no longer need to deal with setting a full list of inclusions and exclusions for profile roaming.Enables application features that don’t work well in virtualised and non-persistent desktop environments by fooling applications into seeing the profile on a local disk.Improves performance by reducing the IO to the file server hosting user profiles.This enhances user experience by improving performance and enables applications or features that are challenging with traditional approaches. Why ContainersĪ profile container (Profile Container or Office Container) will capture the user’s entire profile in a virtual disk and attach the disk to their target VM making the entire profile available at login. This article sets out approaches and considerations for keeping profile sizes in check to help avoid storage capacity headaches. Profile containers have gone mainstream with the Microsoft acquisition of FSLogix, making Profile Container and Office Container available to practically everyone. A container approach to profiles in your virtual desktop environment means you’re going to deal with additional storage requirements that you likely haven’t had previously.

Microsoft office 15 sync maintenance