Configuration Manager 2403 remote Content Library/DP issues with only the Client Package

Clifton Hughes 0 Reputation points
2024-05-16T01:45:43.54+00:00

Strange issue with a "remote" Content Library/DP. I recently setup a remote site system for handling several roles remote from the Primary site server to support a Passive Site Server role. I have remote SQL, and everything but the SMS Provider role running on this new site system, where I also am running the DP for the site, and I moved the content library to this DP's SCCMContentLib folder by using the D$ share to access it. I migrated the content source files to a new disk on this same site system, and all of the content for those apps, packages, OS image packages, etc. distributed fine to the new DP, except one, the Configuration Manager Client package, the default one, I have not used the staging version. Oddly enough it distributed fine to the Cloud Management Gateway DP, just not to itself. both the Primary Site Server and the remote Site system are local admins of each other, and full admins on the shares/folders for the \Servername\site_PR1\client, and if access was not working, it would not have been able to distribute it to the CMG DP? I am unable to remove it from the DP like a normal package, any other ideas on how to troubleshoot this one? I have tried a site reset also.

Microsoft Configuration Manager
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. AllenLiu-MSFT 41,136 Reputation points Microsoft Vendor
    2024-05-17T02:24:40.8166667+00:00

    Hi, @Clifton Hughes

    Thank you for posting in Microsoft Q&A forum.

    It seems that the Configuration Manager Client package is not distributing to the remote DP but is distributing fine to the Cloud Management Gateway DP.

    One troubleshooting step you can take is to review the logs on the site server (distmgr.log and PkgXferMgr.log) and the distribution point (smsdpprov.log) for any pointers to the failures.

    You can also use the Content Library Explorer tool and validate the package from the Configuration Manager console to see if there are any hash mismatches.

    Additionally, you can check for file locks by other processes, such as antivirus software, and exclude the content library on all drives from automatic antivirus scans.

    If all else fails, have we tried to redistribute the content?


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".