No Profile Containing Folder
Verified with Microsoft FSLogix — updated on July 10, 2026 Supported on: v2105 or later
Path in the GPO console
Computer Configuration\Administrative Templates\FS Logix\ODFC Containers\Container and Directory Naming Registry
Software\Policies\FSLogix\ODFC Description
VHD(x) file is placed and used in the root VHDLocation rather than in a SID directory under VHDLocation NOTE: This setting will override ANY OTHER setting related to container folders. - SIDDIRNameMatch has NO EFFECT when used in conjunction with this setting. - SIDDIRNamePattern has NO EFFECT when used in conjunction with this setting. - FlipFlopProfileDirectoryName has NO EFFECT when used in conjunction with this setting. Registry Entry: HKLM\SOFTWARE\Policies\FSLogix\ODFC\NoProfileContainingFolder Type: DWORD Values: 0 = Disable, 1 = Enabled
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: No Profile Containing Folder
; State: Enabled
; Supported on: v2105 or later
[HKEY_LOCAL_MACHINE\Software\Policies\FSLogix\ODFC]
"NoProfileContainingFolder"=dword:00000000 More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: No Profile Containing Folder
# 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 'NoProfileContainingFolder' -Value 0 -Type DWord Intune 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: No Profile Containing Folder
# 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 'NoProfileContainingFolder' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: No Profile Containing Folder
# 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 'NoProfileContainingFolder' -Value 0 -Type DWord SCCM scripts
# Exported from gporais.com
# Policy: No Profile Containing Folder
# 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: No Profile Containing Folder
# 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 'NoProfileContainingFolder' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: No Profile Containing Folder
# 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 'NoProfileContainingFolder' -Value 0 -Type DWord Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.