Menu
CCMEXEC.COM – Enterprise Mobility
  • Home
  • General
  • Configuration Manager
  • Windows 10
  • Intune
  • About the author
  • GitHub
CCMEXEC.COM – Enterprise Mobility

First look – Orchestration groups in MEMCM 2002

Posted on April 3, 2020April 3, 2020 by Jörgen Nilsson

Orchestration Groups is a new feature in Configuration Manager 2002 and replaces Server Groups which never made it out of pre-release.. Orchestration Groups is a pre-release feature that you need to enable if you intend to use it.
NOTE: Orchestration Groups will replace Server Groups if you are using that today and convert your Server Groups to Orchestration Groups.

I have been testing it out since MEMCM 2002 was released in fast-ring and it works really well and I love the new UI.

Orchestration Groups are basically a group of devices you want to install Software Updates to in a controlled way, with Pre and Post PowerShell Scripts that are executed on each device in the Orchestration Group. Could be for example SQL Servers, Clusters and multi layered applications.
We simply deploy our Software Updates to our collections as we normally do if the server is a member of an Orchestration group the Orchestration Group starts and we can track the progress in the Admin Console! Really Nice!

Before we create an Orchestration group let’s look at the limitations.
– A device can only be member of one Orchestration Group
– Max 1000 devices per Orchestration Group
– Make sure the Configuration Manager client is upgraded to at least MEMCM 2002
– If Software updates are installed from Software Center then Orchestration Groups are bypassed.

Create an Orchestration Group

We start with giving it a name.

Select the devices that should be members in the group.

We have three option:
– Allow a precentage of the machines to be updated at the same time
– Allow a number of machines to be updated at the same time
– Specify the the maintenance sequence

We can add a Pre-script, I used a simple one that writes the date and time it started to a log file, C:\Orchestration.log file. It will be executed on all the devices in the group.
Exit 0 = Success
Exit Code 3010 = Success with Reboot

We can use a Post-script as well, same hear it adds stop to the same log file on C:\Orchestration.log file.

The we are done!

How does it work?

We can start the Orchestration group manually using the UI to test it out. When we use it in production the Orchestration Group we simply deploy the Software Updates as normal and when the installation of Software Updates start the Orchestration Group kicks off.
When the Orchestration group starts we have nice UI to track the progress.

We can use Run Scripts for a server in a group and also start remote control to troubleshoot as well. Really nice!

What about log files then?
On the Site server we can track the progress in the SMS_Orchestration.log file.

On each device in an Orchestration Group we can track and troubleshoot the process using the MaintenanceCoordinator.log file, where we can see the Pre-script being executed as shown below for example.

When looking in the file system on one of the target devices we can see that my pre/post script writes to the Orchestration.log file

Conclusion, Orchestration groups is a pre-release feature in MEMCM 2002 which looks really promising! Test it out send frowns and smileys with what you like and what you are missing to the product group!

  • Configuration Manager
  • MEMCM
  • Orchestration Groups
  • SCCM
  • 2 thoughts on “First look – Orchestration groups in MEMCM 2002”

    1. Kenneth says:
      May 31, 2020 at 7:48 pm

      I dont know.. A feature with no automation ?
      Not very SCCM

      Reply
      1. Jörgen Nilsson says:
        May 31, 2020 at 9:37 pm

        But it is automated once you created the Orchestration groups, you just target the Software updates with your ADR and the orchestration group kicks of automatically.

        Reply

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    My name is Jörgen Nilsson and I work as a Senior Consultant at Onevinn in Malmö, Sweden. This is my blog where I will share tips and stuff for my own and everyone elses use on Enterprise Mobility and Windows related topics.
    All code is provided "AS-IS" with no warranties.

    Tweets by ccmexec

    Recent Posts

    • Logging the Co-management and Defender onboarding process during OSD
    • Show DP information during OSD using TSBackground
    • Using Install-language during AutoPilot Windows 11 insider
    • Co-Management and the importance of device token enrollment.
    • Windows 11 Insider Start Menu layout registry customizations

    ©2022 CCMEXEC.COM – Enterprise Mobility | WordPress Theme by Superb Themes
    This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.Accept Reject Read More
    Privacy & Cookies Policy

    Privacy Overview

    This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
    Necessary
    Always Enabled
    Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
    Non-necessary
    Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
    SAVE & ACCEPT