7 days by default.

The client settings that manage this is: Schedule re-evaluation for deployments

https://technet.microsoft.com/en-us/library/gg682067.aspx?f=255&MSPPError=-2147217396

• Edited by Frederick Dicaire Thursday, August 13, 2015 3:07 PM
• Proposed as answer by Jason SandysMVP Thursday, August 13, 2015 4:34 PM

7 days by default.

The client settings that manage this is: Schedule re-evaluation for deployments

https://technet.microsoft.com/en-us/library/gg682067.aspx?f=255&MSPPError=-2147217396

• Edited by Frederick Dicaire Thursday, August 13, 2015 3:07 PM
• Proposed as answer by Jason SandysMVP Thursday, August 13, 2015 4:34 PM

Sorry no clue on how to respond to this. The best thing to do would be to take baseline before the change and after the change.

But why 1 hour hard to believe that you change things so much that this would be required. You should look at why you need this to be 1 hour and maybe you need to change some of thing you are doing.

• Edited by Frederick Dicaire Thursday, August 13, 2015 7:19 PM

Sorry no clue on how to respond to this. The best thing to do would be to take baseline before the change and after the change.

But why 1 hour hard to believe that you change things so much that this would be required. You should look at why you need this to be 1 hour and maybe you need to change some of thing you are doing.

• Edited by Frederick Dicaire Thursday, August 13, 2015 7:19 PM

This action, as mentioned, re-evaluates *every* application regardless of current status and regardless of the scheduled frequency at the scheduled time. This is how the ConfigMgr client agent determines the current state of the deployed applications -- it is an active process -- so that it can remediate any applications that don't meet their expected state.

Changing it to every day is potentially a better option here -- it really depends upon your end goals and configuration of the settings within the toolkit.

Hello,

I had this question and didn't get satisfactory answers when I surfed through the internet.

I need to know how frequently does the "Application deployment evaluation cycle" run on a client PC by default and if that setting can be changed, where can I do it under the client settings?

7 days by default.

The client settings that manage this is: Schedule re-evaluation for deployments

https://technet.microsoft.com/en-us/library/gg682067.aspx?f=255&MSPPError=-2147217396

• Edited by Frederick Dicaire 16 hours 46 minutes ago
• Proposed as answer by Jason SandysMVP 15 hours 18 minutes ago

Thank you Frederick.

In the article above it says "We recommend that you do not change this value to a lower value than the default as this may negatively affect the performance of your network and client computers."

I am curious to know what impact it would create.

I have made a custom client setting and changed it to run every 1 hour and deployed it to 2500 machines. What impact would it possibly create?

Sorry no clue on how to respond to this. The best thing to do would be to take baseline before the change and after the change.

But why 1 hour hard to believe that you change things so much that this would be required. You should look at why you need this to be 1 hour and maybe you need to change some of thing you are doing.

• Edited by Frederick Dicaire 12 hours 33 minutes ago

Every hour? Why would you want to be this aggressive?

Basically, it will re-detect every application deployed to a system as required (by re-running the global conditions referenced as requirements in the deployment types of those applications) and reinstalling those not detected. This in turn could result in download traffic and state and status messages notifying the site of the activity.

Every hour? Why would you want to be this aggressive?

I am curious as well. What do you expect to improve by setting such an aggressive level?

Hmm.. if running this every hour would re-download and reinstall the application that are required, it should do the same even the setting is default (7 days) am I right? Or does it apply only to those applications that are waiting to install?

The reason I wanted to make this change is because we are using a toolkit (PowerShell App Deployment Toolkit) to deploy applications via SCCM and that one gives the user an option to differ from installing the application. So when the user does it, the application status in software center changes to "Past due - will be retried" and we wanted this application to retry installation in another 60 minutes. So I thought changing the client setting is the only option. And I opted for it..

If there would be another option, it would be great!

Thanks Jason for the explanation.

I have decided not to change the default setting and now I need another workaround.

I have planned to add a new return code for the applications to do a retry. When an application installation via the PowerShell toolkit is aborted, it returns an exit code as "5000" and I am adding this return code to do a fast retry within the application itself so that when the user aborts the installation, it does a "Fast retry"

I am not sure if this is a healthy approach but I would need some kind of a solution or a workaround to get this done.

Let me know if I have to open a separate thread to discuss this.  

This is something you might want to discuss with the people on the PowerShell App Deployment Toolkit forum.

SCCM by default doesn't allow us to deploy something as require but let the user postpone for 1 hour. This would require powershell scripting with the concept of a pause in it if the user press the wait box. But what happen if the user close the PC ? To many variable for it to be 100% sure thing are going to be install.

Why not just deploy the application as available and let the user install it when they want. You could also put a deadline after a while so the users don't have a choice.