State Migration Point Status Shows Critical
Our environment is a single primary site with one primary server (MP, FSP, DP, SMP, etc.) and four remote servers that function as DPs and SMPs. The primary site server is reporting in the Site Status window that it is in a Critical status, except
that everywhere else shows nothing is wrong. It has been this way for several weeks. Under Component Status, every component reports OK. All of the smpmgr.log files show no errors and show the typical health check success messages. I
can't find any reason that this role is reporting Critical in the Site Status window, and resetting counts isn't helping. Has anyone run into this before or do you have any ideas how to resolve this short of un-installing and re-installing the role.
Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ
Similar Messages
-
State Migration Point Data not Deleting
Hi
I've seen this issue mentioned numerous times on these forums but it looks like a tricky one to get a solution for - would appreciate if somebody could assist
I have SCCM 2012 Deployed with a State Migration Point on another Site Server - I migrate to Windows 7 and the Task Sequnce used include a Capture User State Section and a restore User State Section - The Migration/Task Sequence completes
successfully - have checked reports ....
The Proble is I have set the Stae Migration Point to delete the User State Data to Delete after 3 days ...
it never does this - the Entries remain in the USMT section of SCCM - and if I log onto the Server with the State Migration Role all the data is still there after 3 days.
This is a major problem - is there anyway to force the State Migration Point to delete after 3 days regardless. I know from reading that the issues look to be around the fact that their may be an issue with the "Release Store" Section - however my task sequence
continues -and is marked as successful
SO Basically is there a way to force the Delation of Data automatically through the State Migration Point and if not .... will a manual delation work and if so what folders should I delete (had a nasty issue the other day where I deleted one of these
User State Folders and the State Migration Point went offline, only came back online when I created a blank folder to replace the folder I deleted)
Would really appreciate assistance here as I have come accross this problem on a number of Sites and its not practical to go through log files for each migration to verify that the stores were released correctlyhere is the issue... Thank you Steve Rachui... http://blogs.msdn.com/b/steverac/
I was lucky enough to have him onsite today... for some reason the loadstate is not releasing the client store. if you check the migrationstatus.xml you will see false under restore status. not sure why the store doesn't release yet but it could be timing
between the release and reboot command im not sure.
FYI: - the next morning..
I removed the reboot cycle on my task and when I came in this morning, the xml file showed the datastore was released. (restore status = true) With that said, you will probably need to extend the delay between the release state and the reboot, or remove
the reboot entirely, (which I probably would't personally do.)
good luck guys
So how did you delete the existing folders for the tasks that had already run? Did you manually change the restore status to TRUE? Or is there no way to delete the old data except removing the SMP role, deleting the folders and then re-enabling the SMP role?
Thanks,
SinghP80 -
How to manually recover user state data saved to a State Migration Point
Hi,
In SCCM 2012, how would you recover the User State saved to the State Migration Point manually?
In SCCM 2007 you could do what was outlined here:
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/159affd3-1726-4829-a0f4-0c875481fc11
However this does not work for SCCM 2012 because the User State Recovery key so long that it cannot be used with a loadstate command (Loadstate commands cannot be longer than 256 characters)
Previously you could also have just opened the User.mig file using Windows Easy Transfer and entered the User State Recovery key stored in SCCM - however in SCCM 2012 this does not work either!
I really need to recover the contents for a user who got a new computer (old one stolen) and requires data from a previous user state capture on the State Migration Point.Hi,
It seems something changed in SCCM 2012.
I've got the same problem and after couple hours of research I found MS article that only helped me -
http://technet.microsoft.com/en-us/library/hh824962.aspx
In SCCM server I run this command:
C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\User State Migration Tool\amd64>usmtutils.exe /extract C:\tmp\_MIG\USMT.MIG C:\tmp\_MIG\Extract /decrypt /keyfile:C:\tmp\_MIG\Key.txt
and received necessary data. -
Restricting State Migration Point to allow 10 GB of data as User State backup
Hi ,
I am using State migration point to backup user data settings through USMT. I am looking for some option either on SMP side or USMT side to restrict data maximum of 10 GB from the system. SMT\USMT should not allow data backup more than 10GB from any system.
Any pointers will be appreciated. Thanks.
Regards,The best you can do is to run scanstate with the estimate parameter to estimate how data it will collect and then branch or abort based on the results.
I outlined how to collect this information beforehand at
http://blog.configmgrftw.com/collecting-usmt-estimates-using-configmgr/
Jason | http://blog.configmgrftw.com | @jasonsandys -
State Migration Point Minimum Free Space
I am in the process of doing OS deployment with Windows 7. I have a State Migration Point in place with minimum free space threshold of 100mb. My question is, will my task sequence error out and fail prior to formatting the drive and installing Windows 7
if the minimum free space is met and all the data cannot be captured? I am nervous that if this threshold is met all user data on a system is not able to be captured and the task sequence continues on to format the drive and install the OS.
Thanks,
Mike
Solutions ArchitectYes, the prepare state capture task will fail if it can't find an SMP with free space on it thus causing the TS as a whole to fail assuming you haven't selected the ignore failure option on the task or any of its parent groups. That's doesn't necessarily
guarantee that there is enough free space or that multiple simultaneous task sequences couldn't cause issues though thus you should plan accordingly, monitor the free space instead of leaving it to chance, and enable the auto cleanup feature with a rational
period of time.
Jason | http://blog.configmgrftw.com -
State Migration Point issues - Error 12030
Hello there,
I wanted to add a state migration point to a host that already operates as a distribution point for several months. The state migration installs successfully when looking at the msi-log, but is not operational afterwards. The log file states that the health
check fails with error 12030. Did I forget something?
This is the content of the smpmgr.log
SMS_EXECUTIVE started SMS_STATE_MIGRATION_POINT as thread ID 3376 (0xD30). $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.256-60><thread=3636 (0xE34)>
******************************************************************************** $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.256-60><thread=3376 (0xD30)>
SMS_STATE_MIGRATION_POINT received START notification. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.256-60><thread=3376 (0xD30)>
SMPPeriodicActivityInterval = 1440 minutes. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.256-60><thread=3376 (0xD30)>
SMPEncryptionCert Length 3008. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.256-60><thread=3376 (0xD30)>
RegOpenKeyEx succeeded for regkeypath SOFTWARE\MICROSOFT\SMS\SMP\STATESTORE $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.256-60><thread=3376 (0xD30)>
StateMsgDir = C:\SMS\MP\outboxes\statemsg.box, StatusmsgDir = C:\SMS\MP\outboxes\stat.box, sitecode = PH2 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.256-60><thread=3376 (0xD30)>
Securing SMP msg dirs successful $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
HandleSMPRegistryChanges: RegQueryInfoKey succeeded. Number of SMP stores=1 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
RegOpenKeyEx succeeded for regkeypath SOFTWARE\MICROSOFT\SMS\SMP\STATESTORE\SMPSTOREE_EAFE6917 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
Directory E:\StateMigration\SMPSTOREE_EAFE6917$ exists. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
Creating share SMPSTOREE_EAFE6917$ succeeded $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
AllowSMPIsapiAccess succeeded for share E:\StateMigration\SMPSTOREE_EAFE6917$. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
SMPPeriodicActivityInterval = 1440 minutes $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
Handling SMP registry Changes succeeded. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.287-60><thread=3376 (0xD30)>
Successfully created factory CSMPMgrFactory $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.303-60><thread=3376 (0xD30)>
Successfully registered class CSMPMgr. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.303-60><thread=3376 (0xD30)>
SMS_STATE_MIGRATION_POINT successfully started $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.303-60><thread=3376 (0xD30)>
Configuration and Availability Monitor thread started. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.303-60><thread=1196 (0x4AC)>
Initialized 'SMS Server Availability' performance instance => SMS State Migration Point.~ $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:28:50.303-60><thread=1196 (0x4AC)>
HandleSMPRegistryChanges: RegQueryInfoKey succeeded. Number of SMP stores=1 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:14.190-60><thread=1196 (0x4AC)>
RegOpenKeyEx succeeded for regkeypath SOFTWARE\MICROSOFT\SMS\SMP\STATESTORE\SMPSTOREE_EAFE6917 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:14.190-60><thread=1196 (0x4AC)>
Directory E:\StateMigration\SMPSTOREE_EAFE6917$ exists. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:14.190-60><thread=1196 (0x4AC)>
Creating share SMPSTOREE_EAFE6917$ succeeded $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:14.206-60><thread=1196 (0x4AC)>
AllowSMPIsapiAccess succeeded for share E:\StateMigration\SMPSTOREE_EAFE6917$. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:14.206-60><thread=1196 (0x4AC)>
SMPPeriodicActivityInterval = 1440 minutes $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:14.206-60><thread=1196 (0x4AC)>
Handling SMP registry Changes succeeded. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:14.206-60><thread=1196 (0x4AC)>
SSL is enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Client authentication is also enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
CRL Checking is also enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Machine name is 'statemigr.something.com'. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Begin validation of Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Certificate has "SSL Client Authentication" capability. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Completed validation of Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Begin validation of Certificate [Thumbprint 35633602ebcd8512702330af54bf349adb3b9b0a] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Certificate doesn't have "SSL Client Authentication" capabilities. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Completed validation of Certificate [Thumbprint 35633602ebcd8512702330af54bf349adb3b9b0a] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Skipping this certificate which is not valid for ConfigMgr usage. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
>>> Selected Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' for HTTPS Client Authentication $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.298-60><thread=1196 (0x4AC)>
Failed to send http request /SMSSMP/.sms_smp?op=healthcheck. Error 12030 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.314-60><thread=1196 (0x4AC)>
Call to HttpSendRequestSync failed for port 443 with 12030 error code. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.314-60><thread=1196 (0x4AC)>
Health check operation failed, error code is 12030 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.314-60><thread=1196 (0x4AC)>
STATMSG: ID=6208 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_STATE_MIGRATION_POINT" SYS=statemigr.something.com SITE=PH2 PID=2904 TID=1196 GMTDATE=Di Mrz 24 19:29:20.314 2015 ISTR0="12030" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.314-60><thread=1196 (0x4AC)>
Completed availability check on local machine $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.314-60><thread=1196 (0x4AC)>
Initialization still in progress. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:20.314-60><thread=1196 (0x4AC)>
SSL is enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Client authentication is also enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
CRL Checking is also enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Machine name is 'statemigr.something.com'. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Begin validation of Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Certificate has "SSL Client Authentication" capability. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Completed validation of Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Begin validation of Certificate [Thumbprint 35633602ebcd8512702330af54bf349adb3b9b0a] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Certificate doesn't have "SSL Client Authentication" capabilities. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Completed validation of Certificate [Thumbprint 35633602ebcd8512702330af54bf349adb3b9b0a] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Skipping this certificate which is not valid for ConfigMgr usage. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
>>> Selected Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' for HTTPS Client Authentication $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Failed to send http request /SMSSMP/.sms_smp?op=healthcheck. Error 12030 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Call to HttpSendRequestSync failed for port 443 with 12030 error code. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Health check operation failed, error code is 12030 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Completed availability check on local machine $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
Initialization still in progress. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:29:50.294-60><thread=1196 (0x4AC)>
SSL is enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Client authentication is also enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
CRL Checking is also enabled. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Machine name is 'statemigr.something.com'. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Begin validation of Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Certificate has "SSL Client Authentication" capability. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Completed validation of Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Begin validation of Certificate [Thumbprint 35633602ebcd8512702330af54bf349adb3b9b0a] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Certificate doesn't have "SSL Client Authentication" capabilities. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Completed validation of Certificate [Thumbprint 35633602ebcd8512702330af54bf349adb3b9b0a] issued to 'statemigr.something.com' $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Skipping this certificate which is not valid for ConfigMgr usage. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
>>> Selected Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' for HTTPS Client Authentication $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Failed to send http request /SMSSMP/.sms_smp?op=healthcheck. Error 12030 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Call to HttpSendRequestSync failed for port 443 with 12030 error code. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Health check operation failed, error code is 12030 $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.289-60><thread=1196 (0x4AC)>
Completed availability check on local machine $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.305-60><thread=1196 (0x4AC)>
Initialization still in progress. $$<SMS_STATE_MIGRATION_POINT><03-24-2015 20:30:20.305-60><thread=1196 (0x4AC)>The server has two certificates, one with client auth and one with server auth capabilities. As you can see in the log, the certificate with the server auth capability is ignored and the client auth is succesfully selected:
>>> Selected Certificate [Thumbprint b1b24deaaa109fa76f892a1ded986dca246d4f60] issued to 'statemigr.something.com' for HTTPS Client Authentication $$<SMS_STATE_MIGRATION_POINT>
This client certificate has been (and still is) working for client authentication of the distribution point on the same server for months. -
Hallo,
I have SCCM 2007 RTM everything is working, but i get this error from Component 'SMS_State_Migration_Point':
SMP Control Manager detected SMP is not responding to HTTP requests. The http status code and text is 500, Internal Server Error.
Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate.
Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use.
Possible cause: The designated Web Site is disabled in IIS.
Solution: Verify that the designated Web Site is enabled, and functioning properly.
Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges.
Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy.
For more information, refer to Microsoft Knowledge Base.
The IIS is working, for example SMS-Reporting. Where do i configure the ports SMS communicate with IIS?
Thanks
Andreas ScheerSrikanth,
I am experiencing the same issue as Tom. Here is an excerpt from my smpisapi log:
========== GetExtensionVersion ==========
smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
SMPRequestHandler::Initialization started.
smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
SMS Sitecode = 001 smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
Inserted store "d:\SMP\" to cache smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
Inserted store "D:\SMP\" to cache smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
Initialization of SMP store completed smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
Started SMPStoreMgr worker thread smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
SMPStoreMgr is now initialized smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
Initializing smpPerfObject. smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
smpPerfObject initialization complete. smpisapi 12/12/2007 1:39:58 PM 3232 (0x0CA0)
========== BEGIN: HttpExtensionProc ========== smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
Query string to parse: 'op=healthcheck'. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
Creating state store - D:\SMP\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
Statestore - D:\SMP\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473 exists. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
SecureAccess failed with error code (80070005) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
AddACE to store with access account domain.com\HOST$ failed for directory \\domain.com\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
Revoke access failed for directory \\domain.com\SMPSTORED_91DAA93F$\FBC02D2321401636EFBD99756C5AAF338C3D018C06B9724EB56B409163928473. smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
StatusRequest::UpdateStatus failed with errorcode (0x80070005) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
StatusRequest::HandleMessage failed with errorcode (0x80070005) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
Failed to process CAPTURESTATUS request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
SMPRequestHandler::HandleMessage for StoreOp CAPTURESTATUS failed with server errorcode 99 smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
HealthCheckRequest::HandleMessage failed with errorcode (0x80040063) smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
Failed to process HEALTHCHECK request for client GUID:33BB9A27-9705-4553-A4F4-C2A46C17ACFB smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
SMPRequestHandler::HandleMessage for StoreOp HEALTHCHECK failed with server errorcode 99 smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
Returning status "500 Internal Server Error" smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0)
========== END: HttpExtensionProc ========== smpisapi 12/12/2007 1:44:58 PM 3232 (0x0CA0) -
Collecting USMT data to State Migration point without imaging.
Hey can anyone help out with this. We are trying to capture user data from one workstation to another using the SCCM and USMT. It works great...for in place migration, but here is the scenerio:
user Bob, gets a new workstation, he wants to back all of the data up from the old workstation to the new workstation. From what I can see as of right now, the only way to do that is to reimage it with USMT, and then associate the computer within
SMP in the console to the new workstation.
Is there a way I can just boot the OS into PE capture the data to the SMP and go from there?
Hope that made sense.
ThanksYou've just described a side-by-side migration and your assumption is almost correct.
This is the process:
1. Create computer association between old & new
2. Create TS with USMT capture to SMP (custom task sequence with USMT only)- deploy to old (you don't have to re-image the old computer - just capture the data)
3. Create TS with OSD and UMST restore - deploy to new
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
User State Migration using SMP with config manager 2012 R2
Hi ,
I have SMP at primary site and need to migrate XP and 7 machines using this SMP (using USMT),
what are the steps do i need to define in TS so that usmt can use State migration point for user setting\data backup?
Another challenge i see it with XP since we are deciding to take 2 phase approach, that means we will backup data using 1 TS (3 step TS) and then restore data as part of another TS that will install windows 8.1 also with user state restore.
Any pointers if we need to define anything special in TS (migration store etc.) or since its SMP, TS should able to take care of finding it automatically and backup\restore user state?
We have MDT based TS, just wondering if we need to define anything inside CS.ini file related to SMP?
Any pointers will be appreciated. Thanks
Regards,Hi,
Please refer to the link below:
How to migrate user data from Windows XP to Windows 8.1 with System Center 2012 R2 Configuration Manager
http://blogs.technet.com/b/configmgrteam/archive/2013/09/12/how-to-migrate-user-data-from-win-xp-to-win-8-1-with-system-center-2012-r2-configmgr.aspx
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 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 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] -
Application Catalog Website Point Status Critical - But why?
I am having some tracking down what is causing this status on a customer's primary site. I've checked the portlctl.log and awebsctl.log where both show a status 0 of running. When I try to reset the status of the Application Catalog website point the status
does not reset and there are no error messages when I query the status messages. Is there something else I can do to try and get the status into the right state?
www.bighatgroup.comI've seen this behavior more often, with different customers. It's always the Application Catalog web site point that shows an error state while it's functioning correct. From what I've seen, the behavior starts after a reinstallation of the role, either
because of a hotfix, service pack, or cu installation.
Also the only workaround I've found so far that works, is reinstalling the role again...
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude -
WCS building shows status as critical, but APs are green.
Hello,
I'm new to the realm of wireless and I'm at a loss of how to resolve this. In WCS when I look at buildings on the map, it shows the status as critical with a red triangle, but when you click on the building all access points are green and okay. Any thoughts?
Thank you for your time.You might want to read back through the logs and see what errors had been reported for the building.
Steve
Sent from Cisco Technical Support iPad App -
Recovery Point Status Report Shows Only One Day
Hello. Our Recovery Point Status Report showed us the last five days until about a month ago and now it only shows us one day. Just happened over a week-end when there was nothing changed on the server. We appear to have recovery points that go back
a week and the recovery point status is set to a month. We are running System Center 2012 R2 DPM.
Any help is appreciated, thank you for your time.
gHi,
Check your status report granularity settings for each protection group and make sure it's set for 1 day instead of weekly.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. -
Database replicaton link status shows unknown
I have an issue with our newly built ConfigMgr 12 R2 hierarchy. We are running SQL12 Sp1 CU6 on our Primary. Our Secondary sites are running express with the same SP and CU level.
I am in the process of migrating objects from our existing CM07. Migration seems to be working fine between source and destination. When I try to distribute software, I see it as successful to the primary, but the remote distro points were stuck at "In
Progress" for hours. I assumed that I had an issue with the distribution, but I see all the files are being downloaded to the correct folders on the distro points.
I checked database replication status and all sites showed as Link state=unknown.
After rebooting the primary site server, checked the database replication status and it shows green. Checked the content status and the distro points are showing updated.
After about 30 minutes, the database replication goes back to unknown. I can only get updated status after a reboot.
Hopefully someone has seen this and has a resolution.
MikeHi,
The Replication Anlyzer is very important to this issue. You need to run it and see what it tells and post the log and xml file here if possible.
Also, take a look at a valuable blog.
http://blogs.msdn.com/b/minfangl/archive/2012/05/16/tips-for-troubleshooting-sc-2012-configuration-manager-data-replication-service-drs.aspx
Juke Chou
TechNet Community Support
Maybe you are looking for
-
Hi Experts we are facing an issue where there is a balance amount left in GR/IR acct because of exchange rate diff . As per my understanding if there is a quantity difference between GR and IR account , then we do MR11 . But in this case there is a
-
Hello, I am receiving the following error message when I try to access any webpage using Safari 2.0.4: Forbidden You don't have permission to access http://www.8notes.com/guitarchordchart/Fmaj7.asp on this server. Apache Server at www.8notes.com Port
-
We created a pdf document with comments and hyperlinks. On iPad, comments/hyperlinks disappear.
Using Acrobat Pro 9, we created a pdf with comments and hyperlinks to be shared with a large community on the iPad, through a server. Once the document is opened on the iPad, all the comments and hyperlinks disappear. Are we missing a tool on the iPa
-
Anyone heard of a problem with the mouse button on a Satellite A30, the left mouse button is solid, it just doesnt press down at all so I have to use an external mouse, Im wary of trying to prize it out to have a look without damanging it further, an
-
10gAS, proxy server and client ip address
Hello, We recently deployed an application in a 10G application server, running behind an apache reverse proxy server. Our developers want to get the client ip addresses, which the proxy server passes in the the header x-forwarded-for. They're curren