Installing Site System Roles In Configuration Manager 2012 R2


In this post we see the steps for installing site system roles in configuration manager 2012 R2. These roles are added to extend the management functionality of the site. In this post we will be installing the Application catalog website point, Application catalog web service point and Fallback status point. There are many sites system roles available in configuration manager 2012 R2, we shall install them when it is required. You can find the step-by-step guide for SCCM 2012 R2 here.

Before we start installing site system roles in configuration manager 2012 R2 we will see a brief description about each and every site system role.

Site System Roles

Site System Role – A computer on which you run the Configuration Manager setup program and which provides the core functionality for the site. Any computer, either server or workstation, hosting a site system role is referred to as a site system server.

Site Database Server – Site Database Server hosts the SQL Server database, which stores information about Configuration Manager assets and site data.

Component server – This is any server running the ConfigMgr Executive service.

Management point – Provides policy and service location information to clients and receives configuration data from clients. The Management Point facilitates communication between a client and site server by storing and providing policy and content location information to the client, and receiving data from the client such as status messages and inventory.

Distribution point – Contains source files for clients to download, such as application content, software packages, software updates, operating system images, and boot images.

Reporting services point – This role is used to integrate reporting through SQL Server Reporting Services and is required if using reports.

State migration point – Stores user state data when a computer is migrated to a new operating system during OSD.

Software update point – Integrates with Windows Server Update Services (WSUS) to provide software updates to Configuration Manager clients.

System Health Validator point – Validates Configuration Manager Network Access Protection (NAP) policies. This role must be installed only on a NAP health policy server.

Endpoint Protection point – This is an optional site system role that Configuration Manager uses to accept the Endpoint Protection license terms and to configure the default membership for Microsoft Active Protection Service.

Fallback status point – The FSP provides an alternative location for clients to send up status messages during installation when they cannot communicate with
their management point. This role helps you monitor client installation and identify the clients that are unmanaged because they cannot communicate with their management point.

Out of band service point – Provisions and configures Intel AMT-based computers for out of band management.

Asset Intelligence synchronization point – Connects to System Center Online to download Asset Intelligence catalog information and upload uncategorized titles so that they can be considered for future inclusion in the catalog.

Application Catalog web service point – Provides software information to the Application Catalog website from the Software Library.

Application Catalog website point – Provides users with a list of available software from the Application Catalog.

Enrollment proxy point – Manages enrollment requests from mobile devices so that they can be managed by Configuration Manager.

Enrollment point – Uses PKI certificates to complete mobile device enrollment and to provision Intel AMT-based computers.

Installing Site System Roles In Configuration Manager 2012 R2 is pretty simple but you must check if the role is really required. In this post we will be installing Application Catalog web service point, Application Catalog website point and Fallback status point. Application Catalog Website Point site system role provides users with a list of available software. When the SCCM client is installed on a computer, the software center includes a link to Application Catalog. The Application Catalog shows the users, list of available softwares. This will be possible only when you install the roles. The Application Catalog Web Service Point system role provides information about available software from the Software Library to the Application Catalog website.

Open the Configuration Manager console, Select Administration, Under Site Configuration select Sites. Click on Add Site System Roles.

Installing Site System Roles In Configuration Manager 2012 R2

Leave this page to default and click on Next.

Installing Site System Roles In Configuration Manager 2012 R2

If you have an Internet proxy server please specify the details here, else click Next.

Installing Site System Roles In Configuration Manager 2012 R2

Select Application Catalog Web Service Point, Application Catalog Website Point, Fallback status point. Click Next.

Installing Site System Roles In Configuration Manager 2012 R2

Leave the fallback status point settings to default and click Next.

Installing Site System Roles In Configuration Manager 2012 R2

Application catalog website communicates with Application catalog web service point using port 80. Do not change anything here, Click Next.

Installing Site System Roles In Configuration Manager 2012 R2

Click on Next.

Installing Site System Roles In Configuration Manager 2012 R2

Provide the Organization Name and choose the color. With the below customization when an user opens the Application Catalog link from his computer, user would see that website theme color is Blue and organization name is what we have entered. Click Next.

Installing Site System Roles In Configuration Manager 2012 R2

Alright, we have added the site system roles. Lets check if they are installed correctly.

Installing Site System Roles In Configuration Manager 2012 R2


You can check logs of Application catalog website point by opening the log file named awebsctl.log. The log file is located in C:\Program Files\Microsoft Configuration Manager\Logs. Look for the line AWEBSVC’s http check returned hr=0, bFailed=0. Wait for few minutes while we see the change in the status.

Installing Site System Roles In Configuration Manager 2012 R2

We see that the AWEBSVC’s status is changed from failed or unknown to online.

Installing Site System Roles In Configuration Manager 2012 R2 Snap12

To check Application catalog Web service point log role installation details, open the log file awebsvcMSI.log with CMtrace log viewer and look for the line Application Web Service — Installation Operation Completed Successfully.

Installing Site System Roles In Configuration Manager 2012 R2


  1. Prajwal, I’m lost on adding MP/DP along with PXE role. Is it possible if you would assist, please. Your tutorial doesn’t include these roles. Thanks. Reza

    • after 1 hr, its showing as online..thts a long time!!!!! the log file keeps on gettin updated even after the site role installation. why ?

      • any changes that is being made including the installation for that role, the respective log file is updated. If you are sure that the role is installed and the status is online then no need to worry. Open the log file only when you need to troubleshoot.

  2. Hi Prajwal

    First I would like to take the time to thank you for your guides they have been invaluable in my quest to learn and understand SCCM 2012.

    I have previously install SCCM all seemed fine but had problem with the MP and deploying a capture of Win 7 x64 (Part 16 of your guide). The build would fail just after entering the password, I checking the smspxe after and was getting issues communicating with the MP..
    I have now reverted to a snapshot of just after the SCCM Install to make sure I have followed the POST Setup part of your guides and have not inadvertently messed something up.
    I had a look for awebsctl.log but it is not present in the log folder I also look in the smspxe and the following error below has already show even though I have not added a build or TS yet.

    “InstallBootFilesForImage failed. 0x80004005 SMSPXE 04/03/2015 08:31:07 4124 (0x101C)
    Warning: Failed to copy the needed boot binaries from the boot image C:RemoteInstallSMSImages0100002boot.00100002.wim.
    The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 04/03/2015 08:31:07 4124 (0x101C)
    Failed adding image C:RemoteInstallSMSImages0100002boot.00100002.wim. Will Retry..
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 04/03/2015 08:31:07 4124 (0x101C)”

    Can you help or guide me in sorting out this issue?

    Also do you need to install VM Workstation drivers for the capture deployment to work?



  3. “awebsctl.log but it is not present in the log folder” – When you revert to snapshot, check if you have installed App catalog website point role.

    1) Install the PXE role again.
    2) Make sure the network access account is configured.
    3) verify if “Deploy this boot image from the PXE-enabled Distribution point ” is checked.
    4) Add the Network Access Account to the Remote Install share.
    5) update the boot images and make sure they are distributed to DP’s.
    80004005 – There is no fixed resolution for this error. We need to just make sure all the things are configured correctly before we deploy OS.

  4. Hello,
    I feel that I have followed your tutorial step by step until I came to a snug. please advise.

    I’ve resolved the issue by…
    I went in and installed a feature under .Net framework 3.5 > WCF Activation > Http activation. and that resolved the issue.

  5. Thinks for your great article, I followed your guide, but after add role, why I cannot find “CMApplicationCatalogSvc” in the “default web site”?

  6. @prajwaldesai:disqus Hey, I am a student trying to install System center for a project (needs to be finished end of next week), but for some reason users cannot connect to the application catalog.
    WFC is installed (reinstalled as well) This is what the logs say.

    And this is what the website shows on the client side:

  7. the log file called awebsctl.log

    AWEBSVCs http check returned hr=0, bFailed=0 $$
    AWEBSVC’s previous status was 0 (0 = Online, 1 = Failed, 4 = Undefined) $$
    Completed the AWEBSVC availability check against local computer. $$
    Waiting for changes for 60 minutes $$
    what is causing this?

  8. Hi Prajwal Desai,

    For my test environment I only have to provide a feature for my client so that he can do on custom image deployment/ force updates…
    Does that mean that I only have to install the features: Distribution point, software update point?
    Are there other features you recommend me installing? I have to say that he wants to keep it as simple as possible. I just have to show him the fundamentals he needs when doing Image deployment and forcing updates.
    Later on in my project, he might ask me to install more features, but is out of the assignment at the moment.

  9. I love your walk throu’s and they have pulled me out of some tricky spots but I have one that I am baffled with on SCCM 2021 SP1. The DP role is missing in from the Specify Roles for this server section. I have followed the prereq’s still no check box for DP. syscenter1 is my WSUS SUP and you were a great resource but I now want to setup syscenter2 as my OS deployment site.

  10. Hi Prajwal. I got my distro Points setup and pxe works (tested); however, when I go to add an image/OS it fails with UNC path does not contain a valid WIM or permissions. I was able to create a boot image in WDS using the same boot.wim and install.wim. Any ideas? I upgraded to SCCM 2012 sp2 fixed my WSUS issue but not the OS Deployment.

  11. Hi Prajwal,
    the Management Point site system role is not available in system role selection tab. what might be the issue?


Please enter your comment!
Please enter your name here