FSLogix

Supported FSLogix releases

Parallels RAS has been tested with FSLogix releases up to and including release 2210 hotfix 2.

Configure installation method

Before you configure FSLogix for a specific server or a template (described later in this guide), you need to configure the FSLogix installation method on the Site level as follows:

  1. Navigate to Farm > Site > Settings and select the Features tab. Here you need to select a method that Parallels RAS will use to install FSLogix on individual hosts. You can select from one of the following:
    • Install manually: Select this option if you want to install FSLogix on every host yourself. If this option is selected, Parallels RAS will not attempt to install FSLogix on a host.
    • Install online: This option installs FSLogix on session hosts from the Internet. Select one of the supported FSLogix versions from the drop-down list or select Custom URL and specify a download URL. Click the Detect latest button to automatically obtain a URL of the latest FSLogix version.
    • Install from a network share: Select this option if you have the FSLogix installation files on a network share and specify its location.
    • Push from RAS Connection Broker: This option allows you to upload the FSLogix installation archive to the RAS Connection Broker server. When you enable FSLogix on a session host, it will be push installed on the host from the RAS Connection Broker server.
  2. When done, click Apply in the RAS Console to apply your changes to Parallels RAS.

Upgrade FSLogix

The dialog described above can also be used to upgrade FSLogix to a newer version. To upgrade, do one of the following:

  • Select Install online and choose from one of the provided FSLogix builds or specify a custom URL. The Detect latest button obtains a URL for the latest stable FSLogix build.
  • Download a new version from the Microsoft website, place it on a network share or upload it to the RAS Connection Broker server and then select Install from a network share or Push from RAS Connection Broker, whichever applies.

If FSLogix is already installed on one or more hosts and a new version of FSLogix becomes available when you do one of the above, FSLogix will be upgraded on hosts that have it installed. Note that if you specify a version that is earlier than the version installed on a host, then FSLogix will be downgraded.

Configure Site defaults and hosts for FSLogix

To configure Site defaults or individual hosts for FSLogix, do one of the following:

  • For Site defaults, navigate to Farm > Site and click Tasks > Site defaults > RD Session Hosts (or VDI to configure defaults for VDI, or one of the AVD options to configure site defaults for Azure Virtual Desktop).
  • To configure individual hosts, navigate to Farm > Site > RD Session Hosts. Right-click a host and choose Properties.
  • When you add an RD Session Host to a Farm, the FSLogix settings are specified on the User profile page.

In the Site defaults or Properties dialog, select the User profile tab and specify the following options:

  1. If you are in the host Properties dialog (or in a wizard where you add a new host or template), clear the Inherit default settings option if you want to specify different settings for this host.
  2. In the Technology section, select FSLogix.
  3. The Deployment method field shows the currently set deployment method as configured on the Site level (see the description above). You can click the Change... link and select a different method. Note that this will modify the Site setting, which will change it for all hosts in the Site.
  4. If you want to use Profile Containers, select the Use Profile Containers options. Click the Configure button to configure settings:
    • Users and Groups tab: Specify include and exclude user and group lists. By default, Everyone is added to the FSLogix profile include list. If you want some user profiles remain local, you can add those users to the exclude list. Users and group can exist in both lists but exclude takes priority.
    • Folders tab: Specify include and exclude lists for folders. You can select from common folders or you can specify your own. Please note that folders must reside in user profile path.
    • Disks tab: Specify the settings of the profile disk. Location type: Select a location type for profile disks (SMB Location or Cloud Cache) and then specify one or more locations. Location of profile disks: Location(s) of profile disks. These are the locations of VHD(X) files (the VHDLocations setting in the registry as specified in the FSLogix documentation). Profile disk format: Select from VHD or VHDX according to your requirements. VHDX is a newer format and has more features. Allocation type: Select Dynamic or Full. This setting is used in conjunction with the Default size setting (see below) to manage the size of a profile. Dynamic causes the profile container to use the minimum space on disk, regardless of the allocated Default size. As a user profile is filled with more data, the amount of data on disk will grow up to the size specified in Default size, but will never exceed it. Default size: Specifies the size of newly created VHD(X) in megabytes.
    • Advanced tab: This tab allows you to modify advanced FSLogix registry settings. To modify a setting, select it and click Tasks > Edit. By default, the settings are disabled. To enable a setting, select the checkbox in front of its name. A description for each setting is provided in the RAS console. For further information regarding FSLogix Profile Containers configurations, visit https://docs.microsoft.com/en-us/fslogix/profile-container-configuration-reference.
  5. If you want to use Office Containers, select the Use Office Containers options. Click the Configure button to configure settings:
    • Users and Groups tab: Same as above.
    • Disks tab: Same as above.
    • Advanced tab: Same as above.
  6. Click the Configure general settings button to configure FSLogix settings for all types of containers:

Rebooting a host

When you enable FSLogix for a new host while running the wizard, no additional steps are necessary. On wizard completion, the host is rebooted and is added to the active load balancing. An existing host must be rebooted manually using the Tasks > Tools > Reboot menu option.

Was this topic helpful?