This is probably the most common type of problem for any Configuration Manager Site admin to wrestle with. For some reason, clients just stop running Advertisements for Application and Update installations. This is not about Advertisements which report “Succeeded” (yet don’t install), or “Failed”. This is really about those which show “No Status”, “Accepted” or “Waiting”, yet never seem to get moving.
David is an author and consultant, working for Endurance IT Services in Virginia Beach, Virginia, specializing in Microsoft enterprise systems and Business Process Automation.
Latest posts by David Stein (see all)
- How to deploy a scripted application installation with SCCM 2012 - Mon, Sep 23 2013
- How to deploy an MSI package with SCCM 2012 - Mon, Aug 19 2013
- SCCM 2007 – General client troubleshooting tips - Tue, Aug 6 2013
Symptoms ^
- Users report that expected Software applications are not being installed.
- Reports show Advertisements in a “Waiting” state, seemingly indefinite.
- Distribution Points seem to be taking too long to replicate or update content
Potential Causes ^
- Package or Deployment content has not been copied to the required Distribution Point (DP) servers. This is often associated with having only a single DP server, or in protected DP server environments where there is no “fallback” unprotected DP accessible to the client.
- A previous Advertisement completed and requires the computer to be rebooted before it will run the next Advertisement.
- Another Advertisement is stuck in a “Running” state, causing other Advertisements to report “Waiting” on another Advertisement.
- Advertisement was set to “Run only when a user is logged on”, but no users have logged on to the affected computers since it was assigned, or users have logged on during a time period outside of an assigned Maintenance Window schedule.
- Client roamed into a different Site in the hierarchy but hasn't obtained the correct DP server yet.
- Client roamed into a different Site in the hierarchy after receiving the Advertisement policy assignment in the originating Site, but the current Site does not have the package content available on the Site's DP server
- The Advertisement was received by the client too close to the beginning of a closing Maintenance Window schedule, or was received outside of an applied Maintenance Window.
- Double-Bonus! Client IP subnet was reconfigured by someone such that it no longer resides in a Site Boundary within Configuration Manager.
