A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
It would be useful to add a bi-weekly option. Weekly is not enough time for Pilot/QA testing prior to a production push, and monthly isn't often enough with the varied release cycle of the 3rd party products.
I'm going to mark this as shipped. The bi-weekly should be pretty easy to implement with the /syncnow feature we implement since this request.
Cody,
My comment was geared toward whomever submitted this request, I don't actually want it, tbh. ADRs should take care of the actual Deployment of updates.
@NicW We were discussing this internally and trying to understand the value of a bi-weekly sync. Ultimately the release of the updates to your environment is controlled by the deployments you create, and not the synchronization of the publishing service. More than happy to discuss this further to better understand the requirement.
Currently, you could create your own schedule using a scheduled task, or any scheduling mechanism, and use the feature that was linked in another comment to trigger the synchronization from the command line. Does that capability fill this request?
https://ideas.patchmypc.com/ideas/PATCHMYPC-I-413
With this idea shipped: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-413
You could use the task scheduler and do any kind of schedule you want.
I agree with adding bi-weekly supprt, but I'm curious what the concern is about publishing every week or every day? The Publishing process doesn't create any deployments, so nothing is being pushed out by PMP though SCCM.