Automated FSLogix Deployment and Per-Host Pool Customization
You can configure FSLogix with Nerdio Manager and apply its settings to each host pool in the WVD Deployment.
For more information refer to Host Pools.
Adding a server includes installing FSLogix and applying the necessary settings that were selected for the host pool. You can use the global default settings or customize the settings for each host pool.
To configure global settings for FSLogix:
Note: FSLogix settings configured here are automatically installed and fully deployed to any newly created host pools.
-
Navigate to Settings > Integrations.
-
In the FSLogix Profiles storage tile, locate the profile you want to use as the default.
-
Select set default, if it isn't already the default.
-
Select the profile and enter the following information:
-
Name: Type the profile's name.
-
Use Cloud Cache: Select this option to enable FSLogix Cloud Cache in the host pools, and the session hosts within those host pools, that use this FSLogix profile.
Tip: For performance reasons, it is strongly recommended that you use Premium SSD and Ephemeral OS disks when Cloud Cache is enabled. (Standard SSD disks might be sufficient in very small environments or a testing scenarios.)
Note: See the following Microsoft document for more information about FSLogix Cloud Cache.
Cloud Cache allows you to specify multiple profile storage location. It asynchronously replicates the profiles and makes the profiles available in multiple storage locations at the same time. So, if one of the locations is not available, the session host automatically fails over to one of the alternate locations.
-
Use Azure page blobs: Select this option to use storage account blob containers to store users profiles. These containers are accessed using storage account access keys.
-
Configure session hosts registry for Entra ID joined storage: Select this option to enable Entra ID Kerberos functionality and Entra ID account credentials loading.
Note: See this Microsoft document for more information.
-
FSLogix Profiles path: From the drop-down list, select an Azure Files share or Azure NetApp Files volumes. Alternatively, type in a UNC path.
Note: You can specify up to 4 paths. In addition, use the arrows to change the order of the paths. The profiles are created in all of these locations.
-
FSLogix Registry Options: Type the FSLogix configuration that is applied when a session host VM is provisioned and FSLogix is installed.
-
Edit mode: From the drop-down list, select the edit mode.
Note: Select all settings to edit in "simple" mode, removing the need to configure registry settings individually. Select Advanced to configure the registry settings as usual.
-
-
Force the installation of FSLogix apps even if already installed: Select this option to force the reinstallation of the FSLogix agent and applications.
-
-
Once you have entered all the desired information, select OK.
To configure customized FSLogix settings for a host pool:
Note: Any settings configured here are applied only to newly created or re-imaged hosts in this pool.
-
Navigate to the list of host pools and locate the host pool you wish to change.
-
From the action menu, select Properties > FSLogix.
-
Enter the following information:
-
Toggle Use FSLogix profiles to On.
Note: If this option is not enabled, Nerdio Manager does not install the FSLogix profile container application on newly created VMs when they are deployed in this host pool. Existing VMs are not affected.
-
FSLogix profile: From the drop-down list, select the FSLogix profile to use.
-
Use Cloud Cache: Select this option to enable FSLogix Cloud Cache.
-
FSLogix Profile path: Modify as needed.
-
FSLogix Registry Options: Modify as needed.
-
Edit mode: From the drop-down list, select the edit mode.
Note: Select all settings to edit in "simple" mode, removing the need to configure registry settings individually. Select Advanced to configure the registry settings as usual.
-
-
Configure Office Container to redirect Microsoft Officer user data: Toggle on this option to redirect only areas of the profile that are specific to Microsoft Office.
Note: Office Containers separate Microsoft Office data (for example, OST files) from the overall user profile for easier troubleshooting. Office Containers and Profile Containers are stored in separate VHDX files can be stored on different file shares. See this Microsoft article for details.
-
FSLogix Office Container path (VHDLocation): Modify as needed.
-
FSLogix Office Container Registry Options: Modify as needed.
-
-
Force the installation of FSLogix apps even if already installed: Select this option to force the reinstallation of the FSLogix agent and applications.
-
Apply to existing hosts: Select this option to apply these changes to existing hosts. Otherwise, the change only effect new or re-imaged hosts.
-
Process hosts in groups of: Type the number of concurrent actions to execute during this bulk operation.
-
Number of failures before aborting: Type the number of failures that causes the process to stop.
-
Messaging: Toggle on the Messaging to send messages to active users.
-
Delay: From the drop-down list, select the number of minutes to wait after sending the message before starting the process.
-
Message: Type the message you want to send to the users.
-
-
Schedule: Toggle on the Schedule to apply the changes at a selected time.
- Start Date: Type the date to start.
-
Time Zone: From the drop-down list, select the time zone for the Start time.
-
Start Time: From the drop-down lists, select the time to start.
-
Repeat: From the drop-down list, select the recurring schedule, if desired.
Note: The drop-down has the option After Patch Tuesday. This allows you to create a recurring schedule based on Patch Tuesday.
-
Days After: If you selected After Patch Tuesday, type the number of days after Patch Tuesday to run the scheduled task.
-
-
-
-
Once you have entered all the desired information, select Save or Save & close.
Host Pool Disaster Recovery: You can enable host pool level active/active DR configuration and Nerdio Manager automatically distributes session hosts across two Azure regions. Users are distributed across VMs in both regions as they sign in and FSLogix profiles are automatically replicated using Cloud Cache. In case of an Azure region failure users continue to access VMs in the available region. See this demo for more information.