Forum Discussion
Existing required application deployments policy is not sent to devices
I have couple hundred applications in SCCM/MCM that are set to required and whenever there is a new device is built, all these required applications automatically get installed. I am on 2503 and 5 days ago i started seeing this issue. But if modify that deployment with current date and time then the application gets deployed right away if i run Application Deployment evaluation cycle. I also tested by deleting the existing deployment and created a new required deployment and run Application Deployment evaluation cycle then the application installs right away. The problem seems like the Primary server is not sending the policy to the client for existing deployments.
The application compliance that we see for every deployment under Monitoring for all the devices moved to Error with Success. Not sure why this is happening. All these changes i noticed in the last one week.
A week ago all these Already Compliant and Success status device count is under Success tab. Let me know if you have any suggestions.
5 Replies
- undefined
Those CI timeout errors usually point to the client struggling to download or process existing application policy metadata, not an installation issue.
Since recreating or modifying the deployment fixes it, it suggests the existing CI versions aren’t being re-evaluated properly. I’ve seen this happen when there’s a site-side policy or MP/IIS issue causing CI downloads or delta policies to time out.
Given this started recently and across many devices, I’d focus more on overall policy infrastructure health (MP, IIS, SQL, recent site maintenance) rather than the applications themselves.
Upgrade to 2509 🙂
Hi MCM1
You could try the following:
- Restart SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER on the Primary to force policy regeneration for existing assignments.
- Restart SMS_MP and recycle IIS app pools on the Management Points to clear cached policies.
- Since you’re already on 2503, upgrading to 2509 may resolve the issue.
Yesterday, I upgraded to 2509 and this did not resolved the issue. For a while this issue seemed like it was resolved when i changed default client polling interval from 15 mins to 60 mins. Everything seemed to work for 1 month and then the issue surfaced again. I also did what you suggested above.
