Configure ODFC containers

FSLogix ODFC containers are a subset to the profile container and are used to redirect specific Microsoft 365 app data into a VHD stored on a storage provider. The most common storage provider is an SMB file share.

All benefits of the ODFC container are automatic when using profile containers in a single container configuration. There's no need or benefit to using the ODFC container when profile containers are your primary profile management solution. ODFC containers can optionally be used in with profile containers in a dual container configuration, to place Microsoft 365 app data in a different VHD from the rest of the profile data.

When pairing the ODFC container with third party roaming profile solutions, ensure to exclude the paths in the profile managed by the ODFC container. The paths to exclude depend on the ODFC configuration settings.

If you've already configured a profile container, you don't need to configure an ODFC container. Profile containers are inclusive of all the benefits and uses found in ODFC containers.

Prerequisites

Before you can configure ODFC containers, you need:

• Windows devices you want use with FSLogix, such as Azure Virtual Desktop session hosts. You can use the Azure Virtual Desktop Quickstart to deploy a sample environment for testing. An SMB file share with NTFS and share-level permissions correctly configured, or other supported storage provider.
• A user account on the local device with administrator privilege in order to configure the registry.
• The latest version of FSLogix downloaded and installed on the Windows device.
• Review configuration options.
• Completed profile container configuration tutorial.

ODFC container configuration

To configure your ODFC container:

1. Verify FSLogix installation and version.

2. Sign in to the virtual machine as a local administrator or with an account with administrative privileges.

3. Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\FSLogix\ODFC.

4. Add the following settings:

   Value Name	Data Type	Data	Description
   Enabled	DWORD	1	Required
   FlipFlopProfileDirectoryName	DWORD	1	Recommended. Provides an easier way to browse the container directories.
   IncludeTeams	DWORD	1	Recommended. Ensures Microsoft Teams data is kept in the container for optimal performance.
   LockedRetryCount	DWORD	3	Recommended. Decreases the retry timing to enable a faster fail scenario.
   LockedRetryInterval	DWORD	15	Recommended. Decreases the retry timing to enable a faster fail scenario.
   ReAttachIntervalSeconds	DWORD	15	Recommended. Decreases the retry timing to enable a faster fail scenario.
   ReAttachRetryCount	DWORD	3	Recommended. Decreases the retry timing to enable a faster fail scenario.
   SizeInMBs	DWORD	30000	Default
   VHDLocations	MULTI_SZ or REG_SZ	SMB Share path	For example: \\<storage-account-name>.file.core.windows.net\<share-name>
   VolumeType	REG_SZ	VHDX	Recommended. VHDX is preferred over VHD due to its supported size and reduced corruption scenarios.

   You can use these PowerShell commands to add the registry settings:

   $VHDLocations = "\\<STORAGE-ACCOUNT-NAME>.file.core.windows.net\<SHARE-NAME>"
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name Enabled -PropertyType dword -Value 1 -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name FlipFlopProfileDirectoryName -PropertyType dword -Value 1 -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name LockedRetryCount -PropertyType dword -Value 3 -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name LockedRetryInterval -PropertyType dword -Value 15 -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name ReAttachIntervalSeconds -PropertyType dword -Value 15 -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name ReAttachRetryCount -PropertyType dword -Value 3 -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name SizeInMBs -PropertyType dword -Value 30000 -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name VHDLocations -PropertyType string -value $VHDLocations -Force
   New-ItemProperty -Path HKLM:\SOFTWARE\FSLogix\ODFC\ -Name VolumeType -PropertyType string -Value vhdx -Force
   

Verify your ODFC container configuration

Once you configure the Windows device to use ODFC containers, you can verify the configuration by following these steps:

1. Sign in as a standard user.

2. Open the Command Prompt and change the directory by running the following command:

   C:\Program Files\FSLogix\Apps
   

3. Run the following command to list each redirect:

   `frx list-redirects`
   

   Here's an example of the output of the command:

   Active redirections
    -------------------
    \Device\HarddiskVolume4\$RECYCLE.BIN\S-1-5-21-000000000-000000000-0000000000-0000000 => \Device\HarddiskVolume6\ODFC_RECYCLE.BIN
    \Device\HarddiskVolume4\Users\contoso\AppData\Local\Microsoft\Outlook => \Device\HarddiskVolume6\ODFC
    \Device\HarddiskVolume4\Users\contoso\AppData\Roaming\Microsoft\Outlook => \Device\HarddiskVolume6\ODFCPersonalization
    \Device\HarddiskVolume4\Users\contoso\AppData\Local\Microsoft\OneDrive => \Device\HarddiskVolume6\OneDrive\UserMeta
    \Device\HarddiskVolume4\OneDriveTemp\S-1-5-21-000000000-000000000-0000000000-0000000 => \Device\HarddiskVolume6\OneDrive\ODTemp
    \Device\HarddiskVolume4\Users\contoso\AppData\Local\Microsoft\Office\16.0\Licensing => \Device\HarddiskVolume6\OfficeLicensing
    \Device\HarddiskVolume4\Users\contoso\AppData\Local\Microsoft\Office\15.0\Lync => \Device\HarddiskVolume6\Skype4B_15\User
    \Device\HarddiskVolume4\Users\contoso\AppData\Local\Microsoft\Office\16.0\Lync => \Device\HarddiskVolume6\Skype4B\User
    \Device\HarddiskVolume4\Users\contoso\AppData\Local\Microsoft\Teams => \Device\HarddiskVolume6\Teams\data
    Operation completed successfully!
   

4. Open File Explorer and open the full path you set for VHDLocations in the registry.

5. Double-click the folder for the standard user.

6. Locate the newly created profile and ODFC VHDX containers.

Exclusions for third party roaming profiles

When pairing the ODFC container with a third party roaming profile solution, the folders managed by the ODFC container should NOT be roamed by the third party provider. The folders to exclude depend on which settings are enabled.

Related content

Learn more about how to use FSLogix:

• Configuration examples
• Configure profile containers with Cloud Cache