FSLogix Per-Host Pool Customization

You can configure FSLogix with Nerdio Manager and apply its settings to each host pool in the AVD 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 customized FSLogix settings for a host pool:

1. Navigate to the list of host pools and locate the host pool you wish to change.

2. From the action menu, select Properties > FSLogix.

3. 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.

   • Profile: From the drop-down list, select an existing profile name. Alternatively, select Custom to create a custom profile for this host pool.

   • Version From the drop-down list, select the FSLogix version.

   • Use Cloud Cache: Select this option to enable FSLogix Cloud Cache.

     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 article 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: If Cloud Cache is enabled, select this option to use storage account blob containers to store user 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 article for more information.

   • Exclude the local admin accounts from FSLogix: Select this option to prevent local admins profiles creation in FSLogix storage location.

     Note: When FSLogix is having issues on a session host, there is still a way to sign in with an excluded user for troubleshooting purposes.

   • Manage App Service settings: Select this option to to edit the FSLogix App Service Registry settings.

     

   • Manage Log settings: Select this option to manage log settings.

     

   • FSLogix Profiles path (CCDLocation): From the drop-down list, select an Azure Files share. 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: From the drop-down list, select whether you want to work with All settings or Advanced.

     • For All settings:

       

       • In the Configuration column, type the setting's value.

       • Select Clear to set a specific setting to Not configured.

       • Select Clear all to set all the settings to Not configured.

     • For Advanced:

       • You can add DWORD values in the format: "ValueName":dword:ValueData (example: "ProfileType"=dword:00000003).

       • You can add string values in the format: "ValueName":"ValueData" (example: "VolumeType":"vhdx").

   • 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.

   • Redirections: Select this option if you want to include Redirections in the global profile for re-use across customers.

     Note: See this Microsoft article for more information about redirections.

   • 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.

4. Once you have entered all the desired information, select Save or Save & close.

Related topics

Host Pools

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.