Instantly delivering applications to users can be a challenge, as even FlexApps can take some time to activate. For instance, it may take 14 seconds for 15 FlexApps to become available. This can cause users to log in to their desktops before the application shortcuts for all 15 apps are ready to use.
To address this issue, we’ve introduced FlexApps on boot. However, the current implementation of FlexApps on boot has a small drawback: all FlexApps on boot are visible to all users logging in to the RDS host or desktop pool. This necessitates creating multiple pools to segment applications that are layered on boot. While this reduces image management, it increases the number of pools to manage, even if they come from the same image.
But with ProfileUnity FlexApp 6.8.5, we have new technology that solves both image sprawl and pool sprawl. When you assign FlexApps on boot, you now have the option to cloak the FlexApps that a user is not entitled to at login. For instance, if you have two apps on boot, one for accounting and the other for marketing, both apps are layered into the OS on boot, so users don’t have to wait for layering to occur. During login, however, the marketing user won’t be able to see the accounting app, and vice versa.
In addition, we offer predictive block caching. FlexApps are typically streamed over the network, but it’s sometimes better to run the app from our block cache to speed up the user experience. However, downloading all the needed blocks can take time. With predictive block caching, we know what blocks are needed to achieve near-native speeds, eliminating the need to download all blocks while the user waits.
To summarize, we remove activation times (FlexApps on boot), launch times (block caching), download times (predictive block caching), reduce image management (using FlexApps), and reduce pools (FlexApps on boot with cloaking).
To accomplish this, first set up ProfileUnity as a Service. then enable the “Enable Cloaking for on-boot FlexApps” checkbox in ProfileUnity FlexApp 6.8.5 when assigning FlexApps on boot. Then, in the normal login configuration, assign the relevant on-boot FlexApps to the appropriate users. This will ensure that users only have access to the applications they need, while reducing image sprawl and pool sprawl.
Overall, this approach simplifies application delivery and management while improving the user experience. Users can log in quickly and seamlessly access the applications they need, without being burdened by unnecessary apps or activation times.
You must log in to post a comment.