PENDING How to have near realtime update in Software Center or Configuration Client

[Muhammad Awais]

I deployed an application for a collection and waited for 20 minutes until it was refreshed in the software center. Sometimes, the time would be even longer. It would be similar if there would be redployments of the revisions. Is there anyway to have more rapid refresh in the clients if an application is deployed for software center to show and offer for installation.

 

[Garth]

I deployed an application for a collection and waited for 20 minutes until it was refreshed in the software center. Sometimes, the time would be even longer. It would be similar if there would be redployments of the revisions. Is there anyway to have more rapid refresh in the clients if an application is deployed for software center to show and offer for installation.

There are a ton of variables here, it will depend on exactly how you are deploying the SW.

 

[SEHSCCM]

The Client Policy polling interval (aka Machine Policy) is what the SCCM client utilizes to check into SCCM for new applications. It is located here: \Administration\Overview\Client Settings\Default Client Settings\Client Policy in the SCCM console.

Be careful lowering this value too much. We have ours set for 30 minutes to try to alleviate the exact same concern you have. Keep in mind this can greatly increase network traffic.

You can always trigger an immediate machine policy sync for a client by clicking Client Notification\Download Computer Policy in the Assets and Compliance workspace in the SCCM console, or by clicking Options\Computer Maintenance\Sync Policy in Software Center on the actual endpoint in question. (Remember it takes about 2 minutes for policy to refresh before changes show up in Software Center).

 

[Garth]

Additionally, ensure that the Application Deployment Evaluation Cycle is also set to a shorter interval (e.g., 5 minutes) to force clients to check for new applications more frequently.

I would not do this as this does not do anything for deployment. This will only help if a user uninstall the app, it will force it to reinstall. The overhead on this to both ConfigMgr and the local system could be huge.