SCCM – A new version (2107) of SCCM Current Branch has been released and this is what you need to know

If you are using System Center Configuration Manager Current Branch (aka SCCM, aka Microsoft Endpoint Configuration Manager) a new version – 2107 – has just been released and there few things you need to know.

In case you did not follow the previous releases, support for the “Application Catalog Website Point” and “Application Catalog Web Service Point” server roles has been deprecated since the 1910 version of SCCM.

Until then there was not real prerequisites warning when deploying new version but with the version 2107 you now have a prerequisites check warning.

While you can bypass the prerequisites warnings to continue the installation you should remove these roles prior to the update the new version (see https://docs.microsoft.com/en-us/mem/configmgr/apps/plan-design/plan-for-and-configure-application-management#remove-the-application-catalog)

Also, SCCM (as many Microsoft products) relies on .Net Framework. Well in a very near future (probably the next version), the .Net version required to deploy SCCM will be 4.8. (see https://go.microsoft.com/fwlink/?linkid=2165437)

Same as for the application catalog role, you will get a prerequisites check warning if you are not yet running .Net Framework on your SCCM servers.

You can install .Net Framework 4.8 after you have upgraded to 2107 but as it requires a server restart you need to plan it in your CAB for SCCM upgrade.

As always if you want to force your SCCM environment to detect the new version for in-console update you can use the PowerShell script available at https://go.microsoft.com/fwlink/?linkid=2099733