Sccm 2012 r2 Fallback status point

as we have intranet and internet user to support for sccm 2012r2
we have one server in DMZ with SUP,DP,MP role for IBCM now, my question .....is it possible to support 
internet client for FSP as it communicates only in HTTP.
Can we install FSP and MP in same box for intranet clients.any advantage or disadvantages.

It's technically possible to use a FSP for Internet clients, but I would strongly advise to not do that. It's a big security risk as it's unauthenticated HTTP traffic. For more information see:
http://technet.microsoft.com/en-us/library/gg681976.aspx#BKMK_Determine_FSP
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

  • 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]

  • SCCM 2012 R2 - Reporting Services Point installation - "The Datasource does not exist"

    Hi all,
    Quick bit of background, we have SCCM 2012 R2 installed on a Windows 2012 R2 server. We have the SQL back end off box, configured on a SQL 2012 R2 server running on a Windows Server 2012 R2 cluster. Then there is yet another server which runs the reporting
    services. I've just tried installing the Reporting Services Point on the srs server but it doesn't appear to have worked that well. Here's the info i've got back: 
    A] Site Status > Reporting services point:
    SMS_SITE_SYSTEM_STATUS_SUMMERIZER
    Site System Status Summarizer detected that the availability of the "Reporting services point" role on server "\\NA-SQLR01.in.tna.local" has changed to Failed.
    B] The last message from the SMS_SRS_REPORTING_POINT Component Status is "Site Component Manager successfully installed this component on this site system"
    C] Here's the first chunk of info which appears in the srsrp.log file:
    SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 4204 (0x106C).
    This is a SRS Reporting Point Role as SRSRP registry key exists.
    Waiting for changes for 0 minutes
    Timed Out...
    Set configuration
    Check state
    Check server health.
    Successfully created srsserver SMS_
    Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
    Reporting Services is running
    The DataSource does not exist.
    [sqlserver.local\SQL1] [SCCM_XXX] [ConfigMgr_XXX] [sqlreportserver.LOCAL]
    [SQL2012] [1] [] [xxx\SCCM2012Server]
    Confirmed version [11.0.5058.0] for the Sql Srs Instance.
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
    Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
    Extract resource language packs if exists
    Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
    Looking for 'English (United Kingdom)' resources
    Looking for 'English' resources
    Found resources for 'English'
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
    Item, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
    System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
    'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
    Folder, String Parent, Property[] Properties)
    (!) SRS root folder was reported missing
    STATMSG: ID=7405 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=sqlreportserver.LOCAL SITE=P01 PID=2120 TID=4204 GMTDATE=Wed Apr 08 08:56:05.349 2015 ISTR0="ConfigMgr_XXX" ISTR1="sqlreportserver.LOCAL"
    ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
        WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
        WARNING: Could not read registry key HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\MPFDM\Inboxes\ on the server, The operating system reported error 2: The system cannot find the file specified.
    Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
    Registry change
    Waiting for changes for 1 minutes
    After this point i simply get the following info messages looping endlessly:
    Set configuration
    Check state
    Check server health.
    Successfully created srsserver
    Reporting Services URL from Registry [http://sqlreportserver/ReportServer_SQL2012/ReportService2005.asmx]
    Reporting Services is running
    The DataSource does not exist.
    [sqlreportserverlocal\SQL1] [SCCM_XXX] [ConfigMgr_P01] [sqlreportserver.LOCAL]
    [SQL2012] [1] [] [XX\SCCM2012Server]
    [1] [0]
    Confirmed version [11.0.5058.0] for the Sql Srs Instance.
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_XXX' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.GetProperties(String
    Item, Property[] Properties, ItemNamespaceEnum itemNamespace, Property[]& Values)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.GetProperties(String Item, Property[] Properties, Property[]& Values)
    Extract resource language packs if exists
    Loading localization resources from directory [D:\SMS_SRSRP\SrsResources.dll]
    Looking for 'English (United Kingdom)' resources
    Looking for 'English' resources
    Found resources for 'English'
    System.Web.Services.Protocols.SoapException: The item '/ConfigMgr_XXX' cannot be found. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: The item '/ConfigMgr_P01' cannot be found.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.SetProperties(String
    Item, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.SetProperties(String Item, Property[] Properties)
    System.Web.Services.Protocols.SoapException: The permissions granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user
    'NT AUTHORITY\SYSTEM' are insufficient for performing this operation.~   at Microsoft.ReportingServices.Library.ReportingService2005Impl.CreateFolder(String Folder, String Parent, Property[] Properties, Guid batchId)~   at Microsoft.ReportingServices.WebServer.ReportingService2005.CreateFolder(String
    Folder, String Parent, Property[] Properties)
    (!) SRS root folder was reported missing
    Failures reported during periodic health check by the SRS Server sqlreportserver.LOCAL.
    Registry change
    Waiting for changes for 1 minutes
    Has anyone come across this issue before? Must admit, I'm not too hot on the sql side of things so any advice or suggestions would be greatly appreciated. Thanks in advance!

    Hi guys, cheers for the swift response.
    Garth, i can access SSRS in IE from the SCCM box and it looks a-ok.
    Paul, nope can't say I've done any configuration of reporting services - the whole thing has been set up by the database team. Having had a trundle through Reporting Services Configuration Manager, it seems the Database team have set up SSRS in line with
    the walkthrough you posted.
    Since i'm not seeing the ConfigMgr_XXX folder appear in SSRS I'm wondering if there's something preventing SCCM from being able to create it. The message
    "Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions
    granted to user 'NT AUTHORITY\SYSTEM' are insufficient for performing this operation" sounds like the account SCCM is leveraging to perform the install might not have the right permissions in SSRS. Do i need to delegate specific rights to the NT
    AUTHORITY\SYSTEM account in SRS perhaps?

  • SCCM 2012 R2 SRS Repointing Point Error 7403

    I have install the Reporting services point and I'm receiving error 7403 "The report server service is not running on Reporting Service Point server "SFSCCM1W.SFCCMO.EDU"; start the service to enable reporting."
    Server 1: SCCM 2012 R2
    Server 2: SQL 2008 R2 CU4

    I install the SSRS on the Server running SCCM 2012.  So I need to install the SSRS role on the SQL server?
    When I browse to the sccm server there are no reports in the browser.
    Okay I found the reports on the sql server when I browse to it http://serversql/reports.

  • SCCM 2012 R2 & Pull Distribution Point Casuing 0 Byte amd64 folders

    Experiencing an extremely frustrating problem.
    ENVIRONMENT:
    1 Primary Site Server / DP (Main Office)
    40 DP's (Remote School Locations)
    - Hosted on a file server VM
    - Contains 3 partitions: C: (System), E: (Data), I: (PKG share)
    OS: Server 2008 R2 (Primary Site Server and File Servers / DP's)
    SCCM Version: SCCM 2012 R2 
    We recently upgrade to SCCM 2012 R2. I have confirmed that this has not caused the problem I am about to describe. The only other change that has occurred recently is that we configured all of our DP's at each of our 40 sites to be pull distribution points.
    While this seems to be working fine we are now seeing a whole bunch of 0 Byte alpha numeric folders with a 0 Byte amd64 subfolder. These folders seem to attach to the E: drive on all of our File server distribution points....for the life of me I cannot figure
    out why and this occurred as soon as we switched to pull distribution points. While this does not seem to be having an erroneous effect on our environment, it is annoying and somewhat disconcerting as I have not been able to ascertain what is causing it. Any
    SCCM admins out their ever encountered this?
    Thanks

    Yes, I have examined the logs using cmtrace and done a search for the amd64 string to see if any of the logs indicate its creation as part of the pull dp process. I have not found anything as of yet.
    Thanks

  • SCCM 2012: Reinstall remote distribution point?

    Hi,
    We have a remote distribution point to which we can't deploy packages anymore. Several attempts to repair it failed.
    I'd like to remove the distribution point and reinstall it via SCCM 2012 console.
    However, I'd like to know the impact since it contains GB of packages already.
    Note: the DP has been removed for clients (temorarely) so no impatc there.
    My questions:
    -what is best practises: can I just remove and add it in 1 go (or need to wait before re-adding, reboot needed in between)?
    -will all data be pulled in again (I activated pull and would reactivate it after reinstall)?
    -what's your experience in this procedure? does it work in general or is it preferrable I continue troubleshooting the current situation?
    Please advise.
    J.
    Jan Hoedt

    I can see there was installed a new dotnet version C:\Windows\Microsoft.NET\Framework64\v4.0.30319
    recently.
    Can/should I register this to IIS?
    http://stackoverflow.com/questions/22952115/asp-net-iis-7-5-http-500-21-error
    C:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis.exe -i
    Jan Hoedt

  • SCCM 2012: configure software update point

    Hi,
    I installed WSUS, installed the software update point on Windows 2012 (for SCCM 2012) with following commands:
    Install-WindowsFeature -Name UpdateServices -IncludeManagementTools
    cd 'C:\Program Files\Update Services\Tools\'
    .\wsusutil.exe postinstall CONTENT_DIR=E:\WSUS
    Add-CMSoftwareUpdatePoint -SiteCode "PRD" -SiteSystemServerName "CM01.contoso.com" -ClientConnectionType Intranet -WsusiisPort 8530 -WsusiissslPort 8531
    Now I'm stuck. How do I configure the specific update (f.e. Windows 2012, forefront etc), download them to a certain folder?
    Please advise.
    J.
    Jan Hoedt

    It really isn't practical (or possible) to try to do an entire ConfigMgr implementation using PowerShell. I don't believe that you can choose your products using PoSH.
    You will find a full list of cmdlets here
    http://technet.microsoft.com/en-us/library/jj821831(v=sc.20).aspx
    The following cmdlets are available to configure your software update infrastructure but I'm pretty sure none of them will help you with this.
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • SCCM 2012 R2 - Multiple Management Points

    Hi,
    We are deploying SCCM 2012 R2 and it will cover 15 geographical locations.  There will be 1 site and 1 site server with DB.  The 15 locations will each have a Distribution Point .  The number of hosts is around 10,000 total.
    Can multiple (15) Management Points be installed along with the Distribution Points to communicate back to 1 site server?  Is it necessary or even possible?
    Thanks.

    It's possible yes (with many caveats), but not generally necessary. If you are concerned about client to MP traffic, which is generally quite small (which I why I say it's generally not necessary), then the use of secondary sites is recommended instead of
    stand-alone DPs. The secondary site will then provide a local DP, MP, and SUP for clients at that location to use.
    Directly placing an MP that is part of the primary site is problematic because clients do not choose MPs within a single primary site based upon their location. Thus, placing an MP remotely does not address geographically dispersed locations/clients in any
    way and may make the problem worse. As of 2012 R2 CU3, you can hard-code MPs into clients, but this creates a bit of an overhead problem and does not address SUPs.
    Thus, as mentioned, if you are truly concerned with this traffic, secondary sites are the way to go. Without knowing how many clients are at each location and the bandwidth available to those locations, I wouldn't make a recommendation as to which to use
    though. In general, I always lean towards stand-alone DPs for remote locations unless the bandwidth is severely constrained or there are a large number of clients at that location.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • SCCM 2012 R2 - Software Update Point

    I have two domains, one where the site server (SCCM) will be installed home office,  and then another untrusted domain Management.  This server will have site roles, SUP, and some others.
    I want to create a site system server with DP, MP in the untrusted domain.    In order to push out updates to clients in the untrusted domain,  what do I need, in the untrusted domain, to make this work.

    Hi,
    For the SUP in the untrusted domain the SCCM Site Server you need the proper patch level of the installed WSUS, the correct ports open on Firewall and an account from the Domain where the SCCM Site is installed which has rights on the WSUS on the primary
    site. This account has to be configured during the installation of the SUP on the Site System Server.
    May this post also give you some hints:
    http://social.technet.microsoft.com/Forums/en-US/c3fbf3ab-ca70-48da-90b1-e7322783140c/sup-in-untrusted-forest-using-sccm-2012-sp1?forum=configmanagerdeployment
    Cheers
    Christoph
    PS: Could somebody please move this thread to the correct Configuration Manager Forum :)

  • 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)>

  • Problem with SCCM 2012 R2 Component status messages

    Hello,
    I have a strange problem with Component status messages. When I try to view all messages from any component, I receive an error message stating that the data could not be recieved from the database. Reporting point is installed.
    And when I try to run a report, nothing happens. The report doesn't run.
    Any idea??

    Oooopsss... Status messages disappeared again !! nothing suspect in srsrp.log and compmon.log.
    There are these entries in compsumm.log that got my attention
    The machine account will be used for ["Display=\\DataBaseServer.domain\"]MSWNET:["SMS_SITE=CPS"]\\DataBaseServer.domain\.~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.643+300><thread=3152 (0xC50)>
    Successfully made a network connection to \\DataBaseServer.domain\ADMIN$.~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.643+300><thread=3152 (0xC50)>
    Failed to read Operations Management component registry key values on DataBaseServer.domain; error = 5 (0x5).~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.909+300><thread=3152 (0xC50)>
    Failed to read in current property values and initialize COpsMgmtComponent object; error = 5 (0x5).~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.909+300><thread=3152 (0xC50)>
    Error: Failed to initialize the COpsMgmtComponent object for component SMS_SITE_SQL_BACKUP_S206UT24.CSDPS.QC.CA on machine DataBaseServer.domain. : L’opération a réussi.~~  $$<SMS_COMPONENT_STATUS_SUMMARIZER><12-17-2014 20:00:00.909+300><thread=3152
    (0xC50)>

  • SCCM 2012 cannot access distribution point as a data source for OS image

    I am trying to path a data source to one of our file servers and get the following error:
    I am guessing this is a permissions issue.  The path is correct. This is also a distribution point and I have no trouble distributing content to it.  The SCCM server is set to have local admin and network share rights to this file server.  Any
    ideas?

    Of course - that would be too easy... had to ask though :)
    Hmm, sounds odd.  I'm guessing that since you're using it as a DP you're on Windows Server... You might try browsing there in your runline but instead of doing
    \\server\share\OS.WIM try doing
    \\Server.FQDN\Share\OS.WIM
    I've seen some odd issues where I need to specify FQDN but it's pretty rare.  I do remember an issue where my own account would not go through even though it had rights and I could navigate.  I used a different account and I think after a while
    it cleared up.  My guess is something got rebooted and it "righted the ship" so-to-speak.  I'm sorry I don't remember more, that particular client had multiple accounts so I just switched to a different one and by the time I had to do the same function
    again the issues had resolved itself so I just moved on.

  • SCCM 2012 Software Metering - Status Message ID

    Hi All,
    I am planning to
    configure “Automatic Software Uninstall”
    based on software metering rules as outlined in the following blogs.
    http://blogs.technet.com/b/neilp/archive/2012/11/27/software-metering-deep-dive-and-automation-part-1-use-it-or-lose-it-the-basics.aspx
    http://blogs.technet.com/b/neilp/archive/2012/11/29/software-metering-deep-dive-and-automation-part-2-use-it-or-lose-it-the-collections.aspx
    However, the account
    is currently installing software based on AD Software install groups.
    If a user does not
    use the software the software metering rule will ensure the machine is
    populated into the application uninstall collection. However, (problem) the
    machine account is still in the Install AD group and therefore, the uninstall
    will not occur, (as install deployment takes precedence over uninstall
    deployment)
    I could configure
    the install collection to exclude the uninstall collection, which would allow
    the software to uninstall. But, then once the machine automatically gets
    removed from the uninstall collection the software will install again as the
    machine is still in the AD group.
    Solution: Remove the machine account from the
    AD install Group.
    Question: What the best automated approach to
    remove the machine from AD install group. I am thinking along the lines of
    using Status Message ID’s based on the metering rule which causes a script to
    fire and remove the machine from the AD group.
    Would I have to
    create a status message Rule for each application? Or is it possible to create
    a generic one that can be leveraged for each application / metering rule
    combination?
    What Status Message ID should I use ?
    I would appreciate
    and comments or suggestions on the matter?
    Thanks
    Paul.

    Hello,
    You referred AD group, did you install this application via group policy?
    I think you can find out these machines via result of software metering. The following article show software metering rule:
    https://technet.microsoft.com/en-us/library/dd334612.aspx
    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]

  • [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?

  • Site Status Error in Monitoring - SCCM 2012

    Hi,
    I am getting alerts under site status in SCCM 2012
    Site System Status Summarizer still cannot access storage object "<server name>E$\SMS" on site system "\<server name>". The operating system reported error 3: The system cannot find the path specified.
    The SMS folder its looking for is actually available in C: drive.
    Please assist

    Hi,
    Which site system got this alert?
    How about compmon.log and sitestat.log?
    Best Regards,
    Joyce
    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.

Maybe you are looking for