FSLogix provides innovative solutions that solve the "last-mile" problems to the adoption of non-persistent desktop computing. Our products are the best, and often the only, solutions to providing a native "persistent" desktop experience for users in a non-persistent environment.
In addition to providing the best performing end user computing environment, FSLogix also reduces management costs, simplifies the computing infrastructure, improves compatibility, all while reducing load on computing, network, and file server resources.
FSLogix Versions Supported by This Documentation
Unless specifically noted, all features and configuration settings described in this documentation are available in FSLogix Apps version 2.8.10 and later.
This feature allows an administrator to control what applications users have access to. In addition to full applications, administrators can also control visibility to printers, fonts, Office add-ins, Internet Explorer plug-ins, etc.
This masking technology also works to control access to particular Java versions. Because this is such a powerful use case, it has been broken out into its own feature set: Java Version Control.
User specific access to applications has traditionally been controlled by using Application Virtualization products (e.g. AppV), products that limit the ability to launch specified applications (e.g. AppLocker), or by creating and managing Server silos. FSLogix introduces a new approach. Simply install the applications normally and then control the user access by completely hiding the application at run-time for users who should not have access. This reduces the number of OS images that must be managed since there is no requirement to have separate images with specific sets of applications. Also, since no work is being done by the system when the application is being used, applications run at native speed and don't use any more computing resources (CPU, RAM, etc.).
This feature is specially designed to roam profiles in remote computing environments (e.g. Citrix, VDI, etc.). Because of this, it is a simpler design and greatly out-performs existing roaming profile solutions.
It accomplishes this by allowing the complete user profile to be stored in a single container. At logon, the container is dynamically attached to the computing environment using native, in-guest VHD/VHDX Microsoft services. The user's profile is then immediately available and appears to the system exactly like a native user profile. Traditionally hard problems for roaming profile solutions (like OST files) are elegantly handled and the user experience when accessing these files is comparable to native speeds.
This feature solves the problems that exist when using Microsoft Office in a roaming profile environment. Users experience fast email, fast searching, fast access to OneDrive files, etc.
The difference is that only Microsoft Office 365 data and the search index are stored in the container vs the whole user profile. This solution should be used in place of Profile Containers where a solution is already in place to manage the user profile. This feature easily layers over any existing profile solution.
This feature is used to control which version of Java particular applications or webpages should use.
It is common in large computing environments to have web pages or Java applications that only work with a specific version of Java. Normally Java requires that all applications and web pages use the latest version of Java that is installed on the local computer, thus breaking the application or web page that requires an older version. FSLogix allows an admin to specify with a policy the version of Java to be used with a specific application or web page. This is seamless to the end user.
FSLogix YouTube Channel: https://www.youtube.com/c/fslogix
FSLogix Facebook Page: https://www.facebook.com/fslogix/
FSLogix on Twitter: https://twitter.com/fslogix
New product releases are announced in the FSLogix Product Forum