Turn on Site Discovery XML output
Verified with Windows 11 25H2 — updated on July 23, 2026
Supported on: At least Internet Explorer 8.0
Path in the GPO console
Computer Configuration\Administrative Templates\Windows Components\Internet Explorer User Configuration\Administrative Templates\Windows Components\Internet Explorer Description
This policy setting allows you to manage the XML output functionality of the Internet Explorer Site discovery Toolkit(SDTK). When enabled the feature will write data collected to an XML file at a location specified when setting this policy. When disabled, no data will be written to the XML file. Enabling or disabling this setting will not impact other output methods available for the SDTK.
Registry
HKLM
Software\Microsoft\Internet Explorer\WMITelemetry HKCU
Software\Microsoft\Internet Explorer\WMITelemetry 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. ⓘ
Applying both scopes creates an ambiguous configuration (computer takes precedence over user). Only do this intentionally.
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Turn on Site Discovery XML output
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: At least Internet Explorer 8.0
[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\WMITelemetry]
"XMLPath"=""More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Turn on Site Discovery XML output
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 8.0
$path = 'HKLM:\Software\Microsoft\Internet Explorer\WMITelemetry'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'XMLPath' -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: Turn on Site Discovery XML output
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 8.0
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\Microsoft\Internet Explorer\WMITelemetry' -Name 'XMLPath' -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: Turn on Site Discovery XML output
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 8.0
$path = 'HKLM:\Software\Microsoft\Internet Explorer\WMITelemetry'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'XMLPath' -Value '' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: Turn on Site Discovery XML output
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 8.0
# 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: Turn on Site Discovery XML output
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 8.0
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\Microsoft\Internet Explorer\WMITelemetry' -Name 'XMLPath' -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: Turn on Site Discovery XML output
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Internet Explorer 8.0
$path = 'HKLM:\Software\Microsoft\Internet Explorer\WMITelemetry'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'XMLPath' -Value '' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.