I have just installed the Fallback Status Point role onto a newly created Windows 2008 R2 Site System with no other roles. The Installation seemed to complete successfully. No errors were found on the SMSFPSetup.log and fspMSI.log during setup and the fspmgr.log is showing the status messages in its FSPStaging folder being successfully copied. I can then run the Fallback Status Point Reports which are showing new status messages for new clients. However we started receiving the following message from SCOM:- ConfigMgr 2007 Monitor Component Health The script 'ConfigMgr 2007 Monitor Component Health' encountered a runtime error. Failed to initialize the object for component 'SMS_FALLBACK_STATUS_POINT' on this server. The error returned was: 'The configuration registry key could not be read.' -2147023884 (0x800703F4 I also noticed that the Availability column in Component Manager for the FSP Site System has returned the following for it listed components SMS_EXECUTIVE Unknown SMS_FALLBACK_STATUS_POINT Unknown SMS_MP_FILE_DISPATCH_MANAGER Online SMS_OUTBOX_MONITOR Online Following research I found that this information is held in the following registry key of each Site Server:- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\Operations Management\Components\<Component Name> The SMS_FALLBACK_STATUS_POINT and SMS_EXECUTIVE registry keys were both missing the Availability State and Execution State Values. Is this normal behaviour for a Fallback Status Point? I have also noticed that SMS_COMPONENT_MONITOR is missing from the Fallback Status Point System Server. I assumed that all Site Systems with roles added should have this component, is this correct?

Did you properly configure IIS on Server 2008 for SCCM? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Hi, If the FSP report works and you have no errors in the log files, then I would look at modifying the OpmsMgr. MP.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund