In this section, we describe how to configure existing FSLogix Profile Containers to be managed by Parallels RAS. FSLogix Profile Container configuration defines how and where the profile is redirected. Normally, you configure profiles through registry settings and GPO. Parallels RAS gives you the ability to configure profiles from the Parallels RAS Console or RAS Management Portal without using external tools.

For existing configuration, please note the following:

• There is no need to change the existing profiles themselves as they will stay the same.

• You can keep using the existing FSLogix Profile Container locations (SMB or Cloud Cache).

To configure user profile from the RAS Console:

1. Follow the instruction from section New FSLogix deployment via Parallels RAS and open the User Profile tab.

2. Specify the following:

   • The location type. In the Location of profile disks list box, specify your existing SMB or Cloud Cache locations where your FSLogix profiles are stored.

   • Profile disk format, allocation type, and default size of the profile.

3. Click the Additional Settings button to configure FSLogix per your requirements, including:

   • User exclusions

   • Folder exclusions

   • FSLogix settings (https://docs.microsoft.com/en-us/fslogix/profile-container-configuration-reference)

To configure profiles in Parallels RAS Management Portal:

1. Go to Infrastructure > RD Sessions Hosts.

2. Select the RD Session Host that you need.

3. Go to Properties > User Profile.

4. Specify the settings as described above for the Parallels RAS Console.

1. Back up your existing profiles. It is highly unlikely that profile data can be lost or corrupted, but it is best practice to have a valid backup prior to any change in the profile configuration.

2. Turn off the GPO configuration of FSLogix Profile Containers. This step is important because you cannot have both GPO and Parallels RAS management of FSLogix profiles enabled at the same time.

3. Before configuring FSLogix profiles for a server in a RAS Farm, make sure there are no user sessions running on the server. As a suggestion, you can make the transition in a maintenance window out of working hours.