locked
Forefront Dashboard 14-Day Not Reporting

    Question

  • Hi,

    My Forefront management server has been working well for the past 2 months until this week. For the last 3 days, the bars in my 14-Day History are showing no data. I have ran the DTS job manually and made the initial database size for the System Center Report DB larger so am waiting to see if this has any effect.

    However, i made a schema change to the domain on the 16th which is when the first No Data bar occurs. The schema change was to extend the AD for a new SCCM 2007 installation. Would this have any effect on Forefront/MOM Reporting? And if so, how can this be fixed?

    Thanks

    PC

    Friday, March 19, 2010 3:23 PM

Answers

  • Hi,

     

    Hi PC,

    Thank you for the update.

     

    I think it is normal behavior. According the this article: http://technet.microsoft.com/en-us/library/bb418842.aspx. the number of N managed computers is equal to:

    •  
      • Computers reporting critical issues
      • Computers reporting no issues
      • Computers not reporting within the last 24 hours
      • Computers reporting non-critical issues

     

     But computers reporting non-critical issues are not reflected in dashboard totals.

     

    Regards,


    Nick Gu - MSFT
    Tuesday, March 30, 2010 1:27 AM
  • Thanks Nick. I thought it was normal but in the past I have had a 100% total on the 3 bar charts. Based on this I did some digging and found something on one of the PC's.

    I checked the MOM service dependencies and it was dependent on rpcss and eventlog. It should also be dependent on winmgmt. I have now used Group Policy Preferences to Update the MOM registry value to include the winmgmt service in its dependencies and have applied this to all PC's in the domain.

    The number of clients reporting out of date policies has dropped by 1000 and bar charts are totalling above 75%. This seems to have done the trick.

    • Marked as answer by P_Ch Tuesday, March 30, 2010 1:35 PM
    Tuesday, March 30, 2010 1:35 PM

All replies

  • Hi,

     

    Thank you for the post.

     

    On the FCS Server, please check the following registry key:
    HKLM\SOFTWARE\Microsoft\Microsoft Forefront\Client Security\1.0\Config\SRS

    The following values should not be blank. You can manually add the following REG_SZ values:

    "MachineName"="<FCS Server Name>"
    "ReportRoot"="ReportServer"
    "ReportURL"="http://<Reporting Server Name>/ReportServer"
    "ReportManagerRoot"="Reports"
    "ReportManagerURL"=
    http://<Reports Server Name>/Reports

     

    Meanwhile, I find the following two similar post may help you:

    http://social.technet.microsoft.com/forums/en-US/Forefrontclientreporting/thread/5b011497-62d8-4bb3-90b6-00352e1ffb8b

    http://social.technet.microsoft.com/Forums/en-US/Forefrontclientreporting/thread/3d43a749-b73b-4cae-85f6-1462377816b3

     

    Regards,


    Nick Gu - MSFT
    Thursday, March 25, 2010 8:20 AM
  • Thanks Nick. I have been through the post that you have mentioned and the reg key you have said above is actually present. Neither solved the issue.
    I have now increased the size of the OnePoint database to 25GB and the SystemCenterReporting one to 30GB. I am hoping this frees up space to allow the items to be processed.
    Along with my 14 day history the bar chart totals do not equal 100% so I think this is all linked and will be resolved by this change. Currently, 2% of my clients are reporting critical issues, 29% are reporting no issues and 18% aren't reporting at all which leaves 51% of clients unaccounted for.
    Could there be any other causes?
    Thanks
    PC
    Friday, March 26, 2010 1:14 PM
  • Hi,

     

    Thank you for the update.

     

    I think it is normal behavior. According the this article: http://technet.microsoft.com/en-us/library/bb418842.aspx. the number of N managed computers is equal to:

    •  
      • Computers reporting critical issues
      • Computers reporting no issues
      • Computers not reporting within the last 24 hours
      • Computers reporting non-critical issues

     

     But computers reporting non-critical issues are not reflected in dashboard totals.

     

    Regards,


    Nick Gu - MSFT
    Tuesday, March 30, 2010 1:26 AM
  • Hi,

     

    Hi PC,

    Thank you for the update.

     

    I think it is normal behavior. According the this article: http://technet.microsoft.com/en-us/library/bb418842.aspx. the number of N managed computers is equal to:

    •  
      • Computers reporting critical issues
      • Computers reporting no issues
      • Computers not reporting within the last 24 hours
      • Computers reporting non-critical issues

     

     But computers reporting non-critical issues are not reflected in dashboard totals.

     

    Regards,


    Nick Gu - MSFT
    Tuesday, March 30, 2010 1:27 AM
  • Thanks Nick. I thought it was normal but in the past I have had a 100% total on the 3 bar charts. Based on this I did some digging and found something on one of the PC's.

    I checked the MOM service dependencies and it was dependent on rpcss and eventlog. It should also be dependent on winmgmt. I have now used Group Policy Preferences to Update the MOM registry value to include the winmgmt service in its dependencies and have applied this to all PC's in the domain.

    The number of clients reporting out of date policies has dropped by 1000 and bar charts are totalling above 75%. This seems to have done the trick.

    • Marked as answer by P_Ch Tuesday, March 30, 2010 1:35 PM
    Tuesday, March 30, 2010 1:35 PM
  • Dear,

                 I am also facing same problem regarding "Forefront Dashboard 14 day history showing no report"

     

     

    • Proposed as answer by Abhijit9 Saturday, June 26, 2010 5:52 AM
    Saturday, June 26, 2010 5:51 AM