SCCM 2012 Alerts

Hi Guys
I'm new to System Center and busy learning the product, the thing is that we have recently deployed SCCM 2012 R2 on our network, but im having issues creating alerts, i need to create an alert that when a server is shutdown or restarted that we are notified
via email "helpdesk"
I also need to create reports to monitor the processors and memory usage and HDD space on all the servers.
any advice is greatly appreciated.
Thanks.

ConfigMgr is not supposed to be used for alerts and reports about that kind of information. There is another product in the System Center stack that provides information like that and that's System Center Operations Manager (http://technet.microsoft.com/en-us/library/hh205987.aspx).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

Can SCCM 2012 alert me when new devices are found on the network?

I have a single SCCM 2012 SP1 CU4 server running on Windows Server 2012. I use it primarily for Endpoint Protection and Windows Updates.
I have 18 locations in my organization. I am having a problem with a particular remote site buying their own IT equipment (computers, switches, access points, etc.). I was wondering if it is possible for my SCCM server to e-mail (alert) me whenever
it detects a new device on the network? Or should I be looking at
SCOM for something like this? If SCCM will not do this, can anyone suggest some freeware that might do what I am looking for?
Thanks!

The answer to that would be ... it depends.
If the computers are domain joined and your AD discovery method is enabled they will end up in the ConfigMgr database. From that point onward you could create a custom reports that lists these systems. You can subscribe to the report to get it through email.
For network devices you could also do something similar but initially you would have to enable network discovery in ConfigMgr.
Highly impractical IMO. I seriously doubt this could ever work in a production environment of any real size.
In addition.... Network discovery in CM is nasty!
John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

SCCM 2012 - how can i make it alert in SCOM if a deployment fails

Can anyone suggest a post or tell me how to get alerts in SCOM when a deployment from SCCM 2012 fails?
The situation is we deploy Microsoft patches on a monthly basis to all workstations in the company, I want an alert in SCOM if the deployment fails to a particular workstation to ensure that we are aware of them and can fix them.

Hi,
You could configure that in Deployment properties Alert tab as the following screenshot.
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.

Alert: Synchronization failure alert for software update point ( SCCM 2012 R2)

SCCM 2012 R2
Alert: Synchronization failure alert for software update point: MY.net(MY)
Alert type: Software update synchronization failure
Severity: Critical
Active time (UTC): 13-09-2014 19:37:34
Condition: Generate an alert if software updates synchronization fails for the Software Update Point role at the
MY (MY) site.
Alert Text: Software updates synchronization for the Software Update Point role at the
MY (MY)) site failed.
Please let me know what will be the cause of this Alert, how to resolve it

The reason is stated in the message: "Generate an alert if software updates synchronization fails
for the Software Update Point role at theMY (MY) site"
Examine wsyncmgr.log
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 integration with SCOM 2012 - Disable Alerts during patching

Have SCCM 2012 R2 and SCOM 2012 R2 and use the Software Update Patching process for servers. When using the checkbox to "Disable Operations Manager Alerts when this program runs" option have noticed on completion of the job and the target
server is rebooted, a scheduled task appears for a short time titled "SCOM 2007 Agent Resume Task". The task disappears and there is no history to view.
Is this a legacy naming convention from 2007 world when the maintenance mode is turned off from the SCCM patching process?
How do I see the actual code behind the SCCM and SCOM integration with Maintenance mode to validate it.

SCCM should use the following SCOM SDK to do that.
http://msdn.microsoft.com/en-us/library/bb437532.aspx
That's incorrect. There is no API or method to put an OpsMgr agent into maintenance mode on the client itself -- maintenance mode is a centrally controlled feature of OpsMgr. The API/code sample you linked is performing that activity on the management server
which assumes you know the management server name and have permissions to carry out the action -- neither of which is fulfilled by the ConfigMgr agent.
The ConfigMgr agent pauses the OpsMgr client agent service and also unloads the workflows from the OpsMgr agent (it only did the first part in ConfigMgr 2007). This effectively puts the agent in Maintenance Mode (although to my knowledge this is not directly
reflected in the OpsMgr console).
Jason | http://blog.configmgrftw.com

AMT 3.2.10 Clients with SCCM 2012 on Windows 2012

Hey
I have a couple of HP dc7800 computers with Intel's AMT/vPro that I'd like to provision with SCCM 2012. The installed firmware version is 3.2.10 which is a supported version according to the documentation [1]. Provisioning of newer clients (5.2.x upwards)
is successful, so I can rule out all the usual suspects like the provisioning certificate from GoDaddy, our internal CA, DHCP options, etc. Provisioning with SCCM 2007 of both 3.2.x and 5.x AMT devices is also still successful.
The amtopmgr.log repeatedly shows the following entries:
Provision target is indicated with SMS resource id. (MachineId = 16777325 WS45.mydomain.ch)
Found valid basic machine property for machine id = 16777325.
Warning: Currently we don't support mutual auth. Change to TLS server auth mode.
The provision mode for device WS45.mydomain.ch is 1.
The IP addresses of the host WS45.mydomain.ch are x.x.x.x.
Root hash of provisioning certificate is 2796BAE63F1801E277261BA0D77770028F20EEE4.
Attempting to establish connection with target device using SOAP.
Create provisionHelper with (Hash: 74B7792EDBD64EBB01E2E3A0B27FAFA04C2D3BCB)
Set credential on provisionHelper...
Try to use provisioning account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioning account #0.
Try to use default factory account to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using default factory account.
Try to use provisioned account (random generated password) to connect target machine WS45.mydomain.ch...
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.
**** Error 0x37f2b370 returned by ApplyControlToken
Fail to connect and get core version of machine WS45.mydomain.ch using provisioned account (random generated password).
Error: Device internal error. This may be caused by: 1. blabla...
Error: Can NOT establish connection with target device. (MachineId = 16777325)
After some investigation with Wireshark, I've found out that SCCM tries connect with TLSv1 to the AMT device. The response from the device is immediately an SSL alert (internal error). Using OpenSSL, I could connect to the device if I explicitly told it
to use SSLv3. This leads me to believe that the 3.2.x firmware cannot handle TLSv1 correctly and SCCM never tries to connect with SSLv3 after a failure.
So the question is: How can I get SCCM 2012 to provision these devices?
Regards,
Ingo
[1]
http://technet.microsoft.com/en-us/library/c1e93ef9-761f-4f60-8372-df9bf5009be0#BKMK_SupConfigOOB

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2012 after SP1 replication link has failed

Hi guys,
after install SP1 on SCCM 2012 I have problem with Global Data Replication status and Site Data replication status on P02. Where I have C01 and P01, P02, P03, P04. P02 is the only one which is broken more. Rest of primary sites have ok
Global Data Replication status.
Site P02 is after 1 week from patch console still in Read Only mode rcmctrl.log says: The current site status: ReplicationMaintenance.
CAS C01 have in rcmctrl.log
ERROR: Replication group "General_Site_Data" has failed to initialize for subscribing site C01, setting link state to Error.
Retry for process replication is requested.
Cleaning the RCM inbox if there are any *.RCM files for further change notifications....
Rcm control is waiting for file change notification or timeout after 60 seconds.
No connector role installed
DRS change application started.
Site is NOT active, so not calling the DrsActivation procedures on DRSSite queue.
replmgr.log says nothing special to be mentioned.
and when I run Replication Link Analyzer on C01 against Link to P02 it says :\
ReplicationAnalysis.xml:
Replication initialization is in progress for replication groups EndpointProtection_Site, Medium_Priority_Site, Operational_Data, General_Site_Data, MDM_SiteSpecial, MDM_Site. Found replication groups Replication Configuration that needs to be re-initialized.
Reason code: ReinitializeSenderDespoolerError. Replication initialization is in progress for replication groups Site Control Data, Configuration Data, Registration Data, Language Neutral, Asset Intelligence Knowledge Base, EndpointProtection_ThreatMetaData,
Alerts, Group Relationships. "
Target site P02 is in maintenance mode. Not checking transmission messages sent to queue ConfigMgrDRSQueue. Target site P02 is in maintenance mode. Not checking transmission messages sent to queue ConfigMgrDRSQueue
Target site C01 is in maintenance mode. Not checking transmission messages sent to queue ConfigMgrDRSQueue. Target site C01 is in maintenance mode. Not checking transmission messages sent to queue ConfigMgrDRSQueue
so I need to somehow quit this maintenance mode. following this link did not helped me:
http://blogs.msdn.com/b/minfangl/archive/2012/05/16/tips-for-troubleshooting-sc-2012-configuration-manager-data-replication-service-drs.aspx
I restarted all these 5 servers with no luck.
thank you for any hint/ help
Jaromir
Jaromir

in my case in rcmctr.log is visible on CAS and primary site this message: ERROR: Replication group "General_Site_Data" has failed to initialize for subscribing site C01, setting link state to Error.
but today we moved in this situation and my P02 2nd primary site fall out from maintenance mode and a lot of replication happened but General_Site_data still remain in problem.
steps taken were: goto monitoring node > database replication > choose link which has problem and on the bottom check Initialization Detail
you can see which replication Group has problem.
Then in SQl server management studio we run following command with relevant name of Sites and Replication Group which are affected in my case
select * from RCM_DrsInitializationTracking
where replicationGroup = 'General_Site_data' AND SiteFulfilling='P02'
it will show you status
then this update query will force that replication group to start replicate(parameter 7):
we run this many times against same or different replication groups which ahd problems
update RCM_DrsInitializationTracking set InitializationStatus = 7 where ReplicationGroup = 'general_site_data' and SiteRequesting = 'C01' and SiteFulfilling = 'P02'
it's still not win but we are moving forward. And it doesn't has to be same issue like you have but it can point you to somewhere...
J.
Jaromir

SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

Hi All,
Good day to all you.
I would like to seek all your help on this issue that i have encountering.
My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
Error:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
below are wsyncmgr.log:
Setting sync alert to active state on site C01 SMS_WSUS_SYNC_MANAGER (0x1690)
Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Starting Sync SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Read SUPs from SCF for MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
5776 (0x1690)
Synchronizing WSUS server MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
5776 (0x1690)
Using account sdb\SCCM-Admin to connect to WSUS Server
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Synchronizing WSUS server myhqkul990707s.sdb.com ...
SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
440 (0x01B8)
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
All response is much appreciated
Thank You

Hi,
I recommend you look at the IIS log. Maybe it can give us some clues.
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.

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.

SCCM 2012 and SQL 2008 R2 Sync problems

Hi
I installed 2 servers for SCCM 2012:
-1 with SCCM 2012, FEP, WSUS console admin
-1 with SQL Server 2008 R2 complete install, WSUS complete install
When I made or the system mades the synchronization, it shows this error in SMS_WSUS_SYNC_MANAGER:
Error 6703:
WSUS Synchronization failed.
Message: Failed to sync some of the updates.
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates.
And in the wsyncmgr.log appears:
sync: SMS synchronizing updates, processed 3336 out of 3368 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:14:11.663+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3360 out of 3392 items (99%), ETA in 00:00:06 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:15:11.669+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3383 out of 3415 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:16:13.206+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3412 out of 3444 items (99%), ETA in 00:00:07 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:14.152+300><thread=4640 (0x1220)>
Synchronized update 3a572bd0-5976-4abc-b2d8-955008c5466f - Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.131.558.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:17:18.227+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3446 out of 3463 items (99%), ETA in 00:00:04 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:14.400+300><thread=4640 (0x1220)>
Synchronized update 3eeb75c2-81aa-4cc0-9b7a-237a6a0bf737 - Definition Update for Microsoft Security Essentials - KB2310138 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:18:47.964+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3482 out of 3484 items (99%), ETA in 00:00:00 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:19:15.587+300><thread=4640 (0x1220)>
Synchronized update 74e86346-9384-4304-9625-2c865738c552 - Definition Update for Microsoft Endpoint Protection - KB2461484 (Definition 1.131.574.0). $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.659+300><thread=4640 (0x1220)>
sync: SMS synchronizing updates, processed 3508 out of 3508 items (100%) $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.662+300><thread=4640 (0x1220)>
Sync failures summary: $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:05.664+300><thread=4640 (0x1220)>
Failed to sync update 1ba2d28f-75fe-49d7-9cb4-cd39b8706f48. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.666+300><thread=4640 (0x1220)>
Failed to sync update 8a042978-e6d7-4ae6-b3ab-687d8f9bcd9c. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.669+300><thread=4640 (0x1220)>
Failed to sync update a3aff37b-ad3b-4dde-9464-767a516c76e5. Error: Failed to get SQL connection. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.RemoveUpdate $$<SMS_WSUS_SYNC_MANAGER><07-24-2012
09:20:05.671+300><thread=4640 (0x1220)>
Sync failed: Failed to sync some of the updates. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.421+300><thread=3536 (0xDD0)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=GDVSCCM1.gdar.local SITE=CRP PID=1908 TID=3536 GMTDATE=mar jul 24 14:20:06.423 2012 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates"
ISTR1="Failed to sync some of the updates" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.425+300><thread=3536 (0xDD0)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.501+300><thread=3536 (0xDD0)>
Setting sync alert to active state on site CRP $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.503+300><thread=3536 (0xDD0)>
Updated 173 items in SMS database, new update source content version is 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.526+300><thread=3536 (0xDD0)>
Set content version of update source {6A4B4446-1B80-4CF4-838D-405D3847A8E3} for site CRP to 36 $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.572+300><thread=3536 (0xDD0)>
Sync time: 0d00h19m46s $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 09:20:06.575+300><thread=3536 (0xDD0)>
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:06.651+300><thread=3536 (0xDD0)>
Next scheduled sync is a retry sync at 24/07/2012 10:20:06 a.m. $$<SMS_WSUS_SYNC_MANAGER><07-24-2012 10:00:11.940+300><thread=3536 (0xDD0)>
Why is this behavior?
Thanks
Doc MX

Hi
Today I think I discovered what was the problem:
I used an user in the domain for deploying the role of SUP, but I forgot to put that user in the group of SQL Admins of the SQL Server.
I done that and after reseting the servers, the error for sync with SQL didn't appear again, al least from this morning until now, before this change every hour showed the error 6703.
Thanks to all for your comments.
Doc MX

Failed – Site Backup Task at site SCCM 2012.

I configured Backup of SCCM 2012 on my site Primary.
I indicated folder in other server for my Backup of SCCM and SQL, I started all services of Backup in two servers and I gave permission for Everyone in the Sharing and Security.
This is image of my SCCM, in tab Backup Site Server Properties:
This is log of archive smsbkup.log
Can anyone help me?
Regards,
Thiago Batista.
http://www.gestaoemti.com.br/

I have a similar issue.
My site backup task is running. The logs show both the Site components and SQL DB backups completing mostly.
Site Server smsbkup.log
LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,880) SMS_SITE_BACKUP 1/17/2015 7:51:46 PM 5200 (0x1450)
FinalSnapshotPath =
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES\. SMS_SITE_BACKUP 1/17/2015 7:51:46 PM 5200 (0x1450)
Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\inboxes. SMS_SITE_BACKUP 1/17/2015 7:53:40 PM 5200 (0x1450)
FinalSnapshotPath =
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS\. SMS_SITE_BACKUP 1/17/2015 7:53:40 PM 5200 (0x1450)
Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\Logs. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
FinalSnapshotPath =
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA\. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\data. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
FinalSnapshotPath =
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT\. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer\srvacct. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
FinalSnapshotPath =
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Program Files\Microsoft Configuration Manager\install.map. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
Backup Succeeded for Component - SI4Backup\SiteServer\SMSServer. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
FinalSnapshotPath =
\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
Backup Succeeded for Component - SI4Backup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
Waiting On SQL Backup for component sccmsi4 to complete... SMS_SITE_BACKUP 1/17/2015 7:53:48 PM 5200 (0x1450)
Sleeping for 30 seconds... SMS_SITE_BACKUP 1/17/2015 7:53:49 PM 5200 (0x1450)
Sleeping for 30 seconds... SMS_SITE_BACKUP 1/17/2015 7:54:19 PM 5200 (0x1450)
Database Server smsbkup.log
Updating the status to [snapshot done]. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:50:50 PM 2420 (0x0974)
Starting the backup complete phase. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:50:50 PM 2420 (0x0974)
Backup Succeeded for Component - SCCMSI4. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974)
Updating the database status to [SCCMSI4:Succeeded;]. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974)
Successfully created the backup metadata file - E:\Site_Backup\SI4Backup\SiteDBServer\\SQLBackupDocument.xml SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974)
Info: Starting asynchronous BackupComplete... SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:42 PM 2420 (0x0974)
Info: Asynchronous BackupComplete finished. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974)
After BackupComplete SQL Writer status = STABLE. SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974)
Updating the status to [backup completed]. SMS_SITE_SQL_BACKUP_P-SC-SCM04.SDOMAINNET 1/17/2015 7:52:43 PM 2420 (0x0974)
SQL backup completed - Sat Jan 17 19:52:43 2015 SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974)
Waiting for the Event Notification... SMS_SITE_SQL_BACKUP_P-SC-SCM04.DOMAIN.NET 1/17/2015 7:52:43 PM 2420 (0x0974)
At the end of the smsbkup.log, after a loooonnnnggg time, the backup task finally times out with this message.
Sleeping for 30 seconds... SMS_SITE_BACKUP 12/25/2014 2:11:53 PM 4296 (0x10C8)
Sleeping for 30 seconds... SMS_SITE_BACKUP 12/25/2014 2:12:23 PM 4296 (0x10C8)
Error: SQL Backup failed for component sccmsi4 SMS_SITE_BACKUP 12/25/2014 2:12:53 PM 4296 (0x10C8)
ERROR: Timed out waiting for SQL backup for component sccmsi4 SMS_SITE_BACKUP 12/25/2014 2:12:53 PM 4296 (0x10C8)
Error: Backup Failed for Component - SI4Backup\SiteDBServer\SMSbkSQLSiteDB.dat.
SMS_SITE_BACKUP 12/25/2014 2:12:53 PM 4296 (0x10C8)
Successfully created the backup metadata file -
\\p-sc-fs04\IT\sccm_site_backup\SI4Backup\BackupDocument.xml SMS_SITE_BACKUP 12/25/2014 2:12:53 PM 4296 (0x10C8)
STATMSG: ID=5057 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=P-SC-SCM04.DOMAIN.net SITE=SI4 PID=9084 TID=4296 GMTDATE=Thu Dec 25 22:12:53.196 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
StateTable::CState::Handle - (5057:1 2014-12-25 22:12:53.196+00:00) >> (5056:1 2014-12-25 10:07:15.149+00:00) SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
CStateMsgReporter::DeliverMessages - Queued message: TT=1401 TIDT=0 TID='EF736CF9-7214-4796-9C85-2549A9056D8D' SID=5057 MUF=0 PCNT=2, P1='SI4' P2='2014-12-25 22:12:53.196+00:00' P3='' P4='' P5='' SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296
(0x10C8)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\e0f0ts1r.SMX SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
Successfully send state change notification EF736CF9-7214-4796-9C85-2549A9056D8D SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
LogEvent(): Successfully logged Event to NT Event Log. (4 - 48 - 1,073,746,881) SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
Waiting On SQL Backup task status... SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
STATMSG: ID=5054 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=P-SC-SCM04.DOMAIN.net SITE=SI4 PID=9084 TID=4296 GMTDATE=Thu Dec 25 22:12:55.789 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
SQL Backup task completed successfully... SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
Info: Starting asynchronous BackupComplete... SMS_SITE_BACKUP 12/25/2014 2:12:55 PM 4296 (0x10C8)
Info: Asynchronous BackupComplete finished. SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296 (0x10C8)
After BackupComplete SMS Writer status = STABLE. SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296 (0x10C8)
WARNING: SMS backup failed for atleast one component. Please check previous errors. SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296 (0x10C8)
SMS_SITE_BACKUP failed. Please see previous errors. SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296 (0x10C8)
STATMSG: ID=5060 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=P-SC-SCM04.DOMAIN.net SITE=SI4 PID=9084 TID=4296 GMTDATE=Thu Dec 25 22:12:57.423 2014 ISTR0="WARNING: SMS backup failed for atleast one component. Please check
previous errors." ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296
(0x10C8)
SMS_SITE_BACKUP service is stopping. SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296 (0x10C8)
STATMSG: ID=502 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_SITE_BACKUP" SYS=P-SC-SCM04.DOMAIN.net SITE=SI4 PID=9084 TID=4296 GMTDATE=Thu Dec 25 22:12:57.423 2014 ISTR0="SMS_SITE_BACKUP" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296 (0x10C8)
Raised backup task failure alert. SMS_SITE_BACKUP 12/25/2014 2:12:57 PM 4296 (0x10C8)
I'm not sure where to go on this. I've tried a bunch of things like permissions, local vs., remote backup target.

Software Update error - SCCM 2012 SP1

HI,
I have SCCM 2012 SP1 installed on Windows server 2008 R2 server. I have configured SUP role and tried sync from sccm console. I get the below error.
LOg:
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:11:42.047+00><thread=3840 (0xF00)>
WSUS sync running~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:12:42.255+00><thread=3840 (0xF00)>
Microsoft.SystemsManagementServer.WSUS.WSUSMSPException: WSUS sync failed with UssCommunicationError: ~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.IsSyncRunning() $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.462+00><thread=3840
(0xF00)>
Done using DEVSWAD\SWDTR-SRV-CMPATCH credentials~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
Failed to set Subscriptions on the WSUS
. Error:(-2146233088)Unknown error 0x80131500~ $$<SMS_WSUS_CONFIGURATION_MANAGER><01-30-2014 14:13:12.478+00><thread=3840 (0xF00)>
STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=3840 GMTDATE=Thu Jan 30 14:13:12.479 2014
I have configured proper proxy account which can connect to microsoft website and the port i have configured in proxy to allow is
80 and 443. I feel the port i need to allow may be i am not sure 8530 and 8531. Or 80 and 443 is fine. Please help
Regards, Pratap

It says to check WCM.log which i posted above
wsync log:
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.118+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 14:02:14.119 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please
refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.122+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.123+00><thread=4388 (0x1124)>
Sync time: 0d00h00m00s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 14:02:14.132+00><thread=4388 (0x1124)>
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:14.495+00><thread=4388 (0x1124)>
Starting Sync $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.157+00><thread=4388 (0x1124)>
Performing sync on retry schedule $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.163+00><thread=4388 (0x1124)>
Read SUPs from SCF for DCMPSTPV01.devswad.net $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.577+00><thread=4388 (0x1124)>
Found 1 SUPs $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.830+00><thread=4388 (0x1124)>
Found active SUP DCMPSTPV01.devswad.net from SCF File.~ $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.833+00><thread=4388 (0x1124)>
Sync failed: WSUS update source not found on site SCW. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.876+00><thread=4388 (0x1124)>
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DCMPSTPV01.devswad.net SITE=SCW PID=2764 TID=4388 GMTDATE=Fri Jan 31 15:02:15.882 2014 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCW. Please refer
to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.892+00><thread=4388 (0x1124)>
Sync failed. Will retry in 60 minutes $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.912+00><thread=4388 (0x1124)>
Setting sync alert to active state on site SCW $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:15.915+00><thread=4388 (0x1124)>
Sync time: 0d00h00m01s $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.024+00><thread=4388 (0x1124)>
Next scheduled sync is a retry sync at 31/01/2014 16:02:15 $$<SMS_WSUS_SYNC_MANAGER><01-31-2014 15:02:17.151+00><thread=4388 (0x1124)>
Regards, Pratap

SCCM 2012 R2: Forefront Endpoint protection via automatic updates only work when manually triggering automatic updat rule

Hi,
I followed this manual to configure forefront endpoint protection on clients: http://www.windows-noob.com/forums/index.php?/topic/6106-using-system-center-2012-configuration-manager-part-6-adding-the-endpoint-protection-role-configure-alerts-and-custom-antimalware-policies/
Now in short: everything works fine ... as long as I trigger the audomatic deployment rules.
Current situation:
1. ADR ran fine (3:30 this night)
2.Software update group is NOT ok
3.I run ADR manually (right click on ADR, run)
4.software update group is ok (green icon)
Then virusupdates are succesfull. This means that clients only update their virus definitions when I manually run the ADR-rule.
I'm missing something here.
Please advise.
J.
Jan Hoedt

Probably this issue: http://social.technet.microsoft.com/Forums/en-US/c6109678-785b-4c6d-9cb4-c9dfc1e34b2e/sccm-2012-automatic-deployment-rule-not-executing-updates-for-scep?forum=configmanagerapps
Iow: wsus updates were scheduled at 3, automatic update rules at 3:15, probably sync wasn't done yet so it doesn't find updates. "The day after" updates are marked as expired.
Jan Hoedt

SCCM 2012 SP1 Maintenance -- Random Environments Rebooting Early

Background on my deployment process for SCCM 2012 SP1: I run a Powershell script that sends out a package and configures settings exactly the same for the particular environment set.
The deployment script will call one or several environments at a time, as applicable.
It will take each environment, affix the settings, push the package to be deployed (based on OS) during the specified maintenance window, and repeat. It is a very consistent process.
Last week, I deployed to A-CLOUD (name changed for simplicity purposes), among others.
A-CLOUD went through the same process as the others in the script (see end of paragraph), in which the appropriate settings were checked.
The environment was supposed to update and reboot on Saturday, July 12.
However, A-CLOUD (only) updated and bounced as soon as I sent out the package on Wednesday, July 9.
Also in the same deployment script was B-CLOUD, C-CLOUD, D-CLOUD, and E-CLOUD, which all updated and rebooted as planned on July 12.
I received an alert that A-CLOUD was rebooted by Configuration Manager. I checked the reboot logs in Task Scheduler to compare A-CLOUD with C-CLOUD days later to compare a faulty reboot with one that ran correctly
(both of these environments are on the same site). There was no difference in the log files.
This issue occurs at least one a month and I have only noticed ONE pattern, Server 2008R2 -- however, it is not always the same environment that will reboot early each month, same week, same day, etc. It seems to be
random.
Any ideas?

This is way too generic to be answered. What ConfigMgr object type are you deploying (package? application?)? How is the reboot initiated? How are the deployment settings etc.?
Torsten Meringer | http://www.mssccmfaq.de

Exchange configuration in SCCM 2012

Hi All,
I was configuring Exchange server connectors on SCCM 2012 SP1 & our organization is using office 365 as exchange so, how do we configure this.
There are options for on premise exchange server & hosted exchange server where should i put this.
Thanks,
Pranay.

Thanks Jorgen, the post was great.
Configured the settings as per the link but got this error in Easdisc.log
ERROR: Failed to initialize managed com instance. Error = Unknown error 0x80131501, -2146233087~ $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:26:21.516-330><thread=3472 (0xD90)>
INFO: End to process for discovery https://outlook.com/PowerShell-LiveID. $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:26:21.516-330><thread=3472 (0xD90)>
INFO: CRC for SCF not changed. $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:26:21.771-330><thread=7388 (0x1CDC)>
INFO: Raise Exchange Connector connection failure alert. $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:26:21.817-330><thread=7388 (0x1CDC)>
INFO: CRC for SCF not changed. $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:26:22.082-330><thread=7388 (0x1CDC)>
INFO: Waiting 3600 seconds for SCF update notification... $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:26:22.082-330><thread=7388 (0x1CDC)>
INFO: Start to process wipe/policy https://outlook.com/PowerShell-LiveID. $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:28:24.767-330><thread=6924 (0x1B0C)>
INFO: [MANAGED] Initialize: ExchangeServer https://outlook.com/PowerShell-LiveID, Account (Admin Account Email id), VerboseLog 0~~ $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:28:27.780-330><thread=6924 (0x1B0C)>
ERROR: [MANAGED] Failed to open Runspace. Exception: System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server failed with the following error message : The WinRM client received an HTTP status code of 301 from the remote
WS-Management service. For more information, see the about_Remote_Troubleshooting Help topic.~~ at System.Management.Automation.Runspaces.AsyncResult.EndInvoke()~~ at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult
asyncResult)~~ at System.Management.Automation.Runspaces.RunspacePool.Open()~~ at System.Management.Automation.RemoteRunspace.Open()~~ at Microsoft.ConfigurationManager.ExchangeConnector.ExchangeRunspace.InitRunspace()~~
$$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:28:31.656-330><thread=6924 (0x1B0C)>
ERROR: Failed to call Initialize of managed COM. error = Unknown error 0x80131501~ $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:28:31.657-330><thread=6924 (0x1B0C)>
INFO: Raise Exchange Connector connection failure alert. $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:28:31.765-330><thread=6924 (0x1B0C)>
ERROR: Failed to initialize managed com instance. Error = Unknown error 0x80131501, -2146233087~ $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:28:31.765-330><thread=6924 (0x1B0C)>
INFO: End to process wipe/policy https://outlook.com/PowerShell-LiveID. $$<SMS_EXCHANGE_CONNECTOR><10-07-2013 13:28:31.765-330><thread=6924 (0x1B0C)>
Thanks,
Pranay.

SCCM 2012 Alerts

Similar Messages

Maybe you are looking for