locked
no proxy but pc still keeps settings from wsus gpo even now it is not in domain RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    the situation

    I deployed a new image the computer was not a domain member. Before connecting to domain I connected the machine to

    dedicated Internet connection (no corporate proxy) for making full updated from Microsoft site. Because I want to capture it back for future domain deployments and have maximum updates to date in the image.

    Update failed. Checked Direct Access (NO PROXY). Refreshed Software Updates folder.

    Windows update always showed the name of previous proxy server with the error. Local GPO were not configured.

    Found one entry with the name of proxy in the registry. Tried different things. still not works. No name in Windows update log but deffinetely Windows Update agent still keeps some settings from previous GPO.

    Before I wipe this thing, please

    see the last WindowsUpdate. May be there is a solution...

    Thanks.

    2014-08-26 12:41:44:098  484 820 Service *************
    2014-08-26 12:41:44:113  484 820 Service ** START **  Service: Service startup
    2014-08-26 12:41:44:129  484 820 Service *********
    2014-08-26 12:41:44:285  484 820 Agent   * WU client version 7.6.7600.256
    2014-08-26 12:41:44:285  484 820 Agent   * Base directory: C:\windows\SoftwareDistribution
    2014-08-26 12:41:44:285  484 820 Agent   * Access type: No proxy
    2014-08-26 12:41:44:285  484 820 Agent   * Network state: Connected
    2014-08-26 12:42:30:118  484 820 Report CWERReporter::Init succeeded
    2014-08-26 12:42:30:118  484 820 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-08-26 12:42:30:118  484 820 Agent ***********  Agent: Initializing global settings cache  ***********
    2014-08-26 12:42:30:118  484 820 Agent   * WSUS server:
    2014-08-26 12:42:30:118  484 820 Agent   * WSUS status server:
    2014-08-26 12:42:30:118  484 820 Agent   * Target group: (Unassigned Computers)
    2014-08-26 12:42:30:118  484 820 Agent   * Windows Update access disabled: No
    2014-08-26 12:42:30:149  484 820 DnldMgr Download manager restoring 0 downloads
    2014-08-26 12:42:30:165  484 820 AU ###########  AU: Initializing Automatic Updates  ###########
    2014-08-26 12:42:30:165  484 820 AU   # WSUS server:
    2014-08-26 12:42:30:165  484 820 AU   # Detection frequency: 22
    2014-08-26 12:42:30:165  484 820 AU   # Approval type: Pre-install notify (User preference)
    2014-08-26 12:42:30:165  484 820 AU   # Auto-install minor updates: No (User preference)
    2014-08-26 12:42:30:165  484 820 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-08-26 12:42:30:165  484 820 Report ***********  Report: Initializing static reporting data  ***********
    2014-08-26 12:42:30:165  484 820 Report   * OS Version = 6.1.7601.1.0.65792
    2014-08-26 12:42:30:165  484 820 Report   * OS Product Type = 0x00000030
    2014-08-26 12:42:30:492  484 820 Report   * Computer Brand = Hewlett-Packard
    2014-08-26 12:42:30:492  484 820 Report   * Computer Model = HP EliteDesk 800 G1 SFF
    2014-08-26 12:42:30:508  484 820 Report   * Bios Revision = L01 v02.30
    2014-08-26 12:42:30:508  484 820 Report   * Bios Name = Default System BIOS
    2014-08-26 12:42:30:508  484 820 Report   * Bios Release Date = 2014-04-22T00:00:00
    2014-08-26 12:42:30:508  484 820 Report   * Locale ID = 3084
    2014-08-26 12:42:30:570  484 820 AU Successfully wrote event for AU health state:0
    2014-08-26 12:42:30:570  484 820 AU Initializing featured updates
    2014-08-26 12:42:30:570  484 820 AU Found 0 cached featured updates
    2014-08-26 12:42:30:570  484 820 AU Successfully wrote event for AU health state:0
    2014-08-26 12:42:30:570  484 820 AU Successfully wrote event for AU health state:0
    2014-08-26 12:42:30:570  484 820 AU AU finished delayed initialization
    2014-08-26 12:42:30:617  484 528 PT WARNING: PTError: 0x80072ee6
    2014-08-26 12:42:30:617  484 528 PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
    2014-08-26 12:42:30:617  484 528 Report WARNING: Reporter failed to upload events with hr = 80072ee6.
    2014-08-26 12:42:30:617  484 528 PT WARNING: PTError: 0x80072ee6
    2014-08-26 12:42:30:617  484 528 PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
    2014-08-26 12:42:30:617  484 528 Report WARNING: Reporter failed to upload events with hr = 80072ee6.
    2014-08-26 12:42:35:609  484 528 Report CWERReporter finishing event handling. (00000000)
    2014-08-26 12:53:55:661  484 528 PT WARNING: PTError: 0x80072ee6
    2014-08-26 12:53:55:661  484 528 PT WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
    2014-08-26 12:53:55:661  484 528 Report WARNING: Reporter failed to upload events with hr = 80072ee6.

    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Tuesday, August 26, 2014 5:32 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Is this image used to be a WSUS client? According to the logs, the client seems to try to connect a WSUS server.

    To remove the WSUS client setting, we have two options:

    1. Set HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer to 0.
    2. Delete entire HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\

    Note: Serious problems might occur if we modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, we can restore the registry if a problem occurs.

    Best Regards.

    Steven Lee

    TechNet Community Support


    • Edited by Steven_Lee0510 Wednesday, August 27, 2014 10:02 AM
    • Marked as answer by pob579 Wednesday, August 27, 2014 2:28 PM
    Wednesday, August 27, 2014 10:02 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Is this image used to be a WSUS client? According to the logs, the client seems to try to connect a WSUS server.

    To remove the WSUS client setting, we have two options:

    1. Set HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer to 0.
    2. Delete entire HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate\

    Note: Serious problems might occur if we modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, we can restore the registry if a problem occurs.

    Best Regards.

    Steven Lee

    TechNet Community Support


    • Edited by Steven_Lee0510 Wednesday, August 27, 2014 10:02 AM
    • Marked as answer by pob579 Wednesday, August 27, 2014 2:28 PM
    Wednesday, August 27, 2014 10:02 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Steven, thanks for the tip. It helped!

    The machine was not in domain but was deployed from MDT and in the task sequence Update from WSUS was enabled.

    "When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

    Wednesday, August 27, 2014 2:28 PM