This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 16%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
All my clients pointed to a new dp seems not able to install mandatory application, they just stuck in Waiting to begin installation status. No issue on mandatory packages or optional applications. Machines are added into AD group and query by collection. If I removed the machine from collection, update policy and then readding them then I can see the app will be install automatically after policy updated again.
All machines is boot up via pxe and built via a osd task sequence. Hence machine object is precreated in sccm and AD.
Anyone has any idea why this happens?
Hi, @Viccc
Thank you for posting in Microsoft Q&A forum.
When there is "Waiting to begin installation" state, normally it indicates that there is already a running process and it has to wait until the process is end. Check that in the software center if there is other task shown as "installing".
And make sure boundary group are configured correctly and the application is distributed to DP successfully when it shows "Waiting to begin installation".
Also we may check AppEnforcr.log, AppDiscovery.log, AppIntentEval.log and CAS.log for detailed information
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks and understand. I have verified there is no other applications or packages or patches running. This seems happens on all machines pointed to this pull dp. The status remains after machine restart, reinstall client, it jjust never get install automatically. Verified appenforce, intent, and discovery does not find any error.
I do have several warnings mentioned "calling back to empty distribution list" in locationservices.log, but this shall be due to I have several applications which currently unable to distribute to the said dp as those just stick in progress status forever. Updating content for those apps seems able to resolve this but it need a plan as it impact thousand of apps.
Back to my issue, I have confirmed those apps stuck in waiting to begin installation having content downloaded in ccmcache, I can trigger wmi command to kick start them for installation. I just keep scratching my head why those apps is not install automatically.
Forgot to mentioned, appenforce.log doesn't update for several days, means no apps is actually install.
Hi, @Viccc
The issue could because of there are mismatches between in DP WMI and PkgLib, we may need to delete those entries and updated the content ID for apps.
For the reference:
https://www.reddit.com/r/SCCM/comments/lct7xh/software_center_status_showing_as_waiting_to/
https://thoughtsonopsmgr.blogspot.com/2014/09/sccm-2012x-package-data-in-wmi-is-not.html
(Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.)
At the end after I distributed those mandatory application required by the machines, the issue has been resolved. I not sure it is due to MS keep all required applications into a group when it run policy update first time after machine build. Some how if partial app content is not on dp, then it cause other apps with content downloaded stuck in waiting to begin installation status. So far I got all the required apps distributed to the dp and building few test machines, issue no longer exist.