FSLogix Profiles puts a user’s entire profile into a VHD or VHDX container. This container is typically stored on a file server and attached dynamically as the user logs on. The Windows Search database can also be roamed in the Profile Container. This capability to roam the Search Database requires an Office 365 Container license. Also, note that roaming the Search Database in a Multi-user environment has specific Windows OS version requirements documented here.
Only two settings are required for Profiles to work: 'Enabled' and 'VHDLocations'. However, there are numerous settings available.
Local User Groups
Two local computer groups are created to control whether or not a user gets a FSLogix Profile:
- FSLogix Profile Include List (By default includes "Everyone")
- FSLogix Profile Exclude List - (Empty by default)
Users and groups (including Active Directory users and groups) can be added to these local groups to control which users will have their profiles in FSLogix Profile containers. Membership in the Exclude group overrides membership in the Include group. The following table shows whether a Profile container is used based on group membership:
|Member of Exclude Group||Not a Member of Exclude Group|
|Member of Include Group||Profile System Inactive||Profile System Active|
|Not a Member of Include Group||Profile System Inactive||Profile System Inactive|
Interoperability with Existing Local Profiles
If the user logging on has an existing profile on the computer, the FSLogix Profile system will not become active and the user will just log on normally using the existing local profile. In order for a FSLogix profile to be used, the local profile must be removed.
Automatic Profile Container Creation
If a user is logging on and a Profile container is not found for the user in any of the folders specified in
VHDLocations, a new container is created dynamically. A new folder whose name begins with the user’s SID will be created in the first location specified in
VHDLocations. A new Profile.vhd file is created in this folder according to the registry settings specified (
SizeInMBs, and so on). As the Profile Service creates a new profile for the user, it is seamlessly redirected into the new VHD. The next time the user logs on, this VHD is found and attached.
Profile Container Location
The Profile container (VHD file) exists under one of the locations specified by the VHDLocations registry setting. For example, if VHDLocations was set to \\server\share\Profiles, under \\server\share\Profiles there would exist a folder with a name beginning with the SID of the user, and in that folder, there would be a VHD file that begins with “Profile”. The user must have Full Control permissions for this file. This is because the Profile VHD is typically accessed as the user that is logging on.
Pre-creating VHD/X Containers
VHD or VHDX files can be created with any tools and put in place on the network for the user’s profile. The VHD/X should contain a formatted volume. When the user logs on and the Profile Service begins to create the user’s profile, it will be placed into the empty volume. This can save the time that an initial creation of a VHD would normally consume during logon.
The FrxTray tool is used to communicate basic information to the user about their Profile status. It can also notify the user when space is running low in their profile container. Advanced information is available via the "Advanced" button that can be useful in a support situation.
The Configuration tool can be used to easily manage local settings.
The FSLogix Apps command line (frx.exe) can be used to migrate existing local profiles to FSLogix containers.
The admin can configure the system to roam the Windows Search database with the Profile container.
If the system is not behaving properly, have a look at this information.