Firstcom
asked on
Software updates not downloading and deploying.
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-3
<![LOG[Deadline received for assignment ({bb255a00-e0ac-4913-8102-
<![LOG[Detection job ({AA999F6D-DBF1-4CFF-AF37-
<![LOG[User logoff system task]LOG]!><time="08:00:45
<![LOG[User logon system task]LOG]!><time="08:09:42
<![LOG[EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0]LOG]!><time="08:10:04.390
Does anyone have any ideas why these software update deployments aren't downloading and installing?
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-3
<![LOG[Deadline received for assignment ({bb255a00-e0ac-4913-8102-
<![LOG[Detection job ({AA999F6D-DBF1-4CFF-AF37-
<![LOG[User logoff system task]LOG]!><time="08:00:45
<![LOG[User logon system task]LOG]!><time="08:09:42
<![LOG[EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0]LOG]!><time="08:10:04.390
Does anyone have any ideas why these software update deployments aren't downloading and installing?
ASKER
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.
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?
Is the package deployed and updated to DP?
Is the Client within the Boundaries?
ASKER
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?
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?
Can you post screenshots and the log files wsyncmgr.log, WSUSCtrl.log, WCM.log?
ASKER
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.
ASKER
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><
Done synchronizing SMS with WSUS Server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
Set content version of update source {D9F889DD-2291-4710-BE3E-5
Synchronizing replica WSUS servers $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Sync succeeded. Setting sync alert to canceled state on site FCC $$<SMS_WSUS_SYNC_MANAGER><
No changes made to the SMS database, content version remains 28 $$<SMS_WSUS_SYNC_MANAGER><
Sync time: 0d00h02m50s $$<SMS_WSUS_SYNC_MANAGER><
Sending sync notification to child site(s): DR1, HQ1, TMP $$<SMS_WSUS_SYNC_MANAGER><
~SQL Replication type has not been set for C:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.b
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Next scheduled sync is a regular sync at 4/10/2014 12:00:00 AM $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for scheduled regular sync $$<SMS_WSUS_SYNC_MANAGER><
Starting Sync $$<SMS_WSUS_SYNC_MANAGER><
Performing sync on regular schedule $$<SMS_WSUS_SYNC_MANAGER><
Read SUPs from SCF for ConfigMgrCentrl.firstcom.l
Found 2 SUPs $$<SMS_WSUS_SYNC_MANAGER><
Found active SUP ConfigMgrCentrl.firstcom.l
Found active SUP wsus.firstcom.local from SCF File.~ $$<SMS_WSUS_SYNC_MANAGER><
DB Server not detected for SUP ConfigMgrCentrl.firstcom.l
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Synchronizing WSUS server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Using account FIRSTCOM\Administrator to connect to WSUS Server $$<SMS_WSUS_SYNC_MANAGER><
Synchronizing WSUS server wsus.firstcom.local ... $$<SMS_WSUS_SYNC_MANAGER><
sync: Starting WSUS synchronization $$<SMS_WSUS_SYNC_MANAGER><
Done synchronizing WSUS Server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
Sleeping 2 more minutes for WSUS server sync results to become available $$<SMS_WSUS_SYNC_MANAGER><
Set content version of update source {D9F889DD-2291-4710-BE3E-5
Synchronizing SMS database with WSUS server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Using account FIRSTCOM\Administrator to connect to WSUS Server $$<SMS_WSUS_SYNC_MANAGER><
Synchronizing SMS database with WSUS server wsus.firstcom.local ... $$<SMS_WSUS_SYNC_MANAGER><
sync: Starting SMS database synchronization $$<SMS_WSUS_SYNC_MANAGER><
requested localization languages: en $$<SMS_WSUS_SYNC_MANAGER><
Syncing updates arrived after 04/09/2014 00:02:21 $$<SMS_WSUS_SYNC_MANAGER><
Requested categories: Company=Microsoft, UpdateClassification=Secur
sync: SMS synchronizing categories $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing categories, processed 0 out of 244 items (0%) $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing categories, processed 244 out of 244 items (100%) $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing categories, processed 244 out of 244 items (100%) $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing updates $$<SMS_WSUS_SYNC_MANAGER><
SyncBatchCount not set, using default 1 $$<SMS_WSUS_SYNC_MANAGER><
SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00 $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS performing cleanup $$<SMS_WSUS_SYNC_MANAGER><
Done synchronizing SMS with WSUS Server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
Set content version of update source {D9F889DD-2291-4710-BE3E-5
Synchronizing replica WSUS servers $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Sync succeeded. Setting sync alert to canceled state on site FCC $$<SMS_WSUS_SYNC_MANAGER><
No changes made to the SMS database, content version remains 28 $$<SMS_WSUS_SYNC_MANAGER><
Sync time: 0d00h04m48s $$<SMS_WSUS_SYNC_MANAGER><
Sending sync notification to child site(s): DR1, HQ1, TMP $$<SMS_WSUS_SYNC_MANAGER><
~SQL Replication type has not been set for C:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.b
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
This one appears to show errors... wsusctrl.log:
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
wcm.log:
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Waiting for changes for 59 minutes $$<SMS_WSUS_CONFIGURATION_
Wait timed out after 59 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONFIGURATION_
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONFIGURATION_
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Verify Upstream Server settings on the Active WSUS Server~ $$<SMS_WSUS_CONFIGURATION_
No changes - WSUS Server settings are correctly configured and Upstream Server is set to wsus.firstcom.local $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: ConfigMgrCentrl.firstcom.l
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketE
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Refreshing categories from WSUS server~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Successfully refreshed categories from WSUS server~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Waiting for changes for 59 minutes $$<SMS_WSUS_CONFIGURATION_
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><
Done synchronizing SMS with WSUS Server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
Set content version of update source {D9F889DD-2291-4710-BE3E-5
Synchronizing replica WSUS servers $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Sync succeeded. Setting sync alert to canceled state on site FCC $$<SMS_WSUS_SYNC_MANAGER><
No changes made to the SMS database, content version remains 28 $$<SMS_WSUS_SYNC_MANAGER><
Sync time: 0d00h02m50s $$<SMS_WSUS_SYNC_MANAGER><
Sending sync notification to child site(s): DR1, HQ1, TMP $$<SMS_WSUS_SYNC_MANAGER><
~SQL Replication type has not been set for C:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.b
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><
Wakeup by SCF change $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Next scheduled sync is a regular sync at 4/10/2014 12:00:00 AM $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for scheduled regular sync $$<SMS_WSUS_SYNC_MANAGER><
Starting Sync $$<SMS_WSUS_SYNC_MANAGER><
Performing sync on regular schedule $$<SMS_WSUS_SYNC_MANAGER><
Read SUPs from SCF for ConfigMgrCentrl.firstcom.l
Found 2 SUPs $$<SMS_WSUS_SYNC_MANAGER><
Found active SUP ConfigMgrCentrl.firstcom.l
Found active SUP wsus.firstcom.local from SCF File.~ $$<SMS_WSUS_SYNC_MANAGER><
DB Server not detected for SUP ConfigMgrCentrl.firstcom.l
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Synchronizing WSUS server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Using account FIRSTCOM\Administrator to connect to WSUS Server $$<SMS_WSUS_SYNC_MANAGER><
Synchronizing WSUS server wsus.firstcom.local ... $$<SMS_WSUS_SYNC_MANAGER><
sync: Starting WSUS synchronization $$<SMS_WSUS_SYNC_MANAGER><
Done synchronizing WSUS Server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
Sleeping 2 more minutes for WSUS server sync results to become available $$<SMS_WSUS_SYNC_MANAGER><
Set content version of update source {D9F889DD-2291-4710-BE3E-5
Synchronizing SMS database with WSUS server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Using account FIRSTCOM\Administrator to connect to WSUS Server $$<SMS_WSUS_SYNC_MANAGER><
Synchronizing SMS database with WSUS server wsus.firstcom.local ... $$<SMS_WSUS_SYNC_MANAGER><
sync: Starting SMS database synchronization $$<SMS_WSUS_SYNC_MANAGER><
requested localization languages: en $$<SMS_WSUS_SYNC_MANAGER><
Syncing updates arrived after 04/09/2014 00:02:21 $$<SMS_WSUS_SYNC_MANAGER><
Requested categories: Company=Microsoft, UpdateClassification=Secur
sync: SMS synchronizing categories $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing categories, processed 0 out of 244 items (0%) $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing categories, processed 244 out of 244 items (100%) $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing categories, processed 244 out of 244 items (100%) $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS synchronizing updates $$<SMS_WSUS_SYNC_MANAGER><
SyncBatchCount not set, using default 1 $$<SMS_WSUS_SYNC_MANAGER><
SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00 $$<SMS_WSUS_SYNC_MANAGER><
sync: SMS performing cleanup $$<SMS_WSUS_SYNC_MANAGER><
Done synchronizing SMS with WSUS Server wsus.firstcom.local $$<SMS_WSUS_SYNC_MANAGER><
Set content version of update source {D9F889DD-2291-4710-BE3E-5
Synchronizing replica WSUS servers $$<SMS_WSUS_SYNC_MANAGER><
STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGE
Sync succeeded. Setting sync alert to canceled state on site FCC $$<SMS_WSUS_SYNC_MANAGER><
No changes made to the SMS database, content version remains 28 $$<SMS_WSUS_SYNC_MANAGER><
Sync time: 0d00h04m48s $$<SMS_WSUS_SYNC_MANAGER><
Sending sync notification to child site(s): DR1, HQ1, TMP $$<SMS_WSUS_SYNC_MANAGER><
~SQL Replication type has not been set for C:\Program Files\Microsoft Configuration Manager\inboxes\wsyncmgr.b
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
Wakeup for a polling cycle $$<SMS_WSUS_SYNC_MANAGER><
This one appears to show errors... wsusctrl.log:
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGE
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONTROL_MANAGE
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONTROL_MANAGE
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
wcm.log:
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Waiting for changes for 59 minutes $$<SMS_WSUS_CONFIGURATION_
Wait timed out after 59 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)~ $$<SMS_WSUS_CONFIGURATION_
Checking runtime v2.0.50727...~ $$<SMS_WSUS_CONFIGURATION_
Found supported assembly Microsoft.UpdateServices.A
Found supported assembly Microsoft.UpdateServices.B
Supported WSUS version found~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Verify Upstream Server settings on the Active WSUS Server~ $$<SMS_WSUS_CONFIGURATION_
No changes - WSUS Server settings are correctly configured and Upstream Server is set to wsus.firstcom.local $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: ConfigMgrCentrl.firstcom.l
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketE
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Refreshing categories from WSUS server~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Successfully refreshed categories from WSUS server~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Using FIRSTCOM\Administrator credentials for network connections~ $$<SMS_WSUS_CONFIGURATION_
Attempting connection to WSUS server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Successfully connected to server: wsus.firstcom.local, port: 8530, useSSL: False $$<SMS_WSUS_CONFIGURATION_
Done using FIRSTCOM\Administrator credentials~ $$<SMS_WSUS_CONFIGURATION_
Waiting for changes for 59 minutes $$<SMS_WSUS_CONFIGURATION_
ASKER
The screen shot did not attach..
Untitled.png
Untitled.png
Your SUP Points do not work properly...See failures in the Logs.
Recheck the configurtion betweeen WSUS and SCCM SUP
Recheck the configurtion betweeen WSUS and SCCM SUP
ASKER
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?
ASKER
One thing I'm noticing in the last log is the line "Attempting connection to WSUS server: ConfigMgrCentrl.firstcom.l
The WSUS server is wsus.firstcom.local, NOT ConfigMgrCentral.firstcom.
The WSUS server is wsus.firstcom.local, NOT ConfigMgrCentral.firstcom.
ASKER
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.
ASKER
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?
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.
ASKER
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
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
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
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
ASKER
For ConfigManagerCentral (FCC), I've attached screenshots.
On ConfigManager (HQ1):
Everything shows up green except for SMS_REPLICATION_CONFIGURAT
FCC-Component.png
FCC-SiteStatus.png
On ConfigManager (HQ1):
Everything shows up green except for SMS_REPLICATION_CONFIGURAT
FCC-Component.png
FCC-SiteStatus.png
Which Messages are shown in WSUS CtrlMgr?
ASKER
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_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
STATMSG: ID=7003 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONTROL_MAN
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
SMS_EXECUTIVE signalled SMS_WSUS_CONTROL_MANAGER to stop. $$<SMS_WSUS_CONTROL_MANAGE
Shutting Down...~ $$<SMS_WSUS_CONTROL_MANAGE
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_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
STATMSG: ID=7003 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONTROL_MAN
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
SMS_EXECUTIVE signalled SMS_WSUS_CONTROL_MANAGER to stop. $$<SMS_WSUS_CONTROL_MANAGE
Shutting Down...~ $$<SMS_WSUS_CONTROL_MANAGE
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
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
ASKER
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?
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?
ASKER
After configuring the SUP points, this is what I have just after setting it up... Is this correct?
Untitled.png
Untitled.png
ASKER
I believe that I may have figured it out. Will let you know.
ASKER
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.A
It also shows "Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
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?
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.A
It also shows "Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
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?
ASKER
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.
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.
ASKER
wsusctrl.log shows the following error:
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
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?
Supported WSUS version found~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes~ $$<SMS_WSUS_CONTROL_MANAGE
Attempting connection to local WSUS server $$<SMS_WSUS_CONTROL_MANAGE
Microsoft.UpdateServices.A
Failures reported during periodic health check by the WSUS Server ConfigMgrCentrl.firstcom.l
~Waiting for changes for 1 minutes $$<SMS_WSUS_CONTROL_MANAGE
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?
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?
as you have installed it on a seperate Server for the same Site.
Is it now installed like this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Duplicate thread.
Im with the same problem but no clue about how to fix it.
Have you installed a Software Update Point on the child Primary site?