WSUS 3.0 SP2 Isolated

We have created a new WSUS Server and i want to download all the updates from microsoft so that i can then export them and take them to a disconnected WSUS server
Q: How can i begin download of updates since no computer report this WSUS server -- who can i approve to so the download begins
Q:How much space should i have on WSUS content directory to be able to download all updates

We have created a new WSUS Server and i want to download all the updates from microsoft so that i can then export them and take them to a disconnected WSUS server
Q: How can i begin download of updates since no computer report this WSUS server
You don't need clients. Just approve the updates you want to import. That will download the files. You're not approving updates for computers, anyway, you approve updates for groups. Every WSUS server has two groups by default: All Computers and Unassigned
Computers. It doesn't really matter what group(s) you approve the updates for because there are no clients.
Q:How much space should i have on WSUS content directory to be able to download all updates
Well, if you really wanted to download ALL updates, you'd need a couple hundred gigabytes. But you don't really want to do that. You want to download only the updates that are likely to be needed.
You can find out which updates are needed by simply exporting the metadata, with no content, from the connected server, importing it to the disconnected server, and then wait 24 hours while all of the clients run a detection and report what is needed. Then
use that list of needed updates to approve updates on the connected server to download the files. Rerun the metadata import after the files have downloaded and are copied to the disconnected server.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

Similar Messages

  • Windows Update Error 80080005 Windows 7 Client with WSUS 3.0 SP2 server

    Hello everyone, I've looked around at other threads related to my issue, and I can't seem to find a correct answer.
    I have a computer lab that I've recently installed a Windows 7 Enterprise image onto 35 Dell Optiplex computers (most are 380's, a few older 360's).
    I created the image using MDT2010 and used one of the 380's as a reference.
    All has been well for about a month or two but recently 6 computers are giving me Windows Update errors with the error code of 80080005.
    I have a WSUS 3.0 SP2 server running, and all of my other computers seem to be getting their updates just fine.  WSUS has the problematic computers in it's database, but it shows that they haven't checked in for "x" days.
    I have Avast 4.8 Professional installed, I have OpenDNS configured to block bad websites, ____, etc. and I also use an Untangle server to prevent access to bad websites.  I've ran a Malwarebytes' Anti-Malware scan on the affected computers, as well
    as Windows Defender scan, and Windows Live OneCare scans, and all have found no malicious software.
    I have also tried resetting the Windows update service as described here: http://support.microsoft.com/kb/971058 as well as a script that supposedly does the same thing, but also resets all previous
    update events, but I can't find the script source right now (I had ran it last week, and it didn't work).
    I'm currently running a SFC /Scannow on one of the computers, and now it has finished.  It gives the error: Windows Resource Protection could not start the repair service.  I'll have to google that next.
    The last windows update that ran on the computer that I'm working on now was installed on 11-18-2010 and was a Windows Defender Update (KB915597 Def: 1.93.1985.0)
    Previous to that was 11/9/2010 2 updates: KB977165 and KB981852.
    I guess I'll have to look at all of the other machines to see if they have the same updates installed.
    Anyway, has anyone else had this problem?  I've seen vista home editions, and RC's but no real Windows 7 Pro+ RTM versions in business environments where updates were controlled by WSUS.
    Thanks for any help that you can provide!
    By the way, I only work at this location once a week (tuesdays, well thursdays too, but I'm next door to this building, but I have remote access), so bare with me on trying to fix things.

    Ok, for the sake of completeness, I have completed the instructions given by Miya Yao.
    After stopping the Windows Update Service (from an Admin Command prompt window), renaming the SoftwareDistribution folder to SDold, then starting the update service again, I still receive the same error when checking for updates.
    The windows update log shows this (starting from about 4am) and I just reset the service at about 9:10, which you can see in the log.
    2010-12-21 04:19:02:342 940 f20 Agent WARNING: WU client failed Searching for update with error 0x80080005
    2010-12-21 04:19:02:342 940 cd4 AU >>## RESUMED ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
    2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Search callback failed, result = 0x80080005
    2010-12-21 04:19:02:342 940 f20 Report CWERReporter finishing event handling. (00000000)
    2010-12-21 04:19:02:342 940 cd4 AU # WARNING: Failed to find updates with error code 80080005
    2010-12-21 04:19:02:342 940 cd4 AU #########
    2010-12-21 04:19:02:342 940 cd4 AU ## END ## AU: Search for updates [CallId = {8957B50F-46F1-44C4-A347-20D4C5E91D47}]
    2010-12-21 04:19:02:342 940 cd4 AU #############
    2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
    2010-12-21 04:19:02:342 940 cd4 AU AU setting next detection timeout to 2010-12-21 14:19:02
    2010-12-21 04:19:02:342 940 cd4 AU Setting AU scheduled install time to 2010-12-22 08:00:00
    2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
    2010-12-21 04:19:02:342 940 cd4 AU Successfully wrote event for AU health state:0
    2010-12-21 04:19:07:350 940 f20 Report REPORT EVENT: {A472759C-BEE7-4161-84E8-41F1C1D03AB4} 2010-12-21 04:19:02:342-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
    2010-12-21 04:19:07:350 940 f20 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2010-12-21 04:19:07:350 940 f20 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
    2010-12-21 04:19:07:350 940 f20 Report CWERReporter finishing event handling. (00000000)
    2010-12-21 04:24:22:767 940 f20 PT WARNING: Cached cookie has expired or new PID is available
    2010-12-21 04:24:22:767 940 f20 PT Initializing simple targeting cookie, clientId = a6d6dc1c-d844-451c-8609-3879e6cacb33, target group = , DNS name = lab24.sja.local
    2010-12-21 04:24:22:767 940 f20 PT Server URL = http://server2:8530/SimpleAuthWebService/SimpleAuth.asmx
    2010-12-21 04:24:22:814 940 f20 Report Uploading 2 events using cached cookie, reporting URL = http://server2:8530/ReportingWebService/ReportingWebService.asmx
    2010-12-21 04:24:22:814 940 f20 Report Reporter successfully uploaded 2 events.
    2010-12-21 06:59:23:020 940 b4c AU AU was unable to detect updates for more than 48 hours
    2010-12-21 06:59:28:027 940 c78 Report REPORT EVENT: {511B1C92-939C-4E97-A51B-50E75FCB7AEF} 2010-12-21 06:59:23:020-0500 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
    2010-12-21 06:59:28:027 940 c78 Report CWERReporter finishing event handling. (00000000)
    2010-12-21 09:02:03:476 940 2f4 AU Triggering AU detection through DetectNow API
    2010-12-21 09:02:03:476 940 2f4 AU Triggering Online detection (interactive)
    2010-12-21 09:02:03:476 940 b4c AU #############
    2010-12-21 09:02:03:476 940 b4c AU ## START ## AU: Search for updates
    2010-12-21 09:02:03:477 940 b4c AU #########
    2010-12-21 09:02:03:488 940 b4c AU <<## SUBMITTED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
    2010-12-21 09:02:03:488 940 e38 Agent *************
    2010-12-21 09:02:03:488 940 e38 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2010-12-21 09:02:03:488 940 e38 Agent *********
    2010-12-21 09:02:03:488 940 e38 Agent * Online = Yes; Ignore download priority = No
    2010-12-21 09:02:03:488 940 e38 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2010-12-21 09:02:03:488 940 e38 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2010-12-21 09:02:03:488 940 e38 Agent * Search Scope = {Machine}
    2010-12-21 09:02:03:488 940 e38 Setup Checking for agent SelfUpdate
    2010-12-21 09:02:03:489 940 e38 Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
    2010-12-21 09:02:03:489 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2010-12-21 09:02:03:496 940 e38 Misc Microsoft signed: Yes
    2010-12-21 09:02:06:071 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2010-12-21 09:02:06:078 940 e38 Misc Microsoft signed: Yes
    2010-12-21 09:02:06:080 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2010-12-21 09:02:06:087 940 e38 Misc Microsoft signed: Yes
    2010-12-21 09:02:06:100 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2010-12-21 09:02:06:107 940 e38 Misc Microsoft signed: Yes
    2010-12-21 09:02:06:123 940 e38 Setup Determining whether a new setup handler needs to be downloaded
    2010-12-21 09:02:06:123 940 e38 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2010-12-21 09:02:06:129 940 e38 Misc Microsoft signed: Yes
    2010-12-21 09:02:06:129 940 e38 Setup SelfUpdate handler update NOT required: Current version: 7.4.7600.226, required version: 7.4.7600.226
    2010-12-21 09:02:06:129 940 e38 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
    2010-12-21 09:02:15:386 940 b4c AU AU received policy change subscription event
    2010-12-21 09:02:36:165 940 e38 Setup WARNING: Cbs StartSession, error = 0x80080005
    2010-12-21 09:02:36:165 940 e38 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
    2010-12-21 09:02:36:165 940 e38 Setup FATAL: SelfUpdate check failed, err = 0x80080005
    2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Skipping scan, self-update check returned 0x80080005
    2010-12-21 09:02:36:165 940 e38 Agent * WARNING: Exit code = 0x80080005
    2010-12-21 09:02:36:165 940 e38 Agent *********
    2010-12-21 09:02:36:165 940 e38 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2010-12-21 09:02:36:165 940 e38 Agent *************
    2010-12-21 09:02:36:165 940 e38 Agent WARNING: WU client failed Searching for update with error 0x80080005
    2010-12-21 09:02:36:165 940 e8c AU >>## RESUMED ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
    2010-12-21 09:02:36:165 940 e8c AU # WARNING: Search callback failed, result = 0x80080005
    2010-12-21 09:02:36:165 940 e8c AU # WARNING: Failed to find updates with error code 80080005
    2010-12-21 09:02:36:165 940 e8c AU #########
    2010-12-21 09:02:36:165 940 e8c AU ## END ## AU: Search for updates [CallId = {B65ACC67-ED84-45D4-9774-D0475806E74B}]
    2010-12-21 09:02:36:165 940 e8c AU #############
    2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
    2010-12-21 09:02:36:165 940 e8c AU AU setting next detection timeout to 2010-12-21 19:02:36
    2010-12-21 09:02:36:165 940 e8c AU Setting AU scheduled install time to 2010-12-22 08:00:00
    2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
    2010-12-21 09:02:36:165 940 e8c AU Successfully wrote event for AU health state:0
    2010-12-21 09:02:41:172 940 e38 Report REPORT EVENT: {678C2913-B3B3-4F14-9310-C2E2B1F3334A} 2010-12-21 09:02:36:165-0500 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 80080005 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80080005.
    2010-12-21 09:02:41:172 940 e38 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2010-12-21 09:02:41:172 940 e38 Report WER Report sent: 7.4.7600.226 0x80080005 61CA813A-7585-442E-A66B-B0D15CE6BDC0 Scan 101 Managed
    2010-12-21 09:02:41:172 940 e38 Report CWERReporter finishing event handling. (00000000)
    2010-12-21 09:06:07:779 940 b4c AU ########### AU: Uninitializing Automatic Updates ###########
    2010-12-21 09:06:37:809 940 b4c Handler FATAL: UH: 0x80080005: StartSession failed in CCbs::IsCbsPending
    2010-12-21 09:06:37:840 940 b4c Report CWERReporter finishing event handling. (00000000)
    2010-12-21 09:06:37:872 940 b4c Service *********
    2010-12-21 09:06:37:872 940 b4c Service ** END ** Service: Service exit [Exit code = 0x240001]
    2010-12-21 09:06:37:872 940 b4c Service *************
    2010-12-21 09:08:37:104 940 e84 Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0500) ===========
    2010-12-21 09:08:37:104 940 e84 Misc = Process: C:\Windows\system32\svchost.exe
    2010-12-21 09:08:37:104 940 e84 Misc = Module: c:\windows\system32\wuaueng.dll
    2010-12-21 09:08:37:104 940 e84 Service *************
    2010-12-21 09:08:37:104 940 e84 Service ** START ** Service: Service startup
    2010-12-21 09:08:37:104 940 e84 Service *********
    2010-12-21 09:08:37:108 940 e84 Agent * WU client version 7.4.7600.226
    2010-12-21 09:08:37:108 940 e84 Agent * Base directory: C:\Windows\SoftwareDistribution
    2010-12-21 09:08:37:108 940 e84 Agent * Access type: No proxy
    2010-12-21 09:08:37:108 940 e84 Agent * Network state: Connected
    2010-12-21 09:08:37:453 940 e84 DtaStor Default service for AU is {00000000-0000-0000-0000-000000000000}
    2010-12-21 09:08:37:462 940 e84 DtaStor Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2010-12-21 09:08:37:464 940 e84 Agent WARNING: failed to access the auth cab, fatal error 0x80070003
    2010-12-21 09:08:37:464 940 e84 Agent WARNING: Invalid service in the backup data store; cleaning up
    2010-12-21 09:08:37:465 940 e84 Agent WARNING: Failed to add and register service 7971f918-a847-4430-9279-4a52d1efe18d to the data store 0x80240031
    2010-12-21 09:08:37:465 940 e84 Agent WARNING: Default Service Recovery: Attempting to add pending registration for service 7971f918-a847-4430-9279-4a52d1efe18d to the data store
    2010-12-21 09:09:22:474 940 e84 Report CWERReporter::Init succeeded
    2010-12-21 09:09:22:474 940 e84 Agent *********** Agent: Initializing Windows Update Agent ***********
    2010-12-21 09:09:22:475 940 e84 Agent *********** Agent: Initializing global settings cache ***********
    2010-12-21 09:09:22:475 940 e84 Agent * WSUS server: http://server2:8530
    2010-12-21 09:09:22:475 940 e84 Agent * WSUS status server: http://server2:8530
    2010-12-21 09:09:22:475 940 e84 Agent * Target group: (Unassigned Computers)
    2010-12-21 09:09:22:475 940 e84 Agent * Windows Update access disabled: No
    2010-12-21 09:09:22:475 940 e84 DnldMgr Download manager restoring 0 downloads
    2010-12-21 09:09:22:476 940 e84 AU ########### AU: Initializing Automatic Updates ###########
    2010-12-21 09:09:22:477 940 e84 AU # WSUS server: http://server2:8530
    2010-12-21 09:09:22:477 940 e84 AU # Detection frequency: 22
    2010-12-21 09:09:22:477 940 e84 AU # Approval type: Scheduled (Policy)
    2010-12-21 09:09:22:477 940 e84 AU # Scheduled install day/time: Every day at 3:00
    2010-12-21 09:09:22:477 940 e84 AU # Auto-install minor updates: Yes (Policy)
    2010-12-21 09:09:22:478 940 e84 AU Setting AU scheduled install time to 2010-12-22 08:00:00
    2010-12-21 09:09:22:751 940 e84 Report *********** Report: Initializing static reporting data ***********
    2010-12-21 09:09:22:751 940 e84 Report * OS Version = 6.1.7600.0.0.65792
    2010-12-21 09:09:22:751 940 e84 Report * OS Product Type = 0x00000004
    2010-12-21 09:09:22:772 940 e84 Report * Computer Brand = Dell Inc.
    2010-12-21 09:09:22:772 940 e84 Report * Computer Model = OptiPlex 380
    2010-12-21 09:09:22:775 940 e84 Report * Bios Revision = A01
    2010-12-21 09:09:22:775 940 e84 Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A01
    2010-12-21 09:09:22:775 940 e84 Report * Bios Release Date = 2010-03-11T00:00:00
    2010-12-21 09:09:22:775 940 e84 Report * Locale ID = 1033
    2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
    2010-12-21 09:09:22:777 940 e84 AU Initializing featured updates
    2010-12-21 09:09:22:777 940 e84 AU Found 0 cached featured updates
    2010-12-21 09:09:22:777 940 e84 AU Successfully wrote event for AU health state:0
    2010-12-21 09:09:22:778 940 e84 AU Successfully wrote event for AU health state:0
    2010-12-21 09:09:22:778 940 e84 AU AU finished delayed initialization
    2010-12-21 09:09:27:781 940 36c Report CWERReporter finishing event handling. (00000000)
    2010-12-21 09:10:20:421 940 bf0 AU Triggering AU detection through DetectNow API
    2010-12-21 09:10:20:422 940 bf0 AU Triggering Online detection (interactive)
    2010-12-21 09:10:20:422 940 e84 AU #############
    2010-12-21 09:10:20:422 940 e84 AU ## START ## AU: Search for updates
    2010-12-21 09:10:20:422 940 e84 AU #########
    2010-12-21 09:10:20:425 940 e84 AU <<## SUBMITTED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
    2010-12-21 09:10:20:425 940 36c Agent *************
    2010-12-21 09:10:20:425 940 36c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2010-12-21 09:10:20:425 940 36c Agent *********
    2010-12-21 09:10:20:425 940 36c Agent * Online = Yes; Ignore download priority = No
    2010-12-21 09:10:20:425 940 36c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2010-12-21 09:10:20:425 940 36c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2010-12-21 09:10:20:425 940 36c Agent * Search Scope = {Machine}
    2010-12-21 09:10:20:425 940 36c Setup Checking for agent SelfUpdate
    2010-12-21 09:10:20:426 940 36c Setup Client version: Core: 7.4.7600.226 Aux: 7.4.7600.226
    2010-12-21 09:10:22:715 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2010-12-21 09:10:22:725 940 36c Misc Microsoft signed: Yes
    2010-12-21 09:10:22:745 940 36c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2010-12-21 09:10:22:750 940 36c Misc Microsoft signed: Yes
    2010-12-21 09:10:22:765 940 36c Setup Determining whether a new setup handler needs to be downloaded
    2010-12-21 09:10:22:765 940 36c Setup SelfUpdate handler is not found. It will be downloaded
    2010-12-21 09:10:22:765 940 36c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226"
    2010-12-21 09:10:52:778 940 36c Setup WARNING: Cbs StartSession, error = 0x80080005
    2010-12-21 09:10:52:778 940 36c Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7600.226" failed, error = 0x80080005
    2010-12-21 09:10:52:778 940 36c Setup FATAL: SelfUpdate check failed, err = 0x80080005
    2010-12-21 09:10:52:779 940 36c Agent * WARNING: Skipping scan, self-update check returned 0x80080005
    2010-12-21 09:10:52:779 940 36c Agent * WARNING: Exit code = 0x80080005
    2010-12-21 09:10:52:779 940 36c Agent *********
    2010-12-21 09:10:52:779 940 36c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
    2010-12-21 09:10:52:779 940 36c Agent *************
    2010-12-21 09:10:52:779 940 36c Agent WARNING: WU client failed Searching for update with error 0x80080005
    2010-12-21 09:10:52:779 940 ba0 AU >>## RESUMED ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
    2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Search callback failed, result = 0x80080005
    2010-12-21 09:10:52:780 940 ba0 AU # WARNING: Failed to find updates with error code 80080005
    2010-12-21 09:10:52:780 940 ba0 AU #########
    2010-12-21 09:10:52:780 940 ba0 AU ## END ## AU: Search for updates [CallId = {F1E8D669-5A48-4C25-832F-4A5ABD80270F}]
    2010-12-21 09:10:52:780 940 ba0 AU #############
    2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
    2010-12-21 09:10:52:783 940 ba0 AU AU setting next detection timeout to 2010-12-21 19:10:52
    2010-12-21 09:10:52:783 940 ba0 AU Setting AU scheduled install time to 2010-12-22 08:00:00
    2010-12-21 09:10:52:783 940 ba0 AU Successfully wrote event for AU health state:0
    2010-12-21 09:10:52:784 940 ba0 AU Successfully wrote event for AU health state:0

  • WSUS 3.0 SP2 on Server 2008 R2 not working (no console or other access)

    Hi,
    In a brand new network with all 2008 R2 servers I setup WSUS. Initially I could not install the role from the Roles tool in Windows and had to install it from a downloaded file from Microsoft (which I later read is due to 2008 R2).
    This ran fine for about 2 weeks, I had all the clients and workstations in groups, approving updates and installing them.. all tickety boo and then one day the console wont connect and I have not been able to get back into WSUS to do anything. I tried removing
    and re-installing WSUS (both keeping the local database and then deleting it the second time) but nothing helps. My event log reports the following every 6 hours:
    Event ID 13042 - Self-update is not working
    Event ID 12002 - The reporting web service is not working
    Event ID 12012 - The API Remoting Web Service is not working
    Event ID 12032 - The Server Synchronization Web Service is not working
    Event ID 12022 - The Client Web Service is not working
    Event ID 12042 - The SimpleAuth Web Service is not working
    Event ID 12052 - The DSS Authentication Web Service is not working
    Some extra points based on what I have read:
    The server DOES have .net 4.0 installed
    WSUS has been removed and re-installed
    All servers are 2008 R2
    The server also runs Remote Desktop Services.. but aside from this is just a file and print server
    Because this server (and the whole network) are brand new, standard practice is to run WSUS against the Microsoft update site and install all critical and optional updates and patches and etc..
    While it was working, I can't recall installing anything that may have broken it, however typically Windows patches do not cause problems on our machines, so I do not pay too close attention to what gets installed.. Perhaps one of these updates broke WSUS?
    Can anyone offer some suggestions for how to troubleshoot this and try get things moving again?
    Thanks!

    Hi,
    > then one day the console wont connect and I have not been able to get back into WSUS to do anything.
    Any error message when you launch WSUS console?
    You mentioned you have Kaspersky Endpoint Security software installed on WSUS server, have you configured antivirus software to exclude WSUS content directory?
    If you cannot access the WSUS console and a timeout error message appears, the CPU of the WSUS server may be at, or very close to, maximum utilization, which causes the database software to time out. If the database software times out, the WSUS console cannot
    be displayed.
    One way of inadvertently overtaxing your WSUS server is to have antivirus software monitor the WSUS content directory. During synchronization, the antivirus software can overload the CPU.
    Please ignore WSUS content in your antivirus software and check the result.
    For more information please refer to following MS articles:
    Issues with the WSUS 3.0 SP2 Administration Console
    http://technet.microsoft.com/en-us/library/dd939877(v=WS.10).aspx
    The DSS Authentication Web Service is not working.
    http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/c901eb7b-7c20-4fb8-87dd-93f128ec8703
    WSUS web services not working
    http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/5b443a1c-01eb-4b73-ad06-03700032bec2
    Lawrence
    TechNet Community Support

  • How to update from WSUS 3.2 SP2 running on Windows 2008 R2 to WSUS 4.0

    Hello, with WSUS 4.0 already in the market, is it adviseable to update from WSUS 3.2 SP2? I am looking at a bare installation of WSUS 4.0 in Server 2012 R2, from basic looks I have not seen yet anything different. We have 12 WSUS servers
    servicing a wide area, and before going ahead with any update of this infrasturture I would like to know of anyone has gone this upgrade path yet? Thanks 
    Shahidul

    is it adviseable to update from WSUS 3.2 SP2?
    I don't think it's critical to upgrade to WSUS v6 at this time, unless your WSUS v3.2 server is still running on a 32-bit system (or any form of WS2003). If you're running WSUS v3.2 on WS2008/WS2008R2 (x64), then those platforms will continue to be supported
    until 2020, so there's no immediate need. However, if you're contemplating a major migration of all systems to Win8/WS2012 environments, then it makes sense to migrate the WSUS server also. If you expect to have Win7/WS2008R2 systems online for the foreseeable
    future, then WSUS v3.2 x64 will continue to meet your needs.
    I am looking at a bare installation of WSUS 4.0 in Server 2012 R2, from basic looks I have not seen yet anything different.
    The most notable difference is a much richer PowerShell interface, so if you're inclined to use PowerShell to manage WSUS, that would be an advantage.
    A notable disadvantage is that you can only partially manage a WSUS v6 system from a Windows 7 workstation: Local publishing requires that activity to be performed from the same generation of system. For example, WSUS v6.3 can only be published to from a
    WS2012R2 or Win8.1 system; WSUS v6.2 can only be published to from a WS2012 or Win8.0 system. This is due to internal dependencies on the BUILD number of the WSUS API.
    I suspect the dependency was a manifestation of protecting WSUS v2 and WSUS v3 systems back in 2007 (local publishing was first introduced in WSUS v3.0), but with SIX possible builds of WSUS now available, it's becoming a major PITA!
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • WSUS 3.0 SP2 Inventory Collection 80072f8f errors

    Environment: Win2008R2 with SCE 2010 & WSUS 3.0 SP2, Win7 Enterprise wkstns on a single domain
    This environment has run fine for several years. But recently, I noticed that most of the workstations are recording the following types of errors when WSUS attempts to collect inventory. Note that the Finding Updates process in the log continues to
    work fine - it is only Inventory Collection which seems to have an issue.
    2014-12-24 02:23:46:632 1100 62c0 AU #############
    2014-12-24 02:23:46:632 1100 f70 Inv ## START ##  Inv: Inventory Collection
    2014-12-24 02:23:46:632 1100 f70 Inv #########
    2014-12-24 02:23:46:632 1100 f70 Inv   # Talking to WSUS server =
    https://ZVR-SCE.mydomain.com:8531
    2014-12-24 02:23:46:632 1100 f70 Inv   # Downloading Rule file from =
    https://ZVR-SCE.mydomain.com:8531/Inventory/InventoryRules.cab
    2014-12-24 02:23:46:632 1100 62c0 AU Successfully wrote event for AU health state:0
    2014-12-24 02:23:46:632 1100 62c0 AU Featured notifications is disabled.
    2014-12-24 02:23:46:632 1100 62c0 AU AU setting next detection timeout to 2014-12-25 02:56:21
    2014-12-24 02:23:46:647 1100 62c0 AU Setting AU scheduled install time to 2014-12-24 08:00:00
    2014-12-24 02:23:46:647 1100 62c0 AU Successfully wrote event for AU health state:0
    2014-12-24 02:23:46:670 1100 62c0 AU Successfully wrote event for AU health state:0
    2014-12-24 02:23:46:692 1100 f70 Misc WARNING: Send failed with hr = 80072f8f.
    2014-12-24 02:23:46:702 1100 f70 Misc WARNING: SendRequest failed with hr = 80072f8f. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-12-24 02:23:46:702 1100 f70 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://ZVR-SCE.mydomain.com:8531/Inventory/InventoryRules.cab>.
    error 0x80072f8f
    2014-12-24 02:23:46:702 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072f8f
    2014-12-24 02:23:46:702 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072f8f
    2014-12-24 02:23:46:702 1100 f70 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072f8f
    2014-12-24 02:23:46:707 1100 f70 Misc WARNING: Send failed with hr = 80072f8f.
    2014-12-24 02:23:46:707 1100 f70 Misc WARNING: SendRequest failed with hr = 80072f8f. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-12-24 02:23:46:707 1100 f70 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://ZVR-SCE.mydomain.com:8531/Inventory/InventoryRules.cab>.
    error 0x80072f8f
    2014-12-24 02:23:46:707 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072f8f
    2014-12-24 02:23:46:707 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072f8f
    2014-12-24 02:23:46:707 1100 f70 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072f8f
    2014-12-24 02:23:46:717 1100 f70 Misc WARNING: Send failed with hr = 80072f8f.
    2014-12-24 02:23:46:717 1100 f70 Misc WARNING: SendRequest failed with hr = 80072f8f. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-12-24 02:23:46:717 1100 f70 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://ZVR-SCE.mydomain.com:8531/Inventory/InventoryRules.cab>.
    error 0x80072f8f
    2014-12-24 02:23:46:717 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072f8f
    2014-12-24 02:23:46:717 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072f8f
    2014-12-24 02:23:46:717 1100 f70 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072f8f
    2014-12-24 02:23:46:725 1100 f70 Misc WARNING: Send failed with hr = 80072f8f.
    2014-12-24 02:23:46:725 1100 f70 Misc WARNING: SendRequest failed with hr = 80072f8f. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2014-12-24 02:23:46:725 1100 f70 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://ZVR-SCE.mydomain.com:8531/Inventory/InventoryRules.cab>.
    error 0x80072f8f
    2014-12-24 02:23:46:725 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072f8f
    2014-12-24 02:23:46:725 1100 f70 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072f8f
    2014-12-24 02:23:46:725 1100 f70 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072f8f
    2014-12-24 02:23:46:725 1100 f70 Inv WARNING: Inventory: Failed to download rule file with error 0x80072f8f
    2014-12-24 02:23:46:725 1100 f70 Inv   # WARNING: Exit code = 0x80072F8F
    2014-12-24 02:23:46:737 1100 f70 Inv #########
    2014-12-24 02:23:46:737 1100 f70 Inv ##  END  ##  Inv: Inventory Collection
    2014-12-24 02:23:46:737 1100 f70 Inv #############
    2014-12-24 02:23:46:737 1100 f70 Inv WARNING: Inventory: Failed to process work item 0x80072f8f
    2014-12-24 02:23:51:502 1100 f70 Report REPORT EVENT: {9ADA1158-FBD7-439E-A672-4F976113A96A} 2014-12-24 02:23:46:482-0500 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2014-12-24 02:23:51:502 1100 f70 Report REPORT EVENT: {04153F2F-2276-44AA-9863-8E88CA7CD985} 2014-12-24 02:23:46:482-0500 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment
    Check Reporting client status.
    2014-12-24 02:23:51:502 1100 f70 Report REPORT EVENT: {B13BA8D6-BBE5-4F96-BBA0-90D7401FC32B} 2014-12-24 02:23:46:725-0500 1 121 104 {00000000-0000-0000-0000-000000000000} 0 80072f8f InventoryEngine Failure Inventory
    Rules Download Inventory: Faied to download rule file
    2014-12-24 02:23:51:922 1100 f70 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2014-12-24 02:23:51:922 1100 f70 Report WER Report sent: 7.6.7600.320 0x80072f8f 00000000-0000-0000-0000-000000000000 Other 104 Managed
    2014-12-24 02:23:51:932 1100 f70 Report CWERReporter finishing event handling. (00000000)

    Interestingly, the 2003R2SP2 servers on our network are not exhibiting this issue. I am wondering if a newer WUA agent on the Win7 and 2008R2 systems are causing the issue.
    From one of the 2003 servers:
    2014-12-25 19:46:14:853  800 6e8 Inv #############
    2014-12-25 19:46:14:853  800 6e8 Inv ## START ##  Inv: Inventory Collection
    2014-12-25 19:46:14:853  800 6e8 Inv #########
    2014-12-25 19:46:14:853  800 6e8 Inv   # Talking to WSUS server =
    https://ZVR-SCE.mydomain.com:8531
    2014-12-25 19:46:14:900  800 6e8 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\Inventory\InventoryRule\InventoryRules.cab:
    2014-12-25 19:46:14:978  800 6e8 Misc  Microsoft signed: Yes
    2014-12-25 19:46:15:119  800 6e8 Inv   # New Rule file needs to be downloaded
    2014-12-25 19:46:15:119  800 6e8 Inv   # Downloading Rule file from =
    https://ZVR-SCE.mydomain.com:8531/Inventory/InventoryRules.cab
    2014-12-25 19:46:15:150  800 6e8 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\Inventory\InventoryRule\InventoryRules.cab:
    2014-12-25 19:46:15:166  800 6e8 Misc  Microsoft signed: Yes
    2014-12-25 19:46:15:166  800 6e8 Inv   # Inventory Rule id = 8226C3A1-70D4-4848-B441-1555AC820A23, version = 1.0
    2014-12-25 19:46:16:088 5336 290 COMAPI   - Updates found = 262
    2014-12-25 19:46:16:088 5336 290 COMAPI ---------
    2014-12-25 19:46:16:088 5336 290 COMAPI --  END  --  COMAPI: Search [ClientId = <NULL>]
    2014-12-25 19:46:16:088 5336 290 COMAPI -------------
    2014-12-25 19:46:22:946  800 6e8 Inv #########
    2014-12-25 19:46:22:946  800 6e8 Inv ##  END  ##  Inv: Inventory Collection
    2014-12-25 19:46:22:946  800 6e8 Inv #############
    2014-12-25 19:46:27:945  800 6e8 Report REPORT EVENT: {F98EFD55-7D75-4995-9397-6291AA65D83F} 2014-12-25 19:46:22:946-0500 1 126 104 {00000000-0000-0000-0000-000000000000} 0 0 InventoryEngine Success Inventory
    processing Inventory: Successfully collected the inventory data
    2014-12-25 19:53:14:177  800 6e8 Report Uploading 7 events using cached cookie, reporting URL =
    https://ZVR-SCE.mydomain.com:8531/ReportingWebService/ReportingWebService.asmx
    2014-12-25 19:53:14:270  800 6e8 Report Reporter successfully uploaded 7 events.

  • WSUS 3.0 SP2 not installing on Server 2008

    Hi
    I'm trying to install WSUS 3.0 SP2 on Server 2008 SP2.
    During the install I am told that IIS and the required roles must be installed before set up can continue. I have confirmed that all of the pre-requisites listed below are installed on this server;
    Microsoft Internet Information Services (IIS) 7.0. Ensure that the following components are enabled:
    Windows Authentication
    ASP.NET
    6.0 Management Compatibility
    IIS Metabase Compatibility
    The installer still tells me that IIS or it's required components are not installed properly.
    Is there anything else that I need to check in relation to this error message?
    Thanks in advance.

    > Is there anything else that I need to check in relation to this error message?
    Perhaps the WSUS 3.0 SP2 Deployment Guide, in the section Configure IIS?
    I don't see "Static Content", "ISAPI Extensions", or "ISAPI Feature" listed in the citation you provided, and I'm not sure what it is you're citing to get that list of components for IIS 7.0, but it doesn't match anything that's ever been officially documented for WSUS v3 in the Deployment Guide.
    In the Select Role Services window, make sure that the following services are selected:
    Common HTTP Features (including Static Content)
    ASP.NET, ISAPI Extensions, and ISAPI Features (under Application Development)
    Windows Authentication (under Security)
    IIS Metabase Compatibility (under Management Tools, expand IIS 6 Management Compatibility)
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com

  • WSUS 3.0 SP2 will not run after installing update 2720211

    http://support.microsoft.com/kb/2720211
    The update was installed and server rebooted.  Now the WSUS console on Server 2008 SP2 will not run.  "Error: Connection Error.  An error occurred trying to connect to WSUS server."
    The update service and IIS are both running.
    When checking for updates from clients, they  show a message saying their update software needs to be upgraded, but they fail updating.
    I was going to uninstall the update, but there is no option to uninstall the update from the WSUS server.
    What are options to fix this?

    This page helped alot. Let me recap for others on the interwebs.
    Cause:
    - Applied KB2720211 to a WSUS 3.0 SP2 server thats running on Windows 2008 64 bit server with local SQL db.
    What happened:
    - I could no longer sync my WSUS server with the interwebs.
    - clients could still connect to WSUS and I could still open the WSUS console.
    - Uninstalled WSUS, left DB and downloads and reinstalled WSUS in attempt to fix broken syncing.
    - Clients could now no longer sync with WSUS server. (They got Windows Update error code 800B0001).
    Solution:
    - Googled, found this page.
    - Followed just these last few steps that Chucker2 posted.
    Extract necessary files from 2720211 installer
    Download the KB2720211 installer for your architecture from Microsoft (http://support.microsoft.com/kb/2720211)
    Extract WUSSetup.msp from the installer by running the installer with the /extract parameter (example: "WSUS-KB2720211-x64.exe /extract")
    With 7-zip, open WUSSetup.msp and extract "PCW_CAB_SUS".
    With 7-zip, open "PCW_CAB_SUS" and extract "DbCert", "DbCertDll", and "DbCertSql".
    Rename those files to "WSUSSignDb.cer", "WSUSSignDb.dll", and "WSUSSignDb.sql", respectively.
    On your WSUS server, navigate to "C:\Windows\SYSMSI\SSEE\MSSQL.2005\MSSQL\SchemaSig" and copy the extracted "WSUSSignDb.cer" and "WSUSSignDb.dll" to it. Make a backup copy of the two existing versions, just in case.
    On your WSUS server, navigate to "C:\Program Files\Update Services\Database" and copy the extracted "WSUSSignDb.sql" to it. Make a backup copy of any existing versions of the file.
    Reinstalled 2720211
    PROBLEM FIXED AND CLIENTS COULD ALL SYNCH AGAIN.
    Thanks Chucker 2.
    ps. Susan Bradley stop polluting every WSUS post on the interwebs with your constant links to WSUS KB2720211 : Common issues
    encountered and how to fix them
    this is the best solution. after reboot the problem is solved .
    kailash

  • WSUS 3.0 SP2 Install - Can't connect to Server.

    I have a server with Windows Server 2008SP2 Standard, IIS7, which was rebuilt to replace the crashed W2003 system.  The original system was running the WSUS 3.0 role and IIS for an existing organizational website.  I was able
    to migrate the website and now have installed WSUS 3.0 SP2 and picked “use default site” during the installation.  However, when running WSUS, I cannot “connect to server”. 
    As far as I could tell, on the old system both the organizational website and WSUS sites were running on port 80 (In fact, I had access to a .WIM copy of the old system so can mount it to look at the old IIS6 configuration, and I had a
    MSbackup that reconstituted WSUS\UpdateServicesDbFiles\ SUS.mdf and SUSDB_lob.ldf).
    Can in fact both WSUS and the other website share port 80?  I see in IIS7 manager that /Selfupdate and /Content are listed in the Vdir section.  Is it merely that I have to configure something further in IIS to allow this? 
    I see no evidence of another web port listed for WSUS in our firewall VLAN exceptions. 
    Also, would using the backed up SUS.mdf from the old WSUS instance be worth trying to use with the new instance of WSUS 3.0 SP@?
    Tnx…

    Why are you looking for issues where they don't exist?  I suppose since I don't know why there is a problem, I'm looking for where the problem may lie after exhausting verification of all other proper methods listed in the MS technet
    directions to prep for the WSUS 3 install, the install itself and the post install configuration, and the diagnostics information.  So my last most thorough uninstall/re-install try produced the same problem I have been getting each time.  They are
    listed below.  It is not a firewall issue as traffic for port 80 is already allowed b/c of the existing organizational website.  Can I narrow this down and infer from the error messages below that they seem to indicate an IIS7 issue?  
    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          2/21/2014 2:41:06 PM
    Event ID:      7053
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      servername.domain.name.com
    Description:
    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.InvalidOperationException -- Client found response content type of '', but expected 'text/xml'.
    The request failed with an empty response.
    Source
    Microsoft.UpdateServices.Administration
    Stack Trace:
       at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
       at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
       at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.get_AdminApiTools()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.get_ServerState()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.SetNavigationItemEnabledStates()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.InitializeNavigationItems()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.OOBEWizardInitialize()
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Server Update Services" />
        <EventID Qualifiers="0">7053</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-21T19:41:06.000Z" />
        <EventRecordID>5241</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Servername.domain.name.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>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.InvalidOperationException -- Client found response content type of '', but expected 'text/xml'.
    The request failed with an empty response.
    Source
    Microsoft.UpdateServices.Administration
    Stack Trace:
       at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
       at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
       at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.get_AdminApiTools()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.get_ServerState()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.SetNavigationItemEnabledStates()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.InitializeNavigationItems()
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.OOBE.OOBEWizard.OOBEWizardInitialize()</Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          2/21/2014 2:41:06 PM
    Event ID:      13051
    Task Category: 6
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      Servername.domain.name.com
    Description:
    No client computers have ever contacted the server.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Server Update Services" />
        <EventID Qualifiers="0">13051</EventID>
        <Level>3</Level>
        <Task>6</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-21T19:41:06.000Z" />
        <EventRecordID>5242</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Servername.domain.name.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>No client computers have ever contacted the server.</Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          2/21/2014 2:41:06 PM
    Event ID:      12002
    Task Category: 9
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Servername.domain.name.com
    Description:
    The Reporting Web Service is not working.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Server Update Services" />
        <EventID Qualifiers="0">12002</EventID>
        <Level>2</Level>
        <Task>9</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-21T19:41:06.000Z" />
        <EventRecordID>5243</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Servername.domain.name.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The Reporting Web Service is not working.</Data>
      </EventData>
    </Event>
    Log Name:      Application
    Source:        Windows Server Update Services
    Date:          2/21/2014 2:41:06 PM
    Event ID:      12012
    Task Category: 9
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Servername.domain.name.com
    Description:
    The API Remoting Web Service is not working.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Server Update Services" />
        <EventID Qualifiers="0">12012</EventID>
        <Level>2</Level>
        <Task>9</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-21T19:41:06.000Z" />
        <EventRecordID>5244</EventRecordID>
    <Channel>Application</Channel>
        <Computer>Servername.domain.name.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>The API Remoting Web Service is not working.</Data>
      </EventData>
    </Event>
    Etc.....

  • WSUS 3.0 SP2 master server cross-forest migration impacts

        Hello to all, I'm preparing a cross-forest migration and have one WSUS 3.0 SP2 master on source forest placed in root domain. This master has 16 replicas scattered among child source domains. As I plan do migrate member servers using MS
    tool named ADMT 3.2 and considering that I will firstly migrate just root domain member servers to target forest, I need to know:
       1- Will WSUS 3.0 SP2 master server work after it's migrated from source to target forest? I mean: can all its replicas still access and donwload the necessary patches from it? Will its configuration be in place (groups, schedules, etc) ?
       2- Should I need to change source domain clients WSUS GPOs to point to the just migrated master server (new FQDN name)?
       3- Is possible to change my just migrated WSUS 3.0 SP2 to be replica from a master server already present on target forest? How this move could affect its existing replicas still present on source forest?
       Suggestion and attention points will be appreciated.
       Regards, EEOC.

    1- Will WSUS 3.0 SP2 master server work after it's migrated from source to target forest? I mean: can all its replicas still access and donwload the necessary patches from it? Will its configuration be in place (groups, schedules, etc) ?
    Fundamentally yes, as long as the downstream servers are updated to use the new hostname and DNS properly resolves that hostname. NOTE: You cannot "migrate" the WSUS role using ADMT. What is your plan for "migrating" the WSUS upstream server?
    2- Should I need to change source domain clients WSUS GPOs to point to the just migrated master server (new FQDN name)?
    Probably. Presumably the hostname and IP Address of the server are going to change.
    3- Is possible to change my just migrated WSUS 3.0 SP2 to be replica from a master server already present on target forest?
    Yes, but that's kind of a cart-before-the-horse move... which brings us back to the original question: How do you plan to "migrate" the upstream server?
    How this move could affect its existing replicas still present on source forest?
    Well.. it will introduce a three-tier replication hierarchy for starters, which will slow everything down by one or two days. But, really, I wouldn't worry about that because there's no real need to do this.
    Suggestion and attention points will be appreciated.
    Install a *NEW* WSUS server in the target forest.
    Configure it as a replica of the existing master in the source forest.
    Replicate.
    When the replication is complete, reconfigure it as an Upstream Server and RESET the Product Category and Update Classifications to what they should be.
    Synchronize with Microsoft.
    When that sync is successful, enabled regular synchronizations.
    Configure clients and downstream servers to sync from the new upstream server in the target forest.
    When all clients and downstream servers are working with the new server, turn off the old one.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • WSUS 3.2 SP2 with KB2720211 and later KB2734608 rebuilt as WSUS 6.3.9600.16384. Will clients connect back OK after initial Sync to parent server?

    Hello all, after many iteration of trying to fix 11 DSS running Windows 2008 R2 WSUS 3.2 SP2 sync issues with parent USS, we have decided to gradually move towards WSUS 6.3.9600.16384 on Windows 2012 R2.
    I have already built a Windows 2012 R2 WSUS server (which will eventually replace the current 2008 R2 WSUS 3.2 SP2 master server) The sync is OK. There was no error on the data base side or anything.
    The idea now is to gradually pick one DSS, rebuild it with Windows 2012 R2 WSUS service, and sync it with newly built and to be main primary server. The fact that I actually picked up a working WSUS 3.2 and rebuilt it with WSUS 6.3, will the clients still
    talk back and connect? Or this version uses totally different update engine..in that case, how is it all going to work?
    Shahidul

    The fact that I actually picked up a working WSUS 3.2 and rebuilt it with WSUS 6.3, will the clients still talk back and connect?
    Theoretically, yes; but in practicality, probably not.
    Almost certainly your original WSUS v3 server was installed to the Default Web Site (port 80). WSUS v6 servers default to their own v-root on port 8530, so at a minimum you will need to reconfigure the GPO that tells the clients where to find their WSUS
    Server. However, once you do that, the clients will register automatically.
    The second part of this question relates to target groups.
    If you're using Client-Side Targeting and you've created the groups on the new WSUS Server, the clients will automatically register in their policy-assigned groups.
    If you're using Server-Side Targeting, you'll have to use the console to reassign the clients from "Unassigned Computers" to their correct target group(s).
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • WSUS 3.0 SP2 on Server 2k8 R2 getting Error 364 and 10032

    This is a FRESH installation of Server 2008 R2, installed with SP1 (no updates applied from Windows Update - I want this to happen via WSUS)
    WSUS 3.0 SP2 FRESH installation from standalone installer.
    Installed KB2720211 to correct the issue of clients being unable to communicate with WSUS server.
    WSUS installs fine, synchronizes fine, but a number of updates showing "The Microsoft Software License Terms for this update failed to download"
    Many other updates report the download failed with REASON: HTTP 404 The requested URL does not exist on the server.
    Throughout the last 2 days of researching and investigating these particular errors, I have performed the following steps:
    Verify correct permissions for the drive and folders - no change
    wsusutil reset - no change
    wsusutil checkhealth - Reports WSUS working correctly
    Uninstalled and reinstalled WSUS 3.0 in full
    Removed server from any and all firewall and ISA devices, turned off the internal Windows Firewall completely - no change
    Reinstalled Server 2008R2 again from scratch, installed WSUS again from scratch - no change
    WSUS and Server 2008R2 configurations are identical to a previous installation that was working perfectly, and is NOT using a proxy.

    In my research on this issue I have encountered a number of posts mentioning this, although none of them specified v3.2.
    Given that the patch only applies to WSUS v3.2, to do so would be notably redundant. :-)
    Is the KB2734608 applicable to WSUS 3.0 as well?
    You seem to be confused by nomenclature.
    "WSUS 3.0" == WSUS v3 RTM (released Spring 2007)
    "WSUS 3.1" == WSUS v3 SP1 (released Summer 2008)
    "WSUS 3.2" == WSUS v3 SP2 (released October 2009)
    Nonetheless, the patch only applies to WSUS v3 with Service Pack 2, aka WSUS v3.2.
    I am hesitant to say that maybe an upgrade to 3.2 may fix the issue
    Since you can only install WSUS v3.2 on a Windows Server 2008 R2 server, this is really a non-issue.
    I added the WSUS role within the server manager rather than from the standalone installer.
    This was probably a key differentiator. I'm curious why you used the standalone installer to begin with.
    I should mention, during the server installation, I also did a full factory reset on the router, and reconfigured it accordingly.
    I'm still inclined to believe this had the most significant impact on your download failures.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.
    Yea, in looking around further I figured out that the 3.2 was a reference to 3.0 SP2. I went ahead and added that patch and lost the ability to synchronize period. At that point I just wiped everything again and am back up and running.
    I used the standalone installer as the server role had originally failed and was unusable in the original installation. I stayed with the standalone installer as I had thought it may have been updated from the version included in the 2k8 R2. I now know otherwise.
    I was still able to use the wizard to start with, which allowed the server manager to add the necessary required roles and services, but would ultimately fail in installing the WSUS role. This time it all worked like a charm, so I went with it.
    As for the router, it may have been the culprit, although prior to the initial server reformat, the previous WSUS installation was working perfectly, about an hour prior to the completion of the the format and the installation and configuration of the WSUS
    server.
    Either way, thanks for the help and the clarifications on some of the items for me.

  • Can a WSUS 3.0 sp2 server be a downstream server of WSUS 2012 R2?

    Can a WSUS 3.0 sp2 server be a downstream server of WSUS 2012 R2?

    Am 17.04.2014 schrieb silverandblackaholic2:
    Can a WSUS 3.0 sp2 server be a downstream server of WSUS 2012 R2?
    Yes, you ca. But if you install WSUS on a W2008R2 have a look at the
    Version from your WSUS 3.0 SP2.
    WSUS 3.0 (SP2):     Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211:     Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608:     Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185:     Build 3.2.7600.262
    The Version you will find on the Startpage from WSUS:
    http://www.wsus.de/images/wsus-version.png
    Servus
    Winfried
    Gruppenrichtlinien
    WSUS Package Publisher
    HowTos zum WSUS Package Publisher
    NNTP-Bridge für MS-Foren

  • Reinstall WSUS 3.0 SP2 on Windows Server 2008 R2

    Hi all,
    I want to reinstall WSUS Server 3.0 SP2 but
    I'm not able to do it due several issues. If I try to install WSUS with the WSUS30-KB972455-x64 .exe file, appears the following issue:
    ParseCommandLine: Failed to read InstallType registry value (Error 0x80070002: The system cannot find the file specified.). DoInstall: ParseCommandLine failed (Error 0x80041453)
    If I try to install WSUS with Server Manager, the issue is different:
    The update could not be found. There may be a network connection issue
    Also, if I try to install the Windows Internal Database feature, the issue is is different:
    Attempt to install WID dailed with error code 0x80070666. Another version of this product is already installed.
    I tried some fixes I've found, for example modifying registry keys, renaming  folders, cmd commands, gpedit, services, etc. I have the prerequisites installed, and the server with the updates in date.
    My ServerManager.log :
    4160: 2014-03-11 15:44:02.547 [WindowsUpdateDownloader]   Search query: 'CategoryIDs contains '4e487029-f550-4c22-8b31-9173f3f95786''
    4160: 2014-03-11 15:44:02.563 [WindowsUpdateDownloader]   Searching....
    4160: 2014-03-11 15:44:06.785 [WindowsUpdateDownloader]   Initial search failed, try again on WU server.
    4160: 2014-03-11 15:44:08.120 [WindowsUpdateDownloader]   Search returned: Succeeded, found 0 updates.
    4160: 2014-03-11 15:44:08.135 [InstallationProgressPage]  Search completed, result: Succeeded.
    4160: 2014-03-11 15:44:08.135 [InstallationProgressPage]  Downloading...
    4160: 2014-03-11 15:44:08.151 [WindowsUpdateDownloader]   Sending failure DownloadComplete event.
    4160: 2014-03-11 15:44:08.151 [InstallationProgressPage]  Download completed, result: NotStarted.
    4160: 2014-03-11 15:44:08.151 [InstallationProgressPage] Error (Id=0) Failure message: 'The update could not be found. There may be a network connection issue. <a href="WSUS.chm::/html/54a9eb1f-5dd1-42d8-ad00-dae55d7b9463.htm">Click here for
    more information.</a>'
    4160: 2014-03-11 15:44:08.151 [InstallationProgressPage]  Invoking LoadFinishPage.
    4160: 2014-03-11 15:44:08.151 [InstallationProgressPage]  About to load finish page...
    4160: 2014-03-11 15:44:08.151 [InstallationFinishPage]    Loading finish page
    4160: 2014-03-11 15:44:08.228 [InstallationFinishPage]    Finish page loaded
    4160: 2014-03-11 15:47:32.304 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 15:47:32.460 [Provider]                  [STAT] DISCOVERY: ComponentInstaller.Initialize() took '164.6411' msec(s) total.
    4160: 2014-03-11 15:49:39.402 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 15:51:41.206 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 15:53:43.435 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 15:53:43.544 [Provider]                  [STAT] DISCOVERY: ComponentInstaller.Initialize() took '113.2189' msec(s) total.
    4160: 2014-03-11 15:55:45.910 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 15:57:47.936 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 15:59:49.989 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 16:01:52.089 [CBS]                       IsCacheStillGood: True.
    4160: 2014-03-11 16:02:30.309 [Provider]                  System changed since last refresh: False
    4160: 2014-03-11 16:02:37.841 [InstallationProgressPage]  Loading progress page...
    4160: 2014-03-11 16:02:37.919 [InstallationProgressPage]  Creating WindowsUpdateDownloader.
    4160: 2014-03-11 16:02:37.919 [InstallationProgressPage]  Searching for Updates...
    4160: 2014-03-11 16:02:37.934 [InstallationProgressPage]  Starting asynchronous download.
    4160: 2014-03-11 16:02:37.981 [WindowsUpdateDownloader]   Creating session.
    4160: 2014-03-11 16:02:37.981 [WindowsUpdateDownloader]   Search query: 'CategoryIDs contains '4e487029-f550-4c22-8b31-9173f3f95786''
    4160: 2014-03-11 16:02:37.981 [WindowsUpdateDownloader]   Searching....
    4160: 2014-03-11 16:02:44.193 [WindowsUpdateDownloader]   Initial search failed, try again on WU server.
    4160: 2014-03-11 16:02:45.529 [WindowsUpdateDownloader]   Search returned: Succeeded, found 0 updates.
    4160: 2014-03-11 16:02:45.529 [InstallationProgressPage]  Search completed, result: Succeeded.
    4160: 2014-03-11 16:02:45.529 [InstallationProgressPage]  Downloading...
    4160: 2014-03-11 16:02:45.544 [WindowsUpdateDownloader]   Sending failure DownloadComplete event.
    4160: 2014-03-11 16:02:45.544 [InstallationProgressPage]  Download completed, result: NotStarted.
    4160: 2014-03-11 16:02:45.544 [InstallationProgressPage] Error (Id=0) Failure message: 'The update could not be found. There may be a network connection issue. <a href="WSUS.chm::/html/54a9eb1f-5dd1-42d8-ad00-dae55d7b9463.htm">Click here for
    more information.</a>'
    4160: 2014-03-11 16:02:45.544 [InstallationProgressPage]  Invoking LoadFinishPage.
    4160: 2014-03-11 16:02:45.544 [InstallationProgressPage]  About to load finish page...
    4160: 2014-03-11 16:02:45.560 [InstallationFinishPage]    Loading finish page
    4160: 2014-03-11 16:02:45.637 [InstallationFinishPage]    Finish page loaded
    4160: 2014-03-11 16:03:33.195 [Provider]                  System changed since last refresh: False
    4160: 2014-03-11 16:03:41.001 [InstallationProgressPage]  Loading progress page...
    4160: 2014-03-11 16:03:41.078 [InstallationProgressPage]  Begining Sync operation...
    4160: 2014-03-11 16:03:41.265 [Sync]                     
    Sync Graph of changed nodes
    ==========
    name     : Windows Internal Database
    state    : Changed
    rank     : 1
    sync tech: MSI
    ant.     : empty
    pred.    : empty
    provider : Provider
    4160: 2014-03-11 16:03:41.265 [Sync]                      Calling sync provider of Windows Internal Database ...
    4160: 2014-03-11 16:03:41.265 [Provider]                  Sync:: guest: 'Windows Internal Database', guest deleted?: False
    4160: 2014-03-11 16:03:41.281 [Provider]                  Begin installation of 'Windows Internal Database'...
    4160: 2014-03-11 16:03:41.281 [Provider]                  Install: Guest: 'Windows Internal Database', MSI-Id: 'WSSEE'
    4160: 2014-03-11 16:03:41.327 [InstallationProgressPage]  Installing...
    4160: 2014-03-11 16:03:41.343 [OCSetup]                   Installing 'WSSEE' ...
    4160: 2014-03-11 16:03:41.358 [OCSetup]                   About to run: 'ocsetup.exe "WSSEE"  /quiet /norestart /x:" /lv* ...\AppData\Local\Temp\msi.log"'
    4160: 2014-03-11 16:03:50.688 [OCSetup]                   ...done. Status: 1638, Message: 'Another version of this product is already installed. Installation of this version
    cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel'
    4160: 2014-03-11 16:03:50.704 [InstallationProgressPage]  Verifying installation...
    4160: 2014-03-11 16:03:50.751 [Provider]                  Skipped configuration of 'Windows Internal Database' because install operation failed.
    4160: 2014-03-11 16:03:50.751 [Provider]                 
    [STAT] For 'Windows Internal Database':
    [STAT] Installation took '9.5095373' second(s) total.
    [STAT] Configuration took '0' second(s) total.
    [STAT] Total time: '9.5095373' second(s).
    4160: 2014-03-11 16:03:50.766 [Provider] Error (Id=0) Sync Result - Success: False, RebootRequired: False, Id: 51
    4160: 2014-03-11 16:03:50.766 [Provider] Error (Id=0) Sync Message - OperationKind: Install, MessageType: Error, MessageCode: -2147023258, Message: Attempt to install Windows Internal Database failed with error code 0x80070666., AdditionalMessage: Another version
    of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel
    4160: 2014-03-11 16:03:50.797 [InstallationProgressPage]  Sync operation completed
    4160: 2014-03-11 16:03:50.797 [InstallationProgressPage]  Performing post install/uninstall discovery...
    4160: 2014-03-11 16:03:50.813 [Provider]                  C:\Windows\system32\ServerManager\Cache\CbsUpdateState.bin does not exist.
    4160: 2014-03-11 16:03:50.859 [CBS]                       IsCacheStillGood: False.
    And my WSUSSetup.log:
    2014-03-11 15:47:46  Error     MWUSSetup          ParseCommandLine: Failed to read InstallType registry value (Error 0x80070002: The system cannot find the file specified.)
    2014-03-11 15:48:46  Error     MWUSSetup          DoInstall: ParseCommandLine failed (Error 0x80041453)
    now I am a little lost, where I could start?

    4160: 2014-03-11 16:03:50.688 [OCSetup]                   ...done. Status: 1638, Message: 'Another version of this product is already installed. Installation
    of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel'
    First step is to get the original installation of WSUS fully uninstalled.
    How to Uninstall WSUS
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • WSUS 3.0 SP2 Some clients have not yet reported

    Hi, I am ready to tear my hair out here. My WSUS Server is running version 3.0 SP2 (Server Version 3.2.7600.274. I have installed the following KB's on the server (KB2720211, KB2734608 and KB29308066). Around 60% of my clients have a status of not yet reported.
    The clients are on client version 7.6.7600.320. I am attaching some of the windowsupdate.log details from one of the clients which has not yet reported. Have I missed something obvious here?
    Many  thanks,
    Niall.
    04:28:04:003+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2014-08-25 04:28:09:019 1328 8488 Report REPORT EVENT: {0141507D-D9AD-4A88-ABD4-AD57621FE5A5} 2014-08-25 04:28:04:004+0100 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment
    Check Reporting client status.
    2014-08-25 04:28:09:019 1328 8488 Report CWERReporter finishing event handling. (00000000)
    2014-08-25 09:26:05:061 24804 9c54 Misc ===========  Logging initialized (build: 7.6.7600.320, tz: +0100)  ===========
    2014-08-25 09:26:05:062 24804 9c54 Misc   = Process: C:\Windows\System32\sdiagnhost.exe
    2014-08-25 09:26:05:062 24804 9c54 Misc   = Module: C:\Windows\system32\wuapi.dll
    2014-08-25 09:26:05:061 24804 9c54 COMAPI -------------
    2014-08-25 09:26:05:062 24804 9c54 COMAPI -- START --  COMAPI: Search [ClientId = <NULL>]
    2014-08-25 09:26:05:062 24804 9c54 COMAPI ---------
    2014-08-25 09:26:05:159 1328 88f0 Agent *************
    2014-08-25 09:26:05:159 24804 9c54 COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = <NULL>]
    2014-08-25 09:26:05:159 1328 88f0 Agent ** START **  Agent: Finding updates [CallerId = ]
    2014-08-25 09:26:05:159 1328 88f0 Agent *********
    2014-08-25 09:26:05:159 1328 88f0 Agent   * Online = Yes; Ignore download priority = No
    2014-08-25 09:26:05:159 1328 88f0 Agent   * Criteria = "IsInstalled=0 and Type='Software'"
    2014-08-25 09:26:05:159 1328 88f0 Agent   * ServiceID = {00000000-0000-0000-0000-000000000000} Third party service
    2014-08-25 09:26:05:159 1328 88f0 Agent   * Search Scope = {Machine}
    2014-08-25 09:26:13:705 1328 88f0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-08-25 09:26:13:705 1328 88f0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://sccm2012:8530/ClientWebService/client.asmx
    2014-08-25 09:26:13:749 1328 88f0 PT WARNING: Cached cookie has expired or new PID is available
    2014-08-25 09:26:13:749 1328 88f0 PT Initializing simple targeting cookie, clientId = 03fda369-08de-4b42-b59b-e98bce63adf7, target group = , DNS name = cipclyn2012.comitirl.local
    2014-08-25 09:26:13:749 1328 88f0 PT   Server URL =
    http://sccm2012:8530/SimpleAuthWebService/SimpleAuth.asmx
    2014-08-25 09:28:16:001 1328 88f0 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-08-25 09:28:16:001 1328 88f0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://sccm2012:8530/ClientWebService/client.asmx
    2014-08-25 09:28:23:751 1328 88f0 Agent   * Found 0 updates and 88 categories in search; evaluated appl. rules of 1664 out of 2963 deployed entities
    2014-08-25 09:28:23:817 1328 88f0 Agent *********
    2014-08-25 09:28:23:817 1328 88f0 Agent **  END  **  Agent: Finding updates [CallerId = ]
    2014-08-25 09:28:23:817 1328 88f0 Agent *************
    2014-08-25 09:28:23:905 24804 8a1c COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
    2014-08-25 09:28:23:916 24804 8a1c COMAPI   - Updates found = 0
    2014-08-25 09:28:23:916 24804 8a1c COMAPI ---------
    2014-08-25 09:28:23:916 24804 8a1c COMAPI --  END  --  COMAPI: Search [ClientId = <NULL>]
    2014-08-25 09:28:23:916 24804 8a1c COMAPI -------------
    2014-08-25 09:28:28:813 1328 88f0 Report REPORT EVENT: {7F3E0617-A580-41BA-B529-EF750F2C7247} 2014-08-25 09:28:23:813+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0  Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2014-08-25 09:28:28:813 1328 88f0 Report REPORT EVENT: {22EEDD35-6254-4F0B-8865-F221A48D37FF} 2014-08-25 09:28:23:817+0100 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0  Success Pre-Deployment
    Check Reporting client status.
    2014-08-25 09:28:28:813 1328 88f0 Report CWERReporter finishing event handling. (00000000)
    2014-08-25 09:29:01:003 1328 2c18 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-08-25 09:29:01:096 1328 2c18 Report CWERReporter finishing event handling. (00000000)
    2014-08-25 09:29:01:704 1328 2c18 Service *********
    2014-08-25 09:29:01:704 1328 2c18 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-08-25 09:29:01:704 1328 2c18 Service *************
    2014-08-25 09:29:02:382 1328 9cac Misc ===========  Logging initialized (build: 7.6.7600.320, tz: +0100)  ===========
    2014-08-25 09:29:02:383 1328 9cac Misc   = Process: C:\Windows\system32\svchost.exe
    2014-08-25 09:29:02:383 1328 9cac Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-08-25 09:29:02:382 1328 9cac Service *************
    2014-08-25 09:29:02:383 1328 9cac Service ** START **  Service: Service startup
    2014-08-25 09:29:02:383 1328 9cac Service *********
    2014-08-25 09:29:02:422 1328 9cac Agent   * WU client version 7.6.7600.320
    2014-08-25 09:29:02:422 1328 9cac Agent   * Base directory: C:\Windows\SoftwareDistribution
    2014-08-25 09:29:02:422 1328 9cac Agent   * Access type: No proxy
    2014-08-25 09:29:02:422 1328 9cac Agent   * Network state: Connected
    2014-08-25 09:29:33:789 1328 9efc Report CWERReporter::Init succeeded
    2014-08-25 09:29:33:789 1328 9efc Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-08-25 09:29:33:809 1328 9efc Agent   * Prerequisite roots succeeded.
    2014-08-25 09:29:33:813 1328 9efc Agent ***********  Agent: Initializing global settings cache  ***********
    2014-08-25 09:29:33:813 1328 9efc Agent   * WSUS server:
    http://sccm2012:8530
    2014-08-25 09:29:33:813 1328 9efc Agent   * WSUS status server:
    http://sccm2012:8530
    2014-08-25 09:29:33:813 1328 9efc Agent   * Target group: (Unassigned Computers)
    2014-08-25 09:29:33:813 1328 9efc Agent   * Windows Update access disabled: No
    2014-08-25 09:29:33:842 1328 9efc DnldMgr Download manager restoring 0 downloads
    2014-08-25 09:29:33:846 1328 9efc AU ###########  AU: Initializing Automatic Updates  ###########
    2014-08-25 09:29:33:847 1328 9efc AU   # WSUS server:
    http://sccm2012:8530
    2014-08-25 09:29:33:848 1328 9efc AU   # Detection frequency: 22
    2014-08-25 09:29:33:848 1328 9efc AU   # Approval type: Scheduled (Policy)
    2014-08-25 09:29:33:848 1328 9efc AU   # Scheduled install day/time: Every day at 3:00
    2014-08-25 09:29:33:848 1328 9efc AU   # Auto-install minor updates: Yes (User preference)
    2014-08-25 09:29:33:848 1328 9efc AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-08-25 09:29:33:848 1328 9efc AU   # Will display featured software notifications (User preference)
    2014-08-25 09:29:33:850 1328 9efc AU Setting AU scheduled install time to 2014-08-26 02:00:00
    2014-08-25 09:29:34:669 1328 9cac Report ***********  Report: Initializing static reporting data  ***********
    2014-08-25 09:29:34:669 1328 9cac Report   * OS Version = 6.1.7601.1.0.65792
    2014-08-25 09:29:34:669 1328 9cac Report   * OS Product Type = 0x00000030
    2014-08-25 09:29:34:679 1328 9cac Report   * Computer Brand = Hewlett-Packard
    2014-08-25 09:29:34:679 1328 9cac Report   * Computer Model = HP Compaq 8200 Elite CMT PC
    2014-08-25 09:29:34:681 1328 9cac Report   * Bios Revision = J01 v02.15
    2014-08-25 09:29:34:681 1328 9cac Report   * Bios Name = Default System BIOS
    2014-08-25 09:29:34:681 1328 9cac Report   * Bios Release Date = 2011-11-10T00:00:00
    2014-08-25 09:29:34:682 1328 9cac Report   * Locale ID = 6153
    2014-08-25 09:29:34:770 1328 9efc AU Successfully wrote event for AU health state:0
    2014-08-25 09:29:34:771 1328 9efc AU Initializing featured updates
    2014-08-25 09:29:34:772 1328 9efc AU Found 0 cached featured updates
    2014-08-25 09:29:34:772 1328 9efc AU Successfully wrote event for AU health state:0
    2014-08-25 09:29:34:773 1328 9efc AU Successfully wrote event for AU health state:0
    2014-08-25 09:29:34:773 1328 9efc AU AU finished delayed initialization
    2014-08-25 09:29:39:774 1328 9ed8 Report CWERReporter finishing event handling. (00000000)
    2014-08-25 09:29:42:391 1328 9efc AU Triggering AU detection through DetectNow API
    2014-08-25 09:29:42:391 1328 9efc AU Triggering Online detection (interactive)
    2014-08-25 09:29:42:391 1328 9cac AU #############
    2014-08-25 09:29:42:391 1328 9cac AU ## START ##  AU: Search for updates
    2014-08-25 09:29:42:391 1328 9cac AU #########
    2014-08-25 09:29:42:440 1328 9cac AU <<## SUBMITTED ## AU: Search for updates [CallId = {A408A720-49E6-4DB1-AD61-086D50DCACDF}]
    2014-08-25 09:29:42:440 1328 9ed8 Agent *************
    2014-08-25 09:29:42:440 1328 9ed8 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-08-25 09:29:42:440 1328 9ed8 Agent *********
    2014-08-25 09:29:42:440 1328 9ed8 Agent   * Online = Yes; Ignore download priority = No
    2014-08-25 09:29:42:440 1328 9ed8 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
    or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-08-25 09:29:42:440 1328 9ed8 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-08-25 09:29:42:440 1328 9ed8 Agent   * Search Scope = {Machine}
    2014-08-25 09:29:42:440 1328 9ed8 Setup Checking for agent SelfUpdate
    2014-08-25 09:29:42:464 1328 9ed8 Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2014-08-25 09:29:44:825 1328 9ed8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2014-08-25 09:29:44:927 1328 9ed8 Misc  Microsoft signed: NA
    2014-08-25 09:29:44:936 1328 9ed8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP5629.tmp with dwProvFlags 0x00000080:
    2014-08-25 09:29:45:042 1328 9ed8 Misc  Microsoft signed: NA
    2014-08-25 09:29:45:125 1328 9ed8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2014-08-25 09:29:45:129 1328 9ed8 Misc  Microsoft signed: NA
    2014-08-25 09:29:45:140 1328 9ed8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2014-08-25 09:29:45:144 1328 9ed8 Misc  Microsoft signed: NA
    2014-08-25 09:29:45:424 1328 9ed8 Setup Determining whether a new setup handler needs to be downloaded
    2014-08-25 09:29:45:424 1328 9ed8 Setup SelfUpdate handler is not found.  It will be downloaded
    2014-08-25 09:29:45:425 1328 9ed8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2014-08-25 09:29:45:427 1328 9ed8 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2014-08-25 09:29:45:427 1328 9ed8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2014-08-25 09:29:45:441 1328 9ed8 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2014-08-25 09:29:45:441 1328 9ed8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2014-08-25 09:29:45:461 1328 9ed8 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2014-08-25 09:29:45:461 1328 9ed8 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-08-25 09:29:47:333 1328 9ed8 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-08-25 09:29:47:333 1328 9ed8 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://sccm2012:8530/ClientWebService/client.asmx
    2014-08-25 09:30:45:148 1328 9ed8 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-08-25 09:30:45:148 1328 9ed8 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://sccm2012:8530/ClientWebService/client.asmx
    2014-08-25 09:30:46:111 1328 9ed8 Agent   * Found 0 updates and 88 categories in search; evaluated appl. rules of 1664 out of 2963 deployed entities
    2014-08-25 09:30:46:166 1328 9ed8 Agent *********
    2014-08-25 09:30:46:166 1328 9ed8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-08-25 09:30:46:166 1328 9ed8 Agent *************
    2014-08-25 09:30:46:189 1328 9dd8 AU >>##  RESUMED  ## AU: Search for updates [CallId = {A408A720-49E6-4DB1-AD61-086D50DCACDF}]
    2014-08-25 09:30:46:189 1328 9dd8 AU   # 0 updates detected
    2014-08-25 09:30:46:190 1328 9dd8 AU #########
    2014-08-25 09:30:46:190 1328 9dd8 AU ##  END  ##  AU: Search for updates [CallId = {A408A720-49E6-4DB1-AD61-086D50DCACDF}]
    2014-08-25 09:30:46:190 1328 9dd8 AU #############
    2014-08-25 09:30:46:190 1328 9dd8 AU Successfully wrote event for AU health state:0
    2014-08-25 09:30:46:190 1328 9dd8 AU Featured notifications is disabled.
    2014-08-25 09:30:46:190 1328 9dd8 AU AU setting next detection timeout to 2014-08-26 02:34:43
    2014-08-25 09:30:46:190 1328 9dd8 AU Setting AU scheduled install time to 2014-08-26 02:00:00
    2014-08-25 09:30:46:191 1328 9dd8 AU Successfully wrote event for AU health state:0
    2014-08-25 09:30:46:191 1328 9dd8 AU Successfully wrote event for AU health state:0
    2014-08-25 09:30:51:194 1328 9ed8 Report REPORT EVENT: {5D2061CD-53DE-4485-A7FE-F3D5C5A56D14} 2014-08-25 09:30:46:161+0100 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2014-08-25 09:30:51:194 1328 9ed8 Report REPORT EVENT: {B3107C31-2383-4E05-9666-735E6BB3376C} 2014-08-25 09:30:46:166+0100 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment
    Check Reporting client status.
    2014-08-25 09:30:51:194 1328 9ed8 Report CWERReporter finishing event handling. (00000000)
    2014-08-25 09:34:46:986 1328 9cac AU AU setting next sqm report timeout to 2014-08-26 08:34:46
    2014-08-25 09:48:15:146 1328 9cac AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-08-25 09:48:16:775 1328 9cac Report CWERReporter finishing event handling. (00000000)
    2014-08-25 09:48:16:818 1328 9cac Service *********
    2014-08-25 09:48:16:818 1328 9cac Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-08-25 09:48:16:818 1328 9cac Service *************
    2014-08-25 09:48:17:313 1328 a228 Misc ===========  Logging initialized (build: 7.6.7600.320, tz: +0100)  ===========
    2014-08-25 09:48:17:313 1328 a228 Misc   = Process: C:\Windows\system32\svchost.exe
    2014-08-25 09:48:17:313 1328 a228 Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-08-25 09:48:17:313 1328 a228 Service *************
    2014-08-25 09:48:17:313 1328 a228 Service ** START **  Service: Service startup
    2014-08-25 09:48:17:313 1328 a228 Service *********
    2014-08-25 09:48:17:335 1328 a228 Agent   * WU client version 7.6.7600.320
    2014-08-25 09:48:17:335 1328 a228 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2014-08-25 09:48:17:335 1328 a228 Agent   * Access type: No proxy
    2014-08-25 09:48:17:335 1328 a228 Agent   * Network state: Connected
    2014-08-25 09:49:02:380 1328 a228 Report CWERReporter::Init succeeded
    2014-08-25 09:49:02:380 1328 a228 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-08-25 09:49:02:381 1328 a228 Agent   * Prerequisite roots succeeded.
    2014-08-25 09:49:02:381 1328 a228 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-08-25 09:49:02:381 1328 a228 Agent   * WSUS server:
    http://sccm2012:8530
    2014-08-25 09:49:02:381 1328 a228 Agent   * WSUS status server:
    http://sccm2012:8530
    2014-08-25 09:49:02:381 1328 a228 Agent   * Target group: (Unassigned Computers)
    2014-08-25 09:49:02:381 1328 a228 Agent   * Windows Update access disabled: No
    2014-08-25 09:49:02:396 1328 a228 DnldMgr Download manager restoring 0 downloads
    2014-08-25 09:49:02:397 1328 a228 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-08-25 09:49:02:397 1328 a228 AU   # WSUS server:
    http://sccm2012:8530
    2014-08-25 09:49:02:397 1328 a228 AU   # Detection frequency: 22
    2014-08-25 09:49:02:397 1328 a228 AU   # Approval type: Scheduled (Policy)
    2014-08-25 09:49:02:397 1328 a228 AU   # Scheduled install day/time: Every day at 3:00
    2014-08-25 09:49:02:397 1328 a228 AU   # Auto-install minor updates: Yes (User preference)
    2014-08-25 09:49:02:397 1328 a228 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-08-25 09:49:02:397 1328 a228 AU   # Will display featured software notifications (User preference)
    2014-08-25 09:49:02:398 1328 a228 AU Setting AU scheduled install time to 2014-08-26 02:00:00
    2014-08-25 09:49:02:731 1328 a228 Report ***********  Report: Initializing static reporting data  ***********
    2014-08-25 09:49:02:731 1328 a228 Report   * OS Version = 6.1.7601.1.0.65792
    2014-08-25 09:49:02:731 1328 a228 Report   * OS Product Type = 0x00000030
    2014-08-25 09:49:02:737 1328 a228 Report   * Computer Brand = Hewlett-Packard
    2014-08-25 09:49:02:737 1328 a228 Report   * Computer Model = HP Compaq 8200 Elite CMT PC
    2014-08-25 09:49:02:738 1328 a228 Report   * Bios Revision = J01 v02.15
    2014-08-25 09:49:02:738 1328 a228 Report   * Bios Name = Default System BIOS
    2014-08-25 09:49:02:739 1328 a228 Report   * Bios Release Date = 2011-11-10T00:00:00
    2014-08-25 09:49:02:739 1328 a228 Report   * Locale ID = 6153
    2014-08-25 09:49:02:799 1328 a228 AU Successfully wrote event for AU health state:0
    2014-08-25 09:49:02:799 1328 a228 AU Initializing featured updates
    2014-08-25 09:49:02:799 1328 a228 AU Found 0 cached featured updates
    2014-08-25 09:49:02:800 1328 a228 AU Successfully wrote event for AU health state:0
    2014-08-25 09:49:02:800 1328 a228 AU Successfully wrote event for AU health state:0
    2014-08-25 09:49:02:800 1328 a228 AU AU finished delayed initialization
    2014-08-25 09:49:07:802 1328 8d90 Report CWERReporter finishing event handling. (00000000)
    2014-08-25 10:13:25:464 1328 a228 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-08-25 10:13:25:508 1328 a228 Report CWERReporter finishing event handling. (00000000)
    2014-08-25 10:13:25:654 1328 a228 Service *********
    2014-08-25 10:13:25:654 1328 a228 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-08-25 10:13:25:654 1328 a228 Service *************
    2014-08-25 10:13:26:952 1328 4f44 Misc ===========  Logging initialized (build: 7.6.7600.320, tz: +0100)  ===========
    2014-08-25 10:13:26:952 1328 4f44 Misc   = Process: C:\Windows\system32\svchost.exe
    2014-08-25 10:13:26:952 1328 4f44 Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-08-25 10:13:26:952 1328 4f44 Service *************
    2014-08-25 10:13:26:952 1328 4f44 Service ** START **  Service: Service startup
    2014-08-25 10:13:26:952 1328 4f44 Service *********
    2014-08-25 10:13:27:025 1328 4f44 Agent   * WU client version 7.6.7600.320
    2014-08-25 10:13:27:025 1328 4f44 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2014-08-25 10:13:27:025 1328 4f44 Agent   * Access type: No proxy
    2014-08-25 10:13:27:025 1328 4f44 Agent   * Network state: Connected
    2014-08-25 10:14:12:113 1328 4f44 Report CWERReporter::Init succeeded
    2014-08-25 10:14:12:113 1328 4f44 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-08-25 10:14:12:113 1328 4f44 Agent   * Prerequisite roots succeeded.
    2014-08-25 10:14:12:113 1328 4f44 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-08-25 10:14:12:113 1328 4f44 Agent   * WSUS server: <NULL>
    2014-08-25 10:14:12:113 1328 4f44 Agent   * WSUS status server: <NULL>
    2014-08-25 10:14:12:113 1328 4f44 Agent   * Target group: (Unassigned Computers)
    2014-08-25 10:14:12:113 1328 4f44 Agent   * Windows Update access disabled: No
    2014-08-25 10:14:12:113 1328 4f44 DnldMgr Download manager restoring 0 downloads
    2014-08-25 10:14:12:114 1328 4f44 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-08-25 10:14:12:114 1328 4f44 AU   # Approval type: Scheduled (User preference)
    2014-08-25 10:14:12:115 1328 4f44 AU   # Scheduled install day/time: Every day at 3:00
    2014-08-25 10:14:12:115 1328 4f44 AU   # Auto-install minor updates: Yes (User preference)
    2014-08-25 10:14:12:115 1328 4f44 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-08-25 10:14:12:115 1328 4f44 AU   # Will display featured software notifications (User preference)
    2014-08-25 10:14:12:115 1328 4f44 AU Setting AU scheduled install time to 2014-08-26 02:00:00
    2014-08-25 10:14:12:371 1328 4f44 Report ***********  Report: Initializing static reporting data  ***********
    2014-08-25 10:14:12:371 1328 4f44 Report   * OS Version = 6.1.7601.1.0.65792
    2014-08-25 10:14:12:371 1328 4f44 Report   * OS Product Type = 0x00000030
    2014-08-25 10:14:12:381 1328 4f44 Report   * Computer Brand = Hewlett-Packard
    2014-08-25 10:14:12:381 1328 4f44 Report   * Computer Model = HP Compaq 8200 Elite CMT PC
    2014-08-25 10:14:12:382 1328 4f44 Report   * Bios Revision = J01 v02.15
    2014-08-25 10:14:12:382 1328 4f44 Report   * Bios Name = Default System BIOS
    2014-08-25 10:14:12:382 1328 4f44 Report   * Bios Release Date = 2011-11-10T00:00:00
    2014-08-25 10:14:12:382 1328 4f44 Report   * Locale ID = 6153
    2014-08-25 10:14:12:496 1328 4f44 AU Successfully wrote event for AU health state:0
    2014-08-25 10:14:12:497 1328 4f44 AU Initializing featured updates
    2014-08-25 10:14:12:497 1328 4f44 AU Found 0 cached featured updates
    2014-08-25 10:14:12:497 1328 4f44 AU Successfully wrote event for AU health state:0
    2014-08-25 10:14:12:497 1328 4f44 AU Successfully wrote event for AU health state:0
    2014-08-25 10:14:12:497 1328 4f44 AU AU finished delayed initialization
    2014-08-25 10:14:12:498 1328 4f44 AU #############
    2014-08-25 10:14:12:498 1328 4f44 AU ## START ##  AU: Search for updates
    2014-08-25 10:14:12:498 1328 4f44 AU #########
    2014-08-25 10:14:12:564 1328 4f44 AU <<## SUBMITTED ## AU: Search for updates [CallId = {6BB38417-0601-472A-8E40-3AC101204669}]
    2014-08-25 10:14:12:564 1328 47f8 Agent *************
    2014-08-25 10:14:12:564 1328 47f8 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-08-25 10:14:12:564 1328 47f8 Agent *********
    2014-08-25 10:14:12:564 1328 47f8 Agent   * Online = No; Ignore download priority = No
    2014-08-25 10:14:12:564 1328 47f8 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
    or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-08-25 10:14:12:564 1328 47f8 Agent   * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
    2014-08-25 10:14:12:564 1328 47f8 Agent   * Search Scope = {Machine}
    2014-08-25 10:14:14:651 1328 47f8 Agent   * Found 0 updates and 6 categories in search; evaluated appl. rules of 29 out of 66 deployed entities
    2014-08-25 10:14:14:674 1328 47f8 Agent *********
    2014-08-25 10:14:14:674 1328 47f8 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-08-25 10:14:14:674 1328 47f8 Agent *************
    2014-08-25 10:14:14:674 1328 63d0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {6BB38417-0601-472A-8E40-3AC101204669}]
    2014-08-25 10:14:14:674 1328 63d0 AU   # 0 updates detected
    2014-08-25 10:14:14:674 1328 63d0 AU #########
    2014-08-25 10:14:14:674 1328 63d0 AU ##  END  ##  AU: Search for updates [CallId = {6BB38417-0601-472A-8E40-3AC101204669}]
    2014-08-25 10:14:14:674 1328 63d0 AU #############
    2014-08-25 10:14:14:674 1328 63d0 AU No featured updates notifications to show
    2014-08-25 10:14:14:675 1328 63d0 AU Setting AU scheduled install time to 2014-08-26 02:00:00
    2014-08-25 10:14:14:675 1328 63d0 AU Successfully wrote event for AU health state:0
    2014-08-25 10:14:14:675 1328 63d0 AU Successfully wrote event for AU health state:0
    2014-08-25 10:14:17:496 1328 47f8 Report REPORT EVENT: {FD2A1084-E566-42D0-8594-505AD2F32CCD} 2014-08-25 10:14:12:497+0100 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content
    Install Reboot completed.
    2014-08-25 10:14:17:503 1328 47f8 Report CWERReporter finishing event handling. (00000000)

    Hi Jesper,Thanks for that. I ran the detect now command as per above.
    I can access the URL: http://sccm2012:8530/selfupdate/wuident.cab
    Machine is still status Not yet reported.
    I ran reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    and it returns:
    C:\Users\lyn>reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
        TargetGroupEnabled    REG_DWORD    0x1
        TargetGroup    REG_SZ    computers
        WUServer    REG_SZ   
    http://sccm2012:8530
        WUStatusServer    REG_SZ   
    http://sccm2012:8530
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
    Regards,
    Niall

  • Cannot reinstall WSUS 3.0 sp2 fails at configuring database

    all -
    a few weeks ago the WSUS stopped working on a ts server.  according to lawrence garvin it cannot be installed on a ts server.  now i'm trying to install it back onto the sbs 2008 server.  it won't install.  when it gets to the configuring
    the db, it throws an error.  when i open the console i cannot connect to the server.  apparently, this is very common, but all the responses have been tried and still no success.
    here's the log.  it's now not installing the db.
    2014-03-03 10:01:10  Success   MWUSSetup          Validating pre-requisites...
    2014-03-03 10:01:11  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2014-03-03 10:01:11  Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
    2014-03-03 10:01:18  Success   MWUSSetup          Initializing installation details
    2014-03-03 10:01:18  Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
    2014-03-03 10:01:18  Success   MWUSSetup          Installing wYukon using ocsetup
    2014-03-03 10:01:18  Success   MWUSSetup          Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
    2014-03-03 10:01:42  Error     MWUSSetup          The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          ExecCmd failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error
    during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:07:11  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:08:53  Success   MWUSSetup          Validating pre-requisites...
    2014-03-03 10:08:53  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2014-03-03 10:08:53  Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
    2014-03-03 10:12:23  Success   MWUSSetup          Initializing installation details
    2014-03-03 10:12:23  Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
    2014-03-03 10:12:23  Success   MWUSSetup          Installing wYukon using ocsetup
    2014-03-03 10:12:23  Success   MWUSSetup          Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
    2014-03-03 10:12:33  Error     MWUSSetup          The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          ExecCmd failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error
    during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    Lee Feldman SMB Consultant

    according to the article i cannot complete steps 6 - 8 because it's an SBS 2k8 server.  here's what happens when i try to install it.
    Windows Server Update Services 3.0 SP2 could not install Windows Internal Database. For more information, see the Setup log "C:\Users\Admin\AppData\Local\Temp\2\WSUSSetup.log".
    2014-03-03 10:01:10  Success   MWUSSetup          Validating pre-requisites...
    2014-03-03 10:01:11  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2014-03-03 10:01:11  Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
    2014-03-03 10:01:18  Success   MWUSSetup          Initializing installation details
    2014-03-03 10:01:18  Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
    2014-03-03 10:01:18  Success   MWUSSetup          Installing wYukon using ocsetup
    2014-03-03 10:01:18  Success   MWUSSetup          Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
    2014-03-03 10:01:42  Error     MWUSSetup          The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          ExecCmd failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:01:42  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:07:11  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:08:53  Success   MWUSSetup          Validating pre-requisites...
    2014-03-03 10:08:53  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2014-03-03 10:08:53  Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
    2014-03-03 10:12:23  Success   MWUSSetup          Initializing installation details
    2014-03-03 10:12:23  Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
    2014-03-03 10:12:23  Success   MWUSSetup          Installing wYukon using ocsetup
    2014-03-03 10:12:23  Success   MWUSSetup          Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
    2014-03-03 10:12:33  Error     MWUSSetup          The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          ExecCmd failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:12:33  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2014-03-03 10:19:56  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    2014-03-05 05:10:47  Success   MWUSSetup          Validating pre-requisites...
    2014-03-05 05:10:47  Error     MWUSSetup          Failed to determine if an higher version of WSUS is installed. Assuming it is not... (Error 0x80070002: The system cannot find the file specified.)
    2014-03-05 05:10:47  Error     MWUSSetup          WSUS is outdated. But this will not block setup (Error 0x00000000: The operation completed successfully.)
    2014-03-05 05:10:55  Success   MWUSSetup          Initializing installation details
    2014-03-05 05:10:55  Success   MWUSSetup          Skipping Asp.Net install since not running on win2k3...
    2014-03-05 05:10:55  Success   MWUSSetup          Installing wYukon using ocsetup
    2014-03-05 05:10:55  Success   MWUSSetup          Installing Windows Internal database using ocsetup with command line as "ocsetup "WSSEE" /quiet /norestart"
    2014-03-05 05:11:36  Error     MWUSSetup          The process ocsetup "WSSEE" /quiet /norestart returned error: 0x643 (Error 0x80070643: Fatal error during installation.)
    2014-03-05 05:11:36  Error     MWUSSetup          ExecCmd failed (Error 0x80070643: Fatal error during installation.)
    2014-03-05 05:11:36  Error     MWUSSetup          Install Windows Internal database: Failed to execute "ocsetup "WSSEE" /quiet /norestart" (Error 0x80070643: Fatal error during installation.)
    2014-03-05 05:11:36  Error     MWUSSetup          CInstallDriver::PerformSetup: Installation of wYukon failed (Error 0x80070643: Fatal error during installation.)
    2014-03-05 05:11:36  Error     MWUSSetup          CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
    2014-03-05 05:12:17  Error     MWUSSetup          DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)
    Lee Feldman SMB Consultant

Maybe you are looking for