Lass mich raten, der Server von dem Du sprichst ist KEIN Windows Server 2008. Richtig? Wenn ja, die 3 Einstellungen sind nicht verantwortlich für das Problem. Und einen Server versetzt  man wohl auch kaum in den Ruhezustand. Vermutlich ist es ein Windows 2000 Server und Du arbeitest mit GPEDIT.MSC.

Wenn Du Einstellungen vornehmen möchtest, dann erstellt man dafür eine zentrale GPO und nicht einzelne auf den Servern. Du hast doch bestimmt ein Active Directory im Einsatz, oder?

JeyJey1779 schrieb on 07.08.09 um 10:38:47:


Und ein 2003 kennt das noch nicht, deshalb siehst Du das auch nicht.

JeyJey1779 schrieb on 07.08.09 um 10:38:47:


Na dann viel Spaß bei der Turnschuhadministration!

BTW: Wenn sich ein Client oder Server nicht beim WSUS meldet, solltest Du zuerst in die %windir%\windowsupdate.log sehen.

Ein oft und gern gemachter Fehler ist auch das klonen von Rechnern: (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen).

Hier ist mein Logfiel ich kann damit nicht allzuviel Anfangen
   :

2009-08-10      00:20:39:608       784      110      PT      WARNING: PTError: 0x80072ee6
2009-08-10      00:20:39:608       784      110      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      00:20:39:608       784      110      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      00:40:27:842       784      ba0      PT      WARNING: PTError: 0x80072ee6
2009-08-10      00:40:27:842       784      ba0      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      00:40:27:842       784      ba0      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      00:58:05:108       784      bfc      PT      WARNING: PTError: 0x80072ee6
2009-08-10      00:58:05:108       784      bfc      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      00:58:05:108       784      bfc      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      01:05:23:748       784      49c      AU      #############
2009-08-10      01:05:23:748       784      49c      AU      ## START ##  AU: Search for updates
2009-08-10      01:05:23:748       784      49c      AU      #########
2009-08-10      01:05:23:748       784      49c      AU      <<## SUBMITTED ## AU: Search for updates [CallId = {FD3C0F69-689F-431F-B4BF-5F3843CF1822}]
2009-08-10      01:05:23:748       784      bfc      Agent      *************
2009-08-10      01:05:23:748       784      bfc      Agent      ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2009-08-10      01:05:23:748       784      bfc      Agent      *********
2009-08-10      01:05:23:748       784      bfc      Agent        * Online = Yes; Ignore download priority = No
2009-08-10      01:05:23:748       784      bfc      Agent        * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
2009-08-10      01:05:23:748       784      bfc      Agent        * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-08-10      01:05:23:748       784      bfc      Agent        * Search Scope = {Machine}
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: Initialize failed with 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: Initialize failed with 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: Initialize failed with 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: WinHttpCrackUrl failed. error 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: WinHttp: Initialize failed with 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Misc      WARNING: DownloadFileInternal failed for 130.30.3.25/selfupdate/wuident.cab: error 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Setup      FATAL: IsUpdateRequired failed with error 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Setup      WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80072ee6
2009-08-10      01:05:23:748       784      bfc      Setup      WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80072EE6
2009-08-10      01:05:23:748       784      bfc      Agent        * WARNING: Skipping scan, self-update check returned 0x80072EE6
2009-08-10      01:05:24:139       784      bfc      Agent        * WARNING: Exit code = 0x80072EE6
2009-08-10      01:05:24:139       784      bfc      Agent      *********
2009-08-10      01:05:24:139       784      bfc      Agent      **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2009-08-10      01:05:24:139       784      bfc      Agent      *************
2009-08-10      01:05:24:139       784      bfc      Agent      WARNING: WU client failed Searching for update with error 0x80072ee6
2009-08-10      01:05:24:139       784      9fc      AU      >>##  RESUMED  ## AU: Search for updates [CallId = {FD3C0F69-689F-431F-B4BF-5F3843CF1822}]
2009-08-10      01:05:24:139       784      9fc      AU        # WARNING: Search callback failed, result = 0x80072EE6
2009-08-10      01:05:24:139       784      9fc      AU        # WARNING: Failed to find updates with error code 80072EE6
2009-08-10      01:05:24:139       784      9fc      AU      #########
2009-08-10      01:05:24:139       784      9fc      AU      ##  END  ##  AU: Search for updates [CallId = {FD3C0F69-689F-431F-B4BF-5F3843CF1822}]
2009-08-10      01:05:24:139       784      9fc      AU      #############
2009-08-10      01:05:24:139       784      9fc      AU      AU setting next detection timeout to 2009-08-10 04:05:24
2009-08-10      01:05:24:139       784      9fc      AU      Setting AU scheduled install time to 2009-08-10 01:00:00
2009-08-10      01:05:28:748       784      bfc      Report      REPORT EVENT: {BE701A48-2B6D-4D7B-9769-89CD2D5A9A7F}      2009-08-10 01:05:23:748+0200      1      148      101      {D67661EB-2423-451D-BF5D-13199E37DF28}      0      80072ee6      SelfUpdate      Failure      Software Synchronization      Windows Update Client failed to detect with error 0x80072ee6.
2009-08-10      01:21:02:405       784      df4      PT      WARNING: PTError: 0x80072ee6
2009-08-10      01:21:02:405       784      df4      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      01:21:02:405       784      df4      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      01:43:02:639       784      cc4      PT      WARNING: PTError: 0x80072ee6
2009-08-10      01:43:02:639       784      cc4      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      01:43:02:639       784      cc4      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      01:53:53:873       784      cc4      PT      WARNING: PTError: 0x80072ee6
2009-08-10      01:53:53:873       784      cc4      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      01:53:53:873       784      cc4      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      02:18:46:123       784      f44      PT      WARNING: PTError: 0x80072ee6
2009-08-10      02:18:46:123       784      f44      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      02:18:46:123       784      f44      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      02:46:24:373       784      154      PT      WARNING: PTError: 0x80072ee6
2009-08-10      02:46:24:373       784      154      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      02:46:24:373       784      154      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      03:00:10:014       784      49c      AU      Forced install timer expired for scheduled install
2009-08-10      03:00:10:014       784      49c      AU      UpdateDownloadProperties: 0 download(s) are still in progress.
2009-08-10      03:00:10:014       784      49c      AU      Setting AU scheduled install time to 2009-08-11 01:00:00
2009-08-10      03:14:06:623       784      7a4      PT      WARNING: PTError: 0x80072ee6
2009-08-10      03:14:06:623       784      7a4      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      03:14:06:623       784      7a4      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      03:43:44:889       784      8bc      PT      WARNING: PTError: 0x80072ee6
2009-08-10      03:43:44:889       784      8bc      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      03:43:44:889       784      8bc      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      04:00:54:139       784      a9c      PT      WARNING: PTError: 0x80072ee6
2009-08-10      04:00:54:139       784      a9c      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      04:00:54:139       784      a9c      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      04:21:25:405       784      2fc      PT      WARNING: PTError: 0x80072ee6
2009-08-10      04:21:25:405       784      2fc      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      04:21:25:405       784      2fc      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      04:36:50:655       784      c84      PT      WARNING: PTError: 0x80072ee6
2009-08-10      04:36:50:655       784      c84      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      04:36:50:655       784      c84      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      04:54:13:889       784      d7c      PT      WARNING: PTError: 0x80072ee6
2009-08-10      04:54:13:889       784      d7c      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      04:54:13:889       784      d7c      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      05:17:36:108       784      ecc      PT      WARNING: PTError: 0x80072ee6
2009-08-10      05:17:36:108       784      ecc      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      05:17:36:108       784      ecc      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      05:44:21:326       784      fe0      PT      WARNING: PTError: 0x80072ee6
2009-08-10      05:44:21:326       784      fe0      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      05:44:21:326       784      fe0      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      06:03:36:545       784      f64      PT      WARNING: PTError: 0x80072ee6
2009-08-10      06:03:36:545       784      f64      PT      WARNING: Initialization failed for Protocol Talker Context: 0x80072ee6
2009-08-10      06:03:36:545       784      f64      Report      WARNING: Reporter failed to upload events with hr = 80072ee6.
2009-08-10      06:05:24:139       784      49c      AU      #############
2009-08-10      06:05:24:139       784      49c      AU      ## START ##  AU: Search for updates
2009-08-10      06:05:24:139       784      49c      AU      #########
2009-08-10      06:05:24:139       784      49c      AU      <<## SUBMITTED ## AU: Search for updates [CallId = {33043455-138B-4B5C-9DD9-1D79705F984D}]
2009-08-10      06:05:24:139       784      f64      Agent      *************
2009-08-10      06:05:24:139       784      f64      Agent      ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2009-08-10      06:05:24:139       784      f64      Agent      *********
2009-08-10      06:05:24:139       784      f64      Agent        * Online = Yes; Ignore download priority = No
2009-08-10      06:05:24:139       784      f64      Agent        * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"

JeyJey1779 schrieb on 10.08.09 um 09:47:37:


Wie genau ist denn der WSUS in der Registry eingetragen? Steht das etwa so drin? (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen). Wenn ja, dann ist es flasch.

Ich versteh kein Wort von dem was Du da schreibst. Könntest Du Punkt und Komma benutzen? Hilft beim lesen ungemein.

Und wollte ich ein Bild von dieser Einstellung: (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen).

Der Regeintrag ist komplett falsch. Liest Du eigentlich auch die Postings die man dir schreibt?

Das muß so aussehen: (Du musst Dich Einloggen oder Registrieren um Multimediadateien oder Links zu sehen).

Wenn das grundsätzliche schon falsch ist, kann sich der Client ja nicht zum WSUS verbinden. Korrigiere das in der GPO oder wo auch immer Du den Eintrag gesetzt hast. Wenn per GPO, dann muß diese Änderung natürlich auf alle DCs repliziert werden und anschließend mußt Du auf dem Client ein gpupdate ausführen.