none
Unable to sync SCCM with offline WSUS RRS feed

  • Question

  • We have an online WSUS server connected offsite to download the package.

    I have export and import the metadata to WSUS production server which has no internet access. SCCM is also installed on the same server.

    The import is successful and we are able to see the patches under WSUS however when we perform a Synchronize Software Updates we are unable to see the software packages under All software under SCCM.

    *This is a new setup servers.

    Please advise which settings i have missed out. 

    Friday, November 29, 2019 9:39 AM

All replies

  • Hi,

    Can you check the following log files located on "SCCM Install directory\Microsoft Configuration Manager\Logs":

    • SUPSetup.log (to make sure that the SUP role is installed correctly)
    • WCM.log
    • WSUSCtrl.log

    Refer to these topics for more details about connecting SUP with upstream:

    https://blogs.technet.microsoft.com/paul_hadad_blog/2013/04/11/synchronize-from-an-upstream-data-source-location-url/

    https://docs.microsoft.com/en-us/previous-versions/system-center/system-center-2012-R2/gg712696(v=technet.10)?redirectedfrom=MSDN#BKMK_WSUSSyncSource

    Regards,

    SAAD Youssef

    ______

    Please remember to mark the replies as answer if they help, thank you!

    Friday, November 29, 2019 9:50 AM
  • SUPSetup.log 

    <11/29/19 11:41:09> ====================================================================
    <11/29/19 11:41:09> SMSWSUS Setup Started....
    <11/29/19 11:41:09> Parameters: E:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:DC1 SMSWSUS 0
    <11/29/19 11:41:09> Installing Pre Reqs for SMSWSUS
    <11/29/19 11:41:09>         ======== Installing Pre Reqs for Role SMSWSUS ========
    <11/29/19 11:41:09> Found 1 Pre Reqs for Role SMSWSUS 
    <11/29/19 11:41:09> Pre Req SqlNativeClient found.
    <11/29/19 11:41:09> SqlNativeClient is already installed (Product Code: {9D93D367-A2CC-4378-BD63-79EF3FE76C78}). But to support TLS1.2, a newe version with Product Code: {B9274744-8BAE-4874-8E59-2610919CD419} needs to be manually installed 
    <11/29/19 11:41:09> Pre Req SqlNativeClient is already installed. Skipping it.
    <11/29/19 11:41:09>         ======== Completed Installation of Pre Reqs for Role SMSWSUS ========
    <11/29/19 11:41:09> Installing the SMSWSUS
    <11/29/19 11:41:09> Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    <11/29/19 11:41:09> Checking runtime v4.0.30319...
    <11/29/19 11:41:09> Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.17763.1
    <11/29/19 11:41:09> Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.17763.1
    <11/29/19 11:41:09> Supported WSUS version found
    <11/29/19 11:41:09> Supported WSUS Server version (6.2.17763.1) is installed.
    <11/29/19 11:41:09> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" "E:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
    <11/29/19 11:41:10> CTool::RegisterManagedBinary: Failed to register E:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll with .Net Fx 2.0
    <11/29/19 11:41:10> CTool::RegisterManagedBinary: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe" "E:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll"
    <11/29/19 11:41:10> CTool::RegisterManagedBinary: Registered E:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll successfully
    <11/29/19 11:41:10> Registered DLL E:\Program Files\Microsoft Configuration Manager\bin\x64\wsusmsp.dll
    <11/29/19 11:41:10> Installation was successful.
    <11/29/19 11:41:10> ~RoleSetup().



    Seem to be fine?

    Friday, November 29, 2019 10:50 AM
  • WCM.log

    Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:27:59 PM 10452 (0x28D4)
    No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:27:59 PM 10452 (0x28D4)
    Done using ISS\iss credentials SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:27:59 PM 10452 (0x28D4)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:27:59 PM 10452 (0x28D4)
    Using ISS\iss credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:27:59 PM 10452 (0x28D4)
    Attempting connection to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:27:59 PM 10452 (0x28D4)
    Successfully connected to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:27:59 PM 10452 (0x28D4)
    Done using ISS\iss credentials SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:21 PM 10452 (0x28D4)
    Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:23 PM 10452 (0x28D4)
    Using ISS\iss credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:28 PM 10452 (0x28D4)
    Attempting connection to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:28 PM 10452 (0x28D4)
    Successfully connected to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:28 PM 10452 (0x28D4)
    Done using ISS\iss credentials SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Using ISS\iss credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Attempting connection to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Successfully connected to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Found published client Configuration Manager Client (5.00.8790.1007) (id=66a33716-da80-48c3-97de-c9c528f73a2d, version=5.00.8790.1007) SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Done using ISS\iss credentials SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Using ISS\iss credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Attempting connection to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Successfully connected to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Successful published and approved package 66A33716-DA80-48C3-97DE-C9C528F73A2D for Install to All Computers, Deadline UTC time=11/29/2019 3:41:15 AM SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Done using ISS\iss credentials SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Using ISS\iss credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Attempting connection to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Successfully connected to local WSUS server SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Done using ISS\iss credentials SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)
    Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER 11/29/2019 6:28:29 PM 10452 (0x28D4)


    Friday, November 29, 2019 10:51 AM
  • WSUSCtrl.log

    SMS_EXECUTIVE started SMS_WSUS_CONTROL_MANAGER as thread ID 2972 (0xB9C).            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         5032 (0x13A8) This is a WSUS Role as WSUS registry key exists.        SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM            2972 (0x0B9C) Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C)Checking runtime v4.0.30319...           SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.17763.1            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.17763.1            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C)Supported WSUS version found           SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Attempting connection to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM            2972 (0x0B9C) Successfully connected to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM            2972 (0x0B9C) No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Waiting for changes for 0 minutes       SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C)Timed Out...     SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C)Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Checking runtime v4.0.30319...           SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C)Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.17763.1            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C)Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.17763.1            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Supported WSUS version found           SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C)Attempting connection to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM            2972 (0x0B9C) Successfully connected to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM            2972 (0x0B9C) No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80            SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Attempting connection to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM            2972 (0x0B9C) Successfully connected to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM            2972 (0x0B9C) There are no unhealthy WSUS Server components on WSUS Server DC1       SMS_WSUS_CONTROL_MANAGER            11/29/2019 11:41:14 AM         2972 (0x0B9C)Successfully checked database connection on WSUS server DC1       SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM    2972 (0x0B9C) Waiting for changes for 57 minutes     SMS_WSUS_CONTROL_MANAGER         11/29/2019 11:41:14 AM         2972 (0x0B9C) Timed Out...     SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM         2972 (0x0B9C) Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)            SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM         2972 (0x0B9C) Checking runtime v4.0.30319...           SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM         2972 (0x0B9C)Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.17763.1            SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM         2972 (0x0B9C)Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.17763.1            SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM         2972 (0x0B9C) Supported WSUS version found           SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM         2972 (0x0B9C)Attempting connection to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM            2972 (0x0B9C) Successfully connected to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM            2972 (0x0B9C) No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80            SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM         2972 (0x0B9C) Attempting connection to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM            2972 (0x0B9C) Successfully connected to local WSUS server  SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM            2972 (0x0B9C) There are no unhealthy WSUS Server components on WSUS Server DC1       SMS_WSUS_CONTROL_MANAGER            11/29/2019 12:38:14 PM         2972 (0x0B9C)Successfully checked database connection on WSUS server DC1       SMS_WSUS_CONTROL_MANAGER         11/29/2019 12:38:14 PM    2972 (0x0B9C) Waiting for changes for 57 minutes     S

    Friday, November 29, 2019 10:53 AM
  • I followed this article as well WSUS has shown the patches but not under SCCM. Not sure where it went wrong.


    Friday, November 29, 2019 11:01 AM
  • From your log above: "No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update"

    You need to change your upstream server to none.

    Also, have you reviewed wsyncmgr.log?

    And, to be clear, you won't see "packages" under the All Software Updates node, you will see individual updates.


    Jason | https://home.configmgrftw.com | @jasonsandys


    Friday, November 29, 2019 3:02 PM
  • Hi Jason,

    Where do i change upstream to none? Is it under WSUS or SCCM?

    wsyncmgr.log as below

    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DC1 SITE=P01 PID=3848 TID=10484 GMTDATE=Fri Nov 29 08:05:42.689 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0         SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:42 PM  10484 (0x28F4)

    Synchronizing SMS database with WSUS, default server is DC1   SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM                10484 (0x28F4)

    STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DC1 SITE=P01 PID=3848 TID=10484 GMTDATE=Fri Nov 29 08:05:43.706 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0         SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM  10484 (0x28F4)

    Using account ISS\iss to connect to WSUS Server              SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM  10484 (0x28F4)

    http://DC1:8530               SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM  3456 (0x0D80)

    Synchronizing SMS database with WSUS server DC1SCCM ...       SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM  3456 (0x0D80)

    sync: Starting SMS database synchronization      SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM  3456 (0x0D80)

    requested localization languages: en      SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM  3456 (0x0D80)

    Syncing updates arrived after 11/29/2019 14:54:33           SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:43 PM  3456 (0x0D80)

    Requested categories: Product=Office 2007, Product=Office 2003, Product=Windows Vista, Product=Windows 8, Product=Windows XP x64 Edition, Product=Windows Internet Explorer 8 Dynamic Installer, Product=Windows XP, Product=Office 2002/XP, Product=Windows Server 2003, Datacenter Edition, Product=Office 2010, Product=Windows Defender, Product=Windows Vista Dynamic Installer, Product=Windows Server 2012, Product=Windows XP 64-Bit Edition Version 2003, Product=Windows Server 2008, Product=Windows 7, Product=Windows Internet Explorer 7 Dynamic Installer, Product=Windows Server 2003, Product=Windows Server 2008 Server Manager Dynamic Installer, Product=Windows Server 2008 R2            SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:44 PM  3456 (0x0D80)

    Third-party software updates is not enabled.     SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:44 PM  3456 (0x0D80)

    sync: SMS synchronizing categories         SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:44 PM  3456 (0x0D80)

    sync: SMS synchronizing categories, processed 0 out of 346 items (0%)  SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:44 PM         3456 (0x0D80)

    sync: SMS synchronizing categories, processed 346 out of 346 items (100%)         SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM          3456 (0x0D80)

    sync: SMS synchronizing categories, processed 346 out of 346 items (100%)         SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM          3456 (0x0D80)

    WARNING: Request filter does not contain any known classifications. Sync will do nothing.                SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  3456 (0x0D80)

    Done synchronizing SMS with WSUS Server DC1SCCM    SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  3456 (0x0D80)

    Set content version of update source {E8D3F7E9-2BFF-463F-AD63-248A08F031F9} for site P01 to 0                SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  10484 (0x28F4)

    Resetting MaxInstall RunTime for Cumulative updates.  SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  10484 (0x28F4)

    Starting cleanup on WSUS, default server DC1    SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  10484 (0x28F4)

    Using account ISS\iss to connect to WSUS Server              SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  10484 (0x28F4)

    http://DC1:8530               SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  5048 (0x13B8)

    Cleaning up WSUS server DC1SCCM ...   SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  5048 (0x13B8)

    sync: Starting SMS database synchronization      SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  5048 (0x13B8)

    requested localization languages: en      SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  5048 (0x13B8)

    Syncing updates arrived after 11/29/2019 16:05:43           SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:47 PM  5048 (0x13B8)

    Requested categories: Product=Office 2007, Product=Office 2003, Product=Windows Vista, Product=Windows 8, Product=Windows XP x64 Edition, Product=Windows Internet Explorer 8 Dynamic Installer, Product=Windows XP, Product=Office 2002/XP, Product=Windows Server 2003, Datacenter Edition, Product=Office 2010, Product=Windows Defender, Product=Windows Vista Dynamic Installer, Product=Windows Server 2012, Product=Windows XP 64-Bit Edition Version 2003, Product=Windows Server 2008, Product=Windows 7, Product=Windows Internet Explorer 7 Dynamic Installer, Product=Windows Server 2003, Product=Windows Server 2008 Server Manager Dynamic Installer, Product=Windows Server 2008 R2            SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  5048 (0x13B8)

    WARNING: Request filter does not contain any known classifications. Sync will do nothing.                SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  5048 (0x13B8)

    Done cleaning up WSUS Server DC1SCCM            SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  5048 (0x13B8)

    Set content version of update source {E8D3F7E9-2BFF-463F-AD63-248A08F031F9} for site P01 to 0                SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  10484 (0x28F4)

    Resetting MaxInstall RunTime for Cumulative updates.  SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  10484 (0x28F4)

    STATMSG: ID=6702 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=DC1 SITE=P01 PID=3848 TID=10484 GMTDATE=Fri Nov 29 08:05:48.846 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0         SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  10484 (0x28F4)

    Sync succeeded. Setting sync alert to canceled state on site P01                SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM         10484 (0x28F4)

    No changes made to the SMS database, content version remains 0          SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM         10484 (0x28F4)

    Sync time: 0d00h00m06s              SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  10484 (0x28F4)

    Skipping Delete Expired Update relations since this is not a scheduled sync.         SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM          10484 (0x28F4)

    Inbox source is local on DC1        SMS_WSUS_SYNC_MANAGER  11/29/2019 4:05:48 PM  10484 (0x28F4)

    Wakeup for a polling cycle           SMS_WSUS_SYNC_MANAGER  11/29/2019 5:05:48 PM  10484 (0x28F4)

    Inbox source is local on DC1        SMS_WSUS_SYNC_MANAGER  11/29/2019 5:05:49 PM  10484 (0x28F4)

    Wakeup for a polling cycle           SMS_WSUS_SYNC_MANAGER  11/29/2019 6:05:49 PM  10484 (0x28F4)

    Inbox source is local on DC1        SMS_WSUS_SYNC_MANAGER  11/29/2019 6:05:49 PM  10484 (0x28F4)

    Wakeup by SCF change SMS_WSUS_SYNC_MANAGER  11/29/2019 6:15:29 PM  10484 (0x28F4)

    Inbox source is local on DC1        SMS_WSUS_SYNC_MANAGER  11/29/2019 6:15:34 PM  10484 (0x28F4)

    Wakeup by inbox drop  SMS_WSUS_SYNC_MANAGER  11/29/2019 6:36:14 PM  10484 (0x28F4)

    Saturday, November 30, 2019 6:39 AM
  • It's empty under all software updates.
    Saturday, November 30, 2019 6:40 AM
  • It's on the Software Update Point component properties; see https://docs.microsoft.com/en-us/configmgr/sum/get-started/install-a-software-update-point#synchronization-source.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Saturday, November 30, 2019 7:55 PM
  • Hi,

    >>WARNING: Request filter does not contain any known classifications. Sync will do nothing. 

    According to the log file, please kindly check the SUP classifications and products configuration are correct. Also, we need to verify the WSUS production server is healthy.

    In addition, we can try following steps to see if it works.
    1) unselect all Classifications in SUP
    2) Perform wsusutil reset
    3) Perform sync
    4) Re add the Classifications.

    Best Regards,
    Tina

     

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 2, 2019 8:41 AM
  • Hi,
     
    How are things going? 
     
    I just checked in to see if there are any updates. Have you tried the suggestion above? Please feel free to feedback and if any reply is helpful, please kindly click “Mark as answer”. It would make the reply to the top and easier to be found for other people who has the similar question.
     
    Thank you for your kindly support.
     
    Best Regards,
    Tina

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, December 5, 2019 8:48 AM