Configure trusted server configuration
Explanation
Use this policy to control how the client identifies the published application or desktop it is connecting to. The client will determine a trust level, called a ""trust region"" with a connection. The trust region will then determine how the client is configured for the connection.
When this policy is enabled, the client can be forced to perform region identification using the "Enforce trusted server configuration" option.
By default, region identification is based on the address of the server the client is connecting to. To be a member of the trusted region, the server must be a member of the Windows Trusted Sites zone. You can configure this using the "Windows Internet zone" setting.
Alternatively, for compatibility with non-Windows clients, the server address can be specifically trusted using the "Address" setting. This is a comma-separated list of servers supporting the use of wildcards, for example, cps*.citrix.com.
Troubleshooting:
In the default configuration, when trusted server configuration prevents the client from connecting, the following error message is displayed:
"<Server> ERROR: Cannot connect to the Citrix XenApp server. The server (xxx) is not trusted for ICA connections. Connections to the (Untrusted Region) Region are not allowed by lockdown settings. Please contact your administrator."
The server identified in the "xxx" must be added to the Windows Trusted Sites zone (as either http:// or https:// for SSL connections) for the connection to succeed.
Note that for SSL connections, the certificate common name must be trusted. For non-SSL connections all servers that are contacted must be individually trusted. This means that when using application browsing, both the XML service and the server this redirects to must be trusted.
Registry
HKEY_CURRENT_USER\Software\Policies\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Network\ClientSelectiveTrust- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
PowerShell
PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.
Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.
Enable
# Enable: receiver/Policy_ConfigureClientSelectiveTrust_1
$k = 'HKCU:\Software\Policies\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Network\ClientSelectiveTrust'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Enforce trusted server configuration
# unchecked: *
Set-ItemProperty -Path $k -Name 'EnableClientSelectiveTrust' -Value 'true' -Type StringDisable
# Disable: receiver/Policy_ConfigureClientSelectiveTrust_1
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": receiver/Policy_ConfigureClientSelectiveTrust_1
$k = 'HKCU:\Software\Policies\Citrix\ICA Client\Engine\Lockdown Profiles\All Regions\Lockdown\Network\ClientSelectiveTrust'
Remove-ItemProperty -Path $k -Name 'EnableClientSelectiveTrust' -ErrorAction SilentlyContinueOptions (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Enforce trusted server configurationPart_EnableClientSelectiveTrust | Check boxboolean | EnableClientSelectiveTrust | REG_SZ | Default (UI): true Checked: REG_SZ = trueUnchecked: REG_SZ = * |
Application
Citrix Workspace app (Citrix) — October 2026 templates
October 2026 templates from pl4nty/web-admx-tool.