Download and own this SCCM Installation Guide in a single PDF file.

The PDF file is a 162 pages document that contains all informations to install and configure SCCM Current Branch. Use our products page or use the button below to download it .

Download


Icon Info

This blog post has been updated. Please refer to the new SCCM Current Branch Installation Guide.

In this part of SCCM 2012 and SCCM 1511 blog series, we will describe how to install SCCM 2012 R2 or SCCM 1511 Fallback Status Point (FSP).

Role Description

The FSP helps monitor client installation and identify unmanaged clients that cannot communicate with their management point.

This is not a mandatory Site System but we recommend to install a FSP for better client management and monitoring. This is the Site System that receive State Message related to client installation, client site assignment, and clients unable to communicate with their HTTPS Management Point.

If the FSP is not configured properly you’ll end up having  A fallback status point has not been specified errors in your logs.

sccm 2012 install fallback status point

Site System Role Placement in Hierarchy

This Site System is a hierarchy-wide option. It’s supported to install this role on a child Primary Site or stand-alone Primary Site but it’s not supported on a Central Administration site nor Secondary Site.

FSP Installation

  • Open the SCCM console
  • Navigate to Administration / Site Configuration / Servers and Site System Roles
  • Right click your Site System and click Add Site System Roles
  • On the General tab, click Next

sccm 2012 install fallback status point

  • On the Proxy tab, click Next

sccm 2012 install fallback status point

  • On the Site System Role tab, select Fallback Status Point, click Next

sccm 2012 install fallback status point

  • On the Fallback Status Point tab, specify the number of state messages to process. We recommend to leave the default value, click Next

sccm 2012 install fallback status point

  • On the Summary tab, review your setting and click Next

sccm 2012 install fallback status point

  • Wait for the setup to complete and close the wizard

Verification and Logs files

  • Smsfspsetup.log – Detailed FSP Installation status

sccm 2012 install fallback status point

  • Fspmgr.log – Verify whether clients are successfully sending state messages to the FSP

You can also check if reports that depend on the FSP are populated with data. See the full list of reports that rely on the FSP here.

Configure clients

Use the FSP client properties to point your clients to your newly created FSP

  • Navigate to Administration / Site Configuration / Site
  • Click the Client Installation Setting icon on the ribbon
  • Select Client Push Installation
  • On the Installation Properties tab
  • Enter your server FQDN in the FSP properties

sccm 2012 install fallback status point

Comments (7)

Rash

04.15.2019 AT 11:24 AM
Better late than never... One of the reasons for the FSP is to allow machines which cannot communicate to their FSP via HTTPS an avenue of fault reporting. Having an Internet enabled FSP would require HTTPS... so that kinda defats the purpose of the object (or vice versa!).

unmanaged dedicated server hosting

08.13.2018 AT 09:32 AM
The sound is bad

SCCM_BUFF

11.04.2015 AT 10:32 AM
Can i install Fallback system role once all the client are installed in organistion ? is it necessary to mention FSP in client installation paramater, cant this be done automatically

Benoit Lecours

11.04.2015 AT 05:07 PM
Yes you can install it after client installation. FSP will be automatically assigned if you have just one, the FSP parameter is used to set your client manually to a specific FSP.

hari

06.22.2015 AT 03:57 PM
Hi Benoit, Thank you for your configuration details on Fallback Status Point. We are running into a problem when configuring the FSP role to support Internet Clients. We have SCCM 2012 SP1 in our company and I have installed FSP role on a dedicated server with intranet FQDN first having Intranet only option. Now when I add the Internet FQDN in Site System properties of this FSP Server, I'm unable to get the option "Allow both intranet and Internet client connections" under Allowed Client Connections. I have already attempted to reinstall the FSP role with Intranet & Internet FQDN together, but still I'm only getting the Intranet Client option. Please suggest or advice which part I'm missing here to configure the FSP for Internet clients as well. Your help will be much appreciated!