FSLogix Profile Container Configuration

FSLOGIX PROFILE CONTAINER CONFIGURATION

Step by step how-to in Citrix Environment

Once downloaded, you`ll need to import admx/adml files in your sysvol policy definitions repository

Full path:

C:\Windows\SYSVOL\sysvol\dexanul.lab\Policies\PolicyDefinitions

Relative path:

Simply create a folder and share it with everyone somewhere on a server in your domain (leave default for testing purposes)
You will need this later when configuring profile container policy

Install the fslogix agent and rule app editor on your target device (master image or VDA)

In this example I am using a ws2k19 server x64
We will need the rule app editor later for application masking (see app masking article)

There are 4 local security groups created on the VDA after fslogix app installation. These basically include/exclude users to which profile container and outlook data container creation will apply

Make sure you populate them with your preferred membership be it user objects or security group objects.
For my testing I included “everyone” group and excluded “domain admins”. This means that everyone will be getting a profile container with the exception of domain admins.

Now that we are done with agent installation, we can move on to the GPO configuration part.

As far as settings go, you would normally just need to enable FSLOGIX functionality, define a profile container size and location where it is stored. Rest of the settings are optional and need research to see what applies for you.
For our testing purposes, as an example, I have configured the following settings:

As you can see, we specified the share path we have created at step 3 and we also have the script defined for Fslogix rules copy. We will talk more about this once we get to that part and why this is needed.

This is it. Reboot your VDA or provision your golden image to your target devices and test by logging on with a user that is allowed to use fslogix profile containers (see step 6 referring to which users/group objects are set within the local fslogix include group).

Once you have rebooted, you will see a profile container created on the share you created earlier at step 3 and defined it in policy on step 7. Should look like this

Share side

VDA side

This how-to has been made based on the following reference article/video

See whitepaper (download PDF) for configuration and particularities

Configuration reference (video) FSLOGIX profile container