The deployment of a task sequence to customers can be done via the Internet. This scenario, which has already been present for several versions of Configuration Manager, has been improved with the 2010 version.

It is now possible to start the update or installation of a Windows 10 workstation from a boot media.

Orchestration groups start with Configuration Manager 2002. This features permit to create a group for control the deployment of Software update.

With this orchestration group, you can update devices based on percentage, explicit order, etc…. The member can be any Configuration Manager client. You can apply rules to any collections and all software update groups.

Since version 1906 of Configuration Manager, it is possible to install a Microsoft Connected Cache server on distribution points. This functionnality has been renamed Microsoft Connected Cache with version 1910 of Configuration Manager. This server is a Transparent on-demand caching server for uploaded content through distribution optimization. It is possible to limit the use of this server using client settings. So it is easy to limit access to this feature only to the local Configuration Manager client.

What is Tenant attach ?

The tenant attach solution allows devices present in SCCM to be managed by Microsoft Intune. This will make it possible to manage them in Microsoft Intune as well.

The tenant attach functionality requires the following prerequisites.

• An account with Global administrator rights in the Intune tenant.

• The AD user is synchronised with Azure AD

With sccm, it is possible to use reports natively using SQL reporting. If you want more advanced reports, more ergonomic, … It is possible to integrate Power BI with SCCM. This way you will be able to use all the power of Power Bi with SCCM.

The Configuration Manager solution is enriched with a new functionality at the application deployment level. Introduced with the latest versions of Configuration Manager, feature Approve Application request feature can now be used.

This functionnality is implemented from sccm 1906. He permit to deploy multiple application as a single deployment. With SCCM 1910, users can uninstall the app group. The App group can be deployed to a user collection. It is possible to specify the order in which the applications are installed in the group.

Using MBAM with SCCM

SCCM 1910 provides full BitLocker lifecycle management. He replace MBAM(Microsoft BitLocker Administration and Monitoring). Configuration Manager provides these capabilities for BitLocker Drive Encryption:

Site Server high availability

With System Center Configuration Manager, you can have redunndancy role with multiple instance of role (Distribution point, …). Configuration Manager 1806 permit to have high availability for Site Server role (it’s not possible before 1806 version of Configuration Manager). For the central administration site and child primary site, you need have 1810 version of Configuration Manager.