WSUS restarts servers unexpectedly

Discussion in 'Update Services' started by Frost''''IK, Mar 25, 2008.

  1. Frost''''IK

    Frost''''IK Guest

    We have installed WSUS 3.0 SP1 in our network and our servers became to
    restart unexpectedly.

    There are this settings in group policy:

    Allow Automatic Updates immediate installation Disabled
    Configure automatic updating: 2 - Notify for download and notify for install
    Enable client-side targeting Enabled Servers
    Target group name for this computer Servers

    As soon as server sees WSUS, it dounloads and installs some updates and
    restarts the server. Even if there is a users loggen on it.

    Why is it happens?

    There is some windows update log from one of this servers

    2008-03-19 00:22:35:695 832 1570 Agent * Added update
    {5D2787CB-BCB5-439D-B734-3E6F1B21B2DD}.103 to search result
    2008-03-19 00:22:35:695 832 1570 Agent * Added update
    {4483F57E-7C9D-42E0-9641-49C284E51ADD}.100 to search result
    2008-03-19 00:22:35:695 832 1570 Agent * Found 2 updates and 38
    categories in search; evaluated appl. rules of 359 out of 451 deployed
    entities
    2008-03-19 00:22:35:711 832 1570 Agent *********
    2008-03-19 00:22:35:711 832 1570 Agent ** END ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2008-03-19 00:22:35:711 832 1570 Agent *************
    2008-03-19 00:22:35:711 832 6d8 AU >>## RESUMED ## AU: Search for updates
    [CallId = {B9E84316-CA15-4C9A-93D9-B7676A6BDCB0}]
    2008-03-19 00:22:35:711 832 6d8 AU # 2 updates detected
    2008-03-19 00:22:35:711 832 6d8 AU Setting next AU forced reboot timeout to
    2008-03-26 00:00:00
    2008-03-19 00:22:35:711 832 6d8 AU Setting next AU forced reboot timeout to
    2008-03-19 00:00:00
    2008-03-19 00:22:35:711 832 6d8 AU #########
    2008-03-19 00:22:35:711 832 6d8 AU ## END ## AU: Search for updates
    [CallId = {B9E84316-CA15-4C9A-93D9-B7676A6BDCB0}]
    2008-03-19 00:22:35:711 832 6d8 AU #############
    2008-03-19 00:22:35:711 832 6d8 AU AU setting next detection timeout to
    2008-03-19 19:20:29
    2008-03-19 00:22:40:695 832 1570 Report REPORT EVENT:
    {CF02C7DA-9B1E-46C3-93C1-526EB05CB8CE} 2008-03-19
    00:22:35:695+0300 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 2 updates.
    2008-03-19 00:22:40:695 832 1570 Report REPORT EVENT:
    {EA51D5F7-6E42-460C-82EC-37055FC3027D} 2008-03-19
    00:22:35:711+0300 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2008-03-19 00:26:30:731 832 1570 Report Uploading 2 events using cached
    cookie, reporting URL =
    http://nms-win01/ReportingWebService/ReportingWebService.asmx
    2008-03-19 00:26:30:731 832 1570 Report Reporter successfully uploaded 2
    events.
    2008-03-19 03:00:09:746 832 5dc AU Forced install timer expired for
    deadline install
    2008-03-19 03:00:09:746 832 5dc AU UpdateDownloadProperties: 0 download(s)
    are still in progress.
    2008-03-19 03:00:09:746 832 5dc AU Enforcing reboot for already installed
    deadline expired update
    2008-03-19 03:00:09:746 832 5dc AU Found a pending reboot, launching reboot
    UI
    2008-03-19 03:00:09:746 832 5dc AU AU setting pending client directive to
    'Reboot Warning'
    2008-03-19 03:00:09:746 832 5dc AU Changing existing AU client directive
    from 'Reboot Pending' to 'Reboot Warning', session id = 0x2
    2008-03-19 03:00:09:746 4100 1318 CltUI AU client got new directive =
    'Reboot Warning', serviceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, return
    = 0x00000000
    2008-03-19 03:00:09:746 4100 1318 CltUI AU client reboot notification: user
    clicked Restart Later
    2008-03-19 03:00:24:746 832 5dc AU FATAL: CAUClient::Launch failed, error =
    0x800704DD
    2008-03-19 03:05:09:751 832 5dc AU AU invoking RebootSystem (OnRebootNow)
    2008-03-19 03:05:09:767 832 5dc Misc WARNING: SUS Client is rebooting system.
    2008-03-19 03:05:09:767 832 5dc AU AU invoking RebootSystem (OnRebootRetry)
    2008-03-19 03:05:11:048 832 5dc AU ########### AU: Uninitializing
    Automatic Updates ###########
    2008-03-19 03:05:11:126 4100 1318 CltUI AU client got new directive =
    'None', serviceId = {00000000-0000-0000-0000-000000000000}, return =
    0x80010108
    2008-03-19 03:05:11:126 4100 1318 CltUI FATAL: Failed to show client UI,
    directive=8, hr=80010108
    2008-03-19 03:05:12:517 832 5dc Service *********
    2008-03-19 03:05:12:517 832 5dc Service ** END ** Service: Service exit
    [Exit code = 0x240001]
    2008-03-19 03:05:12:517 832 5dc Service *************
    2008-03-19 03:05:38:064 400 3d4 Misc =========== Logging initialized
    (build: 7.1.6001.65, tz: +0300) ===========
    2008-03-19 03:05:38:064 400 3d4 Misc = Process:
    \??\C:\WINDOWS\system32\winlogon.exe
    2008-03-19 03:05:38:064 400 3d4 Misc = Module:
    C:\WINDOWS\system32\wuaueng.dll
    2008-03-19 03:05:38:064 400 3d4 Shutdwn FATAL: WUAutoUpdateAtShutdown
    failed, hr=80240FFF
     
    Frost''''IK, Mar 25, 2008
    #1
    1. Advertisements

  2. At least one of your updates has a deadline set. This overrides all other
    configuration settings.

    Harry.
     
    Harry Johnston [MVP], Mar 25, 2008
    #2
    1. Advertisements

  3. Frost''''IK

    Frost''''IK Guest

    Was not "scheduled install" feature instead of "deadline" in previous
    versions of WSUS? Or am I wrong?
     
    Frost''''IK, Mar 26, 2008
    #3
  4. Frost''''IK

    Nigel Jett Guest


    I have noticed the same thing since upgrading to WSUS3 sp1 - when a
    computer first reports in the initial updates somehow force it to reboot
    with a countdown timer. After those first updates are installed it
    behaves correctly and follows its actual configuration. I don't recall
    now what the updates are, I know one of them is Windows Installer 3.1.
    Neither of the initial updates has a deadline set, but I found that if
    you change their approvals so that they don't install for the Unassigned
    Computers group you can at least regain some control over when the
    computers are rebooting themselves.
     
    Nigel Jett, Mar 26, 2008
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.