A fallback status point in Configuration Manager 2007 is a site system role that is used to help administrators monitor client deployment and identify any problems encountered during installation or assignment. It is also used to help identify clients that are unmanaged because they have problems communicating with their management point, which is particularly relevant for when the site is operating in native mode.

The fallback status point is an optional but recommended site system role that helps you manage clients and identify any client-related problems.

SMS 2003 client computers cannot use a fallback status point.

The fallback status point receives state messages from Configuration Manager 2007 client computers and then relays these back to the site. The state message system allows client computers to send short messages to the fallback status point or to the management point that indicate changes of state, for instance, success or failure. These changes of state are then made available to the administrator through a number of Configuration Manager 2007 reports. For more information about the reports generated from data using a fallback status point, see About Reports for Configuration Manager Clients.

There is no equivalent of the status message viewer for state messages.

If you decide to use a fallback status point, install and configure this site system role before you deploy clients. This allows you to assign the fallback status point when the client is installed. Although you can install more than one fallback status point for a Configuration Manager 2007 site, client computers can be assigned to only one fallback status point.

Using the Fallback Status Point for Client Deployment

Examples of state messages a client might send to a fallback status point if it encountered problems during client deployment include the following:

  • The client failed to install properly (for example, because of incorrect setup options or syntax errors, or because it failed to locate the required files).

  • The client failed to be assigned to a site.

  • The client failed to register with its assigned site.

  • The client failed to locate its management point.

  • There was a network connectivity problem between the client and the management point.

  • The management point is not configured correctly (for example, Internet Information Services (IIS) is not configured correctly for a Configuration Manager management point).

In addition to sending state messages when there is a problem during client deployment, the client will send a state message to the fallback status point when it is successfully installed and when it is successfully assigned to a Configuration Manager 2007 site. In this scenario, the client will also report if a restart is required to complete the installation.

Using the Fallback Status Point to Identify Native Mode Communication Problems

Because the fallback status point accepts unauthenticated communications, it accepts state messages from native mode clients when PKI certificate issues prevent communication between the client and its management point. Examples of state messages a client might send to a fallback status point to identify problems with native mode communication include the following:

  • There is no valid client certificate.

  • There is more than one possible valid client certificate without an appropriate certificate selection configuration specified.

  • A server certificate needed for native mode communication fails to chain successfully to the trusted root certification.

  • A server certificate needed for native mode communication is expired.

  • A server certificate needed for native mode communication is revoked.

See Also