SCCM Forefront Monitoring

not really sure where the issue is here. the monitoring tab of sccm2012 reports that i have 0 clients protected with endpoint protectiion when i select the collection of all systems. yet, all my client do in fact have forefront installed via my deployment
from the sccm agent, so i am not getting any reporting features in the console.
any help is appreciated
thanks
Ross Kotter
Systems Administrator
Microsoft Certified
Was This Post Helpful? Please Remember To Mark Post's As Helpful If It Assist's In Solving Your Issue.
If This Post Provides You With An Answer To Your Problem Please Be Sure To Mark As Answer.

yes, i am referring to SCCM forefront, i was pretty sure that it would have been interpreted that way by me describing my issue.
i had an issue last week that required me to remove the management point role and than re-install it due to some other probelms i was having. now that i have done that i noticed yesterday after my original post here that i am getting another error in
my site status for the management point.
this error repeats itself what looks like every hour in the message log. im assuming this is related to my issue
Ross Kotter
Systems Administrator
Microsoft Certified
Was This Post Helpful? Please Remember To Mark Post's As Helpful If It Assist's In Solving Your Issue.
If This Post Provides You With An Answer To Your Problem Please Be Sure To Mark As Answer.

Similar Messages

  • SCCM 2012 monitoring - Site Status - Reporting Services Point - Status Critical

    Hi all,
    I have noticed that the Site Status under Monitoring shows Reporting services point as in Critical state though we do not see anything wrong with SCCM as such (at least we haven't been reported any problems thus far). There is nothing in the event viewer
    on SQL Server. Just wanted to know how to resolve this issue. Could you help?
    When I try to open status messages for Reporting Services (for any days) it does not return anything as if there are no status messages for this role. Also, could you let me know the log file locations/names for Reporting services point?

    Here it is... I have replaced server names with a dummy name.
    =================
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.588-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.596-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.616-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.641-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.713-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.715-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.339-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.336-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.347-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.357-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.377-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.404-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.478-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.480-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.160-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.159-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.168-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.188-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.237-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.264-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.539-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.541-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.796-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.795-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.804-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.813-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.834-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.859-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.904-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.905-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.940-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.942-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.724-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.726-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.723-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.731-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.752-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.776-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.813-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.954-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.956-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.728-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.730-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.727-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.738-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.747-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.769-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.799-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.875-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.496-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.494-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.503-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.512-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.534-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.563-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.646-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.648-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.653-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.654-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.352-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.351-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.361-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.370-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.393-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.432-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.484-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.485-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.520-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.522-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.530-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.531-60><thread=6072 (0x17B8)>
    Next security configuration at [02/09/2014 13:31:30]  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
    Timed Out...~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.268-60><thread=6072 (0x17B8)>
    Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.277-60><thread=6072 (0x17B8)>
    Reporting Services is running  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.286-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.308-60><thread=6072 (0x17B8)>
    Confirmed version [10.50.4000.0] for the Sql Srs Instance.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.334-60><thread=6072 (0x17B8)>
    Retrieved datasource definition from the server.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.380-60><thread=6072 (0x17B8)>
    Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.381-60><thread=6072 (0x17B8)>
    Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.421-60><thread=6072 (0x17B8)>
    Looking for 'English (United Kingdom)' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.423-60><thread=6072 (0x17B8)>
    Looking for 'English' resources  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
    Found resources for 'English'  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
    Confirmed the configuration of SRS role [ConfigMgr Report Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.088-60><thread=6072 (0x17B8)>
    Confirmed the configuration of SRS role [ConfigMgr Report Administrators].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.098-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.700-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.736-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.758-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.791-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.815-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.849-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.870-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.906-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.929-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.961-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.998-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.033-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.067-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.099-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.127-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.155-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.192-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.221-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.265-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.303-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.326-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.362-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.381-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.413-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.432-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.470-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.495-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.529-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.551-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.585-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.609-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.642-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.666-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.700-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.724-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.755-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.778-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.815-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.835-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.867-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.888-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.924-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.952-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.985-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.007-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.042-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.073-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.096-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.132-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.156-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.189-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.209-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.243-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.268-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.298-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.320-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.349-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.367-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.397-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.418-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.458-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.492-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.511-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.542-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.571-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.599-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.632-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.656-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.689-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.709-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.742-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.767-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.800-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.822-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.856-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.880-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.911-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.932-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.966-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.988-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.020-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.045-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.078-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.113-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.137-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.170-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.193-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.227-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Migration].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.247-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.280-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.306-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.339-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.361-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.395-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.415-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.445-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.467-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.497-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.518-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.550-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.570-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.602-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.625-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.655-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.676-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.710-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.731-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.762-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.785-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.821-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.852-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.878-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.899-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.933-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.967-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Users].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.994-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.027-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.052-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.084-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.106-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.135-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.153-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.186-60><thread=6072 (0x17B8)>
    The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync.  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.209-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.250-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.284-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.304-60><thread=6072 (0x17B8)>
    Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health].  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.338-60><thread=6072 (0x17B8)>
    Root Folder exists  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
    Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
    ~Waiting for changes for 1 minutes  $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>

  • SCCM 2012 monitoring

    Hi!
    We deploy SCCM 2012 SP1 with database on the SQL Server cluster. We monitore SQL Server by SCOM 2012 SP1 so, both node FQDN are displayed in SCOM console.
    SCCM display virtual SQL cluster name as FQDN and both SQL cluster nodes as NetBIOS names in its console.
    When we import SCCM management pack into SCOM, it adds 2 SQL Server cluster node as 2 NetBIOS names, so we have 4 objects for SQL cluster nodes in SCOM console:
    1. 2 "old" objects with FQDN names which have status "Available"
    2. 2 "new" objects with short NetBIOS names which have status "Not monitored" and are classified in SCCM views as "ConfigMgr Site Database Server"
    Can I "merge" these 4 objects into 2 "old" monitored objects and can SCOM display all SCCM roles (including database servers) as monitored?

    I have this same problem, except with SCCM 2012 R2 / SCOM 2012 R2. It's quite annoying, as it prevents proper monitoring of the site database.

  • Does SCCM 2012 monitor SCCM 2007 as well?

    I have a SCOM environment and I have two SCCM environments - one is 2007 and the other is 2012R2. We are migrating from 2007 to 2012R2. I have both SCCM 2007 and 2012 MPs imported.
    One thing I've noticed is that all the objects from the 2007 MPs are labeled ConfigMgr 2007, while the objects from the 2012 MPs are just labeled ConfigMgr. And when I create a subscription to send all alerts on ConfigMgr (I filtered to only show objects
    in Microsoft.SystemCenter2012.ConfigurationManager.Library MP) it will send out notifications for all SCCM alerts. 
    So does the 2012 MP monitor 2007 as well? And if so, how can I create a subscription to only notify for 2012? I currently set up the subscription directly against the 2012 servers, but I'd like to have it go against the application instead.
    Thanks.
    - Get on the floor, do that dinosaur

    Yes, we have Exchange. But it doesn't make sense that a subscription criteria set to the ConfigMgr application would send alerts regrading Exchange. Maybe because the SCCM client is installed on those servers...?
    False alerts as in SCOM thinks one thing but its not actually the case. For example, thinking that an Exchange server is a SCCM server. And Alerting on SCCM 2007 instead of 2012. 
    - Get on the floor, do that dinosaur

  • SCCM 2012 Monitoring Parameters for Tivoli

    Hello all,
    I am looking for a list of services/locations for SCCM to be monitored via Tivoli. Please share if someone already have created this..
    Thanks, V@s!m

    I would simply look at the SCOM documentation for monitoring ConfigMgr 2012, see:
    https://www.microsoft.com/en-us/download/details.aspx?id=29267
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Configuring Reporting services for SCCM 2012

    Hi,
    I just finish create SQL reporting services ( configure Database, report manager URL) in SQL 2008 R2 for SCCM 2012. When I open the Report option in SCCM console (Monitoring --> Report), no report listed there and then I try to add in Reporting service
    point for it, but get an error message
    "There is a problem connecting to the specific reporting server. Please check the connection and make sure SQL reporting service is running on the specified server"
    I manually browse to http://sqlserver/reportserver or
    http://sqlserver/reports , that is no any folder exist there (I assume when I configure reporting service it will automatic create a folder for it with all report inside?). Anyone can guide me on how to solve this issue?
    Regards,

    Hi,
    hi ,
    I am new to SCCM 2012 group and i have knowledge on sccm2007. i want to discuss some issue what i have with SCCM2012 installtion. The issue is my machine got rebooted while installing sccm 2012 SP1.i have already installed all the prerequisites for SCCM2012.i
    am installing sccm2012 on Hyper-V machine.
    Please see my system configuration below:
    DomainController(2008R2 server) : 512MB RAM, AD things and DNS ,DHCP has installed on it.
    System center server(2008R2) : 1028MB RAM , Sql 2008 server installed on it.
    i tried to install it many times but still i got the same issue.
    Could anybody please help me with this ?
    This is a new question. So please ask this question on a new thread in this forum.
    Thank you.
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 Application Catalog Website Point role Status is critical

    Hi team,
     In a client's SCCM 2012 R2 environment there is a Critical Icon and Status against one of two Application Catalog Website point roles. Looking at the Component status, there are no errors and all the components show as green.
     Trying to find any warnings or errors in the messages for the Site System role doesnt show any errors, and I tried to reset counts but this has not changed the status.
     I am not sure where to go from here. The application catalog itself works and is up. All the services are running. I am unsure as to where this error status comes from or what it pertains to.
     Any advice would be appreciated.

    Hi,
    Please check portlctl.log and awebsctl.log to see if there is any error.
    You could also check the thread below.
    Symptom: Reporting Services Point Status (under Monitoring - System Status - Site Status) appears as Critical, No error messages in logs or status messages
    Cause: 'Status' can be set to "2" for 'SMS SRS Reporting Point' in dbo.summarizer_sitesystem table in sql
    Resolution: > Run below query:
    update dbo.summarizer_sitesystem set status = '0' where SiteSystem = '["Display=\\abc.local\"]MSWNET:["SMS_SITE=ABC"]\\abc.local\' and role = 'SMS SRS Reporting Point'
    > It should set the status back to 0.
    > Check in console and errors should go away.
    > In case if value reverts back then check below namespace in wmi of site server:
    root\sms\site_pri\sms_sitesystemsummarizer
    > check the value for reporting services point, ideally it should be 0, let's say it's set to 2 there as well then remove role of reporting services point.
    > if entry for reporting services point goes away from both the places then it's good, you can re-install the reporting services point and it should work fine.
    > Let's say if value/values doesn't get removed from sql/wmi , remove them manually via queries and then go with uninstall and re-install.
    > then it should work and errors in console and common.log should go away.
    https://social.technet.microsoft.com/Forums/en-US/5e0b7af6-f00c-4610-a709-f3e0e26505be/sccm-2012-monitoring-site-status-reporting-services-point-status-critical?forum=configmanagergeneral
    Best Regards,
    Joyce
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Tuning Exchange 2013 HealthSet Monitors (example: MailboxTransport - Mapi.Submit.Monitor)

    Hello everyone,
    I was hoping some of you could help me out a bit with the new monitors in Exchange 2013.
    Especially after updating to CU6 we are getting a lot of warnings from SCOM with different HealthSets that show as unhealthy. These are usually “OK” again when we log on to the server and run Get-ServerHealth or Get-HealthReport. The most common healthset is
    Compliance, but also get warnings from MailboxTransport and ActiveSync.
    If we do manage to log on before the healthset returns to healthy again, like in the example below, we can drill down a bit. We are however very unsure about what to do with this information. Perhaps we should change the threshold, but how do we find out exactly
    what this monitor is reporting on? We know it has something to do with Mapi Submit, and that the threshold is 8, but not much more than that?
    Get-ServerHealth SERVER | where {($_.healthsetname -eq "mailboxtransport") -and ($_.alertvalue -eq "unhealthy")} | ft name,alertvalue -auto
    Name                AlertValue
    Mapi.Submit.Monitor  Unhealthy
    (Get-WinEvent -LogName Microsoft-Exchange-ActiveMonitoring/MonitorDefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like "Mapi.Submit.Monitor"}
    auto-ns2                           : http://schemas.microsoft.com/win/2004/08/events
    xmlns                              : myNs
    Id                                 : 266
    AssemblyPath                       : D:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Office.Datacenter.ActiveMonitoringLocal.dll
    TypeName                           : Microsoft.Office.Datacenter.ActiveMonitoring.OverallXFailuresMonitor
    Name                               : Mapi.Submit.Monitor
    WorkItemVersion                    : [null]
    ServiceName                        : MailboxTransport
    DeploymentId                       : 0
    ExecutionLocation                  : [null]
    CreatedTime                        : 2014-11-20T08:51:03.5576888Z
    Enabled                            : 1
    TargetPartition                    : [null]
    TargetGroup                        : [null]
    TargetResource                     : MailboxTransport
    TargetExtension                    : [null]
    TargetVersion                      : [null]
    RecurrenceIntervalSeconds          : 0
    TimeoutSeconds                     : 30
    StartTime                          : 2014-11-20T08:51:03.5576888Z
    UpdateTime                         : 2014-11-20T08:42:58.9416436Z
    MaxRetryAttempts                   : 0
    ExtensionAttributes                : [null]
    SampleMask                         : Mapi.Submit.Probe
    MonitoringIntervalSeconds          : 3600
    MinimumErrorCount                  : 0
    MonitoringThreshold                : 8
    SecondaryMonitoringThreshold       : 0
    MonitoringSamplesThreshold         : 100
    ServicePriority                    : 2
    ServiceSeverity                    : 0
    IsHaImpacting                      : 0
    CreatedById                        : 57
    InsufficientSamplesIntervalSeconds : 28800
    StateAttribute1Mask                : [null]
    FailureCategoryMask                : 0
    ComponentName                      : ServiceComponents/MailboxTransport/High
    StateTransitionsXml                : <StateTransitions>
                                           <Transition ToState="Unrecoverable" TimeoutInSeconds="0" />
                                         </StateTransitions>
    AllowCorrelationToMonitor          : 0
    ScenarioDescription                : [null]
    SourceScope                        : [null]
    TargetScopes                       : [null]
    HaScope                            : Server
    Version                            : 65536
    We have an Exchange 2007 server coexisting in the environment, but it is not in use and will be decommissioned.
                             ServerRole    Edition AdminDisplayVersion
    Mailbox, ClientAccess, HubTransport   Standard Version 8.3 (Build 83.6)
                  Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)
                  Mailbox, ClientAccess Enterprise Version 15.0 (Build 995.29)

    Thanks Belinda.
    We had a look in the log you mentioned, and found some events that appear to be related.
    Mailbox Transport Submission - the verification that the probe messages were successfully submitted within 5 minutes to HUB has failed. 
          This could indicate that the mailbox submissions are taking too long or not progressing at all.
          SequenceNumber: 635515592255510017
          Error: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
          FailureContext: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
          ExecutionContext: MapiSubmitLAMProbe started. This performs - 1. Submits a new message to Store 2. Checks results from previous Send Mail operation. Sequence # = 635515592255510017. First Run? = False. Previous mail submission to store
    was successful. Results -  # of previous results: 0.  Could Not Find stages that ran.  Previous SendMail failure -  Mail submitted to Store during the previous run never reached SendAsCheck. 
                            This may indicate a latency from Store to Submission Service. Investigating.  Found lower SA latency. Indicates an issue in Submission service. 
                                Investigate. In SendMail -  NotificationID=00000044-0000-0000-0000-0000659c9601 Sending mail. SendMail finished. MapiSubmitLAMProbe finished with CheckPreviousMail
    failure. 
          CheckPreviousRunMail exception details: 
          Current SendMail exception details: 
          MailWasSentInLastRun (0(no)/1(yes)): 1
          CheckMailSuccess(0(no)/1(yes)): 0
          SendMailSuccess(0(no)/1(yes)/2(no-noMDBs)/3(no-noActiveMDBs)/4(no-ignorableException)): 1
          PreviousMailLatencies: <[email protected]>,,2014-11-20T08:37:58.817Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.811|SA=0.343|MTSSDMO=0.426|MTSSDPL=0.002|MTSSDSS=0.008|MTSSDS=0.031|MTSS=0.466;;<[email protected]>,,2014-11-20T08:32:58.772Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=0.702|SA=0.203|MTSSDMO=0.451|MTSSDPL=0.003|MTSSDSS=0.007|MTSSDS=0.047|MTSS=0.500;;<[email protected]>,,2014-11-20T08:27:58.664Z;LSRV=SERVER001.DOMAIN.locale:TOTAL=1.170|SA=0.530|MTSSDMO=0.548|MTSSDPL=0.002|MTSSDSS=0.035|MTSSDS=0.078|MTSS=0.647;;
          GetPreviousMailLatencyFailures: 
          (The following are applicable if the mail was actually sent)
          MailSentAt: 20.11.2014 08:42:58
          TimeInSendingToStore: 62,3989
          Sent Mail Result Details:
            (InternetMessageId:<[email protected]>;
            ItemEntryId:0 0 0 0 2E 57 BD C1 1C 4B 5C 47 9E 54 6E B8 B2 C5 75 38 7 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 0 0 1 B 0 0 FA 78 3 5 D1 D4 6 48 B2 FF B 4 D7 25 55 92 0 0 18 1A CD F1 0 0 )
            Properties of Sending mail 
            (Subject:00000044-0000-0000-0000-0000659c9601-MapiSubmitLAMProbe;
            Sender:[email protected];
            MbxGuid:340b204b-c716-4dfe-bbe1-cf09b5c73934;
            MdbGuid:2a6b9801-1647-4378-bc11-6ff342d22fcf;
            Recipient:[email protected];
            Body and MessageClass:MessageClass:IPM.Note.MapiSubmitLAMProbe;MessageBody:This is a Probe Mapi message that's Submitted from Store to Mailbox transport Submission service to Hub transport service;
            DoNotDeliver, DropMessageInHub and DeleteAfterSent:DoNotDeliver:True;DropMessageInHub:True;DeleteAfterSubmit:True;)
    Probe Exception: 'System.ApplicationException: MapiSubmitLAMProbe finished with CheckPreviousMail failure.
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.PerformProbeFinalAction(Boolean potentialForAlertBasedOnPreviousRun, Boolean potentialForAlertBasedOnCurrentRun, Exception previousRunVerificationException,
    Exception currentRunException, DateTime timeMessageSentToStore)
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWorkInternal(CancellationToken cancellationToken)
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Transport.Probes.MapiSubmitLAMProbe.DoWork(CancellationToken cancellationToken)
       at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
       at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
       at System.Threading.Tasks.Task.Execute()'
    Probe Result Name: 'Mapi.Submit.Probe'
    Probe Result Type: 'Failed'
    Monitor Total Value: '0'
    Monitor Total Sample Count: '12'
    Monitor Total Failed Count: '12'
    Monitor Poisoned Count: '0'
    Monitor First Alert Observed Time: '16.11.2014 21:40:10'

  • SCCM software updates reporting

    we are slowly transitioning from WSUS to SCCM for microsoft updates.  I used SCCM to manually update a few servers last night by making a software update group "available" to them.  
    I installed all the upsdates and rebooted.  On the server if i open Software Center there are no more updates to be installed.  If I look in SCCM under Monitoring --> Deployments...it still has these servers as "In progress" .  I
    completed this a day ago.  Why wouldn't this be reporting as completed?
    Is there a better place to look than deployments for this sort of a report?

    Yes, the actual reports. Things in the console tend to lag behind what's actually going on for performance reasons.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • [SCCM 2012] Content distribution to DP's successfull status then in progress

    Hello,
    Had 70 DP on my infrastructure. A distribution group with around 200 contents is created and 70 DP are link to this DP group.
    Every day I check the content distribution status, and the global pourcentage go up and down.
    IE: Monday a DP is fully synched and the day after 10 contents are "in progress" and I have this thing on all DP's. Looks like that content distribution are done again an again....
    Two weeks ago I had 15 DP fully distributed and now only 3... and no changes on the contents...
    So I don't know what is the cause of  this. Any idea?
    Thanks in advance

    We seem to be experiencing this issue in our environment and I just want to try and understand whether this is a bug that only reflects on status messages, or if the status messages reflect on the actual content, and thus, application and task sequence deployments?
    I believe this is becoming a serious issue.
    When the "Content is being distributed to the distribution point" messages first started surfacing, we noticed that certain packages (but not necessarily all), were being sent to all DP's, even when some of those packages weren't assigned to that
    particular DP or the Boundary Group set up for content to that DP (we are viewing this in SCCM 2012 Monitoring | Distribution Status | Distribution Point Configuration Status, and the Details tab.) The biggest issue right now is that this recurrence of packages
    redistributing, is causing task sequences to fail from distribution points that didn't actually have content redistributed to them.
    And yes, validating content individually on those "in progress" packages does remediate the status message and eventually green light the DP. But validating content every time a DP is stood up, or content is distributed is becoming painstaking.
    And scheduling Content Validation to occur more frequently only seems to be a band-aid that will not always help.
    Is there any additional information on this malformed status message that can be provided? Is Microsoft working on a fix? We have not yet upgraded to SP1. Can anyone confirm the issue is resolved with SP1 or later, or if a hotfix exists to address the problem?

  • Auditing IIS Application Settings with SCCM

    Is it possible to use SCCM or any component of MSSC to report on specific settings of a .NET configuration within an application/site object's app.config hosed in IIS?  If so, what are the highlevel components and methods that would be used?  For
    an example, can I define that impersonation=false is my basline for all IIS applications and SCCM identify applications where it is set to true - AKA not in compliance with my baseline/standard?
    I'm having a hard time finding documentation on this level of functionality of configuration manager or any component of system center if it exists.  Audit would tell me of changes, but not of mis-alignments to my .NET configuration standards.  I
    am finding a lot on how to deploy and configure SCCM, or monitor the health of a .NET application, neither are what I'm after.  
    I need to operationalize testing of if IIS .NET applications are in compliance of a predefined .NET/IIS configuration standard.  Or, if I need to defer to remote managment and scripting (not prefered).
    Thanks for all input!
    Jeff

    You could do this with DCMs (Desired Configuration Management). Basically you do a configuration item that you attach to a configuration baseline. Then you deploy that baseline to the servers hosting your IIS applications. You may need to use a script to
    accomplish what you are trying to do. Here are some references to get you started with:
    http://www.addlevel.se/blogg/configmgr-dcmcompliance-check-if-iis-is-using-basic-authentication-over-http.aspx
    http://blogs.technet.com/b/kevinsul_blog/archive/2010/02/15/simple-dcm-example-using-a-ps-script-to-detect-compliance-issues-with-local-administrators-group-membership.aspx
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/b68277e7-926c-47b2-9fae-a7862910aefc/how-to-find-iis-and-its-configuration-by-dcm?forum=configmgrdcm

  • HubTransport and FrontendTransport marked as Unhealthy. How to diagnose and resolve?

    I am trying to do an Exchange 2007 to 2013 migration.  Before doing all the final repointing of DNS and proxying clients, I just want to make sure that the new Exchange 2013 is healthy.  So I run a Get-HealthReport and it shows both the Online
    states of HubTransport and FrontendTransport as Unhealthy.
    In the event logs under Microsoft>Exchange>ManagedAvailability>Monitoring I see Error events for them about the client submission probe failed x times over 15 minutes.  No connection because the target machine actively refused it 127.0.0.1:587.
    There was also another one that said Unable to relay.  For the Hub Transport it does not give as detailed information.  It just says The HubAvailibilityProbe has failed 5 or more times in 15 minutes.  Last failing server: ".
    So it would sound like a connectivity problem, so with TELNET I tried to connect to port 25 and I get this:
    telnet 127.0.0.1 25
    421 4.3.2 Service not available
    BUT if I put the hostname instead of 127.0.0.1, I get the 220 EMAIL.domain.com Microsoft ESMTP MAIL Service ready.
    I tried temporarily disabling the windows firewall and its the same problem.  I know SMTP is running because from another machine I can telnet to the mail server on port 25 and I get the SMTP banner.
    So for me it seems like the Managed Availability is trying to use the IP address of 127.0.0.1 and that fails fundamentally for me when I try that in the command line, so no wonder why its marking the FrontendTransport as unhealthy.  How can I resolve
    this?  I would think a resolution would be either somehow allow 127.0.0.1 access to relay which I DID put in my Frontend Transport receive connector, but it made no difference.  Or the other option is somehow  configure the probe to use the
    hostname instead of 127.0.0.1.  
    As far as the HubTransport being unhealthy, I have a feeling its the same type of issue, but I am not seeing as detailed information in this path of the Event Viewer.

    Bump....
    No issues with mail flow but still getting this in the MOnitoring log from Managed Availability.
    Log Name: Microsoft-Exchange-ManagedAvailability/Monitoring
    Source: Microsoft-Exchange-ManagedAvailability
    Date: 12/8/2014 11:11:29 AM
    Event ID: 4
    Task Category: Monitoring
    Level: Error
    Keywords:
    User: SYSTEM
    Computer: email.domain.com
    Description:
    The inbound proxy probe failed 3 times over 15 minutes.
    Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
    Probe Exception: 'System.Exception: Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
    at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
    at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
    at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
    at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
    at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
    at System.Threading.Tasks.Task.Execute()'
    Failure Context: 'Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
    Execution Context: ''
    Probe Result Name: 'OnPremisesInboundProxy'
    Probe Result Type: 'Failed'
    Monitor Total Value: '3'
    Monitor Total Sample Count: '3'
    Monitor Total Failed Count: '0'
    Monitor Poisoned Count: '0'
    Monitor First Alert Observed Time: '9/25/2014 1:27:15 PM'
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Exchange-ManagedAvailability" Guid="{C424A887-A89F-455F-8319-960917152221}" />
    <EventID>4</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-08T16:11:29.045528200Z" />
    <EventRecordID>7358</EventRecordID>
    <Correlation />
    <Execution ProcessID="7604" ThreadID="1800" />
    <Channel>Microsoft-Exchange-ManagedAvailability/Monitoring</Channel>
    <Computer>email.domain.com</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <UserData>
    <EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
    <HealthSet>FrontendTransport</HealthSet>
    <Subject>The inbound proxy probe failed 3 times over 15 minutes.</Subject>
    <Message>The inbound proxy probe failed 3 times over 15 minutes.
    Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
    Probe Exception: 'System.Exception: Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
    at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
    at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
    at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
    at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
    at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.&lt;&gt;c__DisplayClass2.&lt;StartExecuting&gt;b__0()
    at System.Threading.Tasks.Task.Execute()'
    Failure Context: 'Server email.domain.com on port 587 did not respond with expected response (ServiceReady). The actual response was: 421 4.3.2 Service not available
    Execution Context: ''
    Probe Result Name: 'OnPremisesInboundProxy'
    Probe Result Type: 'Failed'
    Monitor Total Value: '3'
    Monitor Total Sample Count: '3'
    Monitor Total Failed Count: '0'
    Monitor Poisoned Count: '0'
    Monitor First Alert Observed Time: '9/25/2014 1:27:15 PM'
    </Message>
    <Monitor>OnPremisesInboundProxyMonitor</Monitor>
    </EventXML>
    </UserData>
    </Event>

  • OnPremisesSmtpClientSubmissionMonitor unhealthy

    Hi
    I ran "get-healthreport" and got an unhealthy "Frontend Transport". I found out the problem is the monitor "OnPremisesSmtpClientSubmissionMonitor". I found this event:
    The client submission probe failed 3 times over 15 minutes.
    Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
    Probe Exception: 'System.Exception: Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.AssertExpectedResponse(SmtpExpectedResponse expectedResponse)
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection()
       at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
       at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
       at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
       at System.Threading.Tasks.Task.Execute()'
    Failure Context: 'Server 127.0.0.1 on port 587 did not respond with expected response (OK). The actual response was: 550 5.7.1 Client does not have permissions to send as this sender
    Execution Context: ''
    Probe Result Name: 'OnPremisesSmtpClientSubmission'
    Probe Result Type: 'Failed'
    Monitor Total Value: '3'
    Monitor Total Sample Count: '3'
    Monitor Total Failed Count: '0'
    Monitor Poisoned Count: '0'
    Monitor First Alert Observed Time: '3/13/2015 11:56:16 AM'
    But I can telnet the port 487 on 127.0.0.1 and the last run seems to be fine. I have restarted the Frontend transport service with no luck. The state is still "Unhealthy".
    RunspaceId              : b49aab67-784f-464f-9c60-4b07fcde8f6e
    Server                  : srvexchange01
    CurrentHealthSetState   : Online
    Name                    : OnPremisesSmtpClientSubmissionMonitor
    TargetResource          :
    HealthSetName           : FrontendTransport
    HealthGroupName         : ServiceComponents
    AlertValue              : Unhealthy
    FirstAlertObservedTime  : 13.03.2015 12:56:16
    Description             :
    IsHaImpacting           : False
    RecurranceInterval      : 450
    DefinitionCreatedTime   : 17.03.2015 14:47:56
    HealthSetDescription    :
    ServerComponentName     : FrontendTransport
    LastTransitionTime      : 13.03.2015 12:56:16
    LastExecutionTime       : 17.03.2015 15:49:53
    LastExecutionResult     : Succeeded
    ResultId                : 1671349
    WorkItemId              : 70
    IsStale                 : False
    Error                   :
    Exception               :
    IsNotified              : False
    LastFailedProbeId       : 37
    LastFailedProbeResultId : 835260
    ServicePriority         : 2
    Identity                : FrontendTransport\OnPremisesSmtpClientSubmissionMonitor\
    IsValid                 : True
    ObjectState             : New

    Hello,
    Please try:
    Add-GlobalMonitoringOverride -Identity "FrontendTransport\OnPremisesInboundProxy" -PropertyName Enabled -PropertyValue 0 -ApplyVersion "15.0.xxx.xx" -ItemType
    Monitor
    The
    ApplyVersion here is your current Exchange version.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Managedavailability error about inbound proxy probe failing

    getting a managedavailability error about inbound proxy probe failing.
    what does the inbound proxy probe do, and why does this error reference forefront, when I do not have MS forefront installed?
    below are the details:
    The inbound proxy probe failed 3 times over 15 minutes.
    The inbound proxy probe failed 3 times over 15 minutes. No connection could be made because the target machine actively refused it 127.0.0.1:25 Probe Exception: 'System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target
    machine actively refused it 127.0.0.1:25 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SimpleSmtpClient.Connect(String server, Int32 port, Boolean disconnectIfConnected) at
    Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1 cmd) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.MeasureLatency(String reason, ActionWithReturn`1
    cmd, ConnectionLostPoint connectionLostPoint) at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.TestConnection() at Microsoft.Forefront.Monitoring.ActiveMonitoring.Smtp.Probes.SmtpConnectionProbe.DoWork(CancellationToken cancellationToken)
    at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken) at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.b__0() at System.Threading.Tasks.Task.Execute()' Failure Context: 'No connection
    could be made because the target machine actively refused it 127.0.0.1:25' Execution Context: '' Probe Result Name: 'OnPremisesInboundProxy' Probe Result Type: 'Failed' Monitor Total Value: '3' Monitor Total Sample Count: '3' Monitor Total Failed Count: '0'
    Monitor Poisoned Count: '0' Monitor First Alert Observed Time: '1/27/2015 4:46:45 PM

    Hi,
    Please use the Get-ServerHealth and Get-HealthReport commands to check result.
    Here is a related blog for your reference.
    http://blogs.technet.com/b/exchange/archive/2013/06/26/managed-availability-and-server-health.aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Software center reports application installed even though it has not installed

    So basically we are deploying updates for an application. We re-bundle the application installation .exe into an .msi using EMCO repackage. our deployments work in a test environment,  but when we deploy to the production environment it fails. On that
    note it fails with the software center saying it installed the software please see link. 
    I am completely baffled by what is going wrong here. My test environment is only four virtual desktops and the company deployment group in like 70 desktops both are located in the same building. My SCCM12 instance is in a remote location connected via VPN.
    The deployment package size is about 60Mb the software manager reports the package was only 1Mb.  I do not have a copy of a users execmgr.log file as of yet but i will examine and post as soon as I get a copy of one. Any initial help or point in the right
    direction is appreciated.
    I apologize for the lack of visual aid. The forum would not let me post the screen shots I have nor could i link back to my oneDrive.
    Best regards,
    Brett

    Look in the "appenforce.log". It will tell you the exit code, also check the appdiscovery.log to determine the detection is passing or failing. Normally a MSI will use the ProductID by default. The detection method can be viewed/changed looking
    at the deployment package.
    Any reason why you need to deploy this via MSI? Does the exe not have switches to run the install, because you can define your own detection to detect if an exe installed correctly.
    Edit - Exit code 0 means successful, 3010 also but also telling ccmexec that a reboot is required. Anything else would tell ccmexec that it failed. Also, what you will learn here is that SCCM delivers the installation and commands for the install however
    the installer (the MSI) is responsible for all the work after that. SCCM just monitors the install for success/fail.

Maybe you are looking for

  • IMovie - adding a picture (without black frame below) in the very bottom of a video

    Hello iMoviers, I'd like to add a picture on top of a movie. As far as I understand this can be done by using iMovie's picture-in-picture feature. The picture, however, is centered in a black frame. 1) How can I position the picture on the ver bottom

  • When is the next FB 4.7 Update?

    It has been quite some time since FB 4.7 was released and there haven't been any bug-fixing updates so far. Also, Java 7 is not fully supported (at least in OS X). Can we expect anything in the near future?

  • Problem fetch large number of records

    Hi I want to fetch large number of record from database.and I use secondary index database for improve performance for example my database has 100000 records and query fetch 10000 number of records from this database .I use secondary database as inde

  • Need to Create RFC

    Hi Friends, i want to create RFC to return all production orders based on given material no. I want to use this RFC outside SAP. Can you please guide me how to proceed. Apart from checking Radio button Remotely Enabled..do i need to do any thing more

  • Problem with JAXB

    I am trying to run a simple test program to unmarshall and XML doc and am getting the following error: [erdos OpenOfficeDev]$ ./java_jaxb.sh unmarshall sampleDoc.xml JAXBLIB /opt/tomcat50-jwsdp/jaxb/lib CLASSPATH /opt/tomcat50-jwsdp/jaxb/lib/jaxb-api