[Post contributed by Carol Bailey]
Thanks to a recent Configuration Manager TechNet forum posting, I realized that we hadn't documented the prerequisites for the fallback status point, apart from saying that it required IIS. When we released Configuration Manager 2007, we didn't support Windows Server 2008, and configuration for IIS was much simpler. Consequently, I'm not aware of any problems installing this optional site system role on IIS 6.0.
Then, with Configuration Manager SP1 we supported Windows Server 2008 with IIS 7.0 and we had to detail the IIS configuration in order for our site systems to work: How to Configure Windows Server 2008 for Site Systems. For some reason, the fallback status point wasn't included. We knew that it had fewer configuration requirements than many of the other site systems, and following the same instructions for the management point was a safe bet because they share common components. But we were missing what the minimal requirements were, so sent out an urgent request to the product group - and Jeff Nordrum came to the rescue.
Jeff confirmed the following requirements, how to verify installation, and even some troubleshooting tips. We got this information just in time to update the prerequisites in the Configuration Manager library for the February update. However, we didn't have time to incorporate the useful verification/troubleshooting information, so in case anybody is having problems getting the fallback status point to work, I'm including this additional information here.
Fallback Status Point Prerequisites
Windows 2003 Requirements:
How to Verify & Troubleshoot Installation of the Fallback Status Point
Use the following log files to verify and help troubleshoot the fallback status point.
Fallback status point installation log files:
Verify the installation using both of these log files. They will log success or failure. If failure, search for ‘return value 3' in the fspmsi.log - log entry above this will contain the installation error details.
Fallback status point site system log files:
Use these log files to verify whether clients are successfully sending state messages to the fallback status point. You can also check that the reports that depend on the fallback status point are populated with data if clients are assigned to it - for example, "Client Deployment Status Details" (for list of reports that rely on the fallback status point, see http://technet.microsoft.com/en-us/library/bb633154.aspx).
This posting is provided "AS IS" with no warranties, and confers no rights.
I tell you what, Carol Bailey is a writing machine.  She had another article that posted yesterday
Feed: The Configuration Manager Support Team Blog Posted on: Thursday, February 19, 2009 9:31 AM Author
In case you missed them, the following posts were published on the System Center Configuration Manager
Hello. I've posted on TechNet but I've not had any answer to this as yet. I've got a number of dead machine accounts littering the FSP based reports. How can I purge them? Deleting the machines from Config Manager does not remove them from reports based upon FSP data.