SCCM/MECM 2107 Prerequisite Warnings - .net 4.8 and Application Catalog Roles unsupported

bwilkerson217 21 Reputation points

I was going to apply the update to my SCCM/MECM from 2103 to 2107 and received a couple warnings.

First it said that .Net 4.8 is not installed but when I check the .Net Framework it reports as 4.8.03761

Secondly I get an the message that "Application Catalog Roles are Unsupported" but I cannot pinpoint what that means. The detailed description on that is as follows:

[Completed with warning]:The application catalog website point and application catalog web service point site system roles are unsupported. For more information, see

MECM is running on Server 2016 with the latest cumulative updates. Database is on a separate server running Server 2016/SQL 2017.

Last time i applied a version update to SCCM/MECM that showed warnings I had some major issues that my organization had to pay Microsoft to resolve and I am very apprehensive to apply this update until I can verify what this all means.

Any information or insight on this would be most appreciated.

Microsoft Configuration Manager
{count} votes

Accepted answer
  1. Jason Sandys 31,186 Reputation points Microsoft Employee

    The application catalog (the two corresponding roles) hasn't been supported since 1910 so removing the roles won't break anything. See details at

3 additional answers

Sort by: Most helpful
  1. Andreas 1 Reputation point

    I also removed the roles "application catalog website" and "application catalog web service", but now i do not see application deployments for users anymore... do anyone has the same issue?

    0 comments No comments

  2. Emmanuel Toupet (SFPD) 1 Reputation point


    Same issue too. Applications deployed for users disappeared.
    If I disable the CMG traffic or remove the CMG from the boundaries group, applications are back in software center.

    Could you advice please?


  3. Andreas 1 Reputation point

    For me it helped to give the user "NT AUTHORITY\NETWORK SERVICE" the permission "Execute" on the SCCM database (found in another forum)...

    0 comments No comments