SCCM Software Update List Packages are not Visible on Child Primary Servers ConfigMgr. I’m not going to post anything new in this post. We’ve loads of posts about SCCM ConfigMgr Software Update replication issues when you have a large environment with 3 tier hierarchy and a lot of child primary servers.
I’ve seen lots of issues like the latest Software Update packages (A.K.A SCCM patch packages) and software update lists that are created at the central server are not visible on the child primary server console.
Hence the SCCM ConfigMgr administrators at regional locations are not able to deploy the latest patches to their workstations. This will get highlighted very soon within the organization as this is a security issue 🙂
SCCM Software Update List Packages are not Visible on Child Primary Servers
One of the very detailed deep-dive blogs about this issue is Michael Wiles! Read his full post http://blogs.technet.com/b/mwiles/archive/2011/06/24/troubleshooting-failed-to-insert-object-error-message.aspx . There are so many other blogs that tell you about various ways to resolve this issue.
I must warn you most of the resolution steps includes “Editing Database” and directly editing is not supported by Microsoft unless you’re a Microsoft CSS engineer 🙂 SCCM Software Update List and Packages are not Visible on Child Primary Servers.
In the troubleshooting process of the SCCM ConfigMgr Software Update Package and Software Update Update list replication issue, the best friend is ObjReplMgr.log. What do we need to do to resolve Software Update or Patch package replication issues (not visible issues)?
I won’t recommend doing the SQL database edit or running the SQL query to fix the issue. Rather I would suggest dropping <3 digit Child Site Code>.SHA (3 digit site code) file in the folder “<SCCM Installation Folder>\inboxes\objmgr.box” at your Central site. .SHA file is nothing but a blank file with extension .SHA.
When you make a blank file using notepad, by default the extension of the file will be .SHA.TXT then make sure to remove the extension to .TXT.
For example: When I have an SCCM child primary site with SITE CODE = ACN and in that primary server SCCM console, I’m not able to see the latest software update packages. In this case, I need to place ACN.SHA file in inboxes\objmgr.box folder. Software Update List Packages are not Visible.
Note that, this will initiate the full replication of all the objects between the SCCM child primary site and the SCCM Central primary server. This could be bandwidth-intensive, if you don’t have good network bandwidth between both SCCM servers then perform this during off-peak hours. SCCM Software Update List Packages are not Visible on Child Primary Servers.
As mentioned above monitor the ObjReplMgr.log log file at central and child primary SCCM sites to more details about progress. When SCCM finishes its object replication, the ACN.SHA file will get deleted (disappear) from the Inboxes\ObjMgr.box. Look for the following entry “Deleted site attachment file D:\SCCM\inboxes\objmgr.box\G02.SHA” in Objreplmgr.log. After finishing this process also, we should allow SCCM to update all the tables and entries related to these objects so it may take another 3-To 4 hours to complete the entire process.
I’ve seen by following this method, we can resolve 90 % of SCCM software Update related replication issues without taking the risk of editing the Database. SCCM Software Update List Packages are not Visible on Child Primary Servers. Software Update List Packages are not Visible.
If the above-mentioned step doesn’t resolve your replication issue the best troubleshooting steps are documented by Sharad Singh here.
Sample ObjReplMgr.log entries
~Successfully replicated Object - ID= 4dd19ecb-f551-4241-8a9a-031696f310b1 - Name= $<sms_object_replication_manager><thread=4908 (0x132c)=""> ~Successfully replicated SMS Object b9a4a30a-e494-4eaf-8094-2c1d92323108, ReplVarFileName:D:\SCCM\inboxes\objmgr.box\mannj1t7.TMP $<sms_object_replication_manager><thread=4908 (0x132c)=""> ~Successfully replicated Object - ID= b9a4a30a-e494-4eaf-8094-2c1d92323108 - Name= $<sms_object_replication_manager><thread=4908 (0x132c)=""> ~Successfully replicated SMS Object 82625326-e038-4b34-b4ce-8980489c4b6e, Deleted site attachment file D:\SCCM\inboxes\objmgr.box\G02.SHA $<sms_object_replication_manager><thread=4908 (<span="" class="hiddenSpellError" pre="">0x132c)
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a logger, 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…