Quantcast
Channel: Configuration Manager 2012 - Security, Updates and Compliance forum
Viewing all 6382 articles
Browse latest View live
↧

Setting client SCEP uninstall

March 16, 2015, 7:53 pm
$
0
0

Can i configure SCCM 2012 ,for client cannot uninstall SCEP ?

if can, how to configure it


anyone can help me?

thank you

↧
Search

Some Clients Not Updating. Reporting "Compliant." hr=8007000E Error in WindowsUpdate.log

March 17, 2015, 8:33 am
$
0
0

I have a significant number (but not all) of my SCCM 2012 R2 CU3 clients not updating though my SCCM software updates. On these problem clients, I get this error in WindowsUpdate.log:

"COMAPI WARNING: ISusInternal::GetUpdateMetadata2 failed, hr=8007000E"

Then these machines report "Compliant" even though they don't install the updates. Almost all of our workstations are Windows 7 SP1 32bit. We are running SCCM 2012 R2 CU3. My site servers are running Windows 2008 R2.

I don't see much in WUAhandler.log or scanagent.log. These client are however, getting my SCEP definition updates just fine. (I have an ADR for those.) And when you go out to Microsoft for security updates it works. I have tried all of the usual Windows Updates repair suggestions (re-register dlls, rename software distribution folder, etc.) And I tried un-installing and re-installing the SCCM client on a problem PC, to no avail. I also tried using a Software Update Group with fewer updates (<100) and targeting a problem system with only that SUG, to no avail.

Any assistance would be greatly appreciated. Thank you.

↧
↧

Is it possible to configure the SCEP client to perform a daily Quick Scan and a weekly Full Scan?

March 17, 2015, 3:46 pm
$
0
0

From what it looks like it appears it can according to the "Default Client Antimalware Policy" as shown here, unless I am reading this wrong:

According to the settings above, does this mean that the SCEP client will perform a Quick Scan the same day that it will also perform a Full Scan?

Another question I have is if I change the Scan Type to Quick Scan instead of Full and keep the daily Quick Scans enabled, is there any difference in this at all and therefore I would have two Quick Scans being performed on a given scheduled day?

I simply want to run a Full Scan once a week and on a daily basis run Quick Scans, but on the scheduled day that the Full Scan runs, DO NOT run the daily Quick Scan.

Is this not a possibility?

Thanks

↧

Windows update KB3000869 superseded, howto make sure we deploy the new version?

March 18, 2015, 5:14 am
$
0
0

Hi,

We deploy(ed) KB3000869 as urgent patch (zero vulnerability patch), I know see it is superseded. How can we make sure this patch is included in our latest patching?

Please advise.

Jan Hoedt

↧

some of the machines are not installing windows updates in SCCM 2012 SP1

March 18, 2015, 6:14 am
$
0
0

I have deployed the current month patches to the machines. But, some of the machines are failed to install.

Most commonly I am getting the below errors in windowsupdate.log ,

ReportREPORT EVENT: {811D3FE5-A254-4C7E-B7F1-6132320AD5E0}2015-02-23 08:18:40:851-00001148101{00000000-0000-0000-0000-000000000000} 080072ee2 CcmExecFailureSoftware SynchronizationWindows Update Client failed to detect with error 0x80072ee2.
::OnScanComplete -Scan Failed with Error=0x80072f78

How to resolve this issue with installing windows updates?

0x80072ee2 looks like time out error.

↧
↧

SCCM 2012 R2 High CPU with Endpoint Protection

March 18, 2015, 8:34 am
$
0
0

SCCM 2012 R2 (no CUs)

Hi,

We've noticed over the past two months that Endpoint has been causing high CPU on servers and workstations.  It was running for six months prior to that without any issue.  We've since split the deployment and install time, split the collections so that servers and workstations update separately, excluded the following path mentioned in this article

http://techat-jack.blogspot.co.uk/2012/09/solved-high-cpu-usage-of-microsoft.html

but although this seems to have improved things slightly, some users still experience a slowdown at the time the updates are downloading and installing.  Anyone have an ideas or had a similar experience?  I can't see anything in the logs which is obviously the cause.

↧

Reboot Pending for Software Updates

March 18, 2015, 9:13 am
$
0
0

I've recently taken over patching our enterprise servers with SCCM2012R2, whereas previously we were using WSUS + Group Policy. I've broadened my scope of SCCM updates to include more severities (critical through low) and classifications. Consequently, there are patches that are needed from past years that were never applied during the WSUS/GPO regime which only installed Critical and Warning updates.

I've been using my predefined maintenance windows of only 2-3 hours to install the updates needed - the past years and this past month's. My deployments do not allow rebooting outside of maintenance windows.

What I've been finding is that as many updates will install during that window as possible and then the whole process will just stop. No reboots are initiated and the service window ends. The Software Center applet shows Restarts Pending for the updates that need it. Unfortunately now I have to wait until the next planned outage in a month to reboot these systems.

Is there a way to make sure that a reboot is initiated during the window always? My understanding is that the updates install as much as they can, but if they past that 15 minute mark needed for a reboot before the window closes, they won't initiate a reboot. I'm hesitant to deploy a reboot script on the tail end of my service windows just to make sure they reboot, as if the system is in the middle of installing an update that could have bad consequences.

↧

Patching sccm database server

March 18, 2015, 11:20 am
$
0
0

I am soon going to be migrating the SCCM DB from being hosted on the primary site server, to a standalone sql box.  I'm curious how others have handled patch scheduling for the DB server.

I have about 15 different server maintenance windows throughout the week. Currently the site server (which is the DB server also) patches at the same maintenance window as other servers, and it isn't a problem.

With separating the db from the site server, do I need to bounce the site server after the DB is rebooted?  Should I separate the patch window for the site server and db server?  Should I isolate those 2 on their own maintenance window?

Just looking for ideas on how others have handled patching with the roles being separate.

site:

single primary site (2k8 r2)

1 primary site server (holds all roles)

3 dist points (2k8 r2)

@1500 clients

soon to be separate db server (2k12 r2 with sql 2014)

↧
Search

Default Security Scope

July 12, 2013, 8:39 am
$
0
0

Is it possible to change the Default "Security Scope" chosen for new or copied objects from "default"?  For example when creating a new task sequence the default scope is set to "default" and I would like to change that default choice so I do not have to change the scope for all new TS's, or more importantly I do not want to forget to change the scope from "default".  This is also a problem when you copy a TS with an already defined Security Scope the copied TS does not copy the Security Scope it assigns "default" as the security scope.

↧
↧

SCUP 2011 Cert for Multiple Forests

March 18, 2015, 3:39 pm
$
0
0
We've been using SCUP 2011 + SCCM 2012 in one forest and have created a cert for SCUP from our domain CA. Now we need to service another forest. I need to add a cert to that new forest so that it's clients trust SCUP. Do I need to install another SCUP server in the new domain with it's own CA-issued cert?

Orange County District Attorney

↧

Old update folders and files not being deleted

March 18, 2015, 5:37 pm
$
0
0

Hi,

On my SCCM 2012 SP1 server I've been removing old update groups and deployment packages to try and clean up. I've noticed though that if I look at the source folder on the drive where the actual files are downloaded to and also I'm assuming where they are pulled from by the clients,  I can still see old folders and files there related to update groups and deployment packages that I deleted.

Is it safe to delete these old folders and files? 

There are probably some older updates, service packs, etc. that I want to keep but I was going to go back and setup some new update groups that don't include older updates, like for Vista or Windows 2003 server for example.

Thanks in advance,

Nick

↧

Troubleshooting Client install SCCM2012

March 19, 2015, 3:21 am
$
0
0

What logs on the SCCM2012 Server side can I use to troubleshoot the client install not installing on workstations?

thanks

Pat

↧

Type mismatch (Error: 80041005; Source: WMI)

July 27, 2012, 12:29 pm
$
0
0

I've created a Configuration Baseline for workstations that checks for the existence of PageFile.Sys on the root of C:\
I've created a Configuration Baseline for servers that checks for the existence of PageFile.Sys on the root of D:\

The compliance reports for several servers and workstations indicates an Error, 'Type mismatch'. 


DcmWmiProvider.log from a client on a Windows Server:
 Initialize called for the provider 7/27/2012 7:16:01 AM
 CreateInstanceEnumAsync called for the provider 7/27/2012 7:16:01 AM
 Query supplied is: select * from CCM_File_Setting where (((Path = "D:\\" AND Name = "pagefile.sys") AND SearchDepth = 0) AND FileSystemRedirectionMode = 1) 7/27/2012 7:16:01 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: D:\ evaluated to : D:\ 7/27/2012 7:16:01 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %WinDir%\System32 evaluated to : C:\Windows\System32 7/27/2012 7:16:01 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %ProgramFiles% evaluated to : C:\Program Files 7/27/2012 7:16:01 AM
 Query for lantern's provider is (redirected path): Select * from FileSystem_FileMetadata where BasePath = "D:\\" and Name = "pagefile.sys" 7/27/2012 7:16:01 AM
 Failed to serialize discovered filesystem object () to wmi object, error: 0x80041005 7/27/2012 7:16:02 AM
 CPermissionWMIProvider::ExecQueryAsync - failed (0x80041005). 7/27/2012 7:16:02 AM
 Failed to precess CFileSystemWMIProvider::ExecQueryAsync.
 Type mismatch (Error: 80041005; Source: WMI) 7/27/2012 7:16:02 AM
 
 
0x80041005:
 Type mismatch
 Source: Windows Management (WMI)

DcmWmiProvider.log from a Windows 7 client:
 CreateInstanceEnumAsync called for the provider 7/27/2012 11:12:15 AM
 Query supplied is: select * from CCM_File_Setting where (((Path = "C:\\" AND Name = "pagefile.sys") AND SearchDepth = 0) AND FileSystemRedirectionMode = 1) 7/27/2012 11:12:15 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: C:\ evaluated to : C:\ 7/27/2012 11:12:15 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %WinDir%\System32 evaluated to : C:\Windows\System32 7/27/2012 11:12:15 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %ProgramFiles% evaluated to : C:\Program Files 7/27/2012 11:12:15 AM
 Query for lantern's provider is (redirected path): Select * from FileSystem_FileMetadata where BasePath = "C:\\" and Name = "pagefile.sys" 7/27/2012 11:12:15 AM
 Failed to serialize discovered filesystem object (c:\pagefile.sys) to wmi object, error: 0x80041005 7/27/2012 11:12:16 AM
 CPermissionWMIProvider::ExecQueryAsync - failed (0x80041005). 7/27/2012 11:12:16 AM
 Failed to precess CFileSystemWMIProvider::ExecQueryAsync.
 Type mismatch (Error: 80041005; Source: WMI) 7/27/2012 11:12:16 AM
 CreateInstanceEnumAsync called for the provider 7/27/2012 11:12:17 AM
 Query supplied is: select * from CCM_File_Setting where (((Path = "C:\\" AND Name = "pagefile.sys") AND SearchDepth = 0) AND FileSystemRedirectionMode = 1) 7/27/2012 11:12:17 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: C:\ evaluated to : C:\ 7/27/2012 11:12:17 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %WinDir%\System32 evaluated to : C:\Windows\System32 7/27/2012 11:12:17 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %ProgramFiles% evaluated to : C:\Program Files 7/27/2012 11:12:17 AM
 Query for lantern's provider is (redirected path): Select * from FileSystem_FileMetadata where BasePath = "C:\\" and Name = "pagefile.sys" 7/27/2012 11:12:17 AM
 Failed to serialize discovered filesystem object (c:\pagefile.sys) to wmi object, error: 0x80041005 7/27/2012 11:12:18 AM
 CPermissionWMIProvider::ExecQueryAsync - failed (0x80041005). 7/27/2012 11:12:18 AM
 Failed to precess CFileSystemWMIProvider::ExecQueryAsync.
 Type mismatch (Error: 80041005; Source: WMI) 7/27/2012 11:12:18 AM
 Initialize called for the provider 7/27/2012 11:18:15 AM
 CreateInstanceEnumAsync called for the provider 7/27/2012 11:18:15 AM
 Query supplied is: select * from CCM_File_Setting where (((Path = "C:\\" AND Name = "pagefile.sys") AND SearchDepth = 0) AND FileSystemRedirectionMode = 1) 7/27/2012 11:18:15 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: C:\ evaluated to : C:\ 7/27/2012 11:18:15 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %WinDir%\System32 evaluated to : C:\Windows\System32 7/27/2012 11:18:15 AM
 CAppExecutionLibrary::ExpandEnvironmentVariables: %ProgramFiles% evaluated to : C:\Program Files 7/27/2012 11:18:15 AM
 Query for lantern's provider is (redirected path): Select * from FileSystem_FileMetadata where BasePath = "C:\\" and Name = "pagefile.sys" 7/27/2012 11:18:15 AM
 Failed to serialize discovered filesystem object (c:\pagefile.sys) to wmi object, error: 0x80041005 7/27/2012 11:18:16 AM
 CPermissionWMIProvider::ExecQueryAsync - failed (0x80041005). 7/27/2012 11:18:16 AM
 Failed to precess CFileSystemWMIProvider::ExecQueryAsync.
 Type mismatch (Error: 80041005; Source: WMI) 7/27/2012 11:18:16 AM

Does anyone know why this is happening?

Terry Wallner

↧
↧

When SCEP is configured to scan removable storage devices, is it an immediate scan?

March 19, 2015, 11:46 am
$
0
0

I would like to know if the SCEP client is configured to scan removable storage devices, such as a USB thumb drive, will it perform the scan immediately when the thumb drive is plugged in?

Thanks

↧

SCUP 2011 - SCCM 2012 - Certificates?

March 19, 2015, 11:35 am
$
0
0
I am getting into the SCCM game fairly late and am trying to setup SCUP 2011 to install 3rd party patches.  

I have tried the following articles and am not able to successfully deploy Flash

http://blogs.technet.com/b/jasonlewis/archive/2011/07/12/system-center-updates-publisher-signing-certificate-requirements-amp-step-by-step-guide.aspx

https://mikeshellenberger.wordpress.com/2010/09/02/system-center-updates-publisher-microsoft-pki/

http://myitforum.com/myitforumwp/2012/08/20/a-better-guide-to-setting-up-scup-with-a-microsoft-pki/

I get the following error when deploying.
----------------------------------------------------------------------------
Error: Invalid certificate signature
 Updates Targeted:
•    Adobe Flash Player 32-bit/64-bit ActiveX 17.0.0.134 APSB15-05(Article ID)
 General:
•    Deployment Name: Adobe Systems, Inc. Software Updates - 2015-03-19 09:55:23 AM
•    Collection: Laptop
 Deployment Settings:
•    Send wake-up packets: No
•    Verbosity Level: Normal
 Scheduling:
•    Deployment schedules will be based on: Computer local time
•    Available to target computers: 3/19/2015 9:55:30 AM
•    Deadline for software update installation: 3/19/2015 9:55:30 AM
 User Experience:
•    User Notifications: Display in Software Center and show all notifications
•    Install software updates outside the maintenance window when deadline is reached: No
•    Restart system outside the maintenance window when deadline is reached: Suppressed
•    If a restart is required it will be: Allowed
 Alerts:
•    On software update installation error generate a Window Event: No
•    Disable Window Event while software updates install: No
 Download Settings:
•    Computers can retrieve content from remote distribution points: Yes
•    Download and install software updates from the fallback content source location: Yes
Package:
  Success: The software updates will be placed in a new package:
•    Adobe
 Content (1):
•    \\SCCM_Server
Software updates that will be downloaded from the internet
  Error: Adobe Flash Player 32-bit/64-bit ActiveX 17.0.0.134
Errors
    Invalid certificate signature
----------------------------------------------------------------------------
    
I have an internal Certificate Authority and tried issuing a certificate based on that, but I am not sure where is the authoritative source for Certificate Template creation, I have found several How-To sites and they all seem different.

I am currently back to the self-signed certificate.  SCCM 2012, WSUS, are both running on the same Server 2008R2 server.

The other thing, I am not sure what I am supposed to do with the Flash updates that I have published through SCUP 2011 with the old certificates.

Thank you for any help you can provide, if there is more information that would be useful let me know.



↧
Search

I am bit confused between the "Enable real-time protection" setting and the "Monitor file and program activity on your computer" setting

March 19, 2015, 12:16 pm
$
0
0

Can someone help what the difference is between these two? I just assumed that if the "Enable real-time protection" setting was set to No, then file and programs would not be monitored.

Thanks

↧

What does SCEP consider a system file?

March 19, 2015, 1:27 pm
$
0
0

In the default antimalware policy I see that in the Real-time protection section there is a "Scan system files" setting, but I don't understand what SCEP considers that to be. 

Thanks

↧
↧

RBAC for OSD and unknown objects?

March 19, 2015, 2:26 pm
$
0
0

Hi,

We have two OSD team one is All Desktops and the other is All Servers. But what about x64 Unknown Computer (x64 Unknown Computer) and x86 Unknown Computer (x86 Unknown Computer) object, what to do with deploying to this objects?

/SaiTech


↧

If I create an security scope for a group of SCCM-admins should i remove the "Default Scope”?

March 19, 2015, 2:00 pm
$
0
0

Hi,

If I create an security scope for a group of SCCM-admins  should i remove the "Default Scope”?

/PS

/SaiTech

↧

Sync failed. Will retry in 60 minutes although local WSUS has synced successfully.

March 20, 2015, 5:41 am
$
0
0 

Hi
I have a single site server with ConfigMgr 2012 SP1 CU5, SQL 2012 SP2, WSUS  6.2.9200.16384 installed on Windows Server 2012.  Every few days I seem to get a run of Sync Failed. The wsyncmgr.log has the following entries
sync: SMS synchronizing updates, processed 8 out of 8 items (100%)
sync: SMS performing cleanup
Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=2600 TID=6484 GMTDATE=Fri Mar 20 11:36:58.825 2015 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse"
 ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Sync failed. Will retry in 60 minutes
Setting sync alert to active state on site SC9
Sync time: 0d00h05m53s
When I go into the WSUS mmc I see green successful syncs 
WSUSCtrl.log
Shutting Down...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:05:52	17700 (0x4524)
SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 9324 (0x246C).	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:20	10176 (0x27C0)
This is a WSUS Role as WSUS registry key exists.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Assembly WSUSMSP loaded in .NET runtime v4.0.30319.18449	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:21	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:23	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:28	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:34	9324 (0x246C)
Waiting for changes for 0 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:34	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:34	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:34	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
There are no unhealthy WSUS Server components on WSUS Server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Successfully checked database connection on WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 00:07:35	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
There are no unhealthy WSUS Server components on WSUS Server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Successfully checked database connection on WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 01:04:36	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:36	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:37	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:38	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:38	9324 (0x246C)
There are no unhealthy WSUS Server components on WSUS Server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:38	9324 (0x246C)
Successfully checked database connection on WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:38	9324 (0x246C)
Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:01:38	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:37	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:37	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
There are no unhealthy WSUS Server components on WSUS Server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Successfully checked database connection on WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 02:58:38	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
There are no unhealthy WSUS Server components on WSUS Server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Successfully checked database connection on WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 03:55:38	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
There are no unhealthy WSUS Server components on WSUS Server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Successfully checked database connection on WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 04:52:38	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name TMG02 and Proxy Port 8080	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
There are no unhealthy WSUS Server components on WSUS Server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Successfully checked database connection on WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Waiting for changes for 57 minutes	SMS_WSUS_CONTROL_MANAGER	20/03/2015 05:49:38	9324 (0x246C)
Timed Out...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Checking runtime v2.0.50727...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Did not find supported version of assembly Microsoft.UpdateServices.Administration.	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Checking runtime v4.0.30319...	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Supported WSUS version found	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Attempting connection to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/2015 06:46:38	9324 (0x246C)
Successfully connected to local WSUS server	SMS_WSUS_CONTROL_MANAGER	20/03/
wsyncmgr.log  (A sync succeeded at 05:04 today followed by a failure every hour)
sync: SMS synchronizing updates, processed 14752 out of 14752 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:03:55	11236 (0x2BE4)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:03:55	11236 (0x2BE4)
Removed 470 unreferenced updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:01	11236 (0x2BE4)
Done synchronizing SMS with WSUS Server mssccm12.iisltd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:01	11236 (0x2BE4)
Set content version of update source {F382A19D-AE3A-43B0-8AEE-E5AA3E31BF9B} for site SC9 to 2251	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:01	6484 (0x1954)
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 05:04:01.882 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:01	6484 (0x1954)
Sync succeeded. Setting sync alert to canceled state on site SC9	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:01	6484 (0x1954)
Updated 545 items in SMS database, new update source content version is 2251	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:01	6484 (0x1954)
Sync time: 0d01h30m37s	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:01	6484 (0x1954)
Next scheduled sync is a regular sync at 20/03/2015 06:00:00	SMS_WSUS_SYNC_MANAGER	20/03/2015 05:04:02	6484 (0x1954)
Wakeup for scheduled regular sync	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:00	6484 (0x1954)
Starting Sync	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:00	6484 (0x1954)
Performing sync on regular schedule	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:00	6484 (0x1954)
Read SUPs from SCF for MSSCCM12.IISLtd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:00	6484 (0x1954)
Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:00	6484 (0x1954)
Found active SUP MSSCCM12.IISLtd.com from SCF File.	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:00	6484 (0x1954)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 06:00:00.560 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:00	6484 (0x1954)
Synchronizing WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:01	6484 (0x1954)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 06:00:01.624 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:01	6484 (0x1954)
Synchronizing WSUS server mssccm12.iisltd.com ...	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:01	10428 (0x28BC)
sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:01	10428 (0x28BC)
sync: WSUS synchronizing categories	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:09	10428 (0x28BC)
sync: WSUS synchronizing updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:20	10428 (0x28BC)
sync: WSUS synchronizing updates, processed 64 out of 64 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:30	10428 (0x28BC)
Done synchronizing WSUS Server mssccm12.iisltd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:30	10428 (0x28BC)
Sleeping 2 more minutes for WSUS server sync results to become available	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:00:30	10428 (0x28BC)
Set content version of update source {F382A19D-AE3A-43B0-8AEE-E5AA3E31BF9B} for site SC9 to 2251	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:30	6484 (0x1954)
Synchronizing SMS database with WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:30	6484 (0x1954)
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 06:02:30.784 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:30	6484 (0x1954)
Synchronizing SMS database with WSUS server mssccm12.iisltd.com ...	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:30	10196 (0x27D4)
sync: Starting SMS database synchronization	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:30	10196 (0x27D4)
requested localization languages: en	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:30	10196 (0x27D4)
Syncing updates arrived after 03/20/2015 03:35:35	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:30	10196 (0x27D4)
Requested categories: ProductFamily=Office Live, ProductFamily=Internet Security and Acceleration Server, ProductFamily=SQL Server, ProductFamily=Microsoft Dynamics CRM, ProductFamily=Microsoft Research AutoCollage, ProductFamily=Skype, ProductFamily=System Center Online, ProductFamily=System Center, ProductFamily=Microsoft Lync Server and Microsoft Lync, ProductFamily=Bing, ProductFamily=Exchange, ProductFamily=Network Monitor, ProductFamily=Windows Essential Business Server, ProductFamily=Office, ProductFamily=Developer Tools, Runtimes, and Redistributables, ProductFamily=Microsoft StreamInsight, ProductFamily=HPC Pack, ProductFamily=Office Communications Server And Office Communicator, ProductFamily=Microsoft Application Virtualization, ProductFamily=Active Directory, ProductFamily=Microsoft System Center Data Protection Manager, ProductFamily=Windows, ProductFamily=Virtual Server, ProductFamily=Microsoft Online Services, ProductFamily=System Center Virtual Machine Manager, ProductFamily=SDK Components, ProductFamily=Windows Embedded, ProductFamily=Windows Live, ProductFamily=Microsoft Security Essentials, ProductFamily=Microsoft BitLocker Administration and Monitoring, ProductFamily=Expression, ProductFamily=Microsoft HealthVault, ProductFamily=BizTalk Server, ProductFamily=Forefront, ProductFamily=Microsoft SQL Server PowerPivot for Excel, ProductFamily=Silverlight, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Service Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:31	10196 (0x27D4)
sync: SMS synchronizing categories	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:31	10196 (0x27D4)
sync: SMS synchronizing categories, processed 0 out of 264 items (0%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:31	10196 (0x27D4)
sync: SMS synchronizing categories, processed 264 out of 264 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:33	10196 (0x27D4)
sync: SMS synchronizing categories, processed 264 out of 264 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:33	10196 (0x27D4)
sync: SMS synchronizing updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:34	10196 (0x27D4)
sync: SMS synchronizing updates, processed 0 out of 3 items (0%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:43	10196 (0x27D4)
Synchronizing update c14fa2bf-2db7-4c3c-a40d-86c52144c09f - Definition Update for Windows Defender - KB2267602 (Definition 1.193.3223.0)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:02:44	10196 (0x27D4)
Synchronizing update 78d1b96d-9410-4b96-8f7f-b2bc8f6228b3 - Definition Update for Windows Defender - KB915597 (Definition 1.193.3223.0)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:03:19	10196 (0x27D4)
Synchronizing update 9a0fcbae-41c6-4e65-bc7b-f87354fc27f4 - HTTP Malware Definition Update for Microsoft Forefront Threat Management Gateway (Antimalware 1.193.3223.0)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:03:28	10196 (0x27D4)
sync: SMS synchronizing updates, processed 3 out of 3 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:03:32	10196 (0x27D4)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:03:32	10196 (0x27D4)
Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:32	6484 (0x1954)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 06:06:32.951 2015 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:32	6484 (0x1954)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:33	6484 (0x1954)
Setting sync alert to active state on site SC9	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:33	6484 (0x1954)
Updated 90 items in SMS database, new update source content version is 2252	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:33	6484 (0x1954)
Sync time: 0d00h06m32s	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:33	6484 (0x1954)
Deleting old expired updates...	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:33	6484 (0x1954)
Deleted 6 expired updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:36	6484 (0x1954)
Deleted 186 expired updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:41	6484 (0x1954)
Deleted 186 expired updates total	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:41	6484 (0x1954)
Deleted 12 orphaned content folders in package SC900006 (Endpoint Protection Definition Updates)	SMS_WSUS_SYNC_MANAGER	20/03/2015 06:06:41	6484 (0x1954)
Wakeup for a polling cycle	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:33	6484 (0x1954)
Starting Sync	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:33	6484 (0x1954)
Performing sync on retry schedule	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:33	6484 (0x1954)
Read SUPs from SCF for MSSCCM12.IISLtd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:33	6484 (0x1954)
Found 1 SUPs	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:33	6484 (0x1954)
Found active SUP MSSCCM12.IISLtd.com from SCF File.	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:33	6484 (0x1954)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 07:06:33.518 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:33	6484 (0x1954)
Synchronizing WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:34	6484 (0x1954)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 07:06:34.579 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:34	6484 (0x1954)
Synchronizing WSUS server mssccm12.iisltd.com ...	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:34	20656 (0x50B0)
sync: Starting WSUS synchronization	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:34	20656 (0x50B0)
sync: WSUS synchronizing categories	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:38	20656 (0x50B0)
Done synchronizing WSUS Server mssccm12.iisltd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:40	20656 (0x50B0)
Sleeping 2 more minutes for WSUS server sync results to become available	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:06:40	20656 (0x50B0)
Set content version of update source {F382A19D-AE3A-43B0-8AEE-E5AA3E31BF9B} for site SC9 to 2252	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:41	6484 (0x1954)
Synchronizing SMS database with WSUS server MSSCCM12.IISLtd.com	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:41	6484 (0x1954)
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 07:08:41.746 2015 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:41	6484 (0x1954)
Synchronizing SMS database with WSUS server mssccm12.iisltd.com ...	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:41	15880 (0x3E08)
sync: Starting SMS database synchronization	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:41	15880 (0x3E08)
requested localization languages: en	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:41	15880 (0x3E08)
Syncing updates arrived after 03/20/2015 03:35:35	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:41	15880 (0x3E08)
Requested categories: ProductFamily=Office Live, ProductFamily=Internet Security and Acceleration Server, ProductFamily=SQL Server, ProductFamily=Microsoft Dynamics CRM, ProductFamily=Microsoft Research AutoCollage, ProductFamily=Skype, ProductFamily=System Center Online, ProductFamily=System Center, ProductFamily=Microsoft Lync Server and Microsoft Lync, ProductFamily=Bing, ProductFamily=Exchange, ProductFamily=Network Monitor, ProductFamily=Windows Essential Business Server, ProductFamily=Office, ProductFamily=Developer Tools, Runtimes, and Redistributables, ProductFamily=Microsoft StreamInsight, ProductFamily=HPC Pack, ProductFamily=Office Communications Server And Office Communicator, ProductFamily=Microsoft Application Virtualization, ProductFamily=Active Directory, ProductFamily=Microsoft System Center Data Protection Manager, ProductFamily=Windows, ProductFamily=Virtual Server, ProductFamily=Microsoft Online Services, ProductFamily=System Center Virtual Machine Manager, ProductFamily=SDK Components, ProductFamily=Windows Embedded, ProductFamily=Windows Live, ProductFamily=Microsoft Security Essentials, ProductFamily=Microsoft BitLocker Administration and Monitoring, ProductFamily=Expression, ProductFamily=Microsoft HealthVault, ProductFamily=BizTalk Server, ProductFamily=Forefront, ProductFamily=Microsoft SQL Server PowerPivot for Excel, ProductFamily=Silverlight, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Service Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:42	15880 (0x3E08)
sync: SMS synchronizing categories	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:42	15880 (0x3E08)
sync: SMS synchronizing categories, processed 0 out of 264 items (0%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:42	15880 (0x3E08)
sync: SMS synchronizing categories, processed 264 out of 264 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:44	15880 (0x3E08)
sync: SMS synchronizing categories, processed 264 out of 264 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:44	15880 (0x3E08)
sync: SMS synchronizing updates	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:44	15880 (0x3E08)
sync: SMS synchronizing updates, processed 0 out of 3 items (0%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:53	15880 (0x3E08)
Skipped update c14fa2bf-2db7-4c3c-a40d-86c52144c09f - Definition Update for Windows Defender - KB2267602 (Definition 1.193.3223.0) because it is up to date.	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:53	15880 (0x3E08)
Skipped update 78d1b96d-9410-4b96-8f7f-b2bc8f6228b3 - Definition Update for Windows Defender - KB915597 (Definition 1.193.3223.0) because it is up to date.	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:53	15880 (0x3E08)
Skipped update 9a0fcbae-41c6-4e65-bc7b-f87354fc27f4 - HTTP Malware Definition Update for Microsoft Forefront Threat Management Gateway (Antimalware 1.193.3223.0) because it is up to date.	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:54	15880 (0x3E08)
sync: SMS synchronizing updates, processed 3 out of 3 items (100%)	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:54	15880 (0x3E08)
sync: SMS performing cleanup	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:08:54	15880 (0x3E08)
Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:11:54	6484 (0x1954)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MSSCCM12.IISLtd.com SITE=SC9 PID=4532 TID=6484 GMTDATE=Fri Mar 20 07:11:54.896 2015 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:11:54	6484 (0x1954)
Sync failed. Will retry in 60 minutes	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:11:54	6484 (0x1954)
Setting sync alert to active state on site SC9	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:11:54	6484 (0x1954)
Sync time: 0d00h05m21s	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:11:54	6484 (0x1954)
Next scheduled sync is a retry sync at 20/03/2015 08:11:54	SMS_WSUS_SYNC_MANAGER	20/03/2015 07:11:55	6484 (0x1954)
Wakeup for scheduled retry sync	SMS_WSUS_SYNC_MANAGER	20/03/201
Thanks in advance
Simon

                       


                                                                           
                       
                     


                   


                   
↧


                   
                   
                   
                   
                 
               


            
            
                              



               
               





                                   
                     

                     
                        Viewing all 6382 articles
                     
                     

                                                                                                      

               

                
                        

                  
             
         
            
               
             
         
         
                              


               

                                                                     
                     
                        Browse latest
                     
                                                      
                     
                        View live
                     
                                                 


               

               

               


               
                          
                        
            
                                      
            

            

              

                
                
    

              

            

            



          


          
          
            


              
                            


                                
                                

                  

                    
                  

                

                
                  
                                


                                    
                  
                                    

                                                                                                                                        
                

                  

                    
                    

                      Search
                                          

                  

                                    
                  
                

                  


                                                                             
 
 

                
 
              

    
                            

                
              


            

        

                    
        
            
        
        

        


                

        

        

                          
     
      
                        
               



            
     

                              
               



        
    
    



 
        
        
        
    

              

          




            
       












      
 

        
     

        


                

          <script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async>
</script>