Registration fails for PKI clients after updating to Configuration Manager current branch, version 2203

Applies to: Configuration Manager (current branch, version 2203)

Summary of KB14480034

After updating to Configuration Manager current branch, version 2203, the registration process fails for clients using public key infrastructure (PKI) for client authentication if they are unable to authenticate against the domain. This affects the following scenarios:

  • Newly installed workgroup clients using PKI.
  • Clients that are joining an AD or Azure AD domain for the first time, generating a new device identity.
  • Existing clients that are trying to renew their client authentication certificate.

When this issue happens, the following error is logged in the DDM.log file on the site server for each affected client.

ClientIdentity is not a hex string
The registration record is not valid. Bad RDR

The RDR file(s) will be moved to ..\auth\\regreq\bad_ddrs on the site server.

Update information for Microsoft Endpoint Configuration Manager, version 2203

An update to resolve this issue is available in the Updates and Servicing node of the Configuration Manager console for environments that installed version 2203. Customers using the early update ring version must first install the following update:

  • KB 13953025: Update for Microsoft Endpoint Configuration Manager version 2203, early update ring

Members of the Technology Adoption Program (TAP) must first apply the private TAP rollup.

Update replacement information

This update does not replace any previously released updates.

Restart information

This update does not require a computer restart or a site reset after installation.

Additional installation information

After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, select Administration > Site Configuration > Sites > Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.

Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:

select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')

If the value 1 is returned, the site is up to date, with all the hotfixes applied on its parent primary site.

If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.

Version information

No major components are updated with this release.

File information

File information is available in the downloadable KB14480034_FileList.txt text file.

Release history

  • May 23, 2022: Initial hotfix release


Updates and servicing for Configuration Manager