Failed to distribute content to CMG from SCCM

Abrar Adil S 421 Reputation points
2025-12-04T07:47:49.4133333+00:00

Failing to distribute the content from SCCM to CMG DP, we believe that the configuration on the load balancer might have disrupted.
The load balancer health probe configuration as below

The VMSS is now unhealthy, any suggestions on where the setup is going wrong.

User's image

User's image

User's image
User's image

Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Venkatesan S 1,165 Reputation points Microsoft External Staff Moderator
    2025-12-04T08:01:06.9633333+00:00

    Hi Abrar Adil S,

    Thanks for question in Microsoft Q&A forum,

    You seem to be facing challenges with distributing content to the Cloud Management Gateway (CMG) in SCCM, specifically related to the health of the load balancer and VM scale set (VMSS). Below is a step-by-step guide to help you troubleshoot and resolve this issue.

    Steps to Troubleshoot CMG Content Distribution:

    1. Check Health Probe Configuration:
      • Ensure that your health probe settings for the Load Balancer are configured correctly. If your services are marked unhealthy, they won't receive traffic. Make sure the probe can reach the backend instances and that the necessary ports are open.
      • You can review the load balancer’s health probe configuration, ensuring it matches the backend setup.
    2. Evaluate Backend Health:
      • Use Azure Monitor to check the health of your backend resources. The metric DipAvailability will indicate if your VMs are responding correctly. Ensure the count of successful health probes matches the number of instances in your backend pool.
      • (Reference: Azure Monitor Metrics Showing Backend Health)
    3. Session Persistence Settings:
      • Review your Load Balancer's session persistence settings. If set to Source IP or Source IP and Protocol, it may lead to uneven load distribution. Consider setting it to None for proper load distribution.
      • (Reference: Azure Load Balancer Load Distribution)
    4. Check for NSG Issues:
      • Make sure that there are no Network Security Groups (NSGs) blocking the health probes. If the probes can’t access the VMs, they will be considered unhealthy.
      • (Reference: NSGs and Health Probes)
    5. Look for Errors in Logs:
      • Check the PkgXferMgr.log for any transfer issues. Look out for specific error codes like 80070070, which indicate space issues. Make sure the disk where packages are stored has enough space.
      • (Reference: Error 80070070 Troubleshooting)
    6. Consider Flushing BranchCache:
      • If using BranchCache, consider flushing the publication cache if you suspect it might be causing issues during distribution. Use the command:
             
             netsh branchcache flush
             
        
      • (Reference: Error 80070070 Cause and Resolution)

    I hope this helps you get to the bottom of the issue! If you need further clarification or assistance, feel free to ask.

    References:

    Please do not forget to 210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.