locked
Server installing SCEP updates but not Windows updates RRS feed

  • Question

  • All,

    My SCCM 2012 infrastructure is patching my estate properly apart from one server which won't install Windows updates.  SCEP updates are being installed OK and my understanding is that the basic process is the same for both.  There is a maintenance windows controlling the time of the Windows updates, it's working OK for the other servers in the collection but not for this one.

    I've tried completely reinstalling the client, resetting the WSUS config (including deleting the SoftwareDistribution folder), repairing WMI...  I've also downloaded 'Client Center for CM 2012' and it is showing the maintenance window as being in place.

    From WindowsUpdate.log:

    2015-04-20 05:15:09:551  876 36e0 Agent   * Added update {68568DFA-C35C-4BC3-8996-74A818D0E5D7}.200 to search result
    2015-04-20 05:15:09:551  876 36e0 Agent   * Added update {A039BFFA-C1A3-4560-8E65-6E4372E7B6F6}.105 to search result
    2015-04-20 05:15:09:551  876 36e0 Agent   * Added update {278594FC-8551-480E-8B15-202BE7E66E30}.200 to search result
    2015-04-20 05:15:09:551  876 36e0 Agent   * Added update {F46530FF-F31F-4ECA-B7BE-142D51022624}.107 to search result
    2015-04-20 05:15:09:551  876 36e0 Agent   * Added update {FC8561FF-9685-4A86-B0E3-1FB6B45BB55C}.101 to search result
    2015-04-20 05:15:09:567  876 36e0 Agent   * Found 196 updates and 79 categories in search; evaluated appl. rules of 1495 out of 2109 deployed entities
    2015-04-20 05:15:09:676  876 36e0 Agent *********
    2015-04-20 05:15:09:676  876 36e0 Agent **  END  **  Agent: Finding updates [CallerId = CcmExec]
    2015-04-20 05:15:09:676  876 36e0 Agent *************
    2015-04-20 05:15:09:817  876 36e0 Report REPORT EVENT: {F1B2515C-0708-4647-9036-D261C1262659} 2015-04-20 05:15:09:629+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 CcmExec Success Software Synchronization Windows Update Client successfully detected 196 updates.
    2015-04-20 05:15:09:817  876 36e0 Report REPORT EVENT: {2319B086-58E3-4092-B9FF-07B69D0CFFAA} 2015-04-20 05:15:09:629+0100 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 CcmExec Success Pre-Deployment Check Reporting client status.
    2015-04-20 05:15:09:817  876 36e0 Report CWERReporter finishing event handling. (00000000)
    2015-04-20 05:15:09:817  876 36e0 Report CWERReporter finishing event handling. (00000000)
    2015-04-20 05:15:09:817  876 36e0 Report CWERReporter finishing event handling. (00000000)
    2015-04-20 05:15:09:817  876 36e0 Report CWERReporter finishing event handling. (00000000)
    2015-04-20 05:15:09:817  876 36e0 Report CWERReporter finishing event handling. (00000000)

    Which suggests to me that it's finding that updates are required.  It's also listing the correct path for the update server.  The Update*.log files all look like they do on other, functioning servers...I'm stuck!

    My suspicion is that the maintenance window is being ignored but I would have thought that reinstalling the client would have cleared this.  Anyone got any ideas?

    Many thanks.

    Tuesday, April 21, 2015 2:27 PM

Answers

All replies

  • What does the Monitoring node / Deployments tell?

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, April 21, 2015 3:36 PM
  • Hi Torsten,

    The Monitoring/Deployment lists the server as 'compliant' (last compliance message 17/4/2105) even though it hasn't installed any updates this year.  (The deployment contains all Security/Critical patches from the last two months and is generated by an ADR.)

    Wednesday, April 22, 2015 7:10 AM
  • I've also seen this in UpdatesDeployment.log:

    No current service window available to run updates assignment with time required = 1 UpdatesDeploymentAgent 22/04/2015 02:04:31 3948 (0x0F6C)

    The maintenance window runs from 2am-4am which should be enough to get a fair number of updates installed. 

    In ServiceWindowManager.log:

        Active Service Windows List has 1 windows ServiceWindowManager 22/04/2015 02:04:02 3484 (0x0D9C)
            Service Window with ID = {CEFC6A65-1FFA-4444-87DB-BEB93B736DA0} having Starttime=04/22/15 02:00:00 ServiceWindowManager 22/04/2015 02:04:02 3484 (0x0D9C)
                Duration is 0 days, 02 hours, 00 mins, 00 secs ServiceWindowManager 22/04/2015 02:04:02 3484 (0x0D9C)
    ServiceWindowManager 22/04/2015 02:04:02 3484 (0x0D9C)
        Scheduling the Timer Task ServiceWindowManager 22/04/2015 02:04:02 3484 (0x0D9C)
        Scheduled the timer to fire on 04/22/15 04:00:00 ServiceWindowManager 22/04/2015 02:04:02 3484 (0x0D9C)
    ServiceWindowManager 22/04/2015 02:04:02 3484 (0x0D9C)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:4 ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window... ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
            Biggest Active Service Window has ID = {CEFC6A65-1FFA-4444-87DB-BEB93B736DA0} having Starttime=04/22/15 02:00:00 ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
                Duration is 0 days, 02 hours, 00 mins, 00 secs ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    ActiveServiceWindow has 6929 seconds left ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    Program can run! Setting *canProgramRun to TRUE ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    OnIsServiceWindowAvailable called with: Runtime:1, Type:6 ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
            Biggest Active Service Window for Type=6 not found ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    Program cannot Run! Setting *canProgramRun to FALSE ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    WillProgramRun called with: Runtime:1, Type:6 ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    A Service Window of this type exists. ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    There exists a Service Window of this Type, for this duration. The Program will run eventually. ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    ServiceWindowManager 22/04/2015 02:04:31 3948 (0x0F6C)
    OnIsServiceWindowAvailable called with: Runtime:900, Type:2 ServiceWindowManager 22/04/2015 02:04:36 3948 (0x0F6C)
    No Service Windows exist for this type. Will check if the program can run in the All Programs window... ServiceWindowManager 22/04/2015 02:04:36 3948 (0x0F6C)
            Biggest Active Service Window has ID = {CEFC6A65-1FFA-4444-87DB-BEB93B736DA0} having Starttime=04/22/15 02:00:00 ServiceWindowManager 22/04/2015 02:04:36 3948 (0x0F6C)
                Duration is 0 days, 02 hours, 00 mins, 00 secs ServiceWindowManager 22/04/2015 02:04:36 3948 (0x0F6C)
    ActiveServiceWindow has 6924 seconds left ServiceWindowManager 22/04/2015 02:04:36 3948 (0x0F6C)
    Program can run! Setting *canProgramRun to TRUE ServiceWindowManager 22/04/2015 02:04:36 3948 (0x0F6C)
    ServiceWindowManager 22/04/2015 04:00:00 2692 (0x0A84)
    A Timer Event has occurred ServiceWindowManager 22/04/2015 04:00:00 2692 (0x0A84)
        Sending Message SERVICEWINDOWEVENT:END event ServiceWindowManager 22/04/2015 04:00:00 2692 (0x0A84)


    • Edited by Mungus Wednesday, April 22, 2015 8:38 AM
    Wednesday, April 22, 2015 8:27 AM
  • Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?


    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Sunday, July 26, 2015 1:10 AM
  • No, the client is still broken. I'm having to install parches manually and am planning to rebuild it.
    Sunday, July 26, 2015 7:06 AM
  • I recommend opening  a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.

    Garth Jones | My blogs: Enhansoft and Old Blog site | Twitter: @GarthMJ

    Sunday, July 26, 2015 4:05 PM