SCCM team released a new hotfix KB 4042345 for SCCM 1706. SCCM 1706 hotfix KB4042345 is a server-side fix only applicable for CAS + Primary servers. This hotfix is to resolve the issue SCCM CB 1706 Clients cannot download peer cache content.
This hotfix is available for installation on the Updates and Servicing node of the SCCM CB console. This post will explain “SCCM CB 1706 KB4042345 Server Side Fix for Peer Cache”.
Is there any SCCM 1706 Client-side update for KB 4042345?
KB4042345 update is not required for SCCM 1706 clients. We don’t need to update the clients. This SCCM CB hotfix is only applicable for SCCM primary and CAS servers.
This update does not apply to installations of SCCM CB, version 1706, that were downloaded after September 13, 2017.
The issue statement:- SCCM CB clients cannot download content from peer cache sources. An error that resembles the following is recorded in the Contenttransfermanager.log file:
CContentTokenMgr::EncryptToken – Failed Base64Decode cert context
This issue occurs when the SCCM CB 1702 client uses the peer source’s NetBIOS name instead of its fully qualified domain name (FQDN) to get additional information about the connection. The hotfix KB 4042345 fixes the issue where peer-to-peer required AD Discovery is syncing the FQDN.
SCCM CB client peer cache issue will get resolved once you download and install the KB 4042345 on the primary or/and CAS server(s).
Is there any Secondary Server update required for KB4042345?
As I mentioned above, this hotfix is ONLY applicable for CAS and primary servers. The KB 4042345 is NOT required for SCCM CB secondary servers. You don’t have to install the hotfix KB4042345 on SCCM CB secondary servers.
When a hotfix applies to SCCM secondary sites, then Microsoft will add some manual instructions to the KB article. Those instructions will help to get the hotfix installed on the secondary site.
Do we need to install KB4042345 on your SCCM CB infra?
Yes, if you are using the SCCM peer cache feature. If you are NOT using the Peer to Peer cache feature of SCCM CB in your environment, you can wait for the next rollup update of SCCM CB 1706 and install the rollup update whenever it’s available.
Author
Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.