none
Force last update on SCCM RRS feed

  • Question

  • Hi all,

    Last week, Microsoft release a Patch new wormable vulnerabilities in Remote Desktop Services:

    https://msrc-blog.microsoft.com/2019/08/13/patch-new-wormable-vulnerabilities-in-remote-desktop-services-cve-2019-1181-1182/

    How can I deploy to all machines ASAP using SCCM 1802?

    Thanks for your help,

    Regards,


    Gerardo,

    Monday, August 19, 2019 6:41 AM

All replies

  • Hi, Are you using SCCM for patching? if so simply download and deploy it under Software Updates with install as soon a possible. And then use the Client Notification and initiate a Software update scan.

    If you don't use SCCM for patching download the offline installer and deploy it as a package/program. 
    How to use WUSA.exe standalone https://support.microsoft.com/en-us/help/934307/description-of-the-windows-update-standalone-installer-in-windows

    regards,
    Jörgen


    -- My Enterprise Mobility blog ccmexec.com -- Twitter @ccmexec


    Monday, August 19, 2019 6:53 AM
  • We use SCCM to do it, but normally use a schedule deployment to do it, after the 2nd Tuesday of every mounth. 

    But this patch seem to be important but on my sccm I can't see it, latest update have date relesed 21/07/2019...

    I try to run sumarizacion and sync software updates, and the result is the same...

    Some idea to force the dowsload and deploy the specific update of the Microsoft Post?

    Regards and thankyou.


    Gerardo,


    Monday, August 19, 2019 7:05 AM
  • Hi,

    Any errors in the Component Status Sounds like maybe wsus cannot sync?

    /Jörgen


    -- My Enterprise Mobility blog ccmexec.com -- Twitter @ccmexec

    Monday, August 19, 2019 8:15 AM
  • I don't have any wsus error, sccm recieve last updates every month without problems, but now we want to download and deploy a specific update and didn't work.

    Regards,


    Gerardo,

    Monday, August 19, 2019 8:32 AM
  • Kindly check wsyncmgr.log and WCM.log for any error

    Also initiate Sync on WSUS console and check again.

    Monday, August 19, 2019 8:58 AM
  • If you check about three posts earlier in this forum you will see that there are many reports of failed synchs (related to .NET updates):

    https://social.technet.microsoft.com/Forums/en-US/e0ddd770-988b-4448-af99-9153120bfbcf/microsoft-august-patches-synchronization?forum=ConfigMgrCompliance

     

    Rolf Lidvall, Swedish Radio (Ltd)

    Monday, August 19, 2019 9:33 AM
  • Hi again,

    I checked the wsyncmgr and see this:

    Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:06 8788 (0x2254)
    Starting Sync SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:06 8788 (0x2254)
    Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:06 8788 (0x2254)
    Read SUPs from SCF for SVPMI030.ibsesp.loc SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:06 8788 (0x2254)
    Found 1 SUPs SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:06 8788 (0x2254)
    Found active SUP SVPMI030.ibsesp.loc from SCF File. SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:06 8788 (0x2254)
    STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SVPMI030.IBSESP.LOC SITE=CEN PID=16676 TID=8788 GMTDATE=lu. ago. 19 11:26:06.460 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:06 8788 (0x2254)
    Sync Surface Drivers option is not set SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:07 8788 (0x2254)
    Synchronizing WSUS server SVPMI030.ibsesp.loc SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:07 8788 (0x2254)
    STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SVPMI030.IBSESP.LOC SITE=CEN PID=16676 TID=8788 GMTDATE=lu. ago. 19 11:26:07.478 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:07 8788 (0x2254)
    Using account IBS\MC1158 to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:07 8788 (0x2254)
    http://SVPMI030.ibsesp.loc:8530 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:07 10728 (0x29E8)
    Synchronizing WSUS server SVPMI030 ... SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:07 10728 (0x29E8)
    sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:07 10728 (0x29E8)
    sync: WSUS synchronizing categories SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:15 10728 (0x29E8)
    Done synchronizing WSUS Server SVPMI030 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:31 10728 (0x29E8)
    Sync Catalog Drivers SCF value is set to : 0 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:31 10728 (0x29E8)
    SyncGracePeriod not set, use default 120000 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:31 10728 (0x29E8)
    Sleeping 120 more seconds for WSUS server sync results to become available SMS_WSUS_SYNC_MANAGER 19/08/2019 13:26:31 10728 (0x29E8)
    Sync finished successfully SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:31 10728 (0x29E8)
    Set content version of update source {5F049A0F-C733-4B98-9D8C-6DEA7B4D5063} for site CEN to 7580 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:32 8788 (0x2254)
    Resetting MaxInstall RunTime for Cumulative updates. SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:32 8788 (0x2254)
    Synchronizing SMS database with WSUS server SVPMI030.ibsesp.loc SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 8788 (0x2254)
    STATMSG: ID=6705 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SVPMI030.IBSESP.LOC SITE=CEN PID=16676 TID=8788 GMTDATE=lu. ago. 19 11:28:33.265 2019 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 8788 (0x2254)
    Using account IBS\MC1158 to connect to WSUS Server SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 8788 (0x2254)
    http://SVPMI030.ibsesp.loc:8530 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    Synchronizing SMS database with WSUS server SVPMI030 ... SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    sync: Starting SMS database synchronization SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    requested localization languages: en,es SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    Syncing all updates SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    Requested categories: Product=Windows 8.1 Language Packs, Product=Windows 10 and later drivers, Product=Forefront TMG MBE, Product=Forefront Client Security, Product=Windows 10, version 1809 and later, Upgrade & Servicing Drivers, Product=Windows Server 2012 Language Packs, Product=Windows 10 Version 1803 and Later Upgrade   & Servicing Drivers, Product=Office 365 Client, Product=Windows 10 and later upgrade & servicing drivers, Product=Windows 8.1 and later drivers, Product=Forefront TMG, Product=Windows 8.1, Product=Windows 10 Language Interface Packs, Product=Windows 10, version 1809 and later, Servicing Drivers, Product=Forefront Threat Management Gateway, Definition Updates for HTTP Malware Inspection, Product=Windows 10 version 1803 and Later Servicing Drivers, Product=Windows Server 2012 R2 Language Packs, Product=Windows Defender, Product=Windows Server 2012, Product=System Center Endpoint Protection, Product=Windows 10, Product=Forefront Protection Category, Product=Threat Management Gateway Definition Updates for Network Inspection System, Product=Windows Server 2008, Product=Windows 7, Product=TMG Firewall Client, Product=Windows Server 2012 R2, Product=Windows Server 2012 R2  and later drivers, Product=Forefront Server Security Category, Product=Windows 10 Language Packs, Product=Windows Server 2008 R2, UpdateClassification=Security Updates, UpdateClassification=Update Rollups, UpdateClassification=Upgrades, UpdateClassification=Service Packs, UpdateClassification=Tools, UpdateClassification=Feature Packs, UpdateClassification=Updates, UpdateClassification=Definition Updates, UpdateClassification=Critical Updates SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    sync: SMS synchronizing categories SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    sync: SMS synchronizing categories, processed 0 out of 356 items (0%) SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:33 17860 (0x45C4)
    sync: SMS synchronizing categories, processed 356 out of 356 items (100%) SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:37 17860 (0x45C4)
    sync: SMS synchronizing categories, processed 356 out of 356 items (100%) SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:37 17860 (0x45C4)
    sync: SMS synchronizing updates SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:37 17860 (0x45C4)
    SyncBatchCount not set, using default 1 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:37 17860 (0x45C4)
    SyncBatchMinCreationDate not set, using default 01/01/2001 00:00:00 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:28:37 17860 (0x45C4)
    Sync failed: The operation has timed out. Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse SMS_WSUS_SYNC_MANAGER 19/08/2019 13:31:38 8788 (0x2254)
    STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SVPMI030.IBSESP.LOC SITE=CEN PID=16676 TID=8788 GMTDATE=lu. ago. 19 11:31:38.426 2019 ISTR0="Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse" ISTR1="The operation has timed out" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 19/08/2019 13:31:38 8788 (0x2254)
    Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER 19/08/2019 13:31:38 8788 (0x2254)
    Setting sync alert to active state on site CEN SMS_WSUS_SYNC_MANAGER 19/08/2019 13:31:38 8788 (0x2254)
    Sync time: 0d00h05m32s SMS_WSUS_SYNC_MANAGER 19/08/2019 13:31:38 8788 (0x2254)
    Skipping Delete Expired Update relations since this is not a scheduled sync. SMS_WSUS_SYNC_MANAGER 19/08/2019 13:31:38 8788 (0x2254)
    Inbox source is local on SVPMI030.ibsesp.loc SMS_WSUS_SYNC_MANAGER 19/08/2019 13:31:41 8788 (0x2254)

    Now i will check the error code...Some idea?

    Thanks,


    Gerardo,

    Monday, August 19, 2019 11:55 AM
  • Still the updates are not showing?

    Have you checked your proxy server settings for the synchronization ?

    SUP options -> Update Source and Proxy Server -> Use proxy server

    Monday, August 19, 2019 12:01 PM
  • yes, the server proxy shoul be work.

    on event viewer i can see: 

    On 19/08/2019 14:55:09, component SMS_WSUS_SYNC_MANAGER on computer SVPMI030.IBSESP.LOC reported:   WSUS Synchronization failed.
     Message: The operation has timed out.
     Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse.
      The operating system reported error 2148734217: 

    and the console of WSUS report Error: connection error. I don't understand this, because the WSUS is the same server as SCCM, the same of this errors on event viewer...

    Some idea?


    Gerardo,

    Monday, August 19, 2019 1:13 PM
  • Try to do WSUS Cleanup on WSUS console and try to run the Sync again.

    Even it failed, follow the below mentioned article

    https://support.microsoft.com/en-in/help/4490644/complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maint

    Monday, August 19, 2019 1:53 PM
  • WSUS seem not working fine:

    On 19/08/2019 16:06:48, component SMS_WSUS_SYNC_MANAGER on computer SVPMI030.IBSESP.LOC reported:   WSUS Synchronization failed.
     Message: The operation has timed out.
     Source: Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse.
      The operating system reported error 2148734217: 

    *********************************************

    The WSUS administration console was unable to connect to the WSUS Server via the remote API. 

    Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

    System.Net.WebException -- The operation has timed out

    Source
    System.Web.Services

    Stack Trace:
       at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
       at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
       at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
       at Microsoft.UpdateServices.UI.AdminApiAccess.BulkUpdatePropertiesCache.GetAndCacheUpdates(ExtendedUpdateScope updateScope, ComputerTargetScope computerTargetScope)
       at Microsoft.UpdateServices.UI.SnapIn.Pages.UpdatesListPage.GetListRows()

    ****************************

    The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, 

    Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.


    System.NullReferenceException -- Object reference not set to an instance of an object.

    Source
    Microsoft.UpdateServices.UI.SnapIn

    Stack Trace:
       at Microsoft.UpdateServices.UI.SnapIn.Pages.ServerSummaryPage.backgroundWorker_RunWorkerCompleted(Object sender, RunWorkerCompletedEventArgs e)

    We try to add some limit RAM on IIS and the same result...


    Gerardo,

    Monday, August 19, 2019 2:18 PM