Number Session VHD(s) To Keep
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 Description
This setting is used when VHDAccessMode is set to '3'. This controls the number of session VHD(x) containers that are persisted. For example, if this is set to '2' and the user creates a 3rd session, a new session VHD(x) will be created and used and it will be deleted when the 3rd session ends. Th default value is 2 sessions which is the same as "Not Configured" Registry Entry: HKLM\SOFTWARE\Policies\FSLogix\ODFC\NumSessionVHDsToKeep Type: DWORD Values: Min = 0, Max = 10
Registry
HKLM
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: Number Session VHD(s) To Keep
; State: Enabled
; Supported on: v2105 or later
[HKEY_LOCAL_MACHINE\Software\Policies\FSLogix\ODFC]
"NumSessionVHDsToKeep"=dword:00000002More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Number Session VHD(s) To Keep
# 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 'NumSessionVHDsToKeep' -Value 2 -Type DWordIntune 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: Number Session VHD(s) To Keep
# 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 'NumSessionVHDsToKeep' -Expected 2 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Number Session VHD(s) To Keep
# 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 'NumSessionVHDsToKeep' -Value 2 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: Number Session VHD(s) To Keep
# 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: Number Session VHD(s) To Keep
# 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 'NumSessionVHDsToKeep' -Expected 2 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Number Session VHD(s) To Keep
# 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 'NumSessionVHDsToKeep' -Value 2 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.