Let’s have a quick look at the fix for the trust failed Issue with the SCCM HP Client Updates Catalog. This post is applicable if you have already enabled the third-party software update patching from Configuration Manager (a.k.a SCCM).
You can also go through the back-end process details of 3rd party Software update via log file to better understand the troubleshooting process. The out of box solution provided by Microsoft has only three partner catalogs included by default. Those are Dell, Lenovo, and HP.
I have also produced a list of free vendor catalogs available for the SCCM community in the following post Free SCCM Catalogs. You can also purchase third-party patching vendors to get end-to-end automation in the patching process.
- Related Post Fix ConfigMgr Third-Party Updates Last Sync Status Trust Failed | SCCM How To Manage Devices (anoopcnair.com)
I have noticed a Last Sync status as Trust failed for the HP client update catalog. where you can find this error?
- Launch Admin Console for SCCM
- Navigate \Software Library\Overview\Software Updates\Third-Party Software Update Catalogs.
- Select the Last Sync Status column to get the details about the third-party catalog failure because of Trust Failed error.
Troubleshoot via Logs
Check the SMS_ISVUPDATES_SYNCAGENT.log to get more details about the trust failed error with the HP catalog. After reviewing the logs it seems that HP updated the certificate and that certificate is not approved in the Configuration Manager.
The following are the SMS_ISVUPDATES_SYNCAGENT.log snippet to get the details about the flow of SCCM third-party catalog sync.
- Launcher: About to start work item: SyncUpdateCatalog.
- SyncUpdateCatalog: Starting download for catalog ‘HP Client Updates Catalog’ from ‘https://hpia.hpcloud.hp.com/downloads/sccmcatalog/HpCatalogForSms.latest.cab’ …
- SyncUpdateCatalog: Downloading file: ‘https://hpia.hpcloud.hp.com/downloads/sccmcatalog/HpCatalogForSms.latest.cab’ to ‘F:\Program Files\Microsoft Configuration Manager\ISVTemp\0layqc3d.2ig\HpCatalogForSms.latest.cab’.
- SyncUpdateCatalog: Download from ‘https://hpia.hpcloud.hp.com/downloads/sccmcatalog/HpCatalogForSms.latest.cab‘ completed successfully.
- SyncUpdateCatalog: SyncUpdateCatalog : 7b3ff820-0a3f11dc-b22e-f81456d89593 – No previous hash was found, catalog has not been synced previously or hash was reset.
NOTE! – The following lines in the log file give you an error about certificates. These log entries give us details about fixing the issue as well.
- SyncUpdateCatalog: File ‘F:\Program Files\Microsoft Configuration Manager\ISVTemp\0layqc3d.2ig\HpCatalogForSms.latest.cab’ appears to be signed, retrieved certificate, checking signature…
- SyncUpdateCatalog: Certificate ‘60151E2D147EEB09410B50D752AD6’ is not yet approved, try again after approval.
- STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_CATALOG_TRUST_FAILED).
- STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_CATALOG_SYNC_FAILED).
You can check the log called SMS_ISVUPDATES_SYNCAGENT.log from SCCM primary server installation folder called F:\Program Files\Microsoft Configuration Manager\Logs.
Fix – SCCM HP Client Updates Catalog Trust Failed
Now, let’s get into the resolution for the SCCM HP Client Updates Catalog Trust Failed issue. I have seen this issue for other partner catalogs in the SCCM world and fixed those issues with a similar solution. You can get more details about those issues and fixes in the following blog post.
- Launch SCCM admin console.
- Navigate to \Administration\Overview\Security\Certificates.
- Sort the with the Status column.
- Find out the Blocked certificates.
I can see the following HP certificate is blocked:
- CN = HP Inc.
- OU = HP Cybersecurity
- O = HP Inc.
- L = Palo Alto
- S = California
- C = US
Now, let’s unblock the HP client update catalog certificate to fix the HP third-party software update patching issue.
- Right-click on HP update catalog certificate and click on unblock option.
- You can see the HP certificate is unblocked now.
You can go back to the Third-Party Software Update node to confirm whether the sync is getting successful or not. You can check the results of the Fix SCCM HP Client Updates Catalog Trust Failed Issue.
- Navigate to \Software Library\Overview\Software Updates\Third-Party Software Update Catalogs
- Click on HP partner Catalog and select Sync Now option.
NOTE! – You can review the sync catalog process by checking the SMS_ISVUpdates_SyncAgent component in th component status node of the monitoring workspace. Are you sure that you want to sync this catalog? Click on Yes.
Now, let’s check the SMS_ISVUPDATES_SYNCAGENT.log file to get more details about update sync details.
- SyncUpdateCatalog: SyncUpdateCatalog : 7b3ff820-0a3f-11dc-b22e-f81456d89593 – No previous hash was found, catalog has not been synced previously or hash was reset.
- SyncUpdateCatalog: File ‘F:\Program Files\Microsoft Configuration Manager\ISVTemp\24ucmo2n.2f3\HpCatalogForSms.latest.cab’ appears to be signed, retrieved certificate, checking signature…
- SyncUpdateCatalog: Catalog files were decompressed in directory ‘F:\Program Files\Microsoft Configuration Manager\ISVTemp\0gsibmox.tjk’
- SyncUpdateCatalog: Synchronizing an indexed catalog, the index will be used during processing, and the catalog may include certificate information.
- SyncUpdateCatalog: Catalog includes categorized updates.
- SyncUpdateCatalog: Completed parsing of catalog ‘HP Client Updates Catalog’
- SyncUpdateCatalog: Checking for any new catalog certificates…
NOTE! – The following log entries give a clear indication that everything is GREEN after unblocking the HP certificates.
- SyncUpdateCatalog: Updating category configuration data, there are 385 categories in the catalog.
- SyncUpdateCatalog: New category ‘HP ProBook 445 G8 Notebook PC’ specifies a parent category with id ’27ad3850-70cd-4de6-8c77-eb89b75ea496′, however the specified parent category has direct member updates.
- STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_CATALOG_SYNCED).
- SyncUpdateCatalog: SyncUpdateCatalog : 7b3ff820-0a3f-11dc-b22e-f81456d89593 – Completed.
Now, you can go back to the console and confirm whether the HP catalog sync is completed successfully or not.
You can continue to deploy the third-party software updates related to HP laptops and desktops using the newly synced catalog. You can follow the SCCM Third-Party Software Updates Setup Step By Step Guide 1 (anoopcnair.com) deployment process.
- SCCM Third-Party Software Updates Setup Step by Step Guide Post Video Guide
- Free SCCM Catalog List – SCCM Third-Party Updates Post 2
- How to Install, Configure and Integrate with SCUP 2017 with SCCM
- How to Publish 3rd Party Abode Acrobat Patches via SCCM SCUP 2017
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with over 17 years of experience (calculation done in 2018). 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…..…