anonymous user-1505
Here is an answer to your question that hopefully you find helpful!
When using the sequence rule, if one member fails to patch and reboot, the orchestration will not progress through other any members.
In the Assets and Compliance> Orchestration Group node, select an orchestration group. In the ribbon, select Show Members. We could see the members of the group, and their orchestration status.
are you patching all non-DC servers using OG and then patching the DC's separately?
We may put both DC servers and non-DC servers in the same Orchestration group. We may also have one collection for all DC servers and one collection for non-DC servers.
If you had 300+ servers to patch, would it be advisable to patch all in one night? We do use maintenance windows, so we would extend our MW to be 5-6 hours?
Yes, it could usually be done. We have a relatively large number of machines, and we could extend the maintenance window appropriately.
Here are some articles that introduce Orchestration group for reference:
https://learn.microsoft.com/en-us/mem/configmgr/sum/deploy-use/orchestration-groups
https://argonsys.com/microsoft-cloud/library/orchestration-groups-with-microsoft-endpoint-configuration-manager/ (Third-party link, just for your reference.)
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.