Configure Profile Containers
Profile Container is a full remote profile solution for non-persistent environments. Profile Container redirects the entire user profile to a remote location. Profile Container configuration defines how and where the profile is redirected.
Profile Container is inclusive of the benefits found in Office Container.
When using Profile Container, both applications and users see the profile as if it's located on the local drive.
In this unit, learn how to:
- Configure Profile Container Registry Settings.
- Set up Include and Exclude User Groups.
Before configuring Profile Container:
- Download and install FSLogix Software.
- Consider the storage and network requirements for your users' profiles.
- Verify that your users have appropriate storage permissions where profiles will be placed.
- Profile Container is installed and configured after stopping use of other solutions used to manage remote profiles.
- Exclude the VHD(X) files for Profile Containers from Anti Virus (AV) scanning.
Configure Profile Container Registry settings
The configuration of Profile Container is accomplished through registry settings and user groups. Registry settings may be managed manually, with GPOs, or using alternate preferred methods. Configuration settings for Profile Container are set in HKLM\SOFTWARE\FSLogix\Profiles.
Below are settings required to enable Profile Container and to specify the location for the profile VHD to be stored. The minimum required settings to enable Profile Containers are:
|Enabled (required setting)
|0: Profile Containers disabled. 1: Profile Containers enabled
|VHDLocations (required setting)
|MULTI_SZ or REG_SZ
|A list of file system locations to search for the user's profile VHD(X) file. If one isn't found, one is created in the first listed location. If the VHD path doesn't exist, it's created before it checks if a VHD(X) exists in the path. These values can contain variables that will be resolved.
VHDLocations may be replaced by CCDLocations when using Cloud Cache.
These settings below are helpful when configuring Profile Container but aren't required.
|0: no deletion. 1: delete local profile if exists and matches the profile being loaded from VHD. Use caution with this setting. When the FSLogix Profiles system determines a user should have a FSLogix profile, but a local profile exists, Profile Container permanently deletes the local profile. The user will then be signed in with an FSLogix profile.
|When set to '1' the SID folder is created as
"%username%%sid%" instead of the default "%sid%%username%". This setting has the same effect as setting
SIDDirNamePattern = "%username%%sid%" and SIDDirNameMatch = "%username%%sid%".
|If set to 1 Profile Container loads FRXShell if there's a failure attaching to, or using an existing profile VHD(X). The user receives the FRXShell prompt - default prompt to call support, and the users only option will be to sign out.
|If set to 1 Profile Container loads FRXShell if it's determined a temp profile has been created. The user receives the FRXShell prompt - default prompt to call support, and the users only option will be to sign out.
Set up Include and Exclude User Groups
There are often users, such as local administrators that have profiles that should remain local. During installation, four user groups are created to manage users who's profiles are included and excluded from Profile Container and Office Container redirection.
By default Everyone is added to the FSLogix Profile Include List group.
Adding a user to the FSLogix Profile Exclude List group means that the FSLogix agent won't attach a FSLogix profile container for the user. In the case where a user is a member of both the exclude and include groups, exclude takes priority.
Profile Containers is now configured and ready to be used. In order to verify that Profile Container is working, sign in as a user in the Included List group. Using File Manager, navigate to the location specified in VHDLocations. Verify that a folder, with the user name and SID has been created.