Client Settings
Applies to: Patch My PC Publisher
Overview
For client devices to successfully scan for, trust, and install updates, specific client settings must be configured. Software Update client settings configure core Windows Update Agent behavior on managed devices. This client setting is typically already enabled if you manage Microsoft Updates through an existing SUP. It handles setting the intranet update service location and related scan settings based on the SUP assigned through boundary group configuration. As a result, clients automatically know which SUP to scan against and where to obtain update metadata and content.
When third-party software updates are enabled through client settings too, ConfigMgr also handles the additional requirements needed for third-party updates, such as allowing non-Microsoft–signed updates and distributing the WSUS code-signing certificate to clients, without requiring manual registry changes or manual certificate deployment.
Important
If you plan to deploy third-party update content through a Cloud Management Gateway (CMG), do not enable Allow clients to download delta content when available in the corresponding Client Settings for clients that connect to a CMG as their management point (MP) and software update point (SUP).
When a CMG is used for content storage, third-party update content will fail to download to clients if the Download delta content when available client setting is enabled.

Enable Third-Party Software Updates
In the ConfigMgr console:
Navigate to Administration > Client Settings.
Open Default Client Settings or a custom client settings policy.
Select Software Updates.
Ensure the following settings are configured:
Enable software updates on clients = Yes
Enable third party software updates = Yes
Note
This client setting must apply to all devices that will scan for or install third-party updates.
When Enable third party software updates is set to Yes, ConfigMgr configures the client to:
Allow the Windows Update Agent to download and install non-Microsoft–signed updates.
Attempt to retrieve the code-signing certificate from ConfigMgr during a software update scan.
Trust updates signed with that third-party certificate by placing the certificat(s) into the appropriate certificate stores.
Without this client setting enabled, client devices will not trust third-party updates, even if they are correctly published and deployed. This client setting configures local policy on the device, including setting the following registry value:
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
AcceptTrustedPublisherCerts = 1

If you are not using ConfigMgr client settings to manage this behavior, the same configuration can be applied using:
Group Policy
Manual registry configuration
Intune Settings Catalog
Last updated
Was this helpful?