Enabled
Vérifié avec Microsoft FSLogix — mis à jour le 10 juillet 2026
Pris en charge sur : v2105 or later
Chemin dans la console GPO
Configuration ordinateur\Modèles d'administration\FS Logix\Logging Description
NOTE: Once this policy is Enabled, only Disable will remove the registry value. Enabled to Not Configured will have NO EFFECT. Select how FSLogix should enable logging. All logs is the default setting. Registry Entry: HKLM\SOFTWARE\FSLogix\Logging\LoggingEnabled Values: 0 = No Logs, 1 = Specific Logs, 2 = All Logs
Registre
Software\FSLogix\Logging Générateur d'exports
BETAConfigurez l'état, la portée et les options, puis générez les sorties .reg, PowerShell, Intune et SCCM — ou ajoutez le paramètre à une collection multi-paramètres.
Ces exports écrivent le registre — ce n'est pas une GPO managée. ⓘ
Fichier .reg
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Enabled
; State: Enabled
; Supported on: v2105 or later
[HKEY_LOCAL_MACHINE\Software\FSLogix\Logging]
"LoggingEnabled"=dword:00000000 Autres formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Enabled
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\FSLogix\Logging'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'LoggingEnabled' -Value 0 -Type DWord Intune XML
Aucune correspondance directe Policy CSP / OMA-URI pour cette stratégie. Utilisez l'onglet Intune Remediation, ou importez l'ADMX dans Intune. Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Enabled
# 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\FSLogix\Logging' -Name 'LoggingEnabled' -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: Enabled
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\FSLogix\Logging'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'LoggingEnabled' -Value 0 -Type DWord Scripts SCCM
# Exported from gporais.com
# Policy: Enabled
# 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: Enabled
# 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\FSLogix\Logging' -Name 'LoggingEnabled' -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: Enabled
# State: Enabled
# Supported on: v2105 or later
$path = 'HKLM:\Software\FSLogix\Logging'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'LoggingEnabled' -Value 0 -Type DWord Vous construisez une collection multi-paramètres ? Ajoutez ce paramètre et générez des exports combinés (.reg, PowerShell, GPO).