Control update deployments with orchestration groups in Configuration Manager Technical Preview 1909

[Yvette O'Meally]

Update 1909 for the Technical Preview Branch of System Center Configuration Manager has been released.

New in TP 1909 is the orchestration groups feature which is an evolution of the Server Groups feature. You can create an orchestration group to better control the deployment of software updates to devices. This gives you the flexibility to update devices based on a percentage, a specific number, or an explicit order. You can also run a PowerShell script before and after the devices run the update deployment.

Learn more about Orchestration Groups

This preview release also includes:

Improvements to BitLocker management - Starting in technical preview version 1905, you could use Configuration Manager to install and manage the Microsoft BitLocker Administration and Monitoring (MBAM) client. This release now adds support for integrated reports, a helpdesk portal for administration and monitoring, and a self-service portal for users.

Extend and migrate an on-premises site to Microsoft Azure - This new tool helps you to programmatically create Azure virtual machines (VMs) for Configuration Manager. It can install with default settings site roles like a passive site server, management points, and distribution points. Once you validate the new roles, use them as additional site systems for high availability. You can also remove the on-premises site system role and only keep the Azure VM role.

Additional CMPivot entities and enhancements - Based on user-voice feedback, we've added a number of new CMPivot entities and entity enhancements to aid in troubleshooting and hunting. We've included entities to query:

• Windows event logs
• File content
• Dlls loaded by processes
• Azure Active Directory information
• Endpoint protection status

This release also includes several other enhancements to CMPivot.

Task sequence download on demand over the internet - Starting in this release, the task sequence engine can download packages on-demand from a content-enabled CMG or a cloud distribution point. This change provides additional flexibility with your Windows 10 in-place upgrade deployments to internet-based devices.

Improved language support in task sequence - Starting in technical preview version 1908.2, you could specify the default keyboard layout (Input locale) during OS deployment. This release adds further control over language configuration during this process. If you're already applying these language settings, this change can help you simplify your OS deployment task sequence. Instead of using multiple steps per language or separate scripts, use one instance per language of the built-in Apply Windows Settings step with a condition for that language.

Support for Windows Insider - You can now service and update devices running Windows Insider Preview builds with Configuration Manager. This change means you can manage these devices without changing your normal processes or enabling Windows Update for Business. You can download feature updates and cumulative updates for Windows Insider Preview builds into Configuration Manager just like any other Windows 10 update or upgrade.

Update 1909 for Technical Preview Branch is available in the Configuration Manager Technical Preview console. For new installations please use the 1907 baseline version of Configuration Manager Technical Preview Branch available on TechNet Evaluation Center. Technical Preview Branch releases give you an opportunity to try out new Configuration Manager features in a test environment before they are made generally available.

We would love to hear your thoughts about the latest Technical Preview! Send us Feedback directly from the console. You may also use our feedback channels through the Feedback Hub app for product issues, and our UserVoice page for ideas about new features.

Thanks,

The Configuration Manager team

Configuration Manager Resources:

Documentation for System Center Configuration Manager Technical Previews

Try the System Center Configuration Manager Technical Preview Branch

Documentation for System Center Configuration Manager

System Center Configuration Manager Forums

System Center Configuration Manager Support

[Joern_Rink]

Hi Yvette, its a step in the right direction. But some of our customers need a fixed patchrelease für more than one month, because of restricted testing scenarios. When they began to test an application, during the whole release phase of the application, it is necessary not to touch the OS level. Yes, this sounds strange and i do not want to discuss this here. I want to discuss the possibility to hold a Software Update Group content fix and robust against a WSUS or SUP sync. Which means do not touch expired or superseeded or any update in this SUG. ATM this is not possible in SCCM CB. The alternative is to repackage OS Patches in applications or packages. But this is not what we want. Also an alternative is, not to sync WSUS or the SUP, but we have a mixed scenario and we have to patch the rest of our customers. to bring it to the point: From a software release point of view, give us the possibility to have fixed patch software bundles.

[pshMike]

Have you looked at creating specific SUG(s) for this scenario? You could have a collection of devices ( AppX Devices ) and then create a specific SUG just for that collection and deploy that SUG to that collection.  Creating or modifying other SUGs wouldn't impact the set of updates that are deployed to AppX.

Mike J