Update agent?

Hi there,
After upgrading the server to SP1 I want to update the agent version on all our clients
11.0.0.40909 to 11.1.0.10447
How is that accomplished and would it make a difference unless you run RHEL6? I mean the new version is perhaps only for rhel6

I tried to update the agent from http://serverort/zenworks-setup
but I guess its the old version of the agent
sles0222:/tmp # ./PreAgentPkg_AgentLinuxComplete.bin
Starting the installation...
Checking pre-requisites...
Error :Exiting the installation as this device already has ZENworks agent installed.
Cleaning up the installation files...
The ZENworks Adaptive Agent has been successfully installed.

Similar Messages

  • Windows Update Agent via WSUS

    Hi All,
    Is there a way to import the latest Windows Update Agent into WSUS and therefore all 3000 machines that connect to WSUS get the update?
    Reason this has cropped up is because I want to update all machines to IE9 from IE8. Have approved Internet Explorer 9 in WSUS. Some machines have updated ok. Others wont update and clicking on Check for updates (where it checks WSUS) tells me there are
    no updates to install. If I 'Check for Updates from Microsoft Online' it immediately tells me that the machine needs an update. The update that gets installed is Windows Update Agent 7.6.7600.320 which is fine except that means each user will have
    to download the update from MS Update and I want WSUS to do it like it does every other Critical and Important update. Does anyone know the KB number I should be looking for or what I need to import from the Catalogue into WSUS so the Update Agent is deployed
    to all machines. All machines are Windows 7 SP1 32bit. There must be a way otherwise machines are going to be stuck on IE8 and also not receive any future Win 7 updates from WSUS.
    I know IE8 is old and so is IE9 but due to various NHS systems out there some only support IE8 or 9. Tragic I know.
    Thanks
    Rich

    The proper way to distribute the latest WUA (.320) to the clients in a WSUS administered environment, is to update the WSUS server(s) with this update:
    An update to harden Windows Server Update Services
    then the clients WUA will be selfupdated when they connect to the WSUS server.
    Rolf Lidvall, Swedish Radio (Ltd)

  • [SCCM 2012 R2] Windows Update Agent do not scan correctly thus SCCM has bad reports

    Hi All,
    My colleagues reported that after manual download and installation of update Office 2010 SP2 ... SCCM still do not report as Installed:
    https://support.microsoft.com/en-us/kb/2687455
    KB2687455 update on SCCM is reported as:
    Update ID: 9c5e43a3-3ae9-434d-b105-a9d7902d5f9f
    Update Title: Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition
    Test Computer:
    After investigation I found out that Windows Update Agent (verbose logging) is reporting that this update is really not installed:  Agent Update {9C5E43A3-3AE9-434D-B105-A9D7902D5F9F} is deployed for scan, and is installable. It will be reported
    as installable.
    Update KB2687455 is shown in Programs and Features/Installed Updates as installed on this computer.
    Question:
    This update is MSP (not standard update) so it cannot be queried by win32_quickfixengineering WMI class. How to query all installed updates on system (registry, API, ...)?
    How WUA query ALL installed updates?
    Thank you in advance.
    Regards,

    Hi,
    You could check the version number. The version number of Office 2010 SP2 is greater than or equal to
    14.0.7015.1000.
    The script in the blog below could get List of installed Windows / office Updates.
    http://www.blackforce.co.uk/2013/01/27/get-list-of-installed-windows-office-updates-command-line
    The sample in the following article can be used to determine if a critical security update is installed on a computer. If the update isn't installed, the user can ensure that the update is downloaded and installed. The user can also ensure that
    they are notified about the status of the installation.
    https://msdn.microsoft.com/en-us/library/windows/desktop/aa387101(v=vs.85).aspx
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft
    does not guarantee the accuracy of this third-party contact information.
    Best Regards,
    Joyce
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Windows update requesting to install Windows Update Agent 7.6.7600.320

    I received this today when trying to manually scan for available updates via the windows update in control panel. It shows message as below. Seems that it will install the latest Windows Update Agent 7.6.7600.320. Will this machine able to get any patch
    deployed via SCCM if the WUA is not updated to the latest version?

    I can't say I've heard of any widespread issues with this version of the WUA so YMMV as always. If you do have an issue, you should contact CSS though.
    As for it being pushed automatically, that's correct and is no different than past WUA agent updates. It is considered an infrastructure update and is thus automatically installed via Windows Update or WSUS regardless of your client update settings unless
    you've actually disabled the WUA via group policy (not the service though) -- this includes ConfigMgr also because ConfigMgr does not in way pre-empt WSUS and leverages WSUS behind the scenes.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • [Windows 7] Windows Update Agent does not scan correctly

    Hi All,
    After manual installation of update Office 2010 SP2 (KB2687455) ... WUA does not report (KB2687455)
    as Installed:
    https://support.microsoft.com/en-us/kb/2687455
    KB2687455 update is reported as:
    Update ID: 9c5e43a3-3ae9-434d-b105-a9d7902d5f9f
    Update Title: Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition
    MSI Product: {90140000-0015-0409-0000-0000000FF1CE}
    MSI Patch: {D6A2CD7F-C90C-4B90-BBA7-2BADE2E08610}
    After investigation I found out that Windows Update Agent (verbose logging) is reporting this update as not installed: 
    EEHndlr   MSI PatchInfo for product {90140000-0015-0409-0000-0000000FF1CE} and patch {D6A2CD7F-C90C-4B90-BBA7-2BADE2E08610} returned 0x8007066f with state ''
    EEHndlr   MSI PatchInfo for product {90140000-0015-0409-0000-0000000FF1CE} and patch {D6A2CD7F-C90C-4B90-BBA7-2BADE2E08610} returned 'Unknown Patch'
    Perf, PatchStateForProduct, time, 4, patch, primary, {D6A2CD7F-C90C-4B90-BBA7-2BADE2E08610}, product, {90140000-0015-0409-0000-0000000FF1CE}, context, 112456208
    Agent Update {9C5E43A3-3AE9-434D-B105-A9D7902D5F9F} is deployed for scan, and is installable. It will be reported as
    installable.
    Update KB2687455 is shown in Programs and Features/Installed Updates as installed on this computer.
    Question:
    This update is MSP (not standard update) so it cannot be queried by win32_quickfixengineering WMI class. How to query all installed updates on system (registry, API, ...)?
    How WUA query ALL installed updates?
    How to fix this issue?
    Thank you in advance.
    Regards,

    Hi,
    You could check the version number. The version number of Office 2010 SP2 is greater than or equal to
    14.0.7015.1000.
    The script in the blog below could get List of installed Windows / office Updates.
    http://www.blackforce.co.uk/2013/01/27/get-list-of-installed-windows-office-updates-command-line
    The sample in the following article can be used to determine if a critical security update is installed on a computer. If the update isn't installed, the user can ensure that the update is downloaded and installed. The user can also ensure that
    they are notified about the status of the installation.
    https://msdn.microsoft.com/en-us/library/windows/desktop/aa387101(v=vs.85).aspx
    Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft
    does not guarantee the accuracy of this third-party contact information.
    Best Regards,
    Joyce
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Some computers download and install the two approved updates, others only download Windows Update Agent and not the approved updates.

    Some computers download and install the two approved updates, others only download Windows Update Agent and not the approved updates.

    UN-successful Windows Update Log:
    2014-05-07 09:33:56:180
    1036 e70
    Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========
    2014-05-07 09:33:56:220
    1036 e70
    Misc  = Process: C:\Windows\system32\svchost.exe
    2014-05-07 09:33:56:221
    1036 e70
    Misc  = Module: c:\windows\system32\wuaueng.dll
    2014-05-07 09:33:56:180
    1036 e70
    Service *************
    2014-05-07 09:33:56:221
    1036 e70
    Service ** START **  Service: Service startup
    2014-05-07 09:33:56:222
    1036 e70
    Service *********
    2014-05-07 09:33:56:544
    1036 e70
    Agent  * WU client version 7.6.7600.256
    2014-05-07 09:33:56:545
    1036 e70
    Agent  * Base directory: C:\Windows\SoftwareDistribution
    2014-05-07 09:33:56:546
    1036 e70
    Agent  * Access type: No proxy
    2014-05-07 09:33:56:547
    1036 e70
    Agent  * Network state: Connected
    2014-05-07 09:33:57:315
    1036 e70
    Setup Service restarting after SelfUpdate
    2014-05-07 09:33:57:545
    1036 e70
    Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-05-07 09:33:57:592
    1036 e70
    Report CWERReporter::Init succeeded
    2014-05-07 09:33:58:326
    1036 e70
    Report ***********  Report: Initializing static reporting data  ***********
    2014-05-07 09:33:58:376
    1036 e70
    Report  * OS Version = 6.1.7601.1.0.65792
    2014-05-07 09:33:58:376
    1036 e70
    Report  * OS Product Type = 0x00000030
    2014-05-07 09:33:58:394
    1036 e70
    Report  * Computer Brand = Hewlett-Packard
    2014-05-07 09:33:58:444
    1036 e70
    Report  * Computer Model = HP Compaq 4000 Pro SFF PC
    2014-05-07 09:33:58:455
    1036 e70
    Report  * Bios Revision = 786H7 v02.00
    2014-05-07 09:33:58:504
    1036 e70
    Report  * Bios Name = Default System BIOS
    2014-05-07 09:33:58:554
    1036 e70
    Report  * Bios Release Date = 2011-01-31T00:00:00
    2014-05-07 09:33:58:554
    1036 e70
    Report  * Locale ID = 1033
    2014-05-07 09:34:03:562
    1036 f08
    Report REPORT EVENT: {082D455B-6E51-4238-A997-1D27D9214A72}
    2014-05-07 09:33:58:565-0400 1
    199 101
    {0011B9ED-9189-4D58-BE25-FA2F13FC3D6C}
    1 240005
    SelfUpdate Success
    Content Install Installation successful and restart required for the following update: Windows Update Aux
    2014-05-07 09:34:03:614
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:34:42:049
    1036 e70
    Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-05-07 09:34:42:049
    1036 e70
    Agent ***********  Agent: Initializing global settings cache  ***********
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * WSUS server: http://csd26.csd.local:80
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * WSUS status server: http://csd26.csd.local:80
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * Target group: CO
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * Windows Update access disabled: No
    2014-05-07 09:34:42:063
    1036 e70
    DnldMgr Download manager restoring 0 downloads
    2014-05-07 09:34:42:089
    1036 e70
    AU ###########  AU: Initializing Automatic Updates  ###########
    2014-05-07 09:34:42:089
    1036 e70
    AU AU setting next detection timeout to 2014-05-07 13:34:42
    2014-05-07 09:34:42:090
    1036 e70
    AU AU setting next sqm report timeout to 2014-05-07 13:34:42
    2014-05-07 09:34:42:090
    1036 e70
    AU  # WSUS server: http://csd26.csd.local:80
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Detection frequency: 22
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Target group: CO
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Approval type: Scheduled (Policy)
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Scheduled install day/time: Every day at 3:00
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Auto-install minor updates: Yes (User preference)
    2014-05-07 09:34:42:105
    1036 e70
    AU Initializing featured updates
    2014-05-07 09:34:42:116
    1036 e70
    AU Found 0 cached featured updates
    2014-05-07 09:34:42:116
    1036 e70
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:34:42:117
    1036 e70
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:34:42:117
    1036 e70
    AU AU finished delayed initialization
    2014-05-07 09:34:42:117
    1036 e70
    AU AU setting next sqm report timeout to 2014-05-08 13:34:42
    2014-05-07 09:34:42:117
    1036 e70
    AU #############
    2014-05-07 09:34:42:117
    1036 e70
    AU ## START ##  AU: Search for updates
    2014-05-07 09:34:42:117
    1036 e70
    AU #########
    2014-05-07 09:34:42:291
    1036 e70
    AU <<## SUBMITTED ## AU: Search for updates [CallId = {5AA2F00A-8964-4543-A740-EC45C5FD5752}]
    2014-05-07 09:34:42:341
    1036 f08
    Agent *************
    2014-05-07 09:34:42:341
    1036 f08
    Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-05-07 09:34:42:341
    1036 f08
    Agent *********
    2014-05-07 09:34:42:341
    1036 f08
    Agent  * Online = Yes; Ignore download priority = No
    2014-05-07 09:34:42:341
    1036 f08
    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-05-07 09:34:42:341
    1036 f08
    Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-05-07 09:34:42:341
    1036 f08
    Agent  * Search Scope = {Machine}
    2014-05-07 09:34:42:341
    1036 f08
    Setup Checking for agent SelfUpdate
    2014-05-07 09:34:42:342
    1036 f08
    Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-05-07 09:34:42:349
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-05-07 09:34:42:392
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:669
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-05-07 09:34:44:676
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:754
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-05-07 09:34:44:777
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:781
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-05-07 09:34:44:788
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:837
    1036 f08
    Setup Determining whether a new setup handler needs to be downloaded
    2014-05-07 09:34:44:855
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2014-05-07 09:34:44:862
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:862
    1036 f08
    Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
    2014-05-07 09:34:44:862
    1036 f08
    Setup WARNING: Trust verification failed for WuSetupV.exe. It will be deleted and downloaded, error = 0x800B0001
    2014-05-07 09:34:44:863
    1036 f08
    Setup SelfUpdate handler update required: Current version: 7.6.7600.256, required version: 7.6.7600.256
    2014-05-07 09:34:44:873
    1036 f08
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-05-07 09:34:44:932
    1036 f08
    Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-05-07 09:34:44:933
    1036 f08
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-05-07 09:34:45:048
    1036 f08
    Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-05-07 09:34:45:048
    1036 f08
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-05-07 09:34:45:234
    1036 f08
    Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-05-07 09:34:45:235
    1036 f08
    Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-05-07 09:34:48:415
    1036 f08
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-05-07 09:34:48:415
    1036 f08
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://csd26.csd.local:80/ClientWebService/client.asmx
    2014-05-07 09:34:48:424
    1036 f08
    PT WARNING: Cached cookie has expired or new PID is available
    2014-05-07 09:34:48:424
    1036 f08
    PT Initializing simple targeting cookie, clientId = 97287ab2-5824-44d2-bf93-8a98da659f77, target group = CO, DNS name = c18714.csd.local
    2014-05-07 09:34:48:424
    1036 f08
    PT  Server URL = http://csd26.csd.local:80/SimpleAuthWebService/SimpleAuth.asmx
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING: SOAP Fault: 0x00012c
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     faultstring:Fault occurred
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     ErrorCode:ConfigChanged(2)
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     Message:(null)
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     ID:cb5babad-3a1d-4e6b-946e-736ed4746e3f
    2014-05-07 09:34:48:464
    1036 f08
    PT WARNING: Cached cookie has expired or new PID is available
    2014-05-07 09:34:48:464
    1036 f08
    PT Initializing simple targeting cookie, clientId = 97287ab2-5824-44d2-bf93-8a98da659f77, target group = CO, DNS name = c18714.csd.local
    2014-05-07 09:34:48:464
    1036 f08
    PT  Server URL = http://csd26.csd.local:80/SimpleAuthWebService/SimpleAuth.asmx
    2014-05-07 09:35:06:497
    1036 e70
    AU Forced install timer expired for scheduled install
    2014-05-07 09:35:06:497
    1036 e70
    AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2014-05-07 09:35:06:497
    1036 e70
    AU Setting AU scheduled install time to 2014-05-08 07:00:00
    2014-05-07 09:35:06:498
    1036 e70
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:14:236
    1036 f08
    PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-05-07 09:35:14:236
    1036 f08
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://csd26.csd.local:80/ClientWebService/client.asmx
    2014-05-07 09:35:20:118
    1036 f08
    Agent  * Found 0 updates and 79 categories in search; evaluated appl. rules of 859 out of 1494 deployed entities
    2014-05-07 09:35:20:194
    1036 f08
    Agent *********
    2014-05-07 09:35:20:194
    1036 f08
    Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-05-07 09:35:20:194
    1036 f08
    Agent *************
    2014-05-07 09:35:20:209
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:35:20:209
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:35:20:209
    1036 bb8
    AU >>##  RESUMED  ## AU: Search for updates [CallId = {5AA2F00A-8964-4543-A740-EC45C5FD5752}]
    2014-05-07 09:35:20:209
    1036 bb8
    AU  # 0 updates detected
    2014-05-07 09:35:20:209
    1036 bb8
    AU #########
    2014-05-07 09:35:20:209
    1036 bb8
    AU ##  END  ##  AU: Search for updates [CallId = {5AA2F00A-8964-4543-A740-EC45C5FD5752}]
    2014-05-07 09:35:20:209
    1036 bb8
    AU #############
    2014-05-07 09:35:20:210
    1036 bb8
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:20:210
    1036 bb8
    AU Featured notifications is disabled.
    2014-05-07 09:35:20:211
    1036 bb8
    AU AU setting next detection timeout to 2014-05-08 11:19:46
    2014-05-07 09:35:20:211
    1036 bb8
    AU Setting AU scheduled install time to 2014-05-08 07:00:00
    2014-05-07 09:35:20:212
    1036 bb8
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:20:212
    1036 bb8
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:25:183
    1036 f08
    Report REPORT EVENT: {C1B39107-F517-4477-AAE3-9B1F1D6002BF}
    2014-05-07 09:35:20:193-0400 1
    147 101
    {00000000-0000-0000-0000-000000000000}
    0 0 AutomaticUpdates
    Success Software Synchronization
    Windows Update Client successfully detected 0 updates.
    2014-05-07 09:35:25:183
    1036 f08
    Report REPORT EVENT: {669B9537-BB71-4190-BA58-A97F725AE4D8}
    2014-05-07 09:35:20:194-0400 1
    156 101
    {00000000-0000-0000-0000-000000000000}
    0 0 AutomaticUpdates
    Success Pre-Deployment Check
    Reporting client status.
    2014-05-07 09:35:25:184
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:37:32:440
    1036 f08
    Report Uploading 3 events using cached cookie, reporting URL = http://csd26.csd.local:80/ReportingWebService/ReportingWebService.asmx
    2014-05-07 09:37:32:454
    1036 f08
    Report Reporter successfully uploaded 3 events.

  • MBSA Windows Update Agent installation

    I'm implementing MBSA on our domain.  I've worked through the various firewall issues, etc.  Next I received a Security Update Scan Result that "Computer has an older version of the client and security database demands a newer
    version. Current version is and minmum required version is ."  This is pasted directly from the screen.  It appears information is missing from the message.
    Based on research of the message, I reran the scan with the "Configure computers for Microsoft Update and scanning prerequisites" option selected.  Then I get the result "Windows Update Agent installation succeeded.Restart
    the target computer to have Windows Update Agent updated completely."  Scanning the computer after a restart just repeats the same results.  Looking in the WindowsUpdate.log on the target computer, there are messages stating that 3
    CBS packages were evaluated and that each is not applicable.  "WUESTUP has finished.  Exit code is 0.  Reboot is NOT needed."  I have checked and the
    wuaueng.dll version is 7.6.7600.256, which I believe is the latest.
    I have seen this result on multiple Windows 7 computers I have tested.  None have worked so far.  What is causing MBSA to report one thing and the target to indicate something else?
    Ken Kemp Eddy County, NM IT

    At this point, no.  Since I didn't turn up an answer here, I've had to set this aside for more pressing matters.  I hope to get back to it at some point soon.
    If you are fortunate enough to find an answer, please be sure to share it here.
    Ken Kemp Eddy County, NM IT

  • Intermittent Scan issues for Update Agent

    I am having an issue with SUP/WSUS that I am hoping someone can point me on the right direction on..
    The environment is:
    SCCM 2012 R2 Primary Site Server on Server 2012 R2 Update
    SQL 2012 SP1 on Server 2012 R2 Update (standalone server) that houses the SCCM DB and the WSUS DB.  
    Software Update Point is on Server 2012 R2 Update (standalone) with WSUS roll installed. WSUS is configured for SSL (with "requires ssl" checked on the role) and using port 8531.
    No issues with the SUP install.  The SUP is synchronizing just fine with Microsoft and I am able manage update objects in the SCCM Admin console (create update groups, ADR's, etc.)  
    WSUSCtrl.log:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Checking runtime v2.0.50727... SMS_WSUS_CONTROL_MANAGER
    5/27/2014 2:16:03 PM 3304 (0x0CE8)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Checking runtime v4.0.30319... SMS_WSUS_CONTROL_MANAGER
    5/27/2014 2:16:03 PM 3304 (0x0CE8)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Supported WSUS version found SMS_WSUS_CONTROL_MANAGER
    5/27/2014 2:16:03 PM 3304 (0x0CE8)
    Attempting connection to local WSUS server
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Successfully connected to local WSUS server
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    No changes - local WSUS Server Proxy settings are correctly configured as Proxy Name  and Proxy Port 80
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Attempting connection to local WSUS server
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Successfully connected to local WSUS server
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    There are no unhealthy WSUS Server components on WSUS Server SERVER.SUBDOMAIN.DOMAIN.ORG
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    Successfully checked database connection on WSUS server SERVER.SUBDOMAIN.DOMAIN.ORG
    SMS_WSUS_CONTROL_MANAGER 5/27/2014 2:16:03 PM
    3304 (0x0CE8)
    The clients are getting the local policy pointing it to the correct URL.  This is also verified in the log:
    LocationServices.log:
    Current AD site of machine is EWJ LocationServices
    5/27/2014 1:45:41 PM 4236 (0x108C)
    Created and Sent Location Request '{3ABC15E0-70D3-4AE6-991C-B6BAF165C808}' for package {729742E6-9B66-4516-8A69-8569560D88C7}
    LocationServices 5/27/2014 1:45:41 PM
    4236 (0x108C)
    Calling back with the following WSUS locations
    LocationServices 5/27/2014 1:45:41 PM
    4236 (0x108C)
    WSUS Path='https://server.subdomain.domain.org:8531', Server='server.subdomain.domain.org', Version='10'
    LocationServices 5/27/2014 1:45:41 PM
    4236 (0x108C)
    Calling back with locations for WSUS request {3ABC15E0-70D3-4AE6-991C-B6BAF165C808}
    LocationServices 5/27/2014 1:45:41 PM
    4236 (0x108C)
    The issue comes into play in the fact that what appears to be about 85-90% of the time, the client scan cycle fails with error 0x80244004.  This is both Windows 7 x86/64 Pro and Windows XP SP3.  The error translates to:
    Same as SOAPCLIENT_CONNECT_ERROR - SOAP client failed to connect to the server.
    Source: Windows Update Agent
    The REALLY bizarre thing is that the OS's are inverted on their failure rates.  Win 7 fails 85-90% of the time, where as Win XP succeeds 85-90% of the time.
    We completely rebuilt the SUP Server (including OS and reconfigured it again for SSL) and alas the issue remains.
    Here's some snippets from the logs files from a machine when it fails:
    ScanAgent.log
    Message received: '<?xml version='1.0' ?>
    <UpdateSourceMessage MessageType='ScanByUpdateSource'>
    <ForceScan>TRUE</ForceScan>
    <UpdateSourceIDs>
    <ID>{729742E6-9B66-4516-8A69-8569560D88C7}
    </ID>
    </UpdateSourceIDs>
    </UpdateSourceMessage>'
    ScanAgent
    5/27/2014 1:45:41 PM 4236 (0x108C)
    *****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a,  WSUSLocationTimeout = 604800
    ScanAgent 5/27/2014 1:45:41 PM
    4236 (0x108C)
    Sources are current, but Invalid. TTL is also invalid.
    ScanAgent 5/27/2014 1:45:41 PM
    4236 (0x108C)
    ScanJob({DDFF8212-94D4-4BDC-8A47-41E203F6AD79}): - - - - - -Locations requested for ScanJobID={DDFF8212-94D4-4BDC-8A47-41E203F6AD79} (LocationRequestID={3ABC15E0-70D3-4AE6-991C-B6BAF165C808}), will process the scan request once locations are available.
    ScanAgent 5/27/2014 1:45:41 PM
    4236 (0x108C)
    *****WSUSLocationUpdate received for location request guid={3ABC15E0-70D3-4AE6-991C-B6BAF165C808}
    ScanAgent 5/27/2014 1:45:41 PM
    4236 (0x108C)
    Sources are current, but Invalid. TTL is also invalid.
    ScanAgent 5/27/2014 1:45:41 PM
    2216 (0x08A8)
    ScanJob({DDFF8212-94D4-4BDC-8A47-41E203F6AD79}): CScanJob::OnScanComplete -Scan Failed with Error=0x80244004
    ScanAgent 5/27/2014 1:45:44 PM
    4236 (0x108C)
    ScanJob({DDFF8212-94D4-4BDC-8A47-41E203F6AD79}): CScanJob::ScheduleScanRetry- ScanRetry Timer task successfully scheduled. Will wake up in next 1800 seconds
    ScanAgent 5/27/2014 1:45:44 PM
    4236 (0x108C)
    ScanJob({DDFF8212-94D4-4BDC-8A47-41E203F6AD79}): CScanJob::OnScanComplete - Scan Retry successfully scheduled
    ScanAgent 5/27/2014 1:45:44 PM
    4236 (0x108C)
    ScanJob({DDFF8212-94D4-4BDC-8A47-41E203F6AD79}): CScanJobManager::OnScanComplete- Scan has failed, scan request will be pending for scan retry cycle.
    ScanAgent 5/27/2014 1:45:44 PM
    4236 (0x108C)
    CScanAgent::ScanCompleteCallback - failed at OnScanComplete with error=0x87d00631
    ScanAgent 5/27/2014 1:45:44 PM
    4236 (0x108C)
    WindowsUpdate.log:
    2014-05-27 13:45:41:482
    2956 8a8
    COMAPI -------------
    2014-05-27 13:45:41:482
    2956 8a8
    COMAPI -- START --  COMAPI: Search [ClientId = CcmExec]
    2014-05-27 13:45:41:482
    2956 8a8
    COMAPI ---------
    2014-05-27 13:45:41:497
    936 ed4
    Agent *************
    2014-05-27 13:45:41:497
    936 ed4
    Agent ** START **  Agent: Finding updates [CallerId = CcmExec]
    2014-05-27 13:45:41:497
    936 ed4
    Agent *********
    2014-05-27 13:45:41:497
    936 ed4
    Agent  * Include potentially superseded updates
    2014-05-27 13:45:41:497
    936 ed4
    Agent  * Online = Yes; Ignore download priority = Yes
    2014-05-27 13:45:41:497
    936 ed4
    Agent  * Criteria = "(DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')"
    2014-05-27 13:45:41:497
    936 ed4
    Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-05-27 13:45:41:497
    936 ed4
    Agent  * Search Scope = {Machine}
    2014-05-27 13:45:41:497
    2956 8a8
    COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = CcmExec]
    2014-05-27 13:45:44:025
    936 ed4
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-05-27 13:45:44:025
    936 ed4
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = https://server.subdomain.domain::8531/ClientWebService/client.asmx
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: Cached cookie has expired or new PID is available
    2014-05-27 13:45:44:056
    936 ed4
    PT Initializing simple targeting cookie, clientId = cf0c5d2d-2a04-41a7-8a1b-4182de886397, target group = , DNS name = sccmtstw7x641.subdomain.domain:
    2014-05-27 13:45:44:056
    936 ed4
    PT  Server URL = https://server.subdomain.domain:8531/SimpleAuthWebService/SimpleAuth.asmx
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: GetAuthorizationCookie failure, error = 0x80244004, soap client error = 4, soap error code = 0, HTTP status code = 200
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: PopulateAuthCookies failed: 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: RefreshCookie failed: 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: RefreshPTState failed: 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: Sync of Updates: 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    PT WARNING: SyncServerUpdatesInternal failed: 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    Agent  * WARNING: Failed to synchronize, error = 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    Agent  * WARNING: Exit code = 0x80244004
    2014-05-27 13:45:44:056
    936 ed4
    Agent *********
    2014-05-27 13:45:44:056
    936 ed4
    Agent **  END  **  Agent: Finding updates [CallerId = CcmExec]
    2014-05-27 13:45:44:056
    936 ed4
    Agent *************
    2014-05-27 13:45:44:056
    936 ed4
    Agent WARNING: WU client failed Searching for update with error 0x80244004
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = CcmExec]
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI  - Updates found = 0
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI  - WARNING: Exit code = 0x00000000, Result code = 0x80244004
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI ---------
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI --  END  --  COMAPI: Search [ClientId = CcmExec]
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI -------------
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI WARNING: Operation failed due to earlier error, hr=80244004
    2014-05-27 13:45:44:071
    2956 8a8
    COMAPI FATAL: Unable to complete asynchronous search. (hr=80244004)
    Log file for contrast on a client when it works:
    ScanAgent.log
    Message received: '<?xml version='1.0' ?>
    <UpdateSourceMessage MessageType='ScanByUpdateSource'>
    <ForceScan>TRUE</ForceScan>
    <UpdateSourceIDs>
    <ID>{729742E6-9B66-4516-8A69-8569560D88C7}
    </ID>
    </UpdateSourceIDs>
    </UpdateSourceMessage>'
    ScanAgent
    5/27/2014 1:43:20 PM 4052 (0x0FD4)
    *****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a,  WSUSLocationTimeout = 604800
    ScanAgent 5/27/2014 1:43:20 PM
    4052 (0x0FD4)
    Sources are current and valid. TTLs are however, invalid.
    ScanAgent 5/27/2014 1:43:20 PM
    4052 (0x0FD4)
    ScanJob({1BF68613-35BB-4627-A3F3-FCA455547578}): - - - - - -Locations requested for ScanJobID={1BF68613-35BB-4627-A3F3-FCA455547578} (LocationRequestID={F6F11712-31EA-49BF-AD63-FF3FEF1BA29C}), will process the scan request once locations are available.
    ScanAgent 5/27/2014 1:43:20 PM
    4052 (0x0FD4)
    *****WSUSLocationUpdate received for location request guid={F6F11712-31EA-49BF-AD63-FF3FEF1BA29C}
    ScanAgent 5/27/2014 1:43:20 PM
    3648 (0x0E40)
    Sources are current and valid. TTLs are however, invalid.
    ScanAgent 5/27/2014 1:43:20 PM
    4052 (0x0FD4)
    ScanJob({1BF68613-35BB-4627-A3F3-FCA455547578}): Performing Full Scan.
    ScanAgent 5/27/2014 1:43:20 PM
    4052 (0x0FD4)
    ScanJob({1BF68613-35BB-4627-A3F3-FCA455547578}): Scan Succeeded, Resetting Source to Current and TTLs to Valid
    ScanAgent 5/27/2014 1:43:35 PM
    3648 (0x0E40)
    ScanJob({1BF68613-35BB-4627-A3F3-FCA455547578}): CScanJob::OnScanComplete - Scan completed successfully, ScanType=1
    ScanAgent 5/27/2014 1:43:35 PM
    3648 (0x0E40)
    ScanJob({1BF68613-35BB-4627-A3F3-FCA455547578}): CScanJobManager::OnScanComplete -ScanJob is completed.
    ScanAgent 5/27/2014 1:43:35 PM
    3648 (0x0E40)
    ScanJob({1BF68613-35BB-4627-A3F3-FCA455547578}): CScanJobManager::OnScanComplete - Reporting Scan request complete to clients...
    ScanAgent 5/27/2014 1:43:35 PM
    3648 (0x0E40)
    - - Calling back to client on Scan request complete...
    ScanAgent 5/27/2014 1:43:35 PM
    3648 (0x0E40)
    CScanAgent::ScanComplete- Scan completion received.
    ScanAgent 5/27/2014 1:43:35 PM
    3648 (0x0E40)
    I have verified there are no proxy settings on any of these devices by running "Netsh winhttp show proxy"
    Current WinHTTP proxy settings:
        Direct access (no proxy server).
    Firewall is OFF on both clients and servers.  There are no WU GPO settings applied.
    Anyone have any clues on where to look next?  I have been scouring the internet for a couple of days now and seems that all roads with this type of error leads back to a proxy issue, but since no proxy's are in play here, hasn't been of much help.  Still
    digging through stuff but if anyone has any pointers on where to look next it would much appreciated!
    Thanks,

    Found this Technet article: http://social.technet.microsoft.com/Forums/ru-RU/a1c81d16-d5d0-4367-bae6-3338aab0633f/client-updates-failing-windowsupdatelog-0x80244004?forum=configmanagersecurity
    I ran a Wireshark trace and received the exact same error on my client.  I have sent this over to the client to take a closer look.  Fingers crossed that this is the issue as it should be a simple fix.  *fingers crossed*

  • Whats the best way to apply office updates during OSD task sequence with Software Update Agent disabled?

    I am trying to update office via the SCCM 2012 R2 OSD task sequence. I know offline updating only updates the core components in the WIM and I'm trying to figure out how to add office updates as well. I am aware of using powershell to try and kick off
    a WU scan as seen here:
    http://myitforum.com/myitforumwp/2012/01/24/use-powershell-commands-to-assist-with-patching-during-sccm-image-build/
    But the kicker is we don't use SCCM to update the workstations (Solo WSUS install). Is there a way to do this (maybe set the client in the TS to switch on SUP, then off again when it goes off into production) rather than have to build a new image every month?

    You could use the ZTI_WindowsUpdates.wsf script from MDT.
    http://scriptimus.wordpress.com/2012/03/22/mdt-2012-automating-updates-in-lite-touch-deployments/
    How does it work?
    The task sequence steps run a script called ZTIWindowsUpdate.wsf. The script uses the
    Windows Update Agent API to manage the downloading and installation of updates. All audit information is written to the
    ZTIWindowsUpdate.log file. If you find any unusual error codes in your log returned from the API (although I never have)  you can compare the codes
    here. The script will also check and update the
    Windows Update Agent(WUA) as needed at the start.
    In its default state, the ZTIWindowsUpdate.wsf script will connect to Microsoft Update then search for and download all available updates including Security Patches, Drivers, Browser Updates and Service Packs. This is essentially the same
    as opening the GUI and selecting check for updates.
    Daniel Ratliff | http://www.PotentEngineer.com

  • Best practices for updating agents

    We're getting ready to do our first system-wide update of agents to fix a critical bug. Our summer vacation is just ending, and teachers and students will be coming back very soon and turning on our Windows 7 computers for the first time in many weeks, although they won't all be turned on the same day. When they are turned on they will be attempting to get various updates, in particular Windows updates, but also Flash Player and Adobe Reader. I need to update the agents as quickly as possible, but I'm concerned about the possibility of the agent update conflicting with another update, especially Windows updates. Isn't it possible that Windows Update could restart a computer while the agent update is happening (or the other way around), leaving the machine in an unstable or unusable state? What are the best practices for dealing with this? I considered the possibility of deploying the agent to a dynamic workstation group whose members all have a certain file or files that indicate that they have already received the latest Windows updates. However, I can't see how to create a dynamic group based on such criteria.
    So far I have only updated a few devices at a time using "Deploy System Updates to Selected Devices in the Management Zone". When those updates are done I cancel that deployment because that's the only option I can find that does anything. If you can offer general advice for a better strategy of updating agents I'd appreciate that. Specifically, how would you push an agent update to several hundred computers that will be turned on sometime over the next two weeks?
    Thanks very much.

    Originally Posted by jcw_av
    We're getting ready to do our first system-wide update of agents to fix a critical bug. Our summer vacation is just ending, and teachers and students will be coming back very soon and turning on our Windows 7 computers for the first time in many weeks, although they won't all be turned on the same day. When they are turned on they will be attempting to get various updates, in particular Windows updates, but also Flash Player and Adobe Reader. I need to update the agents as quickly as possible, but I'm concerned about the possibility of the agent update conflicting with another update, especially Windows updates. Isn't it possible that Windows Update could restart a computer while the agent update is happening (or the other way around), leaving the machine in an unstable or unusable state? What are the best practices for dealing with this? I considered the possibility of deploying the agent to a dynamic workstation group whose members all have a certain file or files that indicate that they have already received the latest Windows updates. However, I can't see how to create a dynamic group based on such criteria.
    So far I have only updated a few devices at a time using "Deploy System Updates to Selected Devices in the Management Zone". When those updates are done I cancel that deployment because that's the only option I can find that does anything. If you can offer general advice for a better strategy of updating agents I'd appreciate that. Specifically, how would you push an agent update to several hundred computers that will be turned on sometime over the next two weeks?
    Thanks very much.
    To be honest, you have to work around your other deploys, etc. The ZCM agent isn't "aware" of other deploys going on. For example, ZPM doesn't care that you're doing Bundles at the same time (you'll get errors in the logs about the fact that only one MSI can run at a time, for example). ZPM usually recovers and picks up where it left off.
    Bundles on the other hand, with System Update, are not so forgiving. Especially if you have the agents prior to 11.2.4 MU1 (cache corruption errors).
    We usually:
    a) Halt all software rollouts/patching as best we can
    b) Our software deploys (bundles) are on event: user login Typically the system update is on Device Refresh, OR scheduled time, and are device associated.
    IF possible, I'd suggest that you use WOL, system update and voila.
    Or, if no WOL available, then tell your users to leave their pc turned on (doesn't have to be logged in), on X night, and setup your system updates for that night, with the auto-reboot enabled. That worked well
    But otherwise the 3 components of ZCM (Bundles, ZPM, System Update) don't know/care about each other, AFAIK.
    --Kevin

  • Update agent in workgroup server

    Hi,
    I have DPM server and two client servers to backup. all servers in workgroup.
    I installed the agents manually and attached the DPM server.
    The DPM Server see the clients, but when I'm going to DPM console "Management -> Agents" I can see "Agent status OK" and "Agents Updates > Update available" when I click  "Update available" I get an Error
    message that I need to update manually, need to go from the client server to folder "C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\ProtectionAgents\RA\4.2.1205.0\amd64" on DPM server and run the installation.
    when I'm doing it from the client server I get a massage that this is the same agent version, but the " Update available" massage is still shown in the DPM console.
    need help for this issue 
    thanks,

    Hi,
    You need to install the agent from under the "C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Agents\RA\4.2.1xxx.0\amd64 folder.  That is the location for updated agents from update rollups.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • Windows Update Error 800B0109 after Windows Update Agent 7.6.7600.320 Installed

    Hi, I have this error message when running windows update, it happened after Windows Update Agent 7.6.7600.320 installed.
    Any idea how to resolve this?
    Thank you.

    Hi，
    Please make sure that your antivirus application does not scan the files in the
    %windir% \SoftwareDistribution directory on any computer on which Windows Update Agent is installed.
    You can also temporarily turn off the antivirus application and check the result.
    Or run the following commands, and press Enter after each command:
    Net stop wuauserv
    cd %systemroot%
    Ren SoftwareDistribution SoftwareDistribution.old
    Net start wuauserv
    Try to install updates again.
    Yolanda Zhu
    TechNet Community Support
    I tried the commands as well, still prompting the same error.
    Thanks

  • SCCM Software Update Agent remains disabled

    Dear All,
    on single notebooks the Software Updates Agent remains disabled even if the Client Settings policy is set to enale the agent as in the attached images:
    Even though if I set e.g. the remote tool agent as disabled, the agent becomes disabled on the same notebooks, where the SUA does not change state. Therefore a communication error is excluded.
    Does anyone know where to look after more information about this issue and eventually how to solve it?
    CMClient Version on all Clients: 5.00.7804.1000
    OS on the Client: Win 8 or Win 8.1 U1
    SCCM Version on the Server: System Center Configuration manager 2012 SP 1 5.0.7804.1500
    Policy:
    Best,
    Pictop

    Hi t.c.rich,
    Thank you for the response.
    Here the log file.
    <![LOG[Successfully completed scan.]LOG]!><time="12:09:30.983-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="3864" file="cwuahandler.cpp:3557">
    <![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="12:51:54.966-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="sourcemanager.cpp:1232">
    <![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="12:51:55.045-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="sourcemanager.cpp:936">
    <![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="12:51:55.064-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="sourcemanager.cpp:1265">
    <![LOG[Scan results will include all superseded updates.]LOG]!><time="12:51:55.076-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="cwuahandler.cpp:2913">
    <![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="12:51:55.076-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="cwuahandler.cpp:2916">
    <![LOG[Async searching of updates using WUAgent started.]LOG]!><time="12:51:56.701-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4828" file="cwuahandler.cpp:579">
    <![LOG[Async searching completed.]LOG]!><time="12:52:18.732-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="336" file="cwuahandler.cpp:2068">
    <![LOG[Successfully completed scan.]LOG]!><time="12:52:19.513-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="1880" file="cwuahandler.cpp:3557">
    <![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="12:52:19.748-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="sourcemanager.cpp:1232">
    <![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="12:52:19.748-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="sourcemanager.cpp:936">
    <![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="sourcemanager.cpp:1265">
    <![LOG[Scan results will include all superseded updates.]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:2913">
    <![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:2916">
    <![LOG[Async searching of updates using WUAgent started.]LOG]!><time="12:52:19.763-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:579">
    <![LOG[Async searching completed.]LOG]!><time="12:52:38.998-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="4768" file="cwuahandler.cpp:2068">
    <![LOG[Successfully completed scan.]LOG]!><time="12:52:39.888-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="2608" file="cwuahandler.cpp:3557">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="13:38:54.626-120" date="05-29-2014" component="WUAHandler" context="" type="1" thread="3660" file="cwuahandler.cpp:2527">
    <![LOG[Removed Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="10:28:37.696-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="488" file="sourcemanager.cpp:1338">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="10:28:39.508-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="488" file="cwuahandler.cpp:2527">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="10:29:04.622-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="2368" file="cwuahandler.cpp:2527">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="10:42:29.805-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="3092" file="cwuahandler.cpp:2527">
    <![LOG[Tried to remove an update source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) that does not exist.]LOG]!><time="10:45:25.357-120" date="10-10-2014" component="WUAHandler" context="" type="2" thread="3944" file="sourcemanager.cpp:1315">
    <![LOG[Failed to Remove Update Source from WUAgent ({543A840D-5C46-4239-ADB9-17E8FC7359E5}). Error = 0x87d00691.]LOG]!><time="10:45:25.357-120" date="10-10-2014" component="WUAHandler" context="" type="3" thread="3944" file="cwuahandler.cpp:2359">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="10:46:37.231-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="2540" file="cwuahandler.cpp:2527">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="10:49:55.122-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="2128" file="cwuahandler.cpp:2527">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="11:31:03.370-120" date="10-10-2014" component="WUAHandler" context="" type="1" thread="1224" file="cwuahandler.cpp:2527">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="14:30:29.411-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3960" file="cwuahandler.cpp:2527">
    <![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="14:38:38.915-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="2844" file="sourcemanager.cpp:1232">
    <![LOG[Unable to read existing resultant WUA policy. Error = 0x80070002.]LOG]!><time="14:38:38.915-60" date="01-27-2015" component="WUAHandler" context="" type="2" thread="2844" file="sourcemanager.cpp:920">
    <![LOG[Enabling WUA Managed server policy to use server: HTTP://sccm.domain.com:8530]LOG]!><time="14:38:38.915-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="2844" file="sourcemanager.cpp:948">
    <![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="14:38:39.165-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="2844" file="sourcemanager.cpp:954">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="14:40:06.416-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="5736" file="cwuahandler.cpp:2527">
    <![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="14:40:06.416-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="sourcemanager.cpp:1232">
    <![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="14:40:06.447-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="sourcemanager.cpp:936">
    <![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="14:40:06.462-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="sourcemanager.cpp:1265">
    <![LOG[Scan results will include superseded updates only when they are superseded by service packs and definition updates.]LOG]!><time="14:40:06.478-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="cwuahandler.cpp:2909">
    <![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="14:40:06.478-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="cwuahandler.cpp:2916">
    <![LOG[Async searching of updates using WUAgent started.]LOG]!><time="14:40:06.494-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="3796" file="cwuahandler.cpp:579">
    <![LOG[Async searching completed.]LOG]!><time="14:44:15.950-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="1120" file="cwuahandler.cpp:2068">
    <![LOG[Successfully completed scan.]LOG]!><time="14:44:17.325-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="6180" file="cwuahandler.cpp:3557">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="15:51:02.561-60" date="01-27-2015" component="WUAHandler" context="" type="1" thread="4008" file="cwuahandler.cpp:2527">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="12:50:50.102-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="4444" file="cwuahandler.cpp:2527">
    <![LOG[Its a WSUS Update Source type ({543A840D-5C46-4239-ADB9-17E8FC7359E5}), adding it.]LOG]!><time="14:00:00.167-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="sourcemanager.cpp:1232">
    <![LOG[Existing WUA Managed server was already set (HTTP://sccm.domain.com:8530), skipping Group Policy registration.]LOG]!><time="14:00:00.214-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="sourcemanager.cpp:936">
    <![LOG[Added Update Source ({543A840D-5C46-4239-ADB9-17E8FC7359E5}) of content type: 2]LOG]!><time="14:00:00.214-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="sourcemanager.cpp:1265">
    <![LOG[Scan results will include all superseded updates.]LOG]!><time="14:00:00.229-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:2913">
    <![LOG[Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')]LOG]!><time="14:00:00.229-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:2916">
    <![LOG[Async searching of updates using WUAgent started.]LOG]!><time="14:00:01.995-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:579">
    <![LOG[Async searching completed.]LOG]!><time="14:00:21.979-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5076" file="cwuahandler.cpp:2068">
    <![LOG[Successfully completed scan.]LOG]!><time="14:00:23.354-60" date="01-29-2015" component="WUAHandler" context="" type="1" thread="5124" file="cwuahandler.cpp:3557">
    <![LOG[CWuaHandler::SetCategoriesForStateReportingExclusion called with E0789628-CE08-4437-BE74-2495B842F43B;E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for leaves and E0789628-CE08-4437-BE74-2495B842F43B,A38C835C-2950-4E87-86CC-6911A52C34A3; for bundles]LOG]!><time="08:12:47.409-60" date="01-30-2015" component="WUAHandler" context="" type="1" thread="5084" file="cwuahandler.cpp:2527">
    Regards,
    Pictop

  • Windows Update Agent rebooting systems after Software Update deployment

    I have a software update deployment that is configured to install software updates on a collection of servers at 4:00 AM with a suppressed reboot. The updates get deployed and no reboot occurs as expected.  Then ~8 hours later WUA starts up and the
    servers get rebooted.
    There is a maintenance window applied to the collection from 4:00 AM to 6:00 AM to allow the updates to install.
    I've read a few forum and blog posts on this issue and have implemented some settings via GPO, but the reboots are still occurring.  The settings that were applied are referenced in the link below.
    https://support.microsoft.com/kb/2476479?wa=wsignin1.0
    Here is a snippet from the WindowsUpdate.log:
    2014-10-22 12:00:26:153 1428 8a88 AU Received AU Resume timeout
    2014-10-22 12:00:26:153 1428 8a88 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
    2014-10-22 12:00:26:153 1428 8a88 AU Can not perform non-interactive scan if AU is interactive-only
    2014-10-22 12:02:08:512 1428 8a88 AU AU received policy change subscription event
    2014-10-22 12:16:43:463 1428 8a88 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-10-22 12:16:43:479 1428 8a88 WuTask Uninit WU Task Manager
    2014-10-22 12:16:43:697 1428 8a88 Service *********
    2014-10-22 12:16:43:697 1428 8a88 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-10-22 12:16:43:697 1428 8a88 Service *************
    2014-10-22 12:19:29:728 1428 e584 Misc ===========  Logging initialized (build: 7.8.9200.16604, tz: -0400)  ===========
    2014-10-22 12:19:29:728 1428 e584 Misc   = Process: C:\WINDOWS\system32\svchost.exe
    2014-10-22 12:19:29:728 1428 e584 Misc   = Module: c:\windows\system32\wuaueng.dll
    2014-10-22 12:19:29:728 1428 e584 Service *************
    2014-10-22 12:19:29:728 1428 e584 Service ** START **  Service: Service startup
    2014-10-22 12:19:29:728 1428 e584 Service *********
    2014-10-22 12:19:29:744 1428 e584 Agent   * WU client version 7.8.9200.16604
    2014-10-22 12:19:29:744 1428 e584 Agent   * Base directory: C:\WINDOWS\SoftwareDistribution
    2014-10-22 12:19:29:744 1428 e584 Agent   * Access type: No proxy
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:744 1428 e584 Agent   * Network state: Connected
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:744 1428 e584 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 2.
    2014-10-22 12:19:29:791 1428 e584 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-10-22 12:19:29:791 1428 e584 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
    2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS server:
    http://Internal-WSUS.Domain:8530
    2014-10-22 12:19:29:791 1428 e584 Agent   * WSUS status server:
    http://Internal-WSUS.Domain:8530
    2014-10-22 12:19:29:791 1428 e584 Agent   * Target group: (Unassigned Computers)
    2014-10-22 12:19:29:791 1428 e584 Agent   * Windows Update access disabled: No
    2014-10-22 12:19:29:791 1428 e584 Misc WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll
    2014-10-22 12:19:29:806 1428 e584 WuTask WuTaskManager delay initialize completed successfully..
    2014-10-22 12:19:29:822 1428 e584 Report CWERReporter::Init succeeded
    2014-10-22 12:19:29:822 1428 e584 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-10-22 12:19:29:822 1428 e584 DnldMgr Download manager restoring 0 downloads
    2014-10-22 12:19:29:838 1428 e584 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-10-22 12:19:29:838 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
    2014-10-22 12:19:29:838 1428 e584 AU AIR Mode is disabled
    2014-10-22 12:19:29:838 1428 e584 AU   # Policy Driven Provider:
    http://Internal-WSUS.Domain:8530
    2014-10-22 12:19:29:838 1428 e584 AU   # Detection frequency: 22
    2014-10-22 12:19:29:838 1428 e584 AU   # Approval type: Disabled (User preference)
    2014-10-22 12:19:29:838 1428 e584 AU   # Auto-install minor updates: No (User preference)
    2014-10-22 12:19:29:838 1428 e584 AU   # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Pre-install notify)
    2014-10-22 12:19:29:838 1428 e584 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-10-22 12:19:29:838 1428 e584 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037
    2014-10-22 12:19:29:853 1428 e584 AU AU finished delayed initialization
    2014-10-22 12:19:29:884 1428 e584 AU #############
    2014-10-22 12:19:29:884 1428 e584 AU ## START ##  AU: Search for updates
    2014-10-22 12:19:29:884 1428 e584 AU #########
    2014-10-22 12:19:29:884 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
    2014-10-22 12:19:30:416 1428 e584 Report ***********  Report: Initializing static reporting data  ***********
    2014-10-22 12:19:30:416 1428 e584 Report   * OS Version = 6.2.9200.0.0.197008
    2014-10-22 12:19:30:416 1428 e584 Report   * OS Product Type = 0x00000008
    2014-10-22 12:19:30:416 1428 e584 Report   * Computer Brand = HP
    2014-10-22 12:19:30:416 1428 e584 Report   * Computer Model = ProLiant BL460c Gen8
    2014-10-22 12:19:30:416 1428 e584 Report   * Platform Role = 1
    2014-10-22 12:19:30:416 1428 e584 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Revision = I31
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Name = Default System BIOS
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Release Date = 2014-02-10T00:00:00
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Sku Number = 641016-B21     
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Vendor = HP
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Family = ProLiant
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Major Release = 255
    2014-10-22 12:19:30:431 1428 e584 Report   * Bios Minor Release = 255
    2014-10-22 12:19:30:431 1428 e584 Report   * Locale ID = 1033
    2014-10-22 12:19:30:431 1428 e584 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:431 1428 dae0 Agent *************
    2014-10-22 12:19:30:431 1428 dae0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:30:431 1428 dae0 Agent *********
    2014-10-22 12:19:30:431 1428 dae0 Agent   * Online = No; Ignore download priority = No
    2014-10-22 12:19:30:431 1428 dae0 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-10-22 12:19:30:431 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-10-22 12:19:30:431 1428 dae0 Agent   * Search Scope = {Machine & All Users}
    2014-10-22 12:19:30:431 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
    2014-10-22 12:19:30:494 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
    2014-10-22 12:19:30:494 1428 dae0 Agent *********
    2014-10-22 12:19:30:494 1428 dae0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:30:494 1428 dae0 Agent *************
    2014-10-22 12:19:30:509 1428 d158 AU >>##  RESUMED  ## AU: Search for updates [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:509 1428 d158 AU   # 0 updates detected
    2014-10-22 12:19:30:509 1428 d158 AU #########
    2014-10-22 12:19:30:509 1428 d158 AU ##  END  ##  AU: Search for updates  [CallId = {2787252C-D4B8-46B5-BB42-0C616042113C} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:509 1428 d158 AU #############
    2014-10-22 12:19:30:509 1428 d158 AU All AU searches complete.
    2014-10-22 12:19:30:525 1428 e584 AU #############
    2014-10-22 12:19:30:525 1428 e584 AU ## START ##  AU: Search for updates
    2014-10-22 12:19:30:525 1428 e584 AU #########
    2014-10-22 12:19:30:525 1428 e584 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-install notify} added to AU services list
    2014-10-22 12:19:30:525 1428 e584 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
    2014-10-22 12:19:30:525 1428 e584 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:30:525 1428 dae0 Agent *************
    2014-10-22 12:19:30:525 1428 dae0 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:30:525 1428 dae0 Agent *********
    2014-10-22 12:19:30:525 1428 dae0 Agent   * Online = Yes; Ignore download priority = No
    2014-10-22 12:19:30:525 1428 dae0 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-10-22 12:19:30:525 1428 dae0 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
    2014-10-22 12:19:30:525 1428 dae0 Agent   * Search Scope = {Machine & All Users}
    2014-10-22 12:19:30:525 1428 dae0 Agent   * Caller SID for Applicability: S-1-5-18
    2014-10-22 12:19:30:525 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
    2014-10-22 12:19:30:541 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:541 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:556 1428 dae0 EP Got 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL: "http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab"
    2014-10-22 12:19:30:588 1428 dae0 Agent Checking for updated auth cab for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 at
    http://fe2.ws.microsoft.com/w81/2/redir/v2-storeauth.cab
    2014-10-22 12:19:30:588 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
    2014-10-22 12:19:30:603 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:603 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:775 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\AuthCabs\Downloaded\117cab2d-82b1-4b5a-a08c-4d62dbee7782.cab:
    2014-10-22 12:19:30:791 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:791 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:791 1428 dae0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\WuRedir\117CAB2D-82B1-4B5A-A08C-4D62DBEE7782\wuredir.cab:
    2014-10-22 12:19:30:806 1428 dae0 Misc  Microsoft signed: Yes
    2014-10-22 12:19:30:806 1428 dae0 Misc  Infrastructure signed: Yes
    2014-10-22 12:19:30:822 1428 dae0 EP Got 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 redir Client/Server URL: "https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx"
    2014-10-22 12:19:30:978 1428 dae0 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-10-22 12:19:30:978 1428 dae0 PT   + ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}, Server URL =
    https://fe2.ws.microsoft.com/v6/ClientWebService/client.asmx
    2014-10-22 12:19:31:025 1428 dae0 Agent   * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
    2014-10-22 12:19:31:025 1428 dae0 Agent *********
    2014-10-22 12:19:31:025 1428 dae0 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-10-22 12:19:31:025 1428 dae0 Agent *************
    2014-10-22 12:19:31:025 1428 d158 AU >>##  RESUMED  ## AU: Search for updates [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:31:025 1428 d158 AU   # 0 updates detected
    2014-10-22 12:19:31:025 1428 d158 AU #########
    2014-10-22 12:19:31:025 1428 d158 AU ##  END  ##  AU: Search for updates  [CallId = {A3E41A4C-E9CB-4172-B6B0-99D556FB9102} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
    2014-10-22 12:19:31:025 1428 d158 AU #############
    2014-10-22 12:19:31:025 1428 d158 AU All AU searches complete.
    2014-10-22 12:19:31:025 1428 d158 AU AU setting next detection timeout to 2014-10-23 14:19:28
    2014-10-22 12:19:36:025 1428 e214 Report REPORT EVENT: {E04012FD-8FFD-4259-96D5-A5A34127F0A0} 2014-10-22 12:19:31:025-0400 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software
    Synchronization Windows Update Client successfully detected 0 updates.
    2014-10-22 12:19:36:025 1428 e214 Report CWERReporter finishing event handling. (00000000)
    2014-10-22 12:29:29:914 1428 e584 AU AU invoking RebootSystem (OnRebootNow)
    2014-10-22 12:29:30:055 1428 e584 AU Allowing auto firmware installs at next shutdown
    2014-10-22 12:29:30:102 1428 e584 Misc WARNING: SUS Client is rebooting system.
    2014-10-22 12:29:30:102 1428 e584 AU AU invoking RebootSystem (OnRebootRetry)
    2014-10-22 12:29:30:367 1428 e584 Shutdwn Checking to see whether install at shutdown is appropriate
    2014-10-22 12:29:30:367 1428 e584 Shutdwn user declined update at shutdown
    2014-10-22 12:29:30:367 1428 e584 AU AU initiates service shutdown
    2014-10-22 12:29:30:367 1428 e584 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-10-22 12:29:30:399 1428 e584 WuTask Uninit WU Task Manager
    2014-10-22 12:29:30:445 1428 e584 Agent Sending shutdown notification to client
    2014-10-22 12:29:30:445 5788 8084 COMAPI WARNING: Received service shutdown/self-update notification.
    2014-10-22 12:29:30:461 1428 e584 Report CWERReporter finishing event handling. (00000000)
    2014-10-22 12:29:30:539 1428 e584 Service *********
    2014-10-22 12:29:30:539 1428 e584 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-10-22 12:29:30:539 1428 e584 Service *************
    Any assistance is appreciated.
    -Tim

    Hi,
    Any update?
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • 80246002 error after installing Windows Update Agent 7.6.7600.320

    This problem prevents Windows Update from being able to search, download, and install updates.
    I am experiencing this issue on machines running Server 2008 R2 and Windows 7 Enterprise (I imagine this an issue with Windows Update and not the OS so this is probably affecting other OS' as well).
    This problem is becoming widespread quickly.
    The proposed fix (method 1) in the article below did not resolve the problem:
    http://support.microsoft.com/kb/958056/en-us
    Note: Method 2 is not viable when applying more than one update at a time especially when you are updating multiple machines.
    Several others are posting similar problems:
    http://windowsitpro.com/windows-update/tracking-error-80246002-windows-update-problem
    http://forums.techguy.org/windows-7/1132320-windows-update-problems-4.html
    This is preventing scheduled server maintenance from being performed.
    Could this be a targeted attack? Happening at the end of the week before a long holiday weekend is not leaving me with a very good feeling...
    I would hope that fixing this issue would be a very high priority.
    BTW - There is no "Windows Update Issue" forum category that I could find - If there is, sorry for posting in the wrong area.
    Cheers,
    Jeff

    My fix that worked...
    Reviewed the operational log for the WindowsUpdateClient (buried in the Event viewer here:
    Application and Services Logs -> Microsoft -> Windows -> WindowsUpdateClient -> Operational
    After review, I noticed that event 30 "Windows Updates established connectivity" was no longer occurring and that event 42 "There has been a change in the health of Windows Update" was the only thing after the error (Event 25 "Windows Update failed
    to check for updates with error 0x80246002")
    Even though the machine was restarted after applying the "Windows Update Agent 7.6.7600.320" patch and I had tried restarting the Windows Update service, the service appears to be hung.
    Solution:
    1.) restart the Windows update service
    2.) monitor the operational log for the WindowsUpdateClient (refreshing every 5-10 seconds)
    3.) verify that event 30 happens (you should see event 38 after restarting the service followed by (2) event 42, then event 30)
    4.) Once event 30 happens go to the Windows update GUI and run the "Check for updates" - yay!
    5.) You can go back into the operational log and see event 26 "Windows Update successfully found x updates" followed by an event 40 for each update found.
    What is really strange is that I checked the first machine that experienced the problem and it magically fixed itself.
    It seems like this may have been caused by DDOS attack on the source for windows updates that the Windows Update service connects to. Or the source location was having maintenance performed.
    Regardless, in my case, this was not a problem with the OS or the patch but the inability for the Windows Update Service to establish connectivity.
    Hope that helps somebody :)
    Cheers,
    Jeff 

  • How can I disable the HP Updates Agent from running?

    HP pavilion D4100Y
    Windows XP  SP2 or 3 (not sure)
    No error message
    No recent changes
    Problem: The program "Updates from HP Agent" runs frequently and on no particular schedule, certainly not one I chose.  It takes over my computer for hours and uses most of the CPU, fluctuating from 13% to 87% to 1 etc.3% to 6%, etc. The computer hangs and I cannot use it for anything else. On the HP Updates screen, I set the updates to "NEVER" but that didn't work.  The programs still run. On the Windows Task Manager window the program is called "Updates from HP Agent".
    I cannot find anything about this problem in the support database.
    How can I disable the HP Updates Agent from running?
    This question was solved.
    View Solution.

    Select your start button and in the search box type "msconfig" then select msconfig.exe under programs.
    Look under the "Services" and "Boot" tabs. Uncheck HP update agent, select "Apply" and close.
    I work for HP

Maybe you are looking for

  • How can I print my entire draft message, instead of only the part of it that shows on the screen?

    I have drafted response to a message I received. I need a copy of the draft to show my associate, but my printer will only print the portion of the draft that can be seen on the screen at one time. I have not previously encountered this problem. What

  • How to launch many instances of Sun Java ME Platform SDK 3.0 emulator ?

    Hi all, I want to launch two instances of the emulator , how to achieve that ? Thank you very much indeed

  • Reguarding input help .

    Hi All, In my webdynpro ABAP screen iam have one input field , i attached a search help for that input field, and it is working fine , but the problem was when  i enter any values into that input field manually with out taking the input help it is ta

  • Auto create folders for projects

    Hi, wondering if anyone has made oracle files create new users work folders and sub directories based on a new project being entered into PA? if so, please share set up. --thanks

  • Work flow settings in Production

    Dear all, i had developed a workflow in development client . but i want to transport that to production. 1) i need to do the settings in SWU3. as production has status not modifiable i need to transport that . but in my dev settings i had given clien