CCD Locations
Verified with Microsoft FSLogix — updated on July 12, 2026
Supported on: v2105 or later
Path in the GPO console
Computer Configuration\Administrative Templates\FS Logix\ODFC Containers\Cloud Cache Description
CCDLocations are formatted using a type and a connectionString separated using a ; as the delimiter. The type will accept either smb or azure. The connectionString for smb type must include the full UNC path to the file share. The connectionString for azure type should be secured as per the documentation (https://aka.ms/fslogix). The strings are case sensitive. - CCDLocations using SMB: type=smb,name="SMB Share 1",connectionString=\\<server 1 fqdn>\<share name>;type=smb,name="SMB Share 2"connectionString=\\<server 2 fqdn>\<share name> - CCDLocations using Azure (secure): type=smb,name="SMB Share 1",connectionString=\\<server 1 fqdn>\<share name>;type=azure,name="Azure Blob 1",connectionString="|fslogix/stgacct1-connectionstring|" Registry Entry: HKLM\SOFTWARE\Policies\FSLogix\ODFC\CCDLocations Type: REG_SZ
Registry
Software\Policies\FSLogix\ODFC Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: CCD Locations
; State: Enabled
; Supported on: v2105 or later
[HKEY_LOCAL_MACHINE\Software\Policies\FSLogix\ODFC]
"CCDLocations"=""More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: CCD Locations
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\Policies\FSLogix\ODFC'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'CCDLocations' -Value '' -Type StringIntune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune.Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: CCD Locations
# State: Enabled
# Supported on: v2105 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\FSLogix\ODFC' -Name 'CCDLocations' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: CCD Locations
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\Policies\FSLogix\ODFC'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'CCDLocations' -Value '' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: CCD Locations
# State: Enabled
# Supported on: v2105 or later
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: CCD Locations
# State: Enabled
# Supported on: v2105 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\FSLogix\ODFC' -Name 'CCDLocations' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: CCD Locations
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\Policies\FSLogix\ODFC'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'CCDLocations' -Value '' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.