locked
SCCM Waiting for Content Issue RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I worked on deploying a Single-Sign Application throughout an environment.  Out of approximately 30 sites,  There is 3 sites with desktops, roughly 8 to 10 machines at each site, that is unable to receive application deployment either from distribution points of headquarters or branch office.  When I’m monitoring deployments from Monitoring Workspace.  It is specifying Waiting for Contents for deployments at certain particular sites  Have anyone seen this type of scenario in the past?  I checked out the boundary groups and boundaries with sites that I’m deploying to, those settings look fine.  I also want to point out the network trafficing is slow with Branch Offices and using MPLS speed compared to Headquarters are on regular LAN speed. 

    Within Software Library and Application Management, right clicking on the actual application, then going to deployment types, Within Content tab,  Towards the bottoms with deployment options, I have it set to Download content from Distribution Point and run locally. 

    Also Client Settings seems to be normal but is there any specified settings for BITS that should be configured as well.  Thanks ahead for assistance?

    Tuesday, July 28, 2020 6:56 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    My first thought is a problem with your Site Boundaries / boundary groups and their subnets. Are you certain that is all configured properly?

    Are your site based DPs healthy? Check you components health status here...

    Monitoring\System Status\Site Status

    Monitoring\System Status\Component Status

    If you browse to the Package in your Software Library, select the package and at the bottom of the page is all the package properties with a Content Status hyperlink far right under "Related Objects" if you click that hyperlink does the package status show up in the green success state? If not then the package is either faulty or has not been properly distributed.

    Tuesday, July 28, 2020 11:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,


    The first thing to check when you experience application download failures is for missing or misconfigured boundaries and boundary groups. For example, if the client is on the intranet and not configured for internet-only client management, its network location must be in a configured boundary. There must also be a boundary group assigned to this boundary for the client to download content. For more information, see:
    Define site boundaries and boundary groups

    Also, make sure it's distributed to a distribution point. To verify this configuration, use the in-console features to monitor content distribution to the distribution points. For more information, see:
    Monitor content you have distributed



    Best Regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, July 29, 2020 9:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It seems to be misconfiguration with AD Sites at sites that cannot deploy software. Worked with another admin and checking out the client logs (Locationservices) with one of the desktops at site that is having issues with deploying software to find out this evaluation.  We was seeing in the log, unable to retrieve AD site membership and Client is not boundary group even though distribution point for those site are setup.  The subnets within the sites with issues that is setup within boundary, boundary group, distribution point, and distribution point group are not matching with IP subnets with Windows Clients at those sites. 
    Friday, August 7, 2020 3:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It seems to be misconfiguration with AD Sites at sites that cannot deploy software. Worked with another admin and checking out the client logs (Locationservices) with one of the desktops at site that is having issues with deploying software to find out this evaluation.  We was seeing in the log, unable to retrieve AD site membership and Client is not boundary group even though distribution point for those site are setup.  The subnets within the sites with issues that is setup within boundary, boundary group, distribution point, and distribution point group are not matching with IP subnets with Windows Clients at those sites
    Friday, August 7, 2020 3:12 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    My first thought is a problem with your Site Boundaries / boundary groups and their subnets. Are you certain that is all configured properly?

    Are your site based DPs healthy? Check you components health status here...

    Monitoring\System Status\Site Status

    Monitoring\System Status\Component Status

    If you browse to the Package in your Software Library, select the package and at the bottom of the page is all the package properties with a Content Status hyperlink far right under "Related Objects" if you click that hyperlink does the package status show up in the green success state? If not then the package is either faulty or has not been properly distributed.

    Tuesday, July 28, 2020 11:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,


    The first thing to check when you experience application download failures is for missing or misconfigured boundaries and boundary groups. For example, if the client is on the intranet and not configured for internet-only client management, its network location must be in a configured boundary. There must also be a boundary group assigned to this boundary for the client to download content. For more information, see:
    Define site boundaries and boundary groups

    Also, make sure it's distributed to a distribution point. To verify this configuration, use the in-console features to monitor content distribution to the distribution points. For more information, see:
    Monitor content you have distributed



    Best Regards,
    Larry

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, July 29, 2020 9:06 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It seems to be misconfiguration with AD Sites at sites that cannot deploy software. Worked with another admin and checking out the client logs (Locationservices) with one of the desktops at site that is having issues with deploying software to find out this evaluation.  We was seeing in the log, unable to retrieve AD site membership and Client is not boundary group even though distribution point for those site are setup.  The subnets within the sites with issues that is setup within boundary, boundary group, distribution point, and distribution point group are not matching with IP subnets with Windows Clients at those sites. 
    Friday, August 7, 2020 3:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It seems to be misconfiguration with AD Sites at sites that cannot deploy software. Worked with another admin and checking out the client logs (Locationservices) with one of the desktops at site that is having issues with deploying software to find out this evaluation.  We was seeing in the log, unable to retrieve AD site membership and Client is not boundary group even though distribution point for those site are setup.  The subnets within the sites with issues that is setup within boundary, boundary group, distribution point, and distribution point group are not matching with IP subnets with Windows Clients at those sites
    Friday, August 7, 2020 3:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It seems to be misconfiguration with AD Sites at sites that cannot deploy software. Worked with another admin and checking out the client logs (Locationservices) with one of the desktops at site that is having issues with deploying software to find out this evaluation.  We was seeing in the log, unable to retrieve AD site membership and Client is not boundary group even though distribution point for those site are setup.  The subnets within the sites with issues that is setup within boundary, boundary group, distribution point, and distribution point group are not matching with IP subnets with Windows Clients at those sites
    Friday, August 7, 2020 3:12 PM