Cloud Cache registry configuration reference
Cloud Cache configuration may be used for both Profile Container and Office Container. For Profile Container registry settings are applied here: HKLM\SOFTWARE\FSLogix\Profiles. For Office Container registry settings are applied here: HKLM\SOFTWARE\Policies\FSLogix\ODFC.
When using Cloud Cache, CCDLociations replaces VHDLocations. CCDLocations and VHDLocations may not both be present at the same time.
For a the full Profile Container reference see: Profile Container registry configuration reference. For a the full Office Container reference see: Office Container registry configuration reference.
|CCDLocations (Required Setting)||REG_SZ / MULTI_SZ||Specifies the storage type and location of Cloud Cache remote containers. CCDLocations should be used INSTEAD OF VHDLocations when using Cloud Cache, see Profile Containers or Office Container for further instructions. When setting CCDLocations for a base product, Type must be SMB and only and one remote container may be specified. When setting CCDLocations for full products, Type may be any supported CCDLocations type, and up to 4 remote container locations may be specified. When setting CCDLocation, the first location set will be the primary read location. The primary read location will be read from, unless it's unavailable. All locations will be written to. When setting CCDLocations, do not place spaces around delimiters. CCDLocations values are always case-sensitive.. type = Type of Storage. Supported Storage Types: SMB, Azure Page Blobs, andAzure Premium Page Blobs. See the Configure Cloud Cache Tutorial for step by step instructions. ConnectionString = Location of folder for remote container. Example: \Location\Folder. CCDLocations SMB Example: type=smb,connectionString=\Location1\Folder1;type=smb,connectionString=\Location2\folder2|
|ClearCacheOnLogoff||DWORD||0||By default, the Local Cache file won't be removed when the user sign out. If a user accesses a system where it is desirable to have the Local Cache file deleted when they sign out, set ClearCacheOnLogoff to 1|
|Enabled||DWORD||Used as described in Profile Container Reference and Office Container Reference.|
The following values are Cloud Cache Specific and are used for all Cloud Cache implementations whether applied to Profile Containers or Office Containers. These settings are applied here: Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\frxccd\Parameters
|CacheDirectory||REG_SZ||CacheDirectory specifies the location of the Local Cache file. By default, the local Cache file will be placed in C:\ProgramData\FSLogix\Cache. The Local Cache file may be placed on another mapped drive or a UNC. CacheDirectory and ProxyDirectory MUST NOT be the same location as the Proxy File and the Cache File are the same name and will conflict. IMPORTANT: When considering the location of the Local Cache file, it's critical to select storage that is Highly Available and High Performing. Storage that is appropriate for the Local Cache file will have performance and availability characteristics similar to higher performing local storage. NOTE: CacheDirectory is set prior to GPOs being applied, it is not possible to rely on GPOs to set CacheDirectory in environments where a GoldImage is applied at boot.|
The following values are Cloud Cache Specific and are used for all Cloud Cache implementations whether applied to Profile Containers or Office Containers. These settings are applied here: Registry Key: HKLM\SYSTEM\CurrentControlSet\Services\frxccds\Parameters
|ProxyDirectory||REG_SZ||ProxyDirectory specifies the location of the Local Proxy Stub file. By default, the local Cache file will be placed in C:\ProgramData\FSLogix\Proxy. The Proxy Directory may be placed on another mapped drive. CacheDirectory and ProxyDirectory MUST NOT be the same location as the Proxy File and the Cache File are the same name and will conflict.|
Although it is possible to change the location of the Proxy Directory, it is strongly recommended that this is only done when there is no C drive. The Proxy Directory contains no data.