Solved

Software updates not downloading and deploying.

Posted on 2014-04-08
30
2,687 Views
Last Modified: 2016-04-07
We have a SCCM 2012 R2 environment with WSUS.

We have a central server (ConfigMgrCentral) and a secondary server (ConfigManager). We have a couple of other servers that we also use remotely from time to time. The Central server communicates with WSUS and pulls in all updates for deployment, etc. ConfigManager is what the PCs receive software deployment, etc from. It's the primary site that they link to.

So, to recap, ConfigMgrCentral = Central. ConfigManager = Primary.
 
ConfigMgrCentral has a good connection to WSUS and it's receiving updates. All of the applicable ones are marked as downloaded. I've set up an automatic deployment rule for a test collection.

Some of the pertinent options for the ADR that I have set include:

* Enable deployment after run.
* Automatically deploy and accept licenses
* Install "as soon as possible" under software available and installation deadline
* Allow software installation outside of maintenance window
* We also do not have any maintenance window configured for this collection.

When I go into Windows Update on these PCs as an administrator, they are clearly out of date, and the ADR has numerous patches that they should be eligible for. However, nothing seems to download or install at all.

Here's UpdatesDeployment.log:

<![LOG[Assignment {bb255a00-e0ac-4913-8102-3b5bb036a033} has total CI = 145]LOG]!><time="07:56:46.432+300" date="04-07-2014" component="UpdatesDeploymentAgent" context="" type="1" thread="4212" file="updatesassignment.cpp:161">
<![LOG[Deadline received for assignment ({bb255a00-e0ac-4913-8102-3b5bb036a033})]LOG]!><time="07:56:46.432+300" date="04-07-2014" component="UpdatesDeploymentAgent" context="" type="1" thread="4212" file="updatesassignment.cpp:923">
<![LOG[Detection job ({AA999F6D-DBF1-4CFF-AF37-35B906D57613}) started for assignment ({bb255a00-e0ac-4913-8102-3b5bb036a033})]LOG]!><time="07:56:46.448+300" date="04-07-2014" component="UpdatesDeploymentAgent" context="" type="1" thread="4212" file="updatesassignment.cpp:1196">
<![LOG[User logoff system task]LOG]!><time="08:00:45.492+300" date="04-07-2014" component="UpdatesDeploymentAgent" context="" type="1" thread="5988" file="systemtasks.cpp:142">
<![LOG[User logon system task]LOG]!><time="08:09:42.866+300" date="04-07-2014" component="UpdatesDeploymentAgent" context="" type="1" thread="280" file="systemtasks.cpp:90">
<![LOG[EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0]LOG]!><time="08:10:04.390+300" date="04-07-2014" component="UpdatesDeploymentAgent" context="" type="1" thread="4608" file="updatesmanager.cpp:945">

Does anyone have any ideas why these software update deployments aren't downloading and installing?
0
Comment
Question by:Firstcom
  • 20
  • 9
30 Comments
 
LVL 31

Expert Comment

by:merowinger
ID: 39988085
Are updates shown as required in the sccm console.
Have you installed a Software Update Point on the child Primary site?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39988411
Yes, updates are syncing to the SCCM console. And a SUP role has been assigned to both ConfigManagerCentral and ConfigManager, as well as the external wsus server.
0
 
LVL 31

Expert Comment

by:merowinger
ID: 39988562
So you've deployed the required update to the Clients. When choosing a Client in console can you see the update listed in the Clients deployments?
Is the package deployed and updated to DP?
Is the Client within the Boundaries?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39988958
Hi merowinger.

Everything is distributed and deployed. Boundary groups are good.

I did just notice something under Software Update Point Sync Status under Monitoring.

Our wsus server, wsus.domain.local, is showing a successful sync. It's operating fine.

Our ConfigManagerCentral link and our ConfigManager link are showing a blue exclamation with no syncs at all. The unusual part is that ConfigManagerCentral is pointed to Microsoft Updates, while the primary site, ConfigManager, is pointed to wsus.firstcom.local. Neither have synced.

Upon re-installing the SUP role to ConfigManagerCentral, I don't see an option to direct it to our wsus.domain.local server.

Can you advise?
0
 
LVL 31

Expert Comment

by:merowinger
ID: 39990769
Can you post screenshots and the log files wsyncmgr.log, WSUSCtrl.log, WCM.log?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39991465
Yes, I will get that this morning but the problem appears to be with System Center and not WSUS. The connection to wsus is active and it's pulling updates into System Center. For some reason they simply aren't downloading and installing on the clients.
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39991486
Attached are screen shots, pasted are logs.

I snipped some of these logs. FYI, these came from our "central" site. Let me know if you need them from anywhere else.

wsyncmgr.log:

sync: SMS performing cleanup  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:26.576+300><thread=5960 (0x1748)>
Done synchronizing SMS with WSUS Server wsus.firstcom.local  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.206+300><thread=5960 (0x1748)>
Set content version of update source {D9F889DD-2291-4710-BE3E-5338D5EBFA81} for site FCC to 28  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.529+300><thread=3624 (0xE28)>
Synchronizing replica WSUS servers  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.534+300><thread=3624 (0xE28)>
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ConfigMgrCentrl.firstcom.local SITE=FCC PID=404 TID=3624 GMTDATE=Wed Apr 09 05:02:51.534 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.534+300><thread=3624 (0xE28)>
Sync succeeded. Setting sync alert to canceled state on site FCC  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.573+300><thread=3624 (0xE28)>
No changes made to the SMS database, content version remains 28  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.590+300><thread=3624 (0xE28)>
Sync time: 0d00h02m50s  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.590+300><thread=3624 (0xE28)>
Sending sync notification to child site(s): DR1, HQ1, TMP  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.592+300><thread=3624 (0xE28)>
~SQL Replication type has not been set for C:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.box\outbox\FCC.SYN, replicating to (DR1, HQ1, TMP), inbox: C:\Program Files\Microsoft Configuration Manager\inboxes\replmgr.box  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 00:02:51.599+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 01:02:51.583+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 02:02:52.460+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 03:02:52.897+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 04:02:52.273+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 05:02:52.619+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 06:02:52.938+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 07:02:52.286+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 08:02:52.639+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 09:02:52.924+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 10:02:52.213+300><thread=3624 (0xE28)>
Wakeup by SCF change  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 10:13:07.842+300><thread=3624 (0xE28)>
Wakeup by SCF change  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 10:13:52.918+300><thread=3624 (0xE28)>
Wakeup by SCF change  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 10:14:02.942+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 11:14:05.196+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 12:14:05.141+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 13:14:05.163+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 14:14:05.385+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 15:14:05.323+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 16:14:05.324+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 17:14:05.344+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 18:14:05.338+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 19:14:05.340+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 20:14:06.336+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 21:14:06.616+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 22:14:06.640+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 23:14:06.762+300><thread=3624 (0xE28)>
Next scheduled sync is a regular sync at 4/10/2014 12:00:00 AM  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 23:14:06.873+300><thread=3624 (0xE28)>
Wakeup for scheduled regular sync  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 23:59:59.898+300><thread=3624 (0xE28)>
Starting Sync  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 23:59:59.910+300><thread=3624 (0xE28)>
Performing sync on regular schedule  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 23:59:59.911+300><thread=3624 (0xE28)>
Read SUPs from SCF for ConfigMgrCentrl.firstcom.local  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 23:59:59.983+300><thread=3624 (0xE28)>
Found 2 SUPs  $$<SMS_WSUS_SYNC_MANAGER><04-09-2014 23:59:59.988+300><thread=3624 (0xE28)>
Found active SUP ConfigMgrCentrl.firstcom.local from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:00.004+300><thread=3624 (0xE28)>
Found active SUP wsus.firstcom.local from SCF File.~  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:00.005+300><thread=3624 (0xE28)>
DB Server not detected for SUP ConfigMgrCentrl.firstcom.local from SCF File. skipping.~  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:00.005+300><thread=3624 (0xE28)>
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ConfigMgrCentrl.firstcom.local SITE=FCC PID=404 TID=3624 GMTDATE=Thu Apr 10 05:00:00.010 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:00.011+300><thread=3624 (0xE28)>
Synchronizing WSUS server wsus.firstcom.local  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:01.175+300><thread=3624 (0xE28)>
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ConfigMgrCentrl.firstcom.local SITE=FCC PID=404 TID=3624 GMTDATE=Thu Apr 10 05:00:01.177 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:01.178+300><thread=3624 (0xE28)>
Using account FIRSTCOM\Administrator to connect to WSUS Server  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:01.267+300><thread=3624 (0xE28)>
Synchronizing WSUS server wsus.firstcom.local ...  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:01.739+300><thread=5532 (0x159C)>
sync: Starting WSUS synchronization  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:01.786+300><thread=5532 (0x159C)>
Done synchronizing WSUS Server wsus.firstcom.local  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:11.428+300><thread=5532 (0x159C)>
Sleeping 2 more minutes for WSUS server sync results to become available  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:00:11.429+300><thread=5532 (0x159C)>
Set content version of update source {D9F889DD-2291-4710-BE3E-5338D5EBFA81} for site FCC to 28  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.328+300><thread=3624 (0xE28)>
Synchronizing SMS database with WSUS server wsus.firstcom.local  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.328+300><thread=3624 (0xE28)>
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ConfigMgrCentrl.firstcom.local SITE=FCC PID=404 TID=3624 GMTDATE=Thu Apr 10 05:02:12.328 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.332+300><thread=3624 (0xE28)>
Using account FIRSTCOM\Administrator to connect to WSUS Server  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.368+300><thread=3624 (0xE28)>
Synchronizing SMS database with WSUS server wsus.firstcom.local ...  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.493+300><thread=3860 (0xF14)>
sync: Starting SMS database synchronization  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.494+300><thread=3860 (0xF14)>
requested localization languages: en  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.494+300><thread=3860 (0xF14)>
Syncing updates arrived after 04/09/2014 00:02:21  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.577+300><thread=3860 (0xF14)>
Requested categories: Company=Microsoft, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Service Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:12.800+300><thread=3860 (0xF14)>
sync: SMS synchronizing categories  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:13.051+300><thread=3860 (0xF14)>
sync: SMS synchronizing categories, processed 0 out of 244 items (0%)  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:25.452+300><thread=3860 (0xF14)>
sync: SMS synchronizing categories, processed 244 out of 244 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:44.110+300><thread=3860 (0xF14)>
sync: SMS synchronizing categories, processed 244 out of 244 items (100%)  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:44.111+300><thread=3860 (0xF14)>
sync: SMS synchronizing updates  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:44.384+300><thread=3860 (0xF14)>
SyncBatchCount not set, using default 1  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:44.415+300><thread=3860 (0xF14)>
SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:44.415+300><thread=3860 (0xF14)>
sync: SMS performing cleanup  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:02:56.965+300><thread=3860 (0xF14)>
Done synchronizing SMS with WSUS Server wsus.firstcom.local  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.107+300><thread=3860 (0xF14)>
Set content version of update source {D9F889DD-2291-4710-BE3E-5338D5EBFA81} for site FCC to 28  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.416+300><thread=3624 (0xE28)>
Synchronizing replica WSUS servers  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.422+300><thread=3624 (0xE28)>
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=ConfigMgrCentrl.firstcom.local SITE=FCC PID=404 TID=3624 GMTDATE=Thu Apr 10 05:04:48.422 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.427+300><thread=3624 (0xE28)>
Sync succeeded. Setting sync alert to canceled state on site FCC  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.439+300><thread=3624 (0xE28)>
No changes made to the SMS database, content version remains 28  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.478+300><thread=3624 (0xE28)>
Sync time: 0d00h04m48s  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.478+300><thread=3624 (0xE28)>
Sending sync notification to child site(s): DR1, HQ1, TMP  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.479+300><thread=3624 (0xE28)>
~SQL Replication type has not been set for C:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.box\outbox\FCC.SYN, replicating to (DR1, HQ1, TMP), inbox: C:\Program Files\Microsoft Configuration Manager\inboxes\replmgr.box  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 00:04:48.486+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 01:04:48.625+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 02:04:48.622+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 03:04:48.639+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 04:04:48.589+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 05:04:48.755+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 06:04:50.096+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 07:04:50.481+300><thread=3624 (0xE28)>
Wakeup for a polling cycle  $$<SMS_WSUS_SYNC_MANAGER><04-10-2014 08:04:50.834+300><thread=3624 (0xE28)>


This one appears to show errors... wsusctrl.log:

Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:08:19.214+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:08:19.214+300><thread=6004 (0x1774)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:08:19.215+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:08:19.215+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:08:19.215+300><thread=6004 (0x1774)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:08:19.216+300><thread=6004 (0x1774)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:08:19.216+300><thread=6004 (0x1774)>
Timed Out...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.220+300><thread=6004 (0x1774)>
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.220+300><thread=6004 (0x1774)>
Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.220+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.224+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.226+300><thread=6004 (0x1774)>
Supported WSUS version found~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.226+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.227+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.227+300><thread=6004 (0x1774)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.227+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.227+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.228+300><thread=6004 (0x1774)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.228+300><thread=6004 (0x1774)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:09:19.229+300><thread=6004 (0x1774)>
Timed Out...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.232+300><thread=6004 (0x1774)>
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.232+300><thread=6004 (0x1774)>
Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.232+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.236+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.239+300><thread=6004 (0x1774)>
Supported WSUS version found~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.239+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.240+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.240+300><thread=6004 (0x1774)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.241+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.241+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.241+300><thread=6004 (0x1774)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.241+300><thread=6004 (0x1774)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:10:19.242+300><thread=6004 (0x1774)>
Timed Out...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.245+300><thread=6004 (0x1774)>
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.245+300><thread=6004 (0x1774)>
Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.245+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.249+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.254+300><thread=6004 (0x1774)>
Supported WSUS version found~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.254+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.254+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.255+300><thread=6004 (0x1774)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.255+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.255+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.255+300><thread=6004 (0x1774)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.256+300><thread=6004 (0x1774)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:11:19.256+300><thread=6004 (0x1774)>
Timed Out...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.260+300><thread=6004 (0x1774)>
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.260+300><thread=6004 (0x1774)>
Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.260+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.264+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.266+300><thread=6004 (0x1774)>
Supported WSUS version found~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.266+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.268+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.268+300><thread=6004 (0x1774)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.269+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.269+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.269+300><thread=6004 (0x1774)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.269+300><thread=6004 (0x1774)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:12:19.270+300><thread=6004 (0x1774)>
Timed Out...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.273+300><thread=6004 (0x1774)>
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.280+300><thread=6004 (0x1774)>
Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.280+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.285+300><thread=6004 (0x1774)>
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.288+300><thread=6004 (0x1774)>
Supported WSUS version found~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.288+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.289+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.290+300><thread=6004 (0x1774)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.291+300><thread=6004 (0x1774)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.291+300><thread=6004 (0x1774)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.291+300><thread=6004 (0x1774)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.291+300><thread=6004 (0x1774)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 08:13:19.292+300><thread=6004 (0x1774)>

wcm.log:

Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 06:35:55.215+300><thread=3612 (0xE1C)>
Done using FIRSTCOM\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 06:35:55.707+300><thread=3612 (0xE1C)>
Waiting for changes for 59 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 06:35:55.715+300><thread=3612 (0xE1C)>
Wait timed out after 59 minutes while waiting for at least one trigger event.  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:31.866+300><thread=3612 (0xE1C)>
Timed Out...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.867+300><thread=3612 (0xE1C)>
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.868+300><thread=3612 (0xE1C)>
Checking runtime v2.0.50727...~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.869+300><thread=3612 (0xE1C)>
Found supported assembly Microsoft.UpdateServices.Administration version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.873+300><thread=3612 (0xE1C)>
Found supported assembly Microsoft.UpdateServices.BaseApi version 3.1.6001.1, file version 3.1.7600.256~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.876+300><thread=3612 (0xE1C)>
Supported WSUS version found~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.876+300><thread=3612 (0xE1C)>
Using FIRSTCOM\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.902+300><thread=3612 (0xE1C)>
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.902+300><thread=3612 (0xE1C)>
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.966+300><thread=3612 (0xE1C)>
Verify Upstream Server settings on the Active WSUS Server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:41.967+300><thread=3612 (0xE1C)>
No changes - WSUS Server settings are correctly configured and Upstream Server is set to wsus.firstcom.local  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:42.391+300><thread=3612 (0xE1C)>
Done using FIRSTCOM\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:42.399+300><thread=3612 (0xE1C)>
Using FIRSTCOM\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:42.411+300><thread=3612 (0xE1C)>
Attempting connection to WSUS server: ConfigMgrCentrl.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:42.412+300><thread=3612 (0xE1C)>
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.31.36.60:8530~~   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)~~   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)~~   --- End of inner exception stack trace ---~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:44.463+300><thread=3612 (0xE1C)>
Done using FIRSTCOM\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:44.463+300><thread=3612 (0xE1C)>
Refreshing categories from WSUS server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:44.463+300><thread=3612 (0xE1C)>
Using FIRSTCOM\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:44.479+300><thread=3612 (0xE1C)>
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:44.479+300><thread=3612 (0xE1C)>
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:34:44.529+300><thread=3612 (0xE1C)>
Done using FIRSTCOM\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:45.947+300><thread=3612 (0xE1C)>
Successfully refreshed categories from WSUS server~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:48.192+300><thread=3612 (0xE1C)>
Using FIRSTCOM\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:53.316+300><thread=3612 (0xE1C)>
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:53.317+300><thread=3612 (0xE1C)>
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:53.362+300><thread=3612 (0xE1C)>
Done using FIRSTCOM\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:53.864+300><thread=3612 (0xE1C)>
Using FIRSTCOM\Administrator credentials for network connections~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:53.878+300><thread=3612 (0xE1C)>
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:53.878+300><thread=3612 (0xE1C)>
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:53.919+300><thread=3612 (0xE1C)>
Done using FIRSTCOM\Administrator credentials~  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:54.222+300><thread=3612 (0xE1C)>
Waiting for changes for 59 minutes  $$<SMS_WSUS_CONFIGURATION_MANAGER><04-10-2014 07:35:54.224+300><thread=3612 (0xE1C)>
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39991489
The screen shot did not attach..
Untitled.png
0
 
LVL 31

Expert Comment

by:merowinger
ID: 39991573
Your SUP Points do not work properly...See failures in the Logs.
Recheck the configurtion betweeen WSUS and SCCM SUP
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39991604
There's not much to configure. The ports are right, it seems to get a connection, but it's throwing up those errors. Any ideas on where to look for this?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39991613
One thing I'm noticing in the last log is the line "Attempting connection to WSUS server: ConfigMgrCentrl.firstcom.local"

The WSUS server is wsus.firstcom.local, NOT ConfigMgrCentral.firstcom.local. Is it trying to connect to itself?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39991623
Whenever I enable the SUP role on ConfigMgrCentral, it points to "Microsoft Update" per the screen shot, and then the logs seem to suggest that it's trying to connect to itself. This is a little baffling to me.
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39991678
Does the SUP role need to be enabled on the central and primary site, if it's already set on the external wsus server? If yes, why do the logs suggest that SCCM is trying to connect to itself?
0
 
LVL 31

Expert Comment

by:merowinger
ID: 39993438
Sorry i've lost the overview about you config. Could you please explain with a Little list which Servers you have, where the roles are installed, etc.
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994011
See Untitled.png.

FCC = ConfigManagerCentral
HQ1 = ConfigManager Primary Site.

The other two, TMP and DC1, are both servers that are generally no longer used.

We have a server added in ConfigManagerCentral, wsus.firstcom.local, that points to our WSUS server. As of now, that server has the SUP role enabled and it's the only one.
Untitled.png
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 31

Expert Comment

by:merowinger
ID: 39994086
I think you should have a SUP role installed in each site.
But first of all check out the Connection between the Central and the Primary Site. There are Problems which should be solved first.
Check out your Site Status and Component Status
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994124
For ConfigManagerCentral (FCC), I've attached screenshots.


On ConfigManager (HQ1):
Everything shows up green except for SMS_REPLICATION_CONFIGURATION_MONITOR under Component Status, and "Application Catalog web service point" under Site Status.
FCC-Component.png
FCC-SiteStatus.png
0
 
LVL 31

Expert Comment

by:merowinger
ID: 39994153
Which Messages are shown in WSUS CtrlMgr?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994175
Do you mean the WSUSCtrl.log on the FCC/central server? Here is the log, but it doesn't look like it's done anything since early yesterday.

For troubleshooting purposes I removed the SUP role from everything except for the wsus server we have (it's external to the configmanager servers). This server is listed on the central site (FCC).

The unusual part is that when I looked at how the SUPs were set up, ConfigManagerCentral (FCC) was pointed to Microsoft Updates, while the primary site, ConfigManager, is pointed to wsus.firstcom.local, but neither synced.

If I attempt to re-installing the SUP role to ConfigManagerCentral, I don't see an option to direct it to our wsus.domain.local server. It wants to point to Windows Update.



Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.214+300><thread=3680 (0xE60)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.215+300><thread=3680 (0xE60)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.215+300><thread=3680 (0xE60)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.215+300><thread=3680 (0xE60)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.215+300><thread=3680 (0xE60)>
STATMSG: ID=7003 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONTROL_MANAGER" SYS=ConfigMgrCentrl.firstcom.local SITE=FCC PID=404 TID=3680 GMTDATE=Thu Apr 10 14:10:03.215 2014 ISTR0="ConfigMgrCentrl.firstcom.local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.215+300><thread=3680 (0xE60)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.216+300><thread=3680 (0xE60)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:03.217+300><thread=3680 (0xE60)>
SMS_EXECUTIVE signalled SMS_WSUS_CONTROL_MANAGER to stop.  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:56.148+300><thread=2192 (0x890)>
Shutting Down...~  $$<SMS_WSUS_CONTROL_MANAGER><04-10-2014 09:10:56.151+300><thread=3680 (0xE60)>
0
 
LVL 31

Expert Comment

by:merowinger
ID: 39994207
The Central Site should be configured to sync with Microsoft Update, the Child Primary Site should use the Central SUP as an upstream Server.
SCCM uses WSUS to sync with Microsoft Update, so if WSUS is installed on your Central Site Server, SCCM normally uses this Server if you've installed and configured the SUP correctly.

Have you configured WSUS before installing the SUP, this should not be done, as SCCM takes control over SCCM. So if you've configured anything within WSUS, i recommend to uninstall SUP and then WSUS. Then reinstall WSUS (unconfigured) and then install SUP
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994228
Nothing has been configured within WSUS. We installed a clean copy.

WSUS is hosted on a separate server (so not the central server). That server is listed on the central site and has SUP enabled. If this should NOT be done, let me know.

Per your comment, I have also just re-added the SUP role to the central site and primary site.

So now we have the SUP role enabled on the wsus server that's listed on the Central site, as well as the central site itself and the primary site. Is this correct?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994236
After configuring the SUP points, this is what I have just after setting it up... Is this correct?
Untitled.png
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994432
I believe that I may have figured it out. Will let you know.
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994478
I have removed the SUP role from wsus.firstcom.local.

FCC is now configured to obtain updates from wsus.firstcom.local
HQ1 is now configured to obtain updates from FCC1

However, I am still getting connection errors.. WSUSCtrl.log shows:

Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:13:12.211+300><thread=3948 (0xF6C)>

It also shows "Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:18:12.262+300><thread=3948 (0xF6C)>"

This is weird because it should be connecting to wsus.firstcom.local.

WCM.log shows an erorr of "No connection could be made because the target machine actively refused it" but it then shows the IP address of itself rather than the IP of the WSUS server.

Any ideas?
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994503
Here's my new structure:

wsus on site code FCC gets it updates from Microsoft Updates. It's able to successfully sync.

configmanagercentral on site code FCC gets its updates from wsus. There is no link time nor sync time.

configmanager (primary site) on site code HQ1 gets its updates from configmanagercentral. There is a link and sync time but the catalog version number is 0.

It seems that configmanagercentral is having trouble connecting to wsus.
0
 
LVL 1

Author Comment

by:Firstcom
ID: 39994514
wsusctrl.log shows the following error:

Supported WSUS version found~  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.365+300><thread=3948 (0xF6C)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.366+300><thread=3948 (0xF6C)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.366+300><thread=3948 (0xF6C)>
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.367+300><thread=3948 (0xF6C)>
Attempting connection to local WSUS server  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.367+300><thread=3948 (0xF6C)>
Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber)  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.367+300><thread=3948 (0xF6C)>
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.local. Will retry check in 1 minutes~  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.368+300><thread=3948 (0xF6C)>
~Waiting for changes for 1 minutes  $$<SMS_WSUS_CONTROL_MANAGER><04-11-2014 10:29:12.369+300><thread=3948 (0xF6C)>

Why is it pointing to itself and looking for a local wsus server, especially when the monitoring tab shows that it gets its updates from wsus.firstcom.local?
0
 
LVL 31

Expert Comment

by:merowinger
ID: 39998335
The SUP Role on the Central Site Server ist not required,
as you have installed it on a seperate Server for the same Site.
Is it now installed like this?
0
 
LVL 1

Accepted Solution

by:
Firstcom earned 0 total points
ID: 39998337
Hi Jonas,

I have another thread open at http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Q_28406182.html

Can you take a look at that one? It is more updated.
0
 
LVL 1

Author Closing Comment

by:Firstcom
ID: 40008422
Duplicate thread.
0
 

Expert Comment

by:tiago gramacho
ID: 41539808
Im with the same problem but no clue about how to fix it.
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

How can you create a game plan that lets you focus on special projects instead of running from cubicle to cubicle every day and feeling like you’ve accomplished nothing? Try these strategies for prioritizing your tasks, offloading what you can, and …
Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
The viewer will learn how to simulate a series of coin tosses with the rand() function and learn how to make these “tosses” depend on a predetermined probability. Flipping Coins in Excel: Enter =RAND() into cell A2: Recalculate the random variable…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now